Error 1001 Occurs During Installation

[#1]

Summary

This article provides information regarding how to resolve the installation error 1001.

Synopsis

This information applies to the following InstallShield project types:

• Basic MSI
• InstallScript MSI

When the installer includes a .NET Installer Class, one of the following errors may occur during the installation:

• Error 1001.Exception occurred while initializing the installation: System.BadImageFormatException: The format of the file <filename> is invalid.
• Error 1001.InstallUtilLib.dll: Unknown error in CorBindToRuntimeHost (0x80131700).
• Error 1001.The specified service already exists

Discussion

For Errors:

• Error 1001.Exception occurred while initializing the installation
• Error 1001.InstallUtilLib.dll: Unknown error in CorBindToRuntimeHost (0x80131700).

This installation error can occur because the incorrect version of InstallUtilLib.dll has been streamed into the MSI package for the .NET Installer Class custom actions. InstallShield creates four custom actions for each component with ".NET Installer Class" set to "Yes." These are for the install, rollback, commit, and uninstall methods in the Installer Class.

Verify that the correct .NET versions of Regasm.exe and InstallUtilLib.dll have been specified in the Tools Menu - Options - .NET Tab. Also verify that this version of the .NET framework is currently installed on the build machine and will be installed on the target machine during or before the installation. The same .NET version should be specified for both files.

Note that this setting is a product wide setting, so it may be necessary to change the .NET version when working with a different installation project that installs files of a different .NET version.


For Error:

• Error 1001.The specified service already exists

This error will occur if the component installing a .NET Service is incorrectly configured with ".NET Installer Class" set to Yes.

The correct method to install a .NET Service is to use Component\Advanced Settings\Services view, not the ".NET Installer Class" setting. Making definitions in the Component\Advanced Settings\Services view creates entries in the Windows Installer ServiceControl and ServiceInstall Tables. These entries are used by the Windows Installer "InstallServices" action to install the Service.

If the install has already been deployed, then possible solutions are to:

• Uninstall and reinstall with the corrected Services configuration
• Perform a major upgrade that installs a renamed service in a new component that uses the Services configuration to. The old service will be removed during the RemoveExistingProducts action.