Error Codes XXXXXX2A-00000003 or XXXXXX0A-0000000A when attempting to stream an application from a Microsoft Application Virtualization Management Server

Symptoms

You receive the following error when trying to launch or stream an application using the App-V client:

The Application Virtualization Client could not Launch <APPLICATION NAME>

The System Cannot Find the File Specified

Error Code: XXXXXX-XXXXXX2A-00000003

You may also see the following error:

Unexpected Error

Error Code: XXXXXX-XXXXXX0A-0000000A

Cause

This can easily happen if you use the wrong convention for specifying a UNC path as an HREF for the SFT file in the application’s OSD file.

Resolution

If you use the traditional format and not the proper HREF format for specifying a UNC path, the App-V client will error out. You will need to specify the FILE:// HREF prefix in front of the UNC path. For example, if the SFT file located in \\server\share\directory\application.sft path, you will need to specify the format as follows:

FILE://\\server\share\directory\application.sft

More Information

Please note: Specifying a UNC path using the traditional format (\\server\sharename\directory) for the ASR (ApplicationSourceRoot) OSR (OSDSourceRoot) and ISR (IconSourceRoot) is required for those three values per the documentation here:

http://technet.microsoft.com/en-us/library/cc843817.aspx

Properties

Article ID: 2641546 - Last Review: Nov 15, 2011 - Revision: 1

Microsoft Application Virtualization 4.5 for Terminal Services, Microsoft Application Virtualization 4.5 for Windows Desktops, Microsoft Application Virtualization 4.6 for Terminal Services, Microsoft Application Virtualization 4.6 for Terminal Services Service Pack 1, Microsoft Application Virtualization 4.6 for Windows Desktops, Microsoft Application Virtualization 4.6 for Windows Desktops Service Pack 1, Microsoft Application Virtualization for Remote Desktop Services, Microsoft Application Virtualization for Windows Desktops

Feedback