BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 12-12-2007, 09:52 AM   #1 (permalink)
Thumbs Must Hurt
 
Join Date: Oct 2007
Location: Washington, DC
Model: 9930
OS: 7.1
PIN: N/A
Carrier: Sprint
Posts: 64
Post Thanks: 0
Thanked 2 Times in 1 Post
Default SRP Connection dropped > SRP Connection established

Please Login to Remove!

Hello all,

Starting last night I began receiving the following error alerts from my bes:

<N/A> | BlackBerry Dispatcher JCBBES2 (Application Event Log on JCBBES2) | 12/12/2007 10:44:14 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0

Then about 30 seconds later I receive another alert saying it is reconnected:

<N/A> | BlackBerry Dispatcher JCBBES2 (Application Event Log on JCBBES2) | 12/12/2007 10:45:14 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established

This cycle happened about 35 times since 5am today. Nothing has changed on the server in about a week (Windows Updates were done last week but nothing major).

Here is my system specs:
Windows Server 2003 R2 SP2
BES 4.14.15

I have tried restarting the services as well as restarting the server and I am still receiving the alerts.

Any advice woudl be appreciated.
Offline  
Old 12-12-2007, 09:55 AM   #2 (permalink)
New Member
 
jsconyers's Avatar
 
Join Date: Jul 2007
Location: In a van down by the river.
Model: NOTE2
OS: 4.1
PIN: <- Where do I find this?
Carrier: Sprint
Posts: 15,069
Post Thanks: 138
Thanked 139 Times in 120 Posts
Default

I had an issue this morning as well. The logs were showing could not connect to srp.na.blackberry.net. I went into the blackberry config and tested the router connection and it failed. This started around 5:55 am and came back around 8:45am this morning. I contacted RIM and they said their was a "service interruption" on their end and verified my SRP was now connected.

Last edited by jsconyers : 12-12-2007 at 10:04 AM.
Offline  
Old 12-12-2007, 09:58 AM   #3 (permalink)
Thumbs Must Hurt
 
Join Date: Oct 2007
Location: Washington, DC
Model: 9930
OS: 7.1
PIN: N/A
Carrier: Sprint
Posts: 64
Post Thanks: 0
Thanked 2 Times in 1 Post
Default

That is very interesting because one of my coworkers who handles a different BES group contacted RIM and after sitting on hold for over an hour, the tech told her their was no RIM problems and it was on her end. She knew this couldn't be the case since she was on hold for so long.

Unfortunately I am still having the issue though...
Offline  
Old 12-12-2007, 10:06 AM   #4 (permalink)
New Member
 
jsconyers's Avatar
 
Join Date: Jul 2007
Location: In a van down by the river.
Model: NOTE2
OS: 4.1
PIN: <- Where do I find this?
Carrier: Sprint
Posts: 15,069
Post Thanks: 138
Thanked 139 Times in 120 Posts
Default

Very interesting, They gave a service interruption ticket number: BB87981. I don't think it makes a difference, but I am running Groupwise and I waited on hold for a while as well. Normally the there is little to no hold time on the groupwise line.
Offline  
Old 12-12-2007, 10:41 AM   #5 (permalink)
x14
BlackBerry Extraordinaire
 
Join Date: Jul 2005
Location: NYC
Model: 9800
OS: 6.0.0.546
Carrier: AT&T
Posts: 2,344
Post Thanks: 0
Thanked 17 Times in 16 Posts
Default

I got 1 drop at 2am EST.
__________________
Exchange 2007/BES 5.0.2 MR2
Offline  
Old 12-12-2007, 11:20 AM   #6 (permalink)
Thumbs Must Hurt
 
Join Date: Jul 2007
Location: Houston, Texas
Model: z10
PIN: N/A
Carrier: T-mobile
Posts: 79
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

I was having one hell of a day yesterday afternoon trying to activate Blackberries and such. Not working, Contacts or calanders not showing up after activation and so on. Then I noticed this post and checked my logs.

