Windows Installer Error Messages Part 1

Windows Installer errors have an error code of 1000 or greater. The error codes numbered 1000 to 1999 are ship errors and must be authored into the Error table or http://msdn.microsoft.com/en-us/library/aa368554%28VS.85%29.aspx. The error codes numbered greater than 2000 are internal errors and do not have authored strings, but these can occur if the installation package has been incorrectly authored. For a list of reserved error codes, see Error table.

Note  If you are a user experiencing difficulty with your computer either during or after installing or uninstalling an application, you should contact customer support for the software you are trying to install or remove. If you feel you are in need of support for a Microsoft product, please go to our technical support site at support.microsoft.com.

Note  You can search for solutions to many of the messages in the following table in the Microsoft Support Knowledge Base (KB). Go to the Search the Support Knowledge Base page and use the tool provided there to perform a search for a specific Windows Installer error message. Select "Search Product: All Products" to perform a comprehensive search for the message. In the "For:" pane, enter a character string like the following, with quotes enclosing the words Windows Installer, the appropriate Message Code value from the following table, and the keyword "kberrmsg".

"Windows Installer" Message Code kberrmsg

Note  If you are viewing this documentation using the online MSDN library, you can also check the Community Content area at the bottom of this page to see whether any solutions for specific error messages have been contributed.

Developers of installation packages can also test the internal consistency of their packages by using Internal Consistency Evaluators. For more information, see Internal Consistency Evaluators – ICEs.

See also the Error Codes returned by the Windows Installer functions MsiExec.exe and InstMsi.exe.

Message Code Message Remarks

1101

Could not open file stream: [2]. System error: [3]

 

1301

Cannot create the file ‘[2]’. A directory with this name already exists.

 

1302

Please insert the disk: [2]

 

1303

The Installer has insufficient privileges to access this directory: [2].

 

1304

Error writing to File: [2]

 

1305

Error reading from File: [2]; System error code: [3]

 

1306

The file ‘[2]’ is in use. If you can, please close the application that is using the file, then click Retry.

A system restart may be required because a file being updated is also currently in use. For more information, see System Reboots.

1307

There is not enough disk space remaining to install this file: [2]. If you can, free up some disk space, and click Retry, or click Cancel to exit.

 

1308

Source file not found: [2]

 

1309

Error attempting to open the source file: [3]. System error code: [2]

 

1310

Error attempting to create the destination file: [3]. System error code: [2]

 

1311

Could not locate source file cabinet: [2].

 

1312

Cannot create the directory ‘[2]’. A file with this name already exists. Please rename or remove the file and click Retry, or click Cancel to exit.

 

1313

The volume [2] is currently unavailable. Please select another.

 

1314

The specified path ‘[2]’ is unavailable.

 

1315

Unable to write to the specified folder: [2].

 

1316

A network error occurred while attempting to read from the file: [2]

 

1317

An error occurred while attempting to create the directory: [2]

 

1318

A network error occurred while attempting to create the directory: [2]

 

1319

A network error occurred while attempting to open the source file cabinet: [2].

 

1320

The specified path is too long: ‘[2]’

 

1321

The Installer has insufficient privileges to modify this file: [2].

 

1322

A portion of the folder path ‘[2]’ is invalid. It is either empty or exceeds the length allowed by the system.

 

1323

The folder path ‘[2]’ contains words that are not valid in folder paths.

 

1324

The folder path ‘[2]’ contains an invalid character.

 

1325

‘[2]’ is not a valid short file name.

 

1326

Error getting file security: [3] GetLastError: [2]

 

1327

Invalid Drive: [2]

 

1328

Error applying patch to file [2]. It has probably been updated by other means, and can no longer be modified by this patch. For more information, contact your patch vendor. System Error: [3]

 

1329

A file that is required cannot be installed because the cabinet file [2] is not digitally signed. This may indicate that the cabinet file is corrupt.

 

1330

A file that is required cannot be installed because the cabinet file [2] has an invalid digital signature. This may indicate that the cabinet file is corrupt.{ Error [3] was returned by WinVerifyTrust.}

 

