06-08-2006, 03:41 PM
Join Date: Apr 2005
Post Thanks: 0
Thanked 2 Times in 2 Posts
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.