I've been getting the SRP dropped since around 2pm yesterday till about 8am this morning myself.


(12/11 13:52:52.563):{0xB50} 12/11/2007 13:52:52 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/11 13:52:58.876):{0xB50} 12/11/2007 13:52:58 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/11 14:24:55.448):{0xB50} 12/11/2007 14:24:55 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/11 14:25:09.667):{0xB50} 12/11/2007 14:25:09 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/11 16:44:40.856):{0xB50} 12/11/2007 16:44:40 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/11 16:44:48.841):{0xB50} 12/11/2007 16:44:44 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/11 17:35:12.515):{0xB50} 12/11/2007 17:35:12 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/11 17:35:20.797):{0xB50} 12/11/2007 17:35:15 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/11 18:47:49.922):{0xB50} 12/11/2007 18:47:49 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/11 18:48:01.095):{0xB50} 12/11/2007 18:48:01 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/11 18:52:45.783):{0xB50} 12/11/2007 18:52:45 (EFFF2710) -> [SRP] Ping Response not received
(12/11 18:55:01.119):{0xB50} 12/11/2007 18:55:01 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/11 18:55:11.292):{0xB50} 12/11/2007 18:55:11 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/12 04:49:15.305):{0xB50} 12/12/2007 04:49:15 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/12 04:49:23.352):{0xB50} 12/12/2007 04:49:18 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/12 04:51:42.407):{0xB50} 12/12/2007 04:51:42 (EFFF2710) -> [SRP] Ping Response not received
(12/12 04:53:48.383):{0xB50} 12/12/2007 04:53:48 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/12 04:53:53.367):{0xB50} 12/12/2007 04:53:48 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/12 05:23:47.252):{0xB50} 12/12/2007 05:23:47 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/12 05:25:20.492):{0xB50} 12/12/2007 05:25:20 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/12 06:21:24.279):{0xB50} 12/12/2007 06:21:24 (EFFF2710) -> [SRP] Ping Response not received
(12/12 06:24:24.290):{0xB50} 12/12/2007 06:24:24 (EFFF2710) -> [SRP] Ping Response not received
(12/12 06:51:56.541):{0xB50} 12/12/2007 06:51:56 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/12 06:52:27.230):{0xB50} 12/12/2007 06:52:27 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/12 07:21:10.080):{0xB50} 12/12/2007 07:21:10 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/12 07:21:47.457):{0xB50} 12/12/2007 07:21:47 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/12 07:48:01.797):{0xB50} 12/12/2007 07:48:01 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/12 07:48:10.938):{0xB50} 12/12/2007 07:48:10 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established


Was this the cause of all the problems?

Last edited by Urlryn : 12-12-2007 at 11:21 AM.
Offline  
Old 12-12-2007, 05:28 PM   #7 (permalink)
New Member
 
Join Date: Aug 2007
Location: Perth Western Australia
Model: 800
PIN: N/A
Carrier: Optus
Posts: 5
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Drops

Hi all,

I had and issue with no connection to the SRP for about 4 hours but then it reconnected successfully and appears to be fine now. Shame RIM don't have a page where you can check the status of there services considering were the customer I would have thought this was a given.

John
Offline  
Old 12-13-2007, 02:19 AM   #8 (permalink)
BlackBerry Extraordinaire
 
noname's Avatar
 
Join Date: Sep 2005
Location: Congested Islet of "Foreign Talents" (> 45% of workforce) - Singapore.
Model: Z10
OS: 10.0.0
PIN: NUKE(PAP)
Carrier: Singtel
Posts: 1,504
Post Thanks: 6
Thanked 9 Times in 9 Posts
Default

Quote:
Originally Posted by Urlryn View Post
I was having one hell of a day yesterday afternoon trying to activate Blackberries and such. Not working, Contacts or calanders not showing up after activation and so on. Then I noticed this post and checked my logs.

I've been getting the SRP dropped since around 2pm yesterday till about 8am this morning myself.


