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
- :
- Re: Installer Class - Error 1001 InstallShield 2015 Limited Edition
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
‎Feb 13, 2017
07:44 AM
Installer Class - Error 1001 InstallShield 2015 Limited Edition
Hey,
I'm getting the Error 1001 every time I active the Installer Class option on my Primary Output Projects. In Service, Console or any kind of project this error has dropped.
I'm using Windows 10 (version 1607), Visual Studio 2015 with update 3 and InstallShield 2015 Limited Edition.
My Projects are developed using .NET Framework 4.5. C#
Does anyone know how to fix it?
Please.
Thanks.
I'm getting the Error 1001 every time I active the Installer Class option on my Primary Output Projects. In Service, Console or any kind of project this error has dropped.
I'm using Windows 10 (version 1607), Visual Studio 2015 with update 3 and InstallShield 2015 Limited Edition.
My Projects are developed using .NET Framework 4.5. C#
Does anyone know how to fix it?
Please.
Thanks.
(4) Replies
‎May 02, 2018
04:26 AM
am also facing the same issue.Please help to fix this issue
‎May 02, 2018
02:59 PM
I'll help point you guys in the right direction:
The actual error is buried. It won't show in your logfile--error -1001 is just what the Microsoft InstallUtilLib.dll passes back when there's an error inside the installer class.
Your best bet is to debug it yourself by inserting a Debugger.Launch() statement inside your Installer Class and then stepping through with Visual Studio.
Good luck!
The actual error is buried. It won't show in your logfile--error -1001 is just what the Microsoft InstallUtilLib.dll passes back when there's an error inside the installer class.
Your best bet is to debug it yourself by inserting a Debugger.Launch() statement inside your Installer Class and then stepping through with Visual Studio.
Good luck!