Re: regsvr32 error code 0x80004002

"SvenC" <SvenC@xxxxxxxxxxxxxxxx> wrote in message news:C8F17C6A-B309-4E2C-852A-AA57DB569148@xxxxxxxxxxxxxxxx
Hi Norman.

Today regsvr32 gives error code 0x80004002, Interface Not Supported.
(Actual wording: インターフェースがサポートされていません)

That error code has the description "No such interface supported".

To see where it is generated you can debug you ATL dll by using regsvr32 as the debuggee.
Use menu Project properties->Config Props->Debugging
Enter the complete path to regsvr32 into the Command field.

c:\windows\system32\regsvr32

Enter the complete path to your ATL dll (debug version) into Command Arguments.

Ugh. I didn't want to regsvr32 the debug version, I only wanted to regsvr32 the release version. But OK, I'm trying it.

Oh this is really ugly, this is going to depend on debug versions of the CRT. I really didn't want to regsvr32 a debug version. But OK, I'm trying it.

"C:\censored+censored too+installer\censored tree\Debug\censored.dll"
(with quotes because of the spaces)

Put a Breakpoint in the DllRegisterServer function of your ATL dll

HRESULT hr = _AtlModule.DllRegisterServer();

and press F5.

I'm not sure if that will work. The project was built even though registration failed. I don't need to start executing the C# client executable project, I need to make VS2005 call the DLL's DllRegisterServer function.

I thought of right-clicking the DLL project and selecting Rebuild. But wait, this is the reason why you told me how to set the project's debugging properties. OK, F5.

Well, the whole thing executed without breaking at the breakpoint.

Double-checking the properties of the C# client executable project, in the Debug properties, the checkbox to enable debugging of managed code is already checked.
(Actual text: アンマネージ コード デバッグを有効にする(U))

And there's more. The whole thing executed without breaking at the breakpoint, but just before that, the whole thing rebuilt. There's even the error PRJ0050 that registration failed. This VS2005 error message comes about because of the regsvr32 error. The usual response to PRJ0050 is that administrators have to run VS2005 as administrator. I am running VS2005 SP1 as administrator, and this is on XP SP2 not on Vista. So regsvr32 bombed out without even calling my DllRegisterServer function, right?

Single step through the code and watch out which call does return 0x80004002.
You might find the problem yourself with this method otherwise please post which function fails.

Still hoping to reach that point, if you know how to get there.

.

Relevant Pages

  • Re: regsvr32 error code 0x80004002
    ... I'm afraid some of code (regsrv, or any DLL) ... To see where it is generated you can debug you ATL dll by using regsvr32 ... Enter the complete path to regsvr32 into the Command field. ... I don't need to start executing the C# client ...
    (microsoft.public.vc.mfc)
  • Re: regsvr32 CRASH
    ... As has been pointed out in the other thread, this should be easy to debug. ... You can literally write your own regsvr32, since all it does is load the dll ... that wrote DLLRegisterServer, and it is likely that that is where the ... >> when we build it and attempt to register our DLL, it doesn't crash. ...
    (microsoft.public.win32.programmer.ole)
  • Re: Invalid memory access using regsvr32.exe
    ... regsvr32 and the command line to be the arguments you provide to regsvr32 (it has been ... Then debug as usual. ... I am registering an OCX through ... MVP Tips: http://www.flounder.com/mvp_tips.htm ...
    (microsoft.public.vc.mfc)
  • Re: Project : error PRJ0050: Failed to register output.
    ... When you debug it, set a breakpoint at the end of both of those functions ... Regsvr32 being executed from the Visual Studio directory, ... Even if from the DOS prompt within the directory where the DLL resides ... regsvr32 dummy.DLL it fails to register. ...
    (microsoft.public.vc.mfc)
  • Unable to start debugging com+ registry ...
    ... After appling sp2 I started geting the following error. ... "Error while trying to run project: Unable to start debugging on the web ... The com+ registry database detected a system error." ... -run regsvr32 /u aspnet_isapi.dll ...
    (microsoft.public.vsnet.debugging)
Loading