1331

Failed to correctly copy [2] file: CRC error.

 

1332

Failed to correctly move [2] file: CRC error.

 

1333

Failed to correctly patch [2] file: CRC error.

 

1334

The file ‘[2]’ cannot be installed because the file cannot be found in cabinet file ‘[3]’. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.

 

1335

The cabinet file ‘[2]’ required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.

 

1336

There was an error creating a temporary file that is needed to complete this installation. Folder: [3]. System error code: [2]

 

1401

Could not create key: [2]. System error [3].

 

1402

Could not open key: [2]. System error [3].

 

1403

Could not delete value [2] from key [3]. System error [4].

 

1404

Could not delete key [2]. System error [3].

 

1405

Could not read value [2] from key [3]. System error [4].

 

1406

Could not write value [2] to key [3]. System error [4].

 

1407

Could not get value names for key [2]. System error [3].

 

1408

Could not get sub key names for key [2]. System error [3].

 

1409

Could not read security information for key [2]. System error [3].

 

1410

Could not increase the available registry space. [2] KB of free registry space is required for the installation of this application.

 

1500

Another installation is in progress. You must complete that installation before continuing this one.

Test packages in high-traffic environments where users request the installation of many applications. For more information, see _MSIExecute Mutex.

1501

Error accessing secured data. Please make sure the Windows Installer is configured properly and try the install again.

 

1502

User ‘[2]’ has previously initiated an install for product ‘[3]’. That user will need to run that install again before they can use that product. Your current install will now continue.

Test packages in high-traffic environments where users request the installation of many applications. For more information, see _MSIExecute Mutex.

1503

User ‘[2]’ has previously initiated an install for product ‘[3]’. That user will need to run that install again before they can use that product.

Test packages in high-traffic environments where users request the installation of many applications. For more information, see _MSIExecute Mutex.

1601

Out of disk space — Volume: ‘[2]’; required space: [3] KB; available space: [4] KB

Ensure that the custom action costs do not exceed available space.

1602

Are you sure you want to cancel?

 

1603

The file [2][3] is being held in use by the following process: Name: [4], Id: [5], Window Title: ‘[6]’.

A system restart may be required because the file being updated is also currently in use. Users may be given the opportunity to avoid some system restarts by using the FilesInUse Dialog or the MsiRMFilesInUse Dialog. For more information, see System Reboots and Logging of Reboot Requests.

1604

The product ‘[2]’ is already installed, and has prevented the installation of this product.

 

1605

Out of disk space — Volume: ‘[2]’; required space: [3] KB; available space: [4] KB. If rollback is disabled, enough space is available. Click Cancel to quit, Retry to check available disk space again, or Ignore to continue without rollback.

Ensure that the custom action costs do not exceed the available space.

1606

Could not access location [2].

Do not list directories in the Directory table which are not used by the installation.

Rarely, this message is due to the issue discussed by KB886549.

1607

The following applications should be closed before continuing the install:

A system restart may be required because a file that is being updated is also currently in use. Users may be given the opportunity to avoid some system restarts by selecting to close some applications. For more information, see System Reboots.

1608

Could not find any previously installed compliant products on the machine for installing this product

No file listed in the CCPSearch table can be found on the user’s computer.

1609

An error occurred while applying security settings. [2] is not a valid user or group. This could be a problem with the package, or a problem connecting to a domain controller on the network. Check your network connection and click Retry, or Cancel to end the install. Unable to locate the user’s SID, system error [3]

 

1610

The setup must update files or services that cannot be updated while the system is running. If you choose to continue, a reboot will be required to complete the setup.

Available in Windows Installer version 4.0.

1611

The setup was unable to automatically close all requested applications. Please ensure that the applications holding files in use are closed before continuing with the installation.

Available in Windows Installer version 4.0.

1651

Admin user failed to apply patch for a per-user managed or a per-machine application which is in advertise state.

Available in Windows Installer version 3.0.

