Hotfix informationTo resolve this problem, install the Microsoft Exchange Server 2003 hotfix that is described in Microsoft Knowledge Base article 895404. For more information about how to obtain this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:
To work around this problem, you must append the string A;;0x2;;;S-1-5-11 to the CustomSD registry entry on each server that is running the Provisioning Engine. The CustomSD registry entry is located in the following registry subkey:
- Click Start, click Run, type regedit, and the click OK.
- Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Eventlog\Application
- In the right pane, right-click CustomSD, and then click Modify.
- In the Edit String dialog box, append the following string to the value that appears in the Value data box:A;;0x2;;;S-1-5-11
- On the File menu, click Exit.
- After you have changed the registry entry, you must restart the Provisioning Engine on each server that is running the Provisioning Engine. The Provisioning Engine is located in Component Services.
This problem occurs only if the first try to initialize CDOEXM is performed from outside an Exchange provider procedure such as creating a user object. All Exchange provider procedures run under the context of the MPSPriv* account. By default, that account has the rights that are required to fully initialize CDOEXM. However, the Active Directory provider procedures run under the context of the authenticated user account or the impersonated user account.
Article ID: 899194 - Last Review: 29 Mar 2017 - Revision: 2