Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. A Microsoft Application Virtualization MSI run from a mapped drive fails to install the virtual package

A Microsoft Application Virtualization MSI run from a mapped drive fails to install the virtual package

View products that this article applies to.

Symptoms

Consider the following scenario:

- You have created a Microsoft Application Virtualization (App-V) Virtual Package and placed the package contents on a network share. 
- You have mapped a drive to this network share.
- You attempt to install this Virtual Package by double clicking on the .MSI file located on the mapped drive.

In this scenario, the package begins to install then rolls back. No on screen errors are seen and the virtual package does not show in the list of virtual packages.

Additionally, in the Application Event logs you see the following MsiInstaller Event:

Log Name:      Application
Source:        MsiInstaller
Date:         
Event ID:      1033
Task Category: None
Level:         Information
Keywords:      Classic
User:          User1
Computer:      Computer1
Description:
Windows Installer installed the product. Product Name: My Virtual Package. Product Version: 1.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

↑ Back to the top

Cause

The mapped drive that holds the .MSI and the .APPV files is only available for access in the Users' own context, however the MSI Installation is done using the System context. The System context does not have the appropriate privileges to access the mapped drive.

↑ Back to the top

Resolution

Run the MSI directly from a network share (e.g. \\server\share\MyVirtualPackage.MSI) or copy the package to a local drive on the client computer.
Also ensure that the computer account (the computer you are logged into) also has access to the network share.

To test if the account has read access to the share, perform the following steps:

1. Download psexec from the SysInternals site at http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
2. Logon as a local administrator
3. Use the command psexec -s -i cmd.exe to open a command prompt under Local System
4. Perform a DIR of the content location from this window and verify that it succeeds

↑ Back to the top

Keywords: kb

↑ Back to the top

Article Info
Article ID : 2768954
Revision : 2
Created on : 3/27/2020
Published on : 3/27/2020
Exists online : False
Views : 447