Article ID: 313498 - Last Review: January 25, 2006 - Revision: 3.3

BUG: Error 1619 when you install a package that uses Web Bootstrapper

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

This article was previously published under Q313498

Expand all | Collapse all

SYMPTOMS

When you install a Setup application built with Visual Studio .NET that is configured with the Web Bootstrapper settings, you may receive the following error message:

An error occurred installing the package. Windows Installer returned '1619'.

Back to the top

The method that the Windows Installer uses to download the file to the client is prone to a bug that causes the error. The Windows Installer finds that the content expiration date has expired and the installer prevents the setup from continuing.

Back to the top

RESOLUTION

To resolve this issue, follow these steps:

Disable Content Expiration.

Follow the steps that are appropriate for your environment.
Microsoft Windows XP
1. On the Start menu, click Run, type INETMGR, and then click OK.
2. Click to expand these nodes: <local computer>, Web Sites, and Default Web Site.
3. Right-click the Virtual Directory that contains the setup package, and then click Properties.
4. On the HTTP Headers tab, clear the Enable Content Expiration check box (the default value may have changed), and then click OK.
Microsoft Windows 2000
1. On the Start menu, click Run, type INETMGR, and then click OK.
2. Click to expand these nodes: <server name>, and Default Web Site.
3. Right-click the Virtual Directory that contains the setup package, and then click Properties.
4. On the HTTP Headers tab, clear the Enable Content Expiration check box (the default value may have changed), and then click OK.
Change the URL of the update.

After you update the Setup.exe file, do not replace the existing file with the new Setup.exe file. Instead, change the path of the new installation point by creating a subdirectory that identifies that release of the new installation, and then save the updated Setup.exe file in the subdirectory.NOTE: If an existing update contains the same URL as an earlier version, you can use the Windows Installer SDK tool, Msistuff.exe, to modify the URL and not rebuild the project. If the Setup project was signed, Msistuff.exe breaks the signing of the Setup.exe. You must use Signcode.exe to re-sign the package.

Back to the top

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

Back to the top

MORE INFORMATION

For more information and to download the Platform SDK Update, click the following link:

Platform SDK Update:
http://www.microsoft.com/msdownload/platformsdk/sdkupdate/default.htm?p=/msdownload/platformsdk/sdkupdate/SDKInfo.htm (http://www.microsoft.com/msdownload/platformsdk/sdkupdate/default.htm?p=/msdownload/platformsdk/sdkupdate/SDKInfo.htm)

In the Security dialog box, click No for more information, or click Yes to install and run the SDKUpdate ActiveX Control immediately.

Back to the top