1701

[2] is not a valid entry for a product ID.

 

1702

Configuring [2] cannot be completed until you restart your system. To restart now and resume configuration click Yes, or click No to stop this configuration.

A scheduled system restart message. For more information, see System Reboots and ScheduleReboot Action. This message may be customized using the Error table.

1703

For the configuration changes made to [2] to take effect you must restart your system. To restart now click Yes, or click No if you plan to manually restart at a later time.

The scheduled system restart message when no other users are logged on the computer. For more information, see System Reboots and ScheduleReboot Action. This message may be customized using the Error table.

1704

An install for [2] is currently suspended. You must undo the changes made by that install to continue. Do you want to undo those changes?

 

1705

A previous install for this product is in progress. You must undo the changes made by that install to continue. Do you want to undo those changes?

 

1706

No valid source could be found for product [2].

 

1707

Installation operation completed successfully.

 

1708

Installation operation failed.

 

1709

Product: [2] — [3]

 

1710

You may either restore your computer to its previous state or continue the install later. Would you like to restore?

 

1711

An error occurred while writing installation information to disk. Check to make sure enough disk space is available, and click Retry, or Cancel to end the install.

 

1712

One or more of the files required to restore your computer to its previous state could not be found. Restoration will not be possible.

 

1713

[2] cannot install one of its required products. Contact your technical support group. System Error: [3].

 

1714

The older version of [2] cannot be removed. Contact your technical support group. System Error [3].

 

1715

Installed [2].

 

1716

Configured [2].

 

1717

Removed [2].

 

1718

File [2] was rejected by digital signature policy.

A very large installation may cause the operating system to run out of memory.

1719

Windows Installer service could not be accessed. Contact your support personnel to verify that it is properly registered and enabled.

 

1720

There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor. Custom action [2] script error [3], [4]: [5] Line [6], Column [7], [8]

 

1721

There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: [2], location: [3], command: [4]

 

1722

There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action [2], location: [3], command: [4]

 

1723

There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action [2], entry: [3], library: [4]

Ensure that the functions used by custom actions are actually exported. For more information about custom actions based upon a DLL, see Dynamic-Link Libraries.

1724

Removal completed successfully.

 

1725

Removal failed.

 

1726

Advertisement completed successfully.

 

1727

Advertisement failed.

 

1728

Configuration completed successfully.

 

1729

Configuration failed.

 

1730

You must be an Administrator to remove this application. To remove this application, you can log on as an administrator, or contact your technical support group for assistance.

 

1731

The source installation package for the product [2] is out of sync with the client package. Try the installation again using a valid copy of the installation package ‘[3]’.

Available beginning with Windows Installer for Windows Server 2003.

1732

In order to complete the installation of [2], you must restart the computer. Other users are currently logged on to this computer, and restarting may cause them to lose their work. Do you want to restart now?

The scheduled system restart message when other users are logged on the computer. For more information, see System Reboots and ScheduleReboot Action. This message may be customized using the Error table.

Available beginning with Windows Installer for Windows Server 2003.

1801

The path [2] is not valid

 

1802

Out of memory

 

1803

There is no disk in drive [2]. Please, insert one and click Retry, or click Cancel to go back to the previously selected volume.

 

1804

There is no disk in drive [2]. Please, insert one and click Retry, or click Cancel to return to the browse dialog and select a different volume.

 

1805

The path [2] does not exist

 

1806

You have insufficient privileges to read this folder.

 

1807

A valid destination folder for the install could not be determined.

 

1901

Error attempting to read from the source install database: [2]

 

1902

Scheduling restart operation: Renaming file [2] to [3]. Must restart to complete operation.

An file being updated by the installation is currently in use. Windows Installer renames the file to update it and removes the old version at the next restart of the system.

1903

Scheduling restart operation: Deleting file [2]. Must restart to complete operation.

A system restart may be required because the file that is being updated is also currently in use. Users may be given the opportunity to avoid some system restarts by using the FilesInUse Dialog or MsiRMFilesInUse Dialog. For more information, see System Reboots and Logging of Reboot Requests.

