Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
A global event sink is not triggered after you restart the Microsoft Exchange Information Store service in Exchange Server 2003 Service Pack 1
Article ID: 872822 - View products that this article applies to.
After you install Microsoft Exchange Server 2003 Service Pack 1 (SP1) on a computer that is running Exchange 2003, you experience the following symptom:
Note If you have a mailbox event sink configured, that mailbox event sink is still triggered when you restart the computer or when you restart the Microsoft Exchange Information Store service.
This problem occurs because of a problem with the verification code that was introduced in Exchange 2003 SP1. In Exchange 2003 SP1, code is included to verify whether an event binding has a particular variable set. If this variable is not set, the event binding is not registered. Exchange global event sink bindings do not set this particular variable. However, the verification code that was introduced in Exchange 2003 SP1 does not account for the global event sink binding not having this variable set. Therefore, the global store event sink registration fails when the information store is re-mounted.
Service pack informationTo resolve this problem, obtain the latest service pack for Exchange Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/836993/EN-US/ )How to obtain the latest service packs for Exchange Server 2003
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesBecause of file dependencies, you must have Exchange 2003 Service Pack 1 (SP1) installed to apply this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/836993/ )How to obtain the latest service packs for Exchange Server 2003
Restart requirementYou do not have to restart your computer after you apply this hotfix. However, you must restart the Microsoft Exchange Information Store service to apply the changes after you install this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------------- 27-Jul-2004 19:26 6.5.7232.19 2,567,168 Exoledb.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Exchange Server 2003 Service Pack 2.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
(http://support.microsoft.com/kb/817903/ )New naming schema for Exchange Server software update packages