The best practices and the troubleshooting information for the MSI Utility for Microsoft Application Virtualization

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

On This Page

INTRODUCTION

This article describes the best practices and the troubleshooting information for the MSI Utility for Microsoft Application Virtualization (MSI Utility). This article also describes the error messages that you may receive when you run the MSI Utility in an interactive session and in a noninteractive session.

MORE INFORMATION

The MSI Utility is a tool that extends virtualized software installation in certain key scenarios. In scenarios in which you do not have a computer that is running Microsoft System Center Virtual Application Server, the MSI Utility allows for the delivery of sequenced applications directly to systems that are running Microsoft SoftGrid Application Virtualization for Desktops and Microsoft SoftGrid Application Virtualization for Terminal Services.

Best practices

The recommended best practices for using the MSI Utility are as follows:
  • When you use the MSI Utility to bundle virtualized applications, the user context that generates the virtualized application .msi files requires permissions to write to the directory in which the .sprj files are located. Additionally, you must put all the following required files together with the .sprj file in one directory in the output format that the SoftGrid Application Virtualization Sequencer creates:
    • The required files for the virtualized application
    • The required files for the .osd file
    • The required files for the icons directory
    • The required files for the .sft file
    You cannot create virtualized applications from sequenced packages that were copied to Virtual Application Server if the .osd files were modified from the original content.
  • Although the MSI Utility enables application virtualization on systems without access to a computer that is running System Center Virtual Application Server, there are certain limitations to the flexibility of this solution. When you manage virtualized applications by using System Center Virtual Application Server, you can dynamically change the application settings. Examples of the application settings are the file type associations and the shortcuts. Additionally, the application settings are implemented the next time that you start the virtualized application. The MSI Utility takes a point-in-time snapshot of the application settings that are configured in the .osd file when the application bundle is created. You can change the file type associations and the shortcuts. But, you must update the application bundle to incorporate the changes and to install the upgrade on the client computers. You can simplify the deployment process by making sure that the appropriate file type associations and the appropriate shortcuts are in place before the distribution.
  • If you want SoftGrid Application Virtualization for Desktops to support virtualized software installation by using virtualized application .msi files, SoftGrid Application Virtualization for Desktops must operate in stand-alone mode. Additionally, each client computer must have a local copy of the complete virtualized application. You must make sure that the disk space is sufficient and that the SoftGrid Application Virtualization for Desktops file system cache is large enough for the whole virtualized application. When SoftGrid streams the virtualized applications that are segmented into Feature Block 1 (FB1) and Feature Block 2 (FB2), the file system cache requires only the application bits that are used on the client computer. However, the complete virtualized application must be cached on each client computer when SoftGrid Application Virtualization for Desktops operates in stand-alone mode. When you distribute a virtualized application, disk space is also required for the following files:
    • The virtualized application .msi file
    • The .sft file
    • The .msi temporary files that were used during the installation
  • When the virtualized application .msi file is generated, the settings in the .osd file for the virtualized application are embedded in the virtualized application .msi file. The .osd file includes a setting that is named the OS tag. This setting contains information about the operating systems that can run the virtualized application. If you try to install the virtualized application in an operating system that is not in the OS tag in the .osd file, the virtualized application .msi file is not imported. Additionally, you receive an error message that resembles the following:
    Error code: 07708044-00000007
    Error adding application <name of application>
    Note For more information about the error message that you receive, view the Sftlog.txt file that is located in the client installation folder. By default, the path of the Sftlog.txt file is as follows:
    C:\Program Files\Softricity\SoftGrid for Windows Desktops

Troubleshooting information

This section describes the troubleshooting information for the MSI Utility and for the virtualized application .msi file.

Troubleshooting the MSI Utility

