Troubleshooting Application Virtualization Sequencer Issues
Updated: February 3, 2010
Applies To: Application Virtualization
This topic includes information that you can use to help troubleshoot general issues on the Application Virtualization (App-V) Sequencer.
Use the command line to generate a new .sft file. To create the .sft file by using the command line, enter the following at a command prompt:
mkdiffpkg.exe <base SFT file name> <diff SFT file name>
When you open a package for upgrade, you should specify the root Q:\ drive as the output location for the package. Do not specify an associated file name with the output location.
When you stream Microsoft Word 2003 to a client, an error is returned, but Microsoft Word continues to run.
Resequence the virtual application package and select Full Install .
When you create a dependent package by using active upgrade and add new registry entries, it appears to function correctly, but the updated registry entries are not available.
Registry settings are always stored with the original version of the package, so updates to the package will not appear to be available unless you repair the original package.
When you try to view detailed information associated with a Microsoft Office 2007 document by using the properties page, the detailed information is not visible.
App-V does not support the required shell extensions for these property pages.
In App-V 4.5, registry hooking has been moved from kernel mode to user mode. If you want to sequence a 16-bit application or an application that uses a 16-bit installer, you must first configure the sequencer computer so that the process runs in its own copy of the Windows NT Virtual DOS Machine (NTVDM).
Before you sequence the application, set the following global REGSZ registry key value to "yes" on the sequencing computer:
You must restart the computer before this takes effect.
You can learn more about MDOP in the TechNet Library, search for troubleshooting on the TechNet Wiki, or follow us on Facebook or Twitter.