This article was previously published under Q263064
This article has been archived. It is offered "as is" and will no longer be updated.
The Blackberry pager service can monitor multiple Exchange Server computers for new e-mail activity. If one of the monitored Exchange Server computers goes offline, the Blackberry pager service may stop responding, or "hang."
This problem can occur because one thread is waiting for a server response to a remote procedure call (RPC). However, a response never comes because theExchange Server computer is offline. In some instances, two other threads are blocked because they are waiting for the first thread to finish, and many other threads are blocked because they are waiting for a critical section that is held by one of the two threads.
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.5 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Component: Information Store
Install this fix on the Blackberry server. The Blackberry server acts as a client to the Exchange Server computer. There may be more than one instance of the Emsmdb32.dll file on the server, depending on the applications that are installed on that server. You need to replace all instances of the Emsmdb32.dll file.
Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 4.