SelfRegistering a DLL not working

[jfbaude]

Under IS 2009 Premier, I checked the SelfRegister option on one DLL to be installed.

During installation (under a VM on XP SP2) I got the following error:

Error 1904. Module C:\ProgramFiles\...\MyDLL.dll failed to regsiter. HRESULT -2147220473

Does it come the the type of DLL ?
Is there an existing work around ?

Please help.

Rgds

JF BAUDE

[Reureu]

• Have you tried to register the DLL manually on the target PC (or virtual machine)? Does it produce the same result?
  
• Can you reproduce it systematically? Or is it sporadic?
  

One recommended fix is to use the "COM Extract at build" setting instead of the self-registration.

[ChandanOmkar]

Try to register manually the DLL using regsvr32. It must be a COM dll otherwise you will get the error during register.

[jfbaude]

I tried to register manually and it failed....

What do you mean by "It must be a COM dll otherwise etc..." ?
Does it mean that I should modify th VCPROJ configuration for DLL generation ?
If Yes how ?

I'm NOT the DLL developer so I'm not easy with Visual Project configuration...

Rgds

JFB

[jfbaude]

I died other tries:

- If I only check "Self Register" option, installation will fail under VISTA with "Error 1904 ..."
- Same behaviour with "COM at Extract Build"=Yes.

My DLL has NO problem of dependancy (checked through Depends.dll) on the target PC.

- So I tried a CA as:
Working Directory=SystemFolder
command line=regsvr32.exe "[INSTALLDIR]MyDLL.dll"
Synchronous(check exit code)
Sequence=After ScheduleReboot
Deferred Execution in System Context
Exec condition=Not installed

==> installation will fail under VISTA BUT with another error: "Error 1722 ..."

I'm completely disappointed because I saw plenty of similar threads but NOWHERE any answer....

[ChandanOmkar]

your dll is not register manually. so you can not solve this issue with installshield. may be you need to change the code and configuration of your dll and rebuild it. Check with msdn.

[jfbaude]

Hello all

I got the same problem under Windows 7, whatever UAC settings.
Should I transform my MSI into a setup.exe ?

Does it come from the DLL itself or does it come from elevation rights ?

Please advice.