Microsoft KB Archive/324645

= You may receive Event ID 30, Event ID 108, or Event ID 114 after you upgrade Exchange 2000 Server to a new service pack =

Article ID: 324645

Article Last Modified on 10/28/2006

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q324645



SYMPTOMS
After you upgrade Microsoft Exchange 2000 Server to a new service pack, message tracking may not function. Additionally, the following events may be logged in the Application log:

Event Type: Error

Event Source: WinMgmt

Event Category: None

Event ID: 30

Date: 6/10/2002

Time: 4:12:37 PM

User: N/A

Computer: Server_Name

Description:

A WMI/WBEM client executed an asynchronous operation and failed to return from its implementation of IWbemObjectSink.

Event Type: Error

Event Source: EXOLEDB

Event Category: Events

Event ID: 108

Date: 6/5/2002

Time: 10:53:33 PM

User: N/A

Computer: Server_Name

Description:

Microsoft Exchange OLEDB was unable to either create an event sink object or get necessary interface(s) from the sink class specified by ExSchema.XmlPromotion.1, HRESULT = 0x80070005.

Event Type: Error

Event Source: EXOLEDB

Event Category: Events

Event ID: 114

Date: 6/5/2002

Time: 10:53:33 PM

User: N/A

Computer: Server_Name

Description:

Microsoft Exchange OLEDB has disabled the event binding due to the problems in the event sink. Binding ID = {CD16762F-654A-4874-A34B-0D0046BD9B08}. You may need to contact the event sink author and get a fixed or updated copy.



CAUSE
This issue may occur when the following conditions are true:
 * In the DCOM Configuration utility (Dcomcnfg.exe), the default permissions have been modified. They have been modified in the Default Access Permissions area of the Default Security tab in the DCOM Configuration utility.
 * The system account and the Interactive special group have not been explicitly added. They must be granted Allow Access permissions.



RESOLUTION
To resolve the problem, add the system account and the Interactive special group. Grant them Allow Access permissions. To do this, follow these steps:
 * 1) Click Start, click Run, type dcomcnfg in the Open box, and then click OK.
 * 2) Click the Default Security tab, and then click Edit Default under Default Access Permissions.
 * 3) Click Add to add SYSTEM and INTERACTIVE and to grant them Allow Access permissions.
 * 4) Click OK.



STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.



MORE INFORMATION
The following are the default settings of the DCOM Configuration utility. On the Default Security tab, there are no entries in the Default Access Permissions area. There are two implicit entries that have Allow Access permissions. These are the system account and the Interactive special group.

Then, if an access control entry is explicitly added to the Default Access Permissions, the implicit permissions for the system account and for the Interactive special group are revoked.

Therefore, some WinMgmt requests fail because there is no system account. Additionally, message tracking fails because there is no Interactive special group.

If the permissions in the Default Access Permissions area are modified, you must add the System account and the Interactive special group. Additionally, you must grant them Allow Access permissions. You add the system account and the Interactive special group to the discretionary access control list.

Keywords: kbsecurity kberrmsg kbupgrade kbprb KB324645

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.