To register a DLL file on a windows server using regsvr32, do you first need to move the file to your system32 folder or is that actually done automatically once you call the regsvr32 command?
If I just drop a dll file on my desktop and register it there, can I just delete it after registration? What would happen after removing it?
In other words, how does the regsvr actually really work?
Does Windows Server 2003 cache specific DLLs on a per-user basis when in a terminal server environment?
Back-Story:
We recently had to update some DLLs for our application, and a couple clients are still experiencing the issue that the update was to resolve. The build number of the DLL changed, but obviously the name did not. So I'm trying to figure out if these users had a cached version of the old DLL somewhere in their profile.
I'm installing a custom application on a brand new Windows 2003 Server. A couple of DLLs need to be added and registered, and I have copied them to the server in the C:\WINDOWS\System32 folder -- which is where they have always been when we've had the application running on Windows NT and 2000.
However, when I try to register them using:
regsvr32 c:\windows\system32\nameoflibrary.dll
It gives back:
LoadLibrary("c:\windows\system32\nameoflibrary.dll") failed -
The specified module could not be found.
The DLL is however right there. I can see it. If I copy the path to Windows Explorer and attempt to run it, it tells me that I can't run a DLL, so I know it's there. One minor complication is that the DLLs were built in VB5 -- but the VB5 runtime is installed on the server, so this shouldn't be a problem.
Any ideas?
I am having problems running the Windows version of wget on a Windows 7 machine. When I run the command I get this error:
The program can't start because libintl3.dll is missing from your computer. Try reinstalling the program to fix this problem.
Is there a safe place I can download and register this DLL? I do not consider safe any of the Google results I see when searching for this file.
I am attempting to register a basic COM dll on a Windows Server 2008 standard box.
I run regsvr32 capicom.dll and it reports DllRegisterServer in capicom.dll succeeded. This is the same process we've used for years on Windows Server 2003.
Sadly, when I attempt to create the object via a very very basic Microsoft vbscript example Set oStore = CreateObject("CAPICOM.Store") it throws a "ActiveX component can't create object" error.
Thinking maybe it was a problem with this dll, I tried a few other DLLs we use with the same result. I tried using the regsvr32 in system, system32, and syswow64 all with the same result. I don't know too much about the differences between each of those, but figured it was worth a shot.
The dll is being stored on the d:\ and seems to have correct permissions (though that'd be a different error altogether).
*UPDATE: Through additional testing, we have determined (via dependency walker) that ieshims.dll and linkinfo.dll are missing. They are on the machine, but reported as could not find. This is true of both capicom.dll and an internally developed dll.
Thanks to any help or thoughts you might have!