Article ID: 170832 - View products that this article applies to.
Certain custom proxy-stub DLLs may corrupt the registry keys for Oleaut32.dll while being unregistered. After this corruption has taken place, Microsoft Transaction Server does not run correctly. Instead, it reports the following error:
Reinstalling Microsoft Transaction Server does not correct this problem.
An error occurred accessing components in the System package on this computer. Error code was 80004002. Make sure that:
+ Microsoft Transaction Server is installed correctly.
+ If you have set a specific identity for the System package, the user and password are correct.
A bug in the MIDL compiler produces proxy-stub DLLs that corrupt the registry, destroying information about Oleaut32.dll. This DLL is required for Microsoft Transaction Server Explorer to function correctly.
To check whether you are being affected by this bug, run Regedit and check the following key:
You should see that this key has a value of "Oleaut32.dll." If this key is blank instead, your registry has been corrupted, and you will need to follow the directions given in the "Resolution" section of this article.
Microsoft has confirmed this to be a problem in Transaction Server 1.0 and Visual C++, 32-bit Editions, version 5.0.
This corruption is often produced when you drag and drop a DLL with a custom proxy-stub from Windows NT Explorer into Microsoft Transaction Server Explorer.
For more information, visit the following Web sites:
Article ID: 170832 - Last Review: June 22, 2014 - Revision: 3.0
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.