Summary
This article contains a brief overview of how InstallShield supports COM extraction. More specifically, this article discusses how to resolve issues where an application does not work properly due to missing COM information.Synopsis
This article contains a brief overview of how InstallShield supports COM extraction. More specifically, this article discusses how to resolve issues where an application does not work properly due to missing COM information.
Discussion
This behavior usually occurs when files are included in the project through the Component Wizard or when using the "COM Extract at build" option in the Components view. Both of these are commonly used methods to mark files as COM files so that the proper information is extracted at build time.
The issue is that InstallShield looks in locations specified by Microsoft to be standard COM information areas. If information is located in other areas, this is non-standard COM Information. The "COM Extract at Build" option and Component Wizard only retrieve standard COM information, but the self-register setting allows you to register any file that has non-standard COM information.
To resolve this issue, mark each file as "Self-register" in the Setup Design view in the InstallShield Developer IDE. Also, do not use the Component Wizard to add COM files and do not mark Components as "COM Extract at Build" in the Components view.
Another approach involves adding the contents of a REG file to your project. This can be accomplished manually with the REG File Wizard. InstallShield enables you to import any existing registry (.reg) files that you may have from other installation projects or that you have created outside InstallShield. With this approach disable COM extract at build. Extract the COM data required to a REG file. Import the REG file. Reference the links below for more information - Importing Registry Files and Import REG File Wizard.
Additional Information
For additional information on COM registration, refer to InstallShield Help topics Extracting COM Registration at Build Time and Installing COM Servers.
Related Documents
Extracting COM Information from a COM ServerConfiguring COM Registration Settings Manually
Importing Registry Files
Import REG File Wizard
Related Articles
COM Information Missing For Shared Component 3Number of Views Extracting COM Information with RegSpyUI.exe 4Number of Views Beacon control file (policy) missing or does not contain license information, please restart the beacon interface 44Number of Views SQL Edition information from SCCM is Missing in FNMP 19Number of Views Socket information is missing from inventory imported from ILMT 6Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago