[boobleberry]

morning, afternoon, etc.

we are running windows 2003 sp1 and exchange 2003 sp1 with the latest bes 4.0 sp5. we have a long delay in receiving messages on devices. input?

muchos gracias!

BB

[Mlwii]

Could you provide some more detail? How many users do you have on the BES? Hardware specs? Do you have any BES services spread across multiple servers or do all services run on one box? How much of a delay are we talking about?

[boobleberry]

sorry for the lack of detail.

One BES4.0 SP5 with 4 GB RAM on dual 2.8 GHz intel. One SQL 2000 server SP4 with same hardware as BES. 1000 users.

delay is anywhere from 5 minutes to 30 minutes. funny thing is if we reboot, then it clears up. so hung threads or ...?

[BEShelpguy]

try checking the logs (Controller IIRC) as its tells you in plain english if you hae hung threads or not.
Also, where is the BES located in comparision to the Exchange servers that its servicing?
Is it all users who experience delays or always the same users having the longest delays?

Have you monitored the performance counters on the exchange server(s)?

[r007r]

Originally Posted by boobleberry

morning, afternoon, etc.

we are running windows 2003 sp1 and exchange 2003 sp1 with the latest bes 4.0 sp5. we have a long delay in receiving messages on devices. input?

muchos gracias!

BB

Sounds like you are having a domain name resolution issue. I would check your bes logs and reference some of these documents. You might want to check which Global Catalog server that you are using and maybe enable LDAP for address lookups. If not then it could be an issue with your environment. What is the ping response time from bes to exchange? Also is the mapi32.dll the same on the bes and exchange. If you the bes is not installed on the exchange then check for emsmdb32.dll. If the version is 6.5.7226.0 then you might be affected by a memory leak. Apply the patch from ms or install sp2 for exchange 2003 on the bes. Hope this helps!!

Article: Message delays because of domain name resolution problem (RIM_HrGWResolveProxy)
Article Number: KB-03304
Livelink - Redirection

Article: What Is - Error 0x8004010f
Article Number: KB-03433
Livelink - Redirection

Article: How To - Configure Lightweight Directory Access Protocol for the BlackBerry Enterprise Server
Article Number: KB-03193
Livelink - Redirection

Article: What Is - Delayed notifications state for health checks session
Article Number: KB-01892
Livelink - Redirection

[boobleberry]

Hi ppl, sorry for the late reply. It turns out that it was a user threshold which was well under 2000. Once we spread the user load across the Blackberry servers under 700 we did not see the late mails. We have five exchange servers and two BES servers and i should have said that earlier since it makes a difference to the crap we saw.

[admin4bes]

We had this exact same issue! We have an Exchange Cluster and with three EVS' and three BES'. RIM does say you can have a maximun of 2000 users (bs). We ended up spreading our users accross multiple bb servers so that they did not exceed 800 bb accounts. So that is really 800 user acounts spread across three different bes agents on the same server. Is anyone out there with an enviroment more than 1000 or at least close to 2000 on a single bb server? We have just added a forth server. This is kinda expensive. FOUR SRPs and 3000 user CAL!