Article ID: 2552111 - View products that this article applies to.
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.
There are several possible workarounds to enable this scenario:
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.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Contact us for more help
Connect with Answer Desk for expert help.