Creating a Package Accelerator from some applications may fail in Microsoft App-V 4.6 SP1

Article ID: 2496852 - View products that this article applies to.
Expand all | Collapse all


Creating a Package Accelerator from some applications, such as Visual Studio 2008, may fail in Microsoft Application Virtualization 4.6 SP1 when the code that creates the CAB file hits a max path issue.


Windows has a maximum path length limitation of 256 characters and this issue can occur when this limit is exceeded. For example, when sequencing Microsoft Visual Studio 2008 to "Q:\Visual Studio 2008", the additional characters added in the Package Accelerator process exceeds the maximum path length. This path specifically causes the Visual Studio 2008 Package Acclerator creation to fail:

Q:\tfm\pc\Visual Studio 2008\VFS\CSIDL_WINDOWS\Microsoft.Net\assembly\GAC_32\Policy.10.2.Microsoft.TeamFoundation.WorkItemTracking.Client.RuleEngine\v4.0_10.0.0.0__b03f5f7f11d50a3a\Policy.10.2.Microsoft.TeamFoundation.WorkItemTracking.Client.RuleEngine.dll.config


Sequencing to a shorter package root, such as "VS2008", should resolve the issue and allow the Package Accelerator to be created.

NOTE: This only applies to creating Package Accelerators


Maximum path length limitation
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.


Article ID: 2496852 - Last Review: March 21, 2011 - Revision: 4.0
  • Microsoft Application Virtualization 4.6 Sequencer
  • Microsoft Visual Studio 2010 Premium
  • Microsoft Visual Studio 2010 Professional

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from