(12/11 13:52:52.563):{0xB50} 12/11/2007 13:52:52 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/11 13:52:58.876):{0xB50} 12/11/2007 13:52:58 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/11 14:24:55.448):{0xB50} 12/11/2007 14:24:55 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/11 14:25:09.667):{0xB50} 12/11/2007 14:25:09 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/11 16:44:40.856):{0xB50} 12/11/2007 16:44:40 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/11 16:44:48.841):{0xB50} 12/11/2007 16:44:44 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/11 17:35:12.515):{0xB50} 12/11/2007 17:35:12 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/11 17:35:20.797):{0xB50} 12/11/2007 17:35:15 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/11 18:47:49.922):{0xB50} 12/11/2007 18:47:49 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/11 18:48:01.095):{0xB50} 12/11/2007 18:48:01 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/11 18:52:45.783):{0xB50} 12/11/2007 18:52:45 (EFFF2710) -> [SRP] Ping Response not received
(12/11 18:55:01.119):{0xB50} 12/11/2007 18:55:01 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/11 18:55:11.292):{0xB50} 12/11/2007 18:55:11 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/12 04:49:15.305):{0xB50} 12/12/2007 04:49:15 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/12 04:49:23.352):{0xB50} 12/12/2007 04:49:18 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/12 04:51:42.407):{0xB50} 12/12/2007 04:51:42 (EFFF2710) -> [SRP] Ping Response not received
(12/12 04:53:48.383):{0xB50} 12/12/2007 04:53:48 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/12 04:53:53.367):{0xB50} 12/12/2007 04:53:48 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/12 05:23:47.252):{0xB50} 12/12/2007 05:23:47 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/12 05:25:20.492):{0xB50} 12/12/2007 05:25:20 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/12 06:21:24.279):{0xB50} 12/12/2007 06:21:24 (EFFF2710) -> [SRP] Ping Response not received
(12/12 06:24:24.290):{0xB50} 12/12/2007 06:24:24 (EFFF2710) -> [SRP] Ping Response not received
(12/12 06:51:56.541):{0xB50} 12/12/2007 06:51:56 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/12 06:52:27.230):{0xB50} 12/12/2007 06:52:27 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/12 07:21:10.080):{0xB50} 12/12/2007 07:21:10 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/12 07:21:47.457):{0xB50} 12/12/2007 07:21:47 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
(12/12 07:48:01.797):{0xB50} 12/12/2007 07:48:01 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/12 07:48:10.938):{0xB50} 12/12/2007 07:48:10 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established


Was this the cause of all the problems?
Urlryn, Error=0 does not show a potentially network issue. This is a WinSock "0" i.e. meaning no error. Your BES may has intermittent Internet connectivity. Check your internal network.
From your log snippet, it shows that BES is working as it is inteneded i.e. re-established immediately when the connection is dropped. Your BES is good.
__________________
Native but 4th class citizen of a nation governed by idiots who import congestions & contention.
Offline  
Old 12-13-2007, 09:08 AM   #9 (permalink)
Thumbs Must Hurt
 
Join Date: Jul 2007
Location: Houston, Texas
Model: z10
PIN: N/A
Carrier: T-mobile
Posts: 79
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thanks Noname.....i'm checking more into this now!

Is there any books, pdf, classes or anything that gives you more information on how to read these log files and what each one does?
Offline  
Old 12-13-2007, 10:42 AM   #10 (permalink)
BlackBerry Genius
 
hdawg's Avatar
 
Join Date: Aug 2006
Model: hdawg
PIN: port3101.org
Carrier: hdawg
Posts: 6,631
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by Urlryn View Post
Thanks Noname.....i'm checking more into this now!

Is there any books, pdf, classes or anything that gives you more information on how to read these log files and what each one does?
Pretty good article ... just updated too ... How to troubleshoot SRP connectivity issues

There's no real docs on it ... RIMs certification training classes would help; probably best to download the BRK and read through the user guide there ... it explains the output that the tools create when scanning through the logs.
Offline  
Old 12-17-2007, 03:19 AM   #11 (permalink)
Thumbs Must Hurt
 
