Cry about...
MS-Windows Troubleshooting
DllRegisterServer in COM failed.
Return code was: 0xNNNNNNNN
Symptom:
When attempting to register a COM object (e.g. Active-X
component or OCX) with ‘Regsvr32
’, i.e.:
regsvr32 COM
it fails with a message box displaying:
DllRegisterServer in COM failed. Return code was: 0xNNNNNNNN
Where ‘COM
’ is the name of the COM object file
and ‘NNNNNNNN
’ is an eight digit hex number.
Cause:
The cause depends on the specific error.
For a list of possible errors from regsvr32 see the Microsoft Knowledge Base article Q249873.
For a detailed list of error numbers see http://msdn.microsoft.com/library/en-us/netdir/adsi/win32_error_codes.asp or Q155011 (Error codes in NT part 1 of 2).
Errors previously observed:
Error Number | Name | Try |
---|---|---|
0x000000b6 | ERROR_INVALID_ORDINAL |
Try updating system libraries such as MFC42.DLL. |
0x00000485 | ERROR_DLL_NOT_FOUND |
See Microsoft Knowledge Base article Q160018. |
See also:
- DllRegisterServer in COM failed. Return code was: 0x0000007e
- DllRegisterServer in COM failed. Return code was: 0x8002801c
- DllRegisterServer in COM failed. Return code was: 0x80070005
These notes have been tested with Windows NT4 and are believed to be applicable to both Windows 2000 and XP.
About the author: Brian Cryer is a dedicated software developer and webmaster. For his day job he develops websites and desktop applications as well as providing IT services. He moonlights as a technical author and consultant.