Exchange Management Pack: DCOM Failed to create the object 'EMPKP.PubKeyPublisher'

Source: Microsoft Support

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION IN RESPONSE TO EMERGING OR UNIQUE TOPICS, AND MAY BE UPDATED AS NEW INFORMATION BECOMES AVAILABLE.

The DCOM event 10000 indicates the application could not start, most likely a problem with the path or name of the application (notice the "valid Win32 application" in the event). To verify open regedt32 on the Exchange server and search for the following key:

HKEY_CLASSES_ROOT\CLSID\{94A6DCD0-B6F5-40E8-8C9D-CEE2C7796380}\LocalServer32

There will be a default value that points to the DCOM application that failed to start. The normal value will be something similar to:

C:\PROGRA~1\Exchsrvr\bin\empkp.exe

with the drive letter changing according to the install path of the Exchange Binary files. This is 8.3 file naming convention. For this particular customer, the value was:

D:\Program Files\Exchsrvr\BIN\empkp.exe

Since there was a space in this path, DCOM could not resolve the location of the application. Once the customer encapsulated the path in double quotes the DCOM application started as expected and script "Exchange - Publish ExMP Data" ran as expected.

Note that in addition to the EMPKP application, there are other "helper" files that are installed when Exchange 2003 is installed. In the customer's case these other DCOM applications also failed to start because of the same problem. Look for the DCOM errors in the system event log for the GUID and path of the failing applications.

Exchange 2003 SP1 server running on Windows 2003.
MOM 2005 deployed to monitor server in the organization.
Exchange 2003 Management Pack for MOM 2005 successfully deployed.

The following event is logged on MOM server:

EMPKP is a DCOM application that generates the registry keys used to store the encrypted account/password for the Mailbox Access Account, which is used for MAPI logon to monitored mailboxes on Exchange servers to verify mailbox availability. In addition in the system event log on the exchange server, the following event was logged: