02-13-2008, 04:29 AM
A build script that has worked perfectly for a long time is now failing to register DLL's despite no indications that this is the case. What might cause regsvr32 to start "not working" all of a sudden?
02-13-2008, 04:41 AM
Can we see the script or at least the part that attempts to register files?
Have you tried registering the files manually by calling regsvr32? If you do it manually you can make it display any errors
02-13-2008, 04:51 AM
The user that is executing the Script that register the DLL's is the System Administrator?
Only the system administrator, or a user with administration previlegies can Register a COM using RegSvr32.
02-13-2008, 05:16 AM
I think it may be a problem with the version of Installshield that im using. All the components register OK with regsvr32. Installshield is giving me this:
SEXP : warning -4354: The build was unable to extract COM information from the file c:\vss\Nexus\Binaries\Nexus\NXGlobal.dll in component NXGlobal.dll. Please ensure that the file is self-registering and verify that the self-registration process does not fail.
02-13-2008, 07:57 AM
It was the installshield COM extraction process that was being interfered with by Data Execution Prevention. I turned this off on the build box and bob's your uncle - successful build. For reference the process is described here: