InstallShield 2019
Project • This information applies to the following project types:
| • | Basic MSI |
| • | DIM |
| • | InstallScript MSI |
| • | Merge Module |
| • | MSI Database |
| • | MSM Database |
| • | QuickPatch |
| • | Transform |
The following table contains a listing of Windows Installer errors that may occur during run time of an installation. The errors are related to the built-in InstallShield custom actions that are added automatically to InstallShield projects to support different functionality. For a list of the custom actions, see InstallShield Custom Action Reference.
Tip • You can find detailed information—including resolution information—on some of the run-time errors in the Knowledge Base.
|
Error Number |
Message |
Troubleshooting Information |
||||||||||||
|
This setup requires Internet Information Server for configuring IIS Virtual Roots. Please make sure that you have IIS installed. |
This error may occur if your project contains IIS data that you configured in the Internet Information Services view. If you encounter this error, ensure that the target system has IIS installed. |
|||||||||||||
|
This setup requires Administrator privileges for configuring IIS Virtual Roots. |
This error may occur if your project contains IIS data that you configured in the Internet Information Services view. This error occurs if you do not have administrator privileges for configuring IIS virtual directories, but you are running an installation that configures IIS virtual directories. |
|||||||||||||
|
Could not connect to [2] [3]. [4] |
This error may occur if your project contains a SQL connection that you configured in the SQL Scripts view. This error occurs if the installation was unable to connect to the specified database server. |
|||||||||||||
|
Error while retrieving version information from the specified database server. |
This error may occur if your project contains a SQL connection that you configured in the SQL Scripts view. This error occurs if you specified the minimum version requirement for a database server on the Requirements tab for a SQL connection in the SQL Scripts view, but the installation could not determine what version of the database server exists on the target system. |
|||||||||||||
|
The specified database server does not meet the version requirements. |
This error may occur if your project contains a SQL connection that you configured in the SQL Scripts view. This error occurs if the target system does not meet the minimum version requirements for a database server that is selected on the Requirements tab for a SQL connection in the SQL Scripts view. Note that in this scenario, this error occurs only if the Allow installation to continue when minimum requirements are not met check box on this tab is cleared. |
|||||||||||||
|
Fail to open a SQL script file. |
This error may occur if your project contains a SQL script that you configured in the SQL Scripts view, and the run time fails to extract the SQL script file from the .msi package. |
|||||||||||||
|
Error while executing a SQL script. |
This error may occur if your project contains a SQL script that you configured in the SQL Scripts view. This error occurs if the target database server encounters a SQL scripting error. To resolve this error, check the SQL script in your project and make any necessary changes. |
|||||||||||||
|
Browsing for SQL Servers requires that ODBC32.dll be installed and registered. |
This error may occur if your project contains a SQL connection that you configured in the SQL Scripts view. To prevent this error from occurring, add the InstallShield prerequisite for MDAC to your installation project. |
|||||||||||||
|
Error installing COM+ application [2]. [3] |
This error may occur if your project contains a COM+ application that you configured in the Component Services view. This error occurs if there are missing dependencies for COM+ component DLLs or incorrect settings for your COM+ application. To resolve this error, add the dependencies to your project or check the COM+ application in your project and make any necessary changes. |
|||||||||||||
|
Error uninstalling COM+ application [2]. [3] |
This error may occur if your project contains a COM+ application that you configured in the Component Services view. This error occurs if the run time fails to delete the COM+ application from the system. |
|||||||||||||
|
Error installing COM+ application [2]. Could not load Microsoft(R) .NET class libraries. Registering .NET serviced components requires that Microsoft(R) .NET Framework be installed. |
This error may occur if your project contains a COM+ application that you configured in the Component Services view. To prevent this error from occurring, consider adding the .NET Framework to your project. To learn how, see Adding .NET Framework Redistributables to Projects. As an alternative, you can use the Installation Requirements page in the Project Assistant to add a .NET Framework requirement to your project. If a target system does not have the appropriate version of the .NET Framework, the installation displays an error message, and the product is not installed. |
|||||||||||||
|
Could not execute SQL script file [2]. Connection not open: [3] |
This error may occur if your project contains a SQL script that you configured in the SQL Scripts view. This error occurs if the connection is disconnected before the installation runs the SQL script. |
|||||||||||||
|
This installation requires a Microsoft SQL Server. The specified server [3] is a Microsoft SQL Server Desktop Engine or SQL Server Express. |
This error may occur if your project contains a SQL connection that you configured in the SQL Scripts view. This error occurs if the target system has Microsoft SQL Server Desktop Engine or Microsoft SQL Server Express, and if the following check boxes are cleared on the Requirements tab for a SQL connection in the SQL Scripts view:
|
|||||||||||||
|
Error retrieving schema version from [2] [3]. Database: [4]. [5] |
This error may occur if your project contains a SQL script that you configured in the SQL Scripts view, and if a version is specified in the Schema Version setting on the General tab for that SQL script. This error occurs if the target database server encounters a SQL script error when the run time attempts to retrieve the current schema version from the InstallShield table. |
|||||||||||||
|
Error writing schema version to [2] [3]. Database: [4]. [5] |
This error may occur if your project contains a SQL script that you configured in the SQL Scripts view, and if a version is specified in the Schema Version setting on the General tab for that SQL script. This error occurs if the target database server encounters a SQL script error when the run time attempts to write a schema version to the InstallShield table. |
|||||||||||||
|
This installation requires Administrator privileges for installing COM+ applications. Log on as an administrator and then retry this installation. |
This error may occur if your project contains a COM+ application that you configured in the Component Services view. This error occurs if you do not have administrator privileges for installing COM+ applications, but you are running an installation that includes COM+ applications. |
|||||||||||||
|
Error updating XML file [2]. [3] |
This error may occur if your project contains XML references that you configured in the XML File Changes view. This error occurs if MSXML fails to save the target XML file. The [3] parameter refers to the error code that MSXML returned. Possible error codes are:
Other values that can occur indicate that a file system error occurred. |
|||||||||||||
|
Error opening XML file [2]. [3] |
This error may occur if your project contains XML references that you configured in the XML File Changes view. This error occurs if MSXML fails to load the target XML file. The [3] parameter refers to the error code that MSXML returned. A possible error codes is:
|
|||||||||||||
|
This setup requires MSXML 3.0 or higher for configuring XML files. Please make sure that you have version 3.0 or higher. |
This error may occur if your project contains XML references that you configured in the XML File Changes view. To prevent this error from occurring, consider using the Redistributables view to add an InstallShield prerequisite or merge module for MSXML to your project. |
|||||||||||||
|
Error loading NetApi32.DLL. The ISNetApi.dll needs to have NetApi32.DLL properly loaded and requires an NT based operating system. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if NetApi32.dll cannot be loaded on the target system. |
|||||||||||||
|
Server not found. Verify that the specified server exists. The server name can not be empty. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if you do not enter an existing domain or server name on the LogonInfoNameAndServer dialog or the LogonInformation dialog. |
|||||||||||||
|
Unspecified error from ISNetApi.dll. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if an unexpected error is returned from a function in NetApi32.dll. |
|||||||||||||
|
The buffer is too small. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if the run time cannot allocate the amount of memory that is required for retrieving a list of all servers that are visible in a domain. |
|||||||||||||
|
Access denied. Check administrative rights. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if the user does not have access to the Windows user account information that is being configured. |
|||||||||||||
|
Invalid computer. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if the computer name that was entered is invalid. |
|||||||||||||
|
Unhandled exception. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if one of the function calls in NetApi32.dll throws an exception. |
|||||||||||||
|
Invalid user name for this server or domain. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if you specify a user name that does not exist on a domain in the LogonInformation dialog or the LogonInfoNameAndServer dialog. |
|||||||||||||
|
The case-sensitive passwords do not match. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if you enter different passwords in the Password setting and the Confirm Password setting on the LogonInfoCreateUser dialog. |
|||||||||||||
|
The list is empty. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if the LogonInfoListServers dialog needs to be displayed but no servers are found. |
|||||||||||||
|
Access violation. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if a memory access violation is encountered when information about user accounts or servers is retrieved and being processed. |
|||||||||||||
|
Error getting group. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if the installation encounters an error when retrieving information about a group account. |
|||||||||||||
|
Error adding user to group. Verify that the group exists for this domain or server. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if you try adding membership of a user account to a group but the account type is invalid, the member is already a member of the group, or the member does not exist. |
|||||||||||||
|
Error creating user. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if the installation encounters a problem when creating the user account or adding the user to a group. |
|||||||||||||
|
ERROR_NETAPI_ERROR_NOT_PRIMARY returned from NetAPI. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if you are trying to add a user account, give an existing user account membership, or delete a user account, but the operation is allowed only on the primary domain controller of the domain. |
|||||||||||||
|
The specified user already exists. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if you are trying to create a new user account but the user account already exists. |
|||||||||||||
|
The specified group already exists. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if you are trying to create a new user account but the group already exists. |
|||||||||||||
|
Invalid password. Verify that the password is in accordance with your network password policy. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if you are creating a new user account but the password that you specified does not meet the password requirements that were established for the network. To resolve this error, enter an appropriate password. |
|||||||||||||
|
Invalid name. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if you are giving an existing user account membership in a group, or if you are deleting a user account, but the user name that you specified could not be found. |
|||||||||||||
|
Invalid group. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if you are giving a user account membership in a group, but the group that you specified does not exist. |
|||||||||||||
|
The user name can not be empty and must be in the format DOMAIN\Username. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if you are configuring a user account but you did not enter valid information for the User Name setting. |
|||||||||||||
|
Error loading or creating INI file in the user TEMP directory. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if there is a problem opening or creating a configuration .ini file that the InstallShield custom actions use for the creation or configuration of a Windows user account. |
|||||||||||||
|
Error deleting INI file containing new user information from the user's TEMP directory. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if there is a problem deleting the configuration .ini file that the InstallShield custom actions use for the creation or configuration of a Windows user account. |
|||||||||||||
|
Error getting the primary domain controller (PDC). |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if the domain controller for the specified domain could not be found. |
|||||||||||||
|
Every field must have a value in order to create a user. |
This error may occur if you added to your project the ability to create or set a Windows user account. The error occurs if one of the settings on the LogonInfoCreateUser dialog is left blank. |
|||||||||||||
|
ODBC driver for [2] not found. This is required to connect to [2] database servers. |
This error may occur if your project contains a SQL connection that you configured in the SQL Scripts view. This error occurs if the ODBC driver that is associated with the SQL connection does not exist on the target system. To prevent this error from occurring, consider creating an InstallShield prerequisite that installs the driver, and add the prerequisite to your project. |
|||||||||||||
|
Error creating database [4]. Server: [2] [3]. [5] |
This error may occur if your project contains a SQL connection that you configured in the SQL Scripts view, and if the Create Catalog If Absent check box on the General tab for the connection is selected. This error occurs if the target database server encounters a SQL scripting error when creating the database catalog that is specified in the Catalog Name setting on the General tab for a SQL connection in the SQL Scripts view. |
|||||||||||||
|
Error connecting to database [4]. Server: [2] [3]. [5] |
This error may occur if your project contains a SQL connection that you configured in the SQL Scripts view. This error occurs if the target database server encounters a SQL scripting error when connecting to the database catalog that is specified in the Catalog Name setting on the General tab for a SQL connection in the SQL Scripts view. |
|||||||||||||
|
Error attempting to open connection [2]. No valid database metadata associated with this connection. |
This error may occur if your project contains a SQL connection that you configured in the SQL Scripts view. This error occurs if the connection is associated with no valid database metadata. To prevent this error from occurring, check the ISSQLConnectionDBServer table in the Direct Editor view, and make any necessary changes. |
|||||||||||||
|
Error attempting to apply permissions to object [2]. System error: [3] ([4]) |
This error may occur if you used the custom InstallShield handling for securing files, folders, or registry keys in your project. To learn more about this functionality, see Securing Files, Folders, Registry Keys, and Windows Services in a Locked-Down Environment. |
InstallShield 2019 Help LibraryApril 2019 |
Copyright Information | Flexera |