Registering DLL on W7 pcs

[bsutton55]

I am struggling to register a DLL on client PCs. The clients are all W7 Service Pack 1 32 bit. No problems with installing DLL on XP clients!

My main application is located in and runs from C:\localapps\. I have copied mynew.dll into the localapps folder on the clients; I have also copied the tlb and the vbr files - I was not sure if these were needed or not - could someone advise on this point?

When running 'regsvr32 c:\localapps\mynew.dll' at the command line prompt I get errors:

On one W7 client the error states: "The modul "c:\localapps\mynew.dll" was loaded but the call to DllRegisterServer failed with error code 0x80004005".

On another W7 client I get "The module 'c:\localapps\mynew.dll' failed to load. Make sure the binary is stored at the specified path or debug it to check for probles with the binary or dependent .dll files. The specified module could not be found".

I also have the VFP9r.dll ,VFP9t.dll and VFP9RENU.dll in the c:\localapps folder.

I have tried logging on to the client as both local and domain admin. I have also tried "Run as administrator" against the CMD prompt.

I do not understand why I get different error messages on what appear to be 2 identically configured clients.

Could someone shed some light on what I am missing?

Thanks
Barry Sutton.

 

[Olaf Doschke]

What about UAC (User Account Control)?

Bye, Olaf.

 

[Olaf Doschke]

Also: Did you verify this really is a 32bit Win7 and there is no %WINDIR%\Syswow64\ folder? If so, this is the folder containing the 32bit executables of odbc administrator, and many other tools, also regsvr32.exe

Otherwise what should work is starting cmd.exe via run as admin, as you did (or did you try to run a .cmd batch file with "run as admin"?) and then start the correct regsvr32 from that command prompt with the full path to the DLL file.

Bye, Olaf.

 

[bsutton55]

Olaf, Thanks for input. I had assumed that being logged on as domain admin would allow me to run Regsvr32. I now realise that I have to be logged on as local admin; or at least, now that I am logged on locally I can register the dll. So that's great.
Thanks again.
Barry

 

[Olaf Doschke]

Hm, you said "as both local and domain admin".

Of course acting on local resources like a locally stored DLL and adding it to the registry, requires a local admin, yes.

Bye, Olaf.