.NET Services Installation Issues from InstallShield 2009 MSI - Custom Action did not close 1 MSIHANDLEs
I am using InstallShield 2009 to create an MSI for a codebase that I have inherited. The code consists of VB6 and .NET 2.0 (C # and C ++). I am developing and installing on Windows XP SP2 .
I created an InstallShield project (name it "MyClient.ISM"
) by reversing its development from the MSI provided by the previous command. Their configurations are the same now.
Then I configured InstallShield to build the MSI. It was built without errors. However, when I try to start MSI, it fails with two
"Error 1001 InstallUtilLib.dll: Unknown error"
and then successfully undo the changes I made. Then I ran the command MyClient.MSI
using the msiexec command. For example.
msiexec /lvx C:\inst_server.log /i "C:\MyClient.MSI"
The problem seemed to be related to 2769 error
. Below are the locations of the errors from the following log files:
DEBUG: Error 2769: Custom Action _A11801EAD1E34CFF981127F7B95C3BE5.install
did not close 1 MSIHANDLEs.
This custom action was trying to install .NET services. So I switched to InstallShield and removed all custom actions (Install, Uninstall, Commit and Rollback, and its associated SetProperty) and installed and installed over and over again. This worked, but the services were no longer installed. Now I need to install these .NET Services using the InstallShield method that works.
source to share
I see this is an older question, but I thought I would give it a long time in case anyone needs help.
From what I've noticed, all 1001 errors are related to the .NET Framework.
First, I would make sure you create a setup.exe boot file with your msi. To do this, use the ReleaseShield Release Wizard and be sure to include the version of the .NET Framework that your application requires in the loader. Your test computer may not have a version of the .NET Framework installed.
The custom action you mentioned was autogenerated by InstallShield at build time. It has created custom wrapper actions to call methods on installer classes in your components. In your case, it was the .install method of one of your components' installer classes.
If you are confident that you are deploying the .NET Framework correctly and you still have an issue, consider debugging installer classes in an assembly. (More details here: http://www.hanselman.com/blog/BackToBasicsUsingFusionLogViewerToDebugObscureLoaderErrors.aspx )
source to share
I had error 1001, also in the base MSI InstallShield 2009 project. Try adding the auto-generated _isconfig.xml to the \ Language Independent node support files. This will ensure that the CLR starts correctly when it invokes a .NET-related action such as InstallerClass.
In my case, the contents of _isconfig.xml referenced the .NET 2.0 runtime, but could also reference 1.0 \ 1.1.
<?xml version="1.0"?>
<configuration>
<startup>
<supportedRuntime version="v2.0.50727"/>
</startup>
</configuration>
See also: Q108690: INFO: Consuming a Merge Module Creating Cith Microsoft Visual Studio .NET 2003 or 2005
source to share