Article ID: 889710 - Last Review: March 11, 2010 - Revision: 2.0

You receive a "This installation package could not be opened" error message when you try to install a Windows Installer-based program in Windows Server 2003

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.

Expand all | Collapse all

SYMPTOMS

When you try to install a Windows Installer-based program (.msi) on a Microsoft Windows Server 2003-based domain controller, you receive the following error message in a Windows Installer dialog box:

This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package.

Additionally, if you turn on verbose logging for Windows Installer, an error message that is similar to the following may appear in the Windows Installer log file:

Verbose logging started: 26-10-2004 10:50:42
Build type: SHIP UNICODE 2.00.2600.1168
Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (0C:B4): Resetting cached policy values MSI (c) (0C:B4): Machine policy value 'Debug' is 0 MSI (c) (0C:B4): ******* RunEngine: *******
Product: \\ComputerName\sysvol\DomainName.com\msi\SMSClient\ProgramName.msi
******* Action: ******* CommandLine: ********** MSI (c) (0C:B4): Note: 1: 2203 2: \\ComputerName\sysvol\DomainName.com\msi\SMSClient\ProgramName.msi 3: -2147287035 MSI (c) (0C:B4): MainEngineThread is returning 1619
=== Verbose logging stopped: 26-10-2004 10:50:42 ===
On the network you see an access denied:
SMB: C lock & X, FID = 0x800d, Locks = 1 (0x7FFFFF92 for 0x00000001)
SMB: R lock & X - NT error, System, Error, Code = (34) STATUS_ACCESS_DENIED

Note ProgramName.msi is the name of the Windows Installer program.

Back to the top

CAUSE

This behavior occurs when you try to install a program, and the program's installation files are located in the Sysvol folder.

By default, the Net Logon service in Windows Server 2003 creates the Svsvol folder with the SHI1005_FLAGS_RESTRICT_EXCLUSIVE_OPENS attribute. Therefore, the Sysvol folder cannot be exclusively locked. This behavior prevents Active Directory directory service synchronization problems. We recommend that you do not use the Sysvol folder as an installation point for programs.

Back to the top

STATUS

This behavior is by design.

Back to the top

MORE INFORMATION

For more information about the SHI1005_FLAGS_RESTRICT_EXCLUSIVE_OPENS flag, visit the following Microsoft Web site:

http://msdn2.microsoft.com/en-us/library/aa380975.aspx (http://msdn2.microsoft.com/en-us/library/aa380975.aspx)

For additional information about how to enable Windows Installer logging in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:

314852 (http://support.microsoft.com/kb/314852/ ) How to enable Windows Installer logging in Windows XP

Back to the top