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
- :
- Fixed
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
Sep 17, 2015
03:23 PM
-4354: The build was unable to extract COM information from the file
Upgrading from an InstallShield 2013LE edition to 2015LE and it breaks COM extraction for the two OCX files I have in my project, MSCAL.OCX and MSCOMDLG32.OCX. (and any other random OCX file I have tested)
I receive the message: -4354: The build was unable to extract COM information from the file...
What I have noticed:
- Upgrading to 2015 breaks the COM extraction in both Visual studio 2013 and 2015.
- Removing 2015 and reinstalling 2013 fixes the problem.
- Starting from scratch with a new project makes no difference.
- I have tried disabling DEP with no result.
- I am running with Administrator permissions.
- Both OCX files will register and unregister without problem using regsvr32.
This is driving me crazy. Anyone have ideas why this would be happening and/or how to fix?
Thanks!
I receive the message: -4354: The build was unable to extract COM information from the file...
What I have noticed:
- Upgrading to 2015 breaks the COM extraction in both Visual studio 2013 and 2015.
- Removing 2015 and reinstalling 2013 fixes the problem.
- Starting from scratch with a new project makes no difference.
- I have tried disabling DEP with no result.
- I am running with Administrator permissions.
- Both OCX files will register and unregister without problem using regsvr32.
This is driving me crazy. Anyone have ideas why this would be happening and/or how to fix?
Thanks!
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Sep 17, 2015
09:34 PM
While uninstalling 2015 and reinstalling 2015 did nothing, it finally started working after uninstalling 2015, reinstalling 2013, reinstalling 2015, and then uninstalling 2013.
Very strange.
Very strange.