Article ID: 979598 - View products that this article applies to.
After you sequence an application that uses the Microsoft Application Virtualization (App-V) Sequencer version 4.5 or a later version, you have the option of generating a Windows Installer package to publish the application. If you try to publish a Windows Installer package that is located on a network share, you may receive the following error message:
Additionally, the corresponding Sftlog.txt file contains several additional errors that have a result code (also known as rc) of xxxxxx2A-00000005. Also, the Windows Installer log file contains logs that resemble the following:
The Application Virtualization Client could not complete the operation.
The Application Virtualization Client is operating in disconnected mode and cannot perform the operation requested. Ensure that you can connect to the Application Virtualization Server, and then retry the operation. If the problem persists, report the following error code to your System Administrator.
Error code: xxxxxx-xxxxxx0A-000001D1
=== Logging stopped: date time === MSI (c) (3C:68) [11:53:01:145]: Note: 1: 1708 MSI (c) (3C:68) [11:53:01:145]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (3C:68) [11:53:01:145]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (3C:68) [11:53:01:145]: Product: msitest -- Installation failed.
This problem occurs because the Windows Installer service installs the Windows Installer package under the Local System context. Therefore, the Windows Installer commands are run under the context of the "NT AUTHORITY\SYSTEM" account.
Note The Windows Installer commands are a series of some sftmime commands.
If the "Domain\computername$" account does not have access to the network share or the Windows Installer package itself, the installation fails as expected.
Note When network access is necessary, the "NT AUTHORITY\System" account uses the "Domain\computername$" account to access the network.
To resolve this problem, use one of the following methods: