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
- :
- error when Attach to build Setup.msi file
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
Nov 18, 2015
01:44 AM
error when Attach to build Setup.msi file
Hi
recently I installed installshield 2015 LE for Visual studio 2015. but when I press attach button in visual studio 2015 to create setup.msi I got this error : "the debugger cannot continue running the process. unable to start debugging."
even when I want to build the solution I faced this error too: "-6017: The build was unable to extract COM information; make sure that you are running as Administrator. "
I never faced such error when I was using installshield 2013
please help me to solve that.
thanks
recently I installed installshield 2015 LE for Visual studio 2015. but when I press attach button in visual studio 2015 to create setup.msi I got this error : "the debugger cannot continue running the process. unable to start debugging."
even when I want to build the solution I faced this error too: "-6017: The build was unable to extract COM information; make sure that you are running as Administrator. "
I never faced such error when I was using installshield 2013
please help me to solve that.
thanks
(1) Reply
Nov 18, 2015
02:48 PM
Hi,
Try setting a startup project for the debugger issue.
For error 6017, can you check if you are running as admin as the error suggests.
If you are, there might be a PE that has the Registration Type set to Extract COM Information in the files property that does not have COM info.
Try setting a startup project for the debugger issue.
For error 6017, can you check if you are running as admin as the error suggests.
If you are, there might be a PE that has the Registration Type set to Extract COM Information in the files property that does not have COM info.