The Microsoft App-V Team Blog

The official blog for Microsoft Application Virtualization

New KB: Microsoft App-V 4.6 Applications Advertised Through Configuration Manager 2007 Fail with Error 14-00000005

New KB: Microsoft App-V 4.6 Applications Advertised Through Configuration Manager 2007 Fail with Error 14-00000005

  • Comments 1
  • Likes

hotfixI just wanted to let you know about a new Knowledge Base article we published today. This one talks about an issue where apps virtualized with Microsoft Application Virtualization and published via ConfigMgr 2007 may fail with a 00000005 error:

=====

Symptoms

Microsoft Application Virtualization (App-V) 4.6 applications published through Microsoft Configuration Manager 2007 (ConfigMgr 2007) may fail to install with the following error in sftlog.txt:

[07/07/2011 11:50:26:571 SRVC WRN] {tid=BB0}
The Application Virtualization Client was unable to initialize the user's profile for a system session (rc 0FD00D14-00000005).

VirtualApp.log (located in %systemroot%\syswow64\ccm\logs by default) will show entries similar to:

Registering the virtual application package [XXX01588] with the AppVirtMgmt client. VAppRegistration 7/7/2011 11:46:43 AM 3652 (0x0E44)
Loading package properties from the manifest file: C:\Windows\SysWOW64\CCM\Cache\SSD01588.8.S-1-5-21-00000000-0000000-11111111-1234567\appv1_manifest.xml. VAppRegistration 7/7/2011 11:46:43 AM 3652 (0x0E44)
The package name is AppName 7/7/2011 11:46:43 AM 3652 (0x0E44)
Failed to get the package object [Package.PackageGUID="903AB33A-3547-406C-88C4-6960770A6F2F"] from WMI. Error (0x80041001) VAppQuery 7/7/2011 11:46:43 AM 3652 (0x0E44)
CVAppQuery::PackageInUse() failed for virtual app package [{903AB33A-3547-406C-88C4-6960770A6F2F}]. (0x80041001) VAppQuery 7/7/2011 11:46:43 AM 3652 (0x0E44)
CVAppRegistration::ExecuteAdd failed for the virtual application package. (0x80041001) VAppRegistration 7/7/2011 11:46:43 AM 3652 (0x0E44)

Cause

This error may occur if the following conditions are all true:

  • The application is being advertised through Configuration Manager
  • The user's data directory is being redirected to a UNC (check the value of HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client\Configuration\UserDataDirectory)
  • The client is running App-V 4.6 SP1 or lower
Resolution

This issue is resolved by applying the latest App-V 4.6 SP1 hotfix package. Currently, this is App-V 4.6 SP1 Hotfix Package 2 : (http://support.microsoft.com/kb/2549352).

More Information

Configuration Manager clients using virtualized applications also need to have the Configuration Manager client version at Service Pack 2 or higher : (http://technet.microsoft.com/en-us/systemcenter/cm/bb625747)

=====

For the latest information please see the following KB article:

KB2579122: Microsoft App-V 4.6 Applications Advertised Through Configuration Manager 2007 Fail with Error 14-00000005

J.C. Hornbeck | System Center Knowledge Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis
The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager
The AVIcode Team blog: http: http://blogs.technet.com/b/avicode
The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials
The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv

clip_image001 clip_image002

Comments
  • <p>It seems that this problem is being reintroduced with the release of SP2 for App-V 4.6 We get the error code: rc-0FD00D14-00000043 while using Roaming Profiles. A quick fix is creating a new user profile. Still looking for a permanent fix.</p>

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment