Understanding the %SFT_SOFTGRIDSERVER% environmental variable in Microsoft App-V

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

Symptoms

After modifying the %SFT_SOFTGRIDSERVER% environment variable, Microsoft Application Virtualization (App-V) packages may fail to load or may connect to an incorrect server.  In some cases, you may receive a 0A-10000002 error ("The specified Application Virtualization Server could not be accessed. Try again in a few minutes. If the problem persists, report the following error code to your System Administrator") if the system variable references a non-existent or inaccessible server.

This is most common in scenarios where the intent is to test packages located on a development server with the intention of later copying the package to the production environment.  In this case, changes to either the user or system environmental variable %SFT_SOFTGRIDSERVER% will not be used by the App-V client.

In the case of user variables (that is, adding a variable called SFT_SOFTGRIDSERVER under Control Panel\System\Advanced System Settings\Advanced tab\Environmental Variables...\User variables for username), App-V does not read the %SFT_SOFTGRIDSERVER% for individual users.  Only the system variable is honored.

In the case of system variables, this setting is only reflected after a system reboot.  This is necessary for the App-V client services and drivers to properly and consistently read these variables.  Any changes made to the %SFT_SOFTGRIDSERVER% variable are not reflected until either the Application Virtualization client service is restarted or the client operating system is rebooted.

Cause

This behavior is by design.

Resolution

There are several possible workarounds to enable this scenario:

  1. Change the system %SFT_SOFTGRIDSERVER% environmental variable and then either restart the Application Virtualization Client service or reboot the client (in most cases restarting the service is sufficient; if this does not resolve the issue, you may need to restart the client).  This is obviously the easiest method, but may not be desirable in some environments (for instance on, on a heavily-utilized Terminal Server).
  2. Edit the OSD directly and replace the %SFT_SOFTGRIDSERVER% variable with the actual name of the development server, or use another variable.
  3. Use an alternate application source root (ASR) (http://technet.microsoft.com/en-us/library/cc843817.aspx).
  4. Use two separate versions of the application for testing.

More Information

User environmental variables override system environmental variables in Windows.  Executables (including services and drivers) read environmental variables when they first launch, but do not subsequently re-read values.
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.

Properties

Article ID: 2552111 - Last Review: June 3, 2011 - Revision: 6.0
APPLIES TO
  • Microsoft Application Virtualization 4.6 Sequencer
Keywords: 
KB2552111

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