Troubleshooting the Application Virtualization Sequencer
Updated: December 1, 2008
Applies To: Application Virtualization
This topic includes information that you can use to help troubleshoot general issues on the Application Virtualization (App-V) Sequencer.
The version number associated with an SFTD file increases unexpectedly.
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>
After you upgrade an existing package, the file name is not correct.
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 package 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 sequence a package that requires .NET 2.0, you get an error.
Sequencing packages that require .NET 2.0 is not supported.
You can learn more about MDOP in the TechNet Library, search for troubleshooting on the TechNet Wiki, or follow us on Facebook or Twitter.