1904

Module [2] failed to register. HRESULT [3].

 

1905

Module [2] failed to unregister. HRESULT [3].

 

1906

Failed to cache package [2]. Error: [3]

 

1907

Could not register font [2]. Verify that you have sufficient permissions to install fonts, and that the system supports this font.

 

1908

Could not unregister font [2]. Verify that you have sufficient permissions to remove fonts.

 

1909

Could not create shortcut [2]. Verify that the destination folder exists and that you can access it.

 

1910

Could not remove shortcut [2]. Verify that the shortcut file exists and that you can access it.

 

1911

Could not register type library for file [2]. Contact your support personnel.

Error loading a type library or DLL.

1912

Could not unregister type library for file [2]. Contact your support personnel.

Error loading a type library or DLL.

1913

Could not update the .ini file [2][3]. Verify that the file exists and that you can access it.

 

1914

Could not schedule file [2] to replace file [3] on restart. Verify that you have write permissions to file [3].

 

1915

Error removing ODBC driver manager, ODBC error [2]: [3]. Contact your support personnel.

 

1916

Error installing ODBC driver manager, ODBC error [2]: [3]. Contact your support personnel.

 

1917

Error removing ODBC driver: [4], ODBC error [2]: [3]. Verify that you have sufficient privileges to remove ODBC drivers.

 

1918

Error installing ODBC driver: [4], ODBC error [2]: [3]. Verify that the file [4] exists and that you can access it.

 

1919

Error configuring ODBC data source: [4], ODBC error [2]: [3]. Verify that the file [4] exists and that you can access it.

 

1920

Service ‘[2]’ ([3]) failed to start. Verify that you have sufficient privileges to start system services.

 

1921

Service ‘[2]’ ([3]) could not be stopped. Verify that you have sufficient privileges to stop system services.

 

1922

Service ‘[2]’ ([3]) could not be deleted. Verify that you have sufficient privileges to remove system services.

 

1923

Service ‘[2]’ ([3]) could not be installed. Verify that you have sufficient privileges to install system services.

 

1924

Could not update environment variable ‘[2]’. Verify that you have sufficient privileges to modify environment variables.

 

1925

You do not have sufficient privileges to complete this installation for all users of the machine. Log on as administrator and then retry this installation.

 

1926

Could not set file security for file ‘[3]’. Error: [2]. Verify that you have sufficient privileges to modify the security permissions for this file.

 

1927

The installation requires COM+ Services to be installed.

 

1928

The installation failed to install the COM+ Application.

 

1929

The installation failed to remove the COM+ Application.

 

1930

The description for service ‘[2]’ ([3]) could not be changed.

 

1931

The Windows Installer service cannot update the system file [2] because the file is protected by Windows. You may need to update your operating system for this program to work correctly. Package version: [3], OS Protected version: [4]

Windows Installer protects critical system files. For more information, see Using Windows Installer and Windows Resource Protection. For Windows Me, see the InstallSFPCatalogFile action, the FileSFPCatalog table, and the SFPCatalog table.

1932

The Windows Installer service cannot update the protected Windows file [2]. Package version: [3], OS Protected version: [4], SFP Error: [5]

Windows Installer protects critical system files. For more information, see Using Windows Installer and Windows Resource Protection. For Windows Me, see the InstallSFPCatalogFile action, the FileSFPCatalog table, and the SFPCatalog table.

1933

The Windows Installer service cannot update one or more protected Windows files. SFP Error: [2]. List of protected files:\r\n[3]

Windows Installer protects critical system files. For more information, see Using Windows Installer and Windows Resource Protection. For Windows Me, see the InstallSFPCatalogFile action, the FileSFPCatalog table, and the SFPCatalog table.

1934

User installations are disabled through policy on the machine.

 

1935

An error occurred during the installation of assembly component [2]. HRESULT: [3]. {{assembly interface: [4], function: [5], assembly name: [6]}}

