HOTFIX: Install Fails With Error 1001 When a .NET Installer Class Component is Present in InstallShield 2015 SP1
HOTFIX: Install Fails With Error 1001 When a .NET Installer Class Component is Present in InstallShield 2015 SP1
Summary
When an install containing a .NET installer class component is built on a machine with a certain version of.NET 4.6, the resulting install fails with error 1001.
Symptoms
When an install containing a .NET installer class component is built on a machine with a certain version of.NET 4.6, the resulting install fails with error 1001. The log shows that the error occurred on the .install custom action used to perform the .NET installer class install actions
Cause
This behavior is caused by an issue with InstallShield 2015.
Steps To Reproduce
The easiest way to reproduce the issue is on a Windows 10 machine with .NET 4.6.
Steps to Reproduce:
Create a new Basic MSI project on the Windows 10 machine.
Add a .NET installer class dll as a key file of a component.
Set the .NET Installer Class setting to Yes.
Build the project.
Install the built install.
Resolution
This issue has been submitted as a bug and is pending review from our Engineering team. The issue is being tracked under issue #IOJ-1752933..
Engineering has released a hotfix that resolves this issue. In order to apply the hotfix, please do the following steps:
Close InstallShield.
Go to <PROGRAM_FILES>\InstallShield\2015\System.
Find and rename ISWIBuild.dll to ISWIBuild.dll.bak
Extract the ISWIBuild.dll from the downloaded zip to the InstallShield System folder.
Open InstallShield and make sure that the path in Tools > Options > .NET tab correctly points to the v4 folder.
Hi, We are still using IS 2014 Premier Edition SP1 and run into the same issue. In one of our setups the .NET installer class installation is failing with error 1001. If we build the setup manually on a different machine, where .NET 4.7 is not installed, everything is fine, but on our common build server, we cannot uninstall .NET 4.7. Could you please provide us a patch for IS 2014? Or is there any other workaround for this? What we have found, is that IS is generating an _isconfig.xml (c:\Users\abal\AppData\Local\Temp\{7EEBF761-FDBD-47C0-B393-ED7F18BB072C}\_isconfig.xml) with wrong .NET version, which is causing then the failure. Please take this as an urgent case as we are in the releasing phase of our software. Thanks, Attila Balazsy
