Is anyone having any issues with their BES servers not sending email? About 5:00pm EDT today, my BES (4.0.3) stopped processing mail, and the server has a red X on it. When I look at the properties it shows 'Running, SRP disconnected'.
I ran the BBsrptest.exe and it said the connection was successful.
We've rebooted the server and it still won't come up. On hold with RIM as I type....been a long hold time so I almost wonder if there is a major outage?
Well, after over an hour on hold with RIM, we finally got thru. They said the SRP was disabled because it had tried to connect 5 times within 1 minute and failed. They were able to re-enable it (and we're up!), but we don't know what caused it. I sent them the application log and they said there wasn't anything in it that would point to a problem (like a network connectivity issue). He said the app log actually was very 'clean'.
Anyone know which log file I can look in and what error I should look for? I know what time it started happening, so can start there.
Anyone know which log file I can look in and what error I should look for? I know what time it started happening, so can start there.
Anyone? I've been waiting for a flood of replys from the wonderful BES Admins I know are lurking out here. Ok, maybe not a flood, but a trickle would be nice.
The logs you should familiarize yourself with are: DISP, MAGT, SYNC, CEXC & ROUT
There are obviously others, but these usually give a good indication of the nature of the BES services.
The DISP logs show user specific info - datagrams sent/received by the users' device for example, and BES server info which shows the status of Ping responses - sent/received - by the RIM infrastructure. So generally this log file indicates data transfer issues between the BES synchronization service, BES messaging agent and the Blackberry device.
The MAGT log shows more user specific info - status of Rescans of PIM items, mailbox; OTAFM (over the air folder management) activity...this is Inbox activity; status of Ping responses and data packets sent/received/delivered
The SYNC logs shows info related to data processing or conversion (PIM data)
The CEXC logs show the activity between the BES agent and the enabled BES users. Sometimes if the Exchange server has to be restarted (for whatever reason) this log also shows when the Exchange server was stopped. The event viewer also shows the "red" marker when this service has stopped and if the Controller service has not restarted it, it (CEXC) needs to be restarted for continued mail redirection to occur.
The ROUT logs indicate relay session activity between the BES and the RIM infrastructure and the devices ( loading configuration, sync activity) It's usually of the type - (SERVICE_RELAY_SESSION:SXXXXXXXX:007cb9e0), where the hexadecimal # represents the process ID.
Some typical SRP connectivity issues - connection timeout (10060)
connection reset by peer (10054), host not found (11001), or connection refused (10061) - 5 in 5 rule takes precedence here.
What causes the above to occur? It could be network-related (failed network connectivity between the BES and the mail server; failed mail API connectivity between the BES and the mail server [sever reboot, mailbox corruption]; low bandwidth and latency can cause hung threads).
Somtimes firewall configurations, proxy configurations, and network switches (is it full-duplex or half-duplex mode?) can be the culprit.
The same thing happened to me today 6/13/2006. I had to call RIM, give them my site number and key. Then they reset it. Our BB server has been running flawless for 6 months. So I do not know what caused the problem. I think this is rediculous that we have to wait for tech support to do this. There should be a utility to request a reset. What a waste of a morning.
SRP Disconnected -
06-07-2006, 08:23 PM
