This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- COM Registration Fails in 2008, worked in X
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 03, 2009
12:08 PM
COM Registration Fails in 2008, worked in X
We recently upgraded one of our product's InstallScript projects to InstallShield 2008 from InstallShield X, and we are having a few issues during the registration of an OCX and DLL file on Vista.
In the installer, we register a number of third-party OCX controls, using the "Self-Register" option. The project built in X would install fine on Vista.
Recently, a few changes were required for unrelated pieces of the project, so we made those changes in InstallShield 2008. However, we now receive a Self-Registration Error for two third-party files. Everything seems to work just fine on Windows XP. When the installer is run, Vista correctly prompts with UAC to elevate privileges.
The error we get on Vista is (text in brackets has been altered):
[CODE]
The following files did not self-register or unregister:
1. [path\to\our\file\filename.ocx]
Error accessing the OLE registry.
2. C:\Windows\system32\[filename].dll
Error accessing the OLE registry.
[/CODE]
The DLL is NOT a file that is shipped with Vista. We register a number of other DLLs and OCX files, all of which seem to register properly. We only have an issue with two files. The files themselves have not been changed. To confirm, we rebuilt the old version of the installer with X using the same files and it worked fine.
Does anyone have any idea what the issue could be, and why it does not work in 2008 but did in X?
I've searched through the forums, and am having a hard time finding any clear answers. What is COM Extraction? Does that apply to InstallScript projects?
Thanks in advance.
In the installer, we register a number of third-party OCX controls, using the "Self-Register" option. The project built in X would install fine on Vista.
Recently, a few changes were required for unrelated pieces of the project, so we made those changes in InstallShield 2008. However, we now receive a Self-Registration Error for two third-party files. Everything seems to work just fine on Windows XP. When the installer is run, Vista correctly prompts with UAC to elevate privileges.
The error we get on Vista is (text in brackets has been altered):
[CODE]
The following files did not self-register or unregister:
1. [path\to\our\file\filename.ocx]
Error accessing the OLE registry.
2. C:\Windows\system32\[filename].dll
Error accessing the OLE registry.
[/CODE]
The DLL is NOT a file that is shipped with Vista. We register a number of other DLLs and OCX files, all of which seem to register properly. We only have an issue with two files. The files themselves have not been changed. To confirm, we rebuilt the old version of the installer with X using the same files and it worked fine.
Does anyone have any idea what the issue could be, and why it does not work in 2008 but did in X?
I've searched through the forums, and am having a hard time finding any clear answers. What is COM Extraction? Does that apply to InstallScript projects?
Thanks in advance.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 04, 2009
09:38 AM
An update:
I made a NEW test project that installs only the third-party OCX file, and it fails on Vista after UAC elevation. So this doesn't seem to be an issue with the upgrade.
I made a NEW test project that installs only the third-party OCX file, and it fails on Vista after UAC elevation. So this doesn't seem to be an issue with the upgrade.