Dookie's Avatar
 
Join Date: Oct 2005
Location: Prague
Model: 9000
Carrier: T-Mo
Posts: 175
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

I can see SRP drops about 2/3 times per week. Old servers are pointing to srp.eu.blackberry.net, new one points to srp.cz.blackberry.net. If I have SRP drops, they are not at the same time for both machines, so that points to a "easy" conclusion. And our network is not the problem ...
Offline  
Old 12-17-2007, 07:47 PM   #12 (permalink)
BlackBerry Extraordinaire
 
noname's Avatar
 
Join Date: Sep 2005
Location: Congested Islet of "Foreign Talents" (> 45% of workforce) - Singapore.
Model: Z10
OS: 10.0.0
PIN: NUKE(PAP)
Carrier: Singtel
Posts: 1,504
Post Thanks: 6
Thanked 9 Times in 9 Posts
Default

Usually SRP connections issue are written into the MAGT log with the log line similar to below and there will be an WinSock error code tagged to it:-

(12/12 07:48:01.797):{0xB50} 12/12/2007 07:48:01 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
(12/12 07:48:10.938):{0xB50} 12/12/2007 07:48:10 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established

Error=0 means no error and you can pretty much check with your Internet Service Provider to see if there is any short outages or maintenance going on.

Winsock Reference: Appendix C: WinSock Error Reference (continued)
__________________
Native but 4th class citizen of a nation governed by idiots who import congestions & contention.
Offline  
Old 12-27-2007, 04:01 PM   #13 (permalink)
New Member
 
Join Date: May 2005
Location: North Bay, ON
Model: 8700
Carrier: Rogers
Posts: 8
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default SRP Disconnections are hard to pin down

I haven't experienced this recently but have had it before. I was eventually able to trace it to gateway firewall issues.So long as you don't repeat the disconnect/reconnect pattern 5 times within a minute your SRP ID shouldn't get disabled (security feature). The interval wasn't tweakable in 3.6 but I believe it is in 4.0 onward, via reg hack.

Depending on your level of TSupport the queue length can be quite long even when there isn't a general issue on RIM's end. I noticed a big difference when I went from Tx2 to Tx3.

Good luck.
Offline  
Old 12-27-2007, 07:14 PM   #14 (permalink)
BlackBerry Extraordinaire
 
noname's Avatar
 
Join Date: Sep 2005
Location: Congested Islet of "Foreign Talents" (> 45% of workforce) - Singapore.
Model: Z10
OS: 10.0.0
PIN: NUKE(PAP)
Carrier: Singtel
Posts: 1,504
Post Thanks: 6
Thanked 9 Times in 9 Posts
Default

Visualize this picture.

The Firewall sits between the BES and the Internet (that eventually connects the BES to RIM). The points that will break are:-

(1) Firewall
(2) Internet
(3) RIM relay

SRP errors in the MAGT logs are usually Winsock error numbers and these can give us some clues to the issue. For example errors that are more alarming and serious are those like 10054 and 10064:-

WSAECONNRESET (10054) Connection reset by peer.
- WinSock description: Same as Berkeley. On a datastream socket, the connection was reset. This reset could be generated locally by the network system when it detects a connection failure, or it might be received from the remote host (in TCP terms, the remote host sent a RST packet). This error is also possible on a datagram socket; for instance, this error could result if your application sends a UDP datagram to a host, which rejects it by responding with an ICMP Port Unreachable.

WSAEHOSTDOWN (10064) Host is down.
- WinSock description: No equivalent. The only time a WinSock might use this error--at least with a TCP/IP implementation of WinSock--it fails a function with other errors (for example, WSAETIMEDOUT).

Source: Appendix C: WinSock Error Reference (continued)
__________________
Native but 4th class citizen of a nation governed by idiots who import congestions & contention.
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Copyright 2004-2014 BlackBerryForums.com.
The names RIM and BlackBerry are registered Trademarks of BlackBerry Inc.