When you run the MSI Utility in an interactive session, you may receive an error message that resembles the following:
SoftGrid MSI Packager Error.
Unable to locate icons in
C:\\Users\User\Documents\docs\prjl2_vis_4.2.O.235 -
Copy\prjl2_vis_4.2.O.235 Icons\*.ico, The system cannot find the path specified.
No icons will be packaged in the MSI.
The MSI Utility provides additional information about the error message in a log file. The MSI Utility writes diagnostic information to a log file that is named the Msipack.log file. The Msipack.log file is located in the %TEMP% folder.

The entries that are logged in the Msipack.log file resemble the following:
-------- Start processing
C:\Users\User\Documents\docs\prj12_vis_4.2.0.235 – 
Copy\prj12_vis_4.2.0.235.sprj --------
[11/26/2007 14:53:41] Parsing sequencer project file C:\Users\User\Documents\docs\prj12_vis_4.2.0.235 – 
Copy\prj12_vis_4.2.0.235.sprj
[11/26/2007 14:53:43] Unable to locate icons in C:\\Users\User\Documents\docs\prj12_vis_4.2.0.235 –
Copy\prj12_vis_4.2.0.235 Icons\*.ico, The system cannot find the path specified.
No icons will be packaged in the MSI.
[11/26/2007 14:53:43] SoftGrid MSI Packager Error. 
Unable to locate icons in C:\\Users\User\Documents\docs\prj12_vis_4.2.0.235 - Copy\prj12_vis_4.2.0.235 Icons\*.ico, The system cannot find the path specified.
No icons will be packaged in the MSI.

Troubleshooting the virtualized application .msi file

You can run the virtualized application .msi file in an interactive session or in a noninteractive session. In an interactive session, any issue that you experience generates an error message. For example, if the SoftGrid client is not installed on the computer and if you try to run the virtualized application .msi file, you receive an error message that resembles the following:
The Microsoft SoftGrid client is not installed on this system. Please install SoftGrid before proceeding.
If you experience any issues when you run the virtualized application .msi file in a noninteractive session, you may receive the following error message:
ERROR_INSTALL_FAILURE
In this case, you must examine the log file that is generated for the virtualized application .msi file to learn more about the issue. For example, to run a virtualized application .msi file that is named the Project.msi file, run the following command at the command prompt:
msiexec.exe /i project.msi /q /log log.txt
Note In this command, you use the /q option to install the virtualized application .msi file in silent mode. You use the /log option to create a log file for the virtualized application .msi file. Or, you can use the /lv option instead of the /log option to enable verbose logging.

If the SoftGrid client is not installed on the computer, the entries that are logged in the log file resemble the following:
Action start 16:25:05: LaunchConditions.
MSI (s) (80:CC) [16:25:05:047]: Product: prj12_vis_4.2.0.235 -- The Microsoft SoftGrid client is not installed on this system.  Please install SoftGrid before proceeding.
The Microsoft SoftGrid client is not installed on this system.  Please install SoftGrid before proceeding.
The entries indicate that the SoftGrid client is not installed. However, the error message only indicates that an installation failure occurred.

For situations in which the log file that is generated for the virtualized application .msi file does not provide sufficient detail, examine the desktop client log for SoftGrid Virtual Application Server to learn more about the issue that occurred.

The following table lists the error codes and the possible conditions that generate the error codes.
Collapse this tableExpand this table
Error codePossible conditions
07708004-00000007There is no valid implementation for this computer. Or, you tried to deploy the virtualized application .msi file to an operating system that is not supported by the underlying sequencing.
0B206A04-00000C0CThe application is currently being used.
0F802F04-00000A28An error occurs when you import data for the application. Verify that the free disk space is sufficient on the SoftGrid client computer. Additionally, verify that the SYSTEM account has access to the share if the .sft file is located on a file share.

Properties

Article ID: 949050 - Last Review: March 25, 2008 - Revision: 1.0
APPLIES TO
  • Microsoft SoftGrid Application Virtualization for Terminal Services
  • Microsoft SoftGrid Application Virtualization for Windows Desktops
Keywords: 
kbexpertiseadvanced kbhowto kbinfo KB949050

Give Feedback

 

Contact us for more help

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