[Fletchi18]

I just had to reboot our BES this morning and email is *very* slow to be delivered to the devices (usual time is within seconds, after reboot it took about 45 minutes for an email to be delivered).

Just brainstorming as to the possible cause of the slow down. The server looks to be in good shape. No errors in events, services are all started.

Could the BES simply be preoccupied with trying to catch up old devices (ones that have been off for weeks/months) and it is not able to handle the real time delivery of emails until it finishes with those devices that have been off for a while?

I'm not sure I'm wording my thoughts correctly. If you need any clarification, please feel free to ask!!

And thank you!!

[penguin3107]

How many users? What messaging platform? What version and SP of BES?
BES is likely busy doing mailbox rescans of all your users as a result of the reboot.

[Fletchi18]

Knew I forgot something:
BES 4.1.7 on Win2k3
Exchange 2003 on Win2k3.
~120 devices

Does having devices that have not communicated with the BES in days/weeks affect the performance of the server? For example, we have 4 devices that have not communicated with the server in over a month (That's a great way to waste $180!!). Could they be what is causing things to be slow after the start or is it simply general mailbox scans?

[freakinvibe]

I never experienced 45 minutes delays in mails after a BES reboot. You should really check in the message flow where the mails are stuck for so long. Do all users have pending data packets?

The message goes from Exchange to the BES messaging agent and then to the dispatcher and then to the router and then to the RIM infrastructure. Any of those elements could be causing the delay. Inspecting the different logs might help or you could use the resource kit tool

MessageFlow.exe

to help finding the problem.