For more information, see Assemblies.

Help and Support may have published a KB article that discusses the installation of this assembly. Go to the Search the Support Knowledge Base page and search for articles that discuss this Windows Installer error message.

1935

An error occurred during the installation of assembly ‘[6]’. Please refer to Help and Support for more information. HRESULT: [3]. {{assembly interface: [4], function: [5], component: [2]}}

For more information, see Assemblies.

Help and Support may have published a KB article that discusses the installation of this assembly. Go to the Search the Support Knowledge Base page and search for articles that discuss this Windows Installer error message.

Available beginning with Windows Installer for Windows Server 2003.

1936

An error occurred during the installation of assembly ‘[6]’. The assembly is not strongly named or is not signed with the minimal key length. HRESULT: [3]. {{assembly interface: [4], function: [5], component: [2]}}

For more information, see Assemblies.

Help and Support may have published a KB article that discusses the installation of this assembly. Go to the Search the Support Knowledge Base page and search for articles that discuss this Windows Installer error message.

Available beginning with Windows Installer for Windows Server 2003.

1937

An error occurred during the installation of assembly ‘[6]’. The signature or catalog could not be verified or is not valid. HRESULT: [3]. {{assembly interface: [4], function: [5], component: [2]}}

For more information, see Assemblies.

Help and Support may have published a KB article that discusses the installation of this assembly. Go to the Search the Support Knowledge Base page and search for articles that discuss this Windows Installer error message.

Available beginning with Windows Installer for Windows Server 2003.

1938

An error occurred during the installation of assembly ‘[6]’. One or more modules of the assembly could not be found. HRESULT: [3]. {{assembly interface: [4], function: [5], component: [2]}}

For more information, see Assemblies.

Help and Support may have published a KB article that discusses the installation of this assembly. Go to the Search the Support Knowledge Base page and search for articles that discuss this Windows Installer error message.

Available beginning with Windows Installer for Windows Server 2003.

1939

Service ‘[2]’ ([3]) could not be configured. This could be a problem with the package or your permissions. Verify that you have sufficient privileges to configure system services.

For information, seeUsing Services Configuration.

Available beginning with Windows Installer 5.0 for Windows 7 and Windows Server 2008 R2.

1940

Service ‘[2]’ ([3]) could not be configured. Configuring services is supported only on Windows Vista/Server 2008 and above.

For information, seeUsing Services Configuration.

Available beginning with Windows Installer 5.0 for Windows 7 and Windows Server 2008 R2.

1941

Both LockPermissions and MsiLockPermissionsEx tables were found in the package. Only one of them should be present. This is a problem with the package.

A package cannot contain both the MsiLockPermissionsEx Table and the LockPermissions Table.

Available beginning with Windows Installer 5.0 for Windows 7 and Windows Server 2008 R2.

1942

Multiple conditions (‘[2]’ and ‘[3]’)have resolved to true while installing Object [4] (from table [5]). This may be a problem with the package.

Available beginning with Windows Installer 5.0 for Windows 7 and Windows Server 2008 R2.

1943

SDDL string ‘[2]’ for object [3](in table [4]) could not be resolved into a valid Security Descriptor.

See Securing Resources for information on using MsiLockPermissionsEx table.

Available beginning with Windows Installer 5.0 for Windows 7 and Windows Server 2008 R2.

1944

Could not set security for service ‘[3]’. Error: [2]. Verify that you have sufficient privileges to modify the security permissions for this service.

Available beginning with Windows Installer 5.0 for Windows 7 and Windows Server 2008 R2.

1945

You do not have sufficient privileges to complete the re-advertisement of this product. Re-advertisement requires initiation by a local system account calling the MsiAdvertiseScript API

The process calling MsiAdvertiseScript must be running under the LocalSystem account.

Available beginning with Windows Installer 5.0 for Windows 7 and Windows Server 2008 R2.

Message Codes from 2000-3002

Advertisements

About oleggap

IT Pro
This entry was posted in Reference. Bookmark the permalink.