Registering OC30.dll in Vista
-
Hi, I've got a 3rd party component that we use in our product that uses OC30.dll. So I've packaged up OC30.dll in the installation. Problem is, that on Vista the installation always gives this error: --------------------------- Self-Registration Error --------------------------- The following files did not self-register or unregister: 1. C:\Windows\system32\OC30.DLL Error : 0x80040200 Manually, I can register the file fine, but unregistering always gives "The module "c:\Windows\System32\OC30.DLL" was loaded but the call to DllUnregisterServer failed with error code 0x80040201." Firstly, If I can register the file fine manually, why is the installation failing? (InstallShield 12 by the way, and it works fine on XP) Secondly, Why can't I unregister the file? The 3rd party component seems to work fine once I've manually registered OC30.dll Yes, the installation runs elevated & I'm using an elevated command prompt to do the manual reg/unreg. I've googled around, but all anything anyone says is about running elevated. Does anyone know anything about this & what I can do to fix it?
Simon
-
Hi, I've got a 3rd party component that we use in our product that uses OC30.dll. So I've packaged up OC30.dll in the installation. Problem is, that on Vista the installation always gives this error: --------------------------- Self-Registration Error --------------------------- The following files did not self-register or unregister: 1. C:\Windows\system32\OC30.DLL Error : 0x80040200 Manually, I can register the file fine, but unregistering always gives "The module "c:\Windows\System32\OC30.DLL" was loaded but the call to DllUnregisterServer failed with error code 0x80040201." Firstly, If I can register the file fine manually, why is the installation failing? (InstallShield 12 by the way, and it works fine on XP) Secondly, Why can't I unregister the file? The 3rd party component seems to work fine once I've manually registered OC30.dll Yes, the installation runs elevated & I'm using an elevated command prompt to do the manual reg/unreg. I've googled around, but all anything anyone says is about running elevated. Does anyone know anything about this & what I can do to fix it?
Simon
-
Thanks, I've read these links, but all they seem to talk about is elevation. As I said in my first post, The installation program is running elevated, but still fails, and I am using an elevated command prompt when manually registering.
Simon
-
Hi, I've got a 3rd party component that we use in our product that uses OC30.dll. So I've packaged up OC30.dll in the installation. Problem is, that on Vista the installation always gives this error: --------------------------- Self-Registration Error --------------------------- The following files did not self-register or unregister: 1. C:\Windows\system32\OC30.DLL Error : 0x80040200 Manually, I can register the file fine, but unregistering always gives "The module "c:\Windows\System32\OC30.DLL" was loaded but the call to DllUnregisterServer failed with error code 0x80040201." Firstly, If I can register the file fine manually, why is the installation failing? (InstallShield 12 by the way, and it works fine on XP) Secondly, Why can't I unregister the file? The 3rd party component seems to work fine once I've manually registered OC30.dll Yes, the installation runs elevated & I'm using an elevated command prompt to do the manual reg/unreg. I've googled around, but all anything anyone says is about running elevated. Does anyone know anything about this & what I can do to fix it?
Simon
-
Have you tried running the installer by right-clicking and choosing the
"Run as administerator"? :)Sojaner!
Yes. The installation runs elevated.
Simon
-
Yes. The installation runs elevated.
Simon
Try this one too: Right-Click the installer file (exe file) and choose properties, in the compatibility tab, choose "Run this program in compatibility mode for:" and from the list choose the "Windows XP (Service Pack 2)", and down the window in the "Privilege Level" group box, check the "Run this program as an administerator" the click on ok and run the setup again. :):rose:
Sojaner!
-
Try this one too: Right-Click the installer file (exe file) and choose properties, in the compatibility tab, choose "Run this program in compatibility mode for:" and from the list choose the "Windows XP (Service Pack 2)", and down the window in the "Privilege Level" group box, check the "Run this program as an administerator" the click on ok and run the setup again. :):rose:
Sojaner!
Yes, I've tried that. As I've said before, the installation already runs elevated, so that isn't the issue. Besides, requiring my users to change the setup exe to run in xp compatibility mode isn't an option I'm keen on. Thanks for trying though.
Simon