KB: Launching an App-V application fails with "Unable to initialize package information (0x00000000)" error
Here’s a new Knowledge Base article we published this morning. This one talks about a couple work arounds for an App-V issue where launching an App-V application fails with "Unable to initialize package information (0x00000000)":
=====
Symptoms
When launching an application virtualized with Microsoft Application Virtualization (App-V), the application fails to start and generates the following error message:
Unable to initialize package information (0x00000000)
Cause
This can occur when App-V is set to work in Full Infrastructure Mode (https://technet.microsoft.com/en-us/magazine/2008.10.appv.aspx#id0110023) and the Configuration Manager (ConfigMgr) client agent is installed on the same machine where the App-V client is already installed. When the Configuration Manager client agent is installed, it assumes that it should handle the virtualized applications. During the Configuration Manager client agent installation, the App-V client cache is flushed and App-V registry keys are modified, causing the error described above.
Resolution
There are 3 potential work arounds for this issue:
1. The ConfigMgr client agent takes managing virtualized applications when “Allow virtual application package advertisement" in the Advertised Programs Client Agent properties in the ConfigMgr console is checked. If this box is unchecked, it is then possible to run both ConfigMgr and App-V client agents at the same time. To modify this setting, open the ConfigMgr Console, expand Site Database, Site Management, <Site Name>, Site Settings, Client Agents; then open the properties for Advertised Programs Client Agent. The next time the client agents refresh (or if you kick off a Machine Policy Retrieval & Evaluation Cycle), the App-V client will become the default handler again.
2. The second option is to manually modify the registry keys on the client back to the original values. Thus, we can make the following modifications:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\UserInterface
Change to the following:
LaunchCommand "C:\Program Files\Microsoft Application Virtualization Client\sfttray.exe" /launch "<APP>"
DDELaunchCommand"C:\Program Files\Microsoft Application Virtualization Client\sftdde.exe" "<APP>" <DDE>"
However, keep in mind that if “Allow virtual application package advertisement" in the Advertised Programs Client Agent properties in the ConfigMgr console remains checked, it is possible that it will reset the registries to their previous values and the issue will reoccur.
3. The third option is to use ConfigMgr to manage the virtual applications instead of using the App-V management server. More info on this can be found here:
More Information
Below are the App-V registry keys that are changed during the SCCM client agent installation:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\UserInterfaceLaunchCommand "C:\Windows\system32\CCM\VappLauncher.exe" /launch "<APP>" DDELaunchCommand "C:\Windows\system32\CCM\VappLauncher.exe" /launch "<APP>"
Instead of the original values shown below:
LaunchCommand "C:\Program Files\Microsoft Application Virtualization Client\sfttray.exe" /launch "<APP>" DDELaunchCommand "C:\Program Files\Microsoft Application Virtualization Client\sftdde.exe" "<APP>" <DDE>"
=====
For the most current version of this article please see the following:
J.C. Hornbeck | System Center & Security Knowledge Engineer
Get the latest System Center news on Facebook and Twitter :
App-V Team blog: https://blogs.technet.com/appv/
ConfigMgr Support Team blog: https://blogs.technet.com/configurationmgr/
DPM Team blog: https://blogs.technet.com/dpm/
MED-V Team blog: https://blogs.technet.com/medv/
Orchestrator Support Team blog: https://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: https://blogs.technet.com/momteam/
SCVMM Team blog: https://blogs.technet.com/scvmm
Server App-V Team blog: https://blogs.technet.com/b/serverappv
Service Manager Team blog: https://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: https://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: https://blogs.technet.com/sus/
The Forefront Server Protection blog: https://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : https://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : https://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: https://blogs.technet.com/b/isablog/
The Forefront UAG blog: https://blogs.technet.com/b/edgeaccessblog/