Article ID: 198841
Article Last Modified on 10/28/2006
APPLIES TO
- Microsoft Exchange Server 5.5 Service Pack 2
- Microsoft Exchange Server 5.5 Service Pack 3
This article was previously published under Q198841
IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
The Microsoft Exchange Calendar Connector relies on store notifications for processing MAPI-based queries from Exchange clients. In certain cases, this notification mechanism may stop, and require a restart of the Calendar Connector.
CAUSE
There is a problem with the store's push notification mechanism. In a heavy stress environment, this problem becomes more apparent. This problem occurs more often on high-powered Alpha-based servers than on Intel servers.
WORKAROUND
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that you can solve
problems that result from using Registry Editor incorrectly. Use Registry Editor at your own
risk.
To work around this problem, add a key to the registry. To do this, follow these steps:
- Start Registry Editor (Regedt32.exe).
- Locate the following key in the registry:
HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
- On the Edit menu, click Add Value, and then add the following registry value:
Value Name: Notification Timeout
Data Type: REG_DWORD
Value: 1
- Quit Registry Editor.
STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5.
Keywords: kbbug kbpending KB198841