The Microsoft App-V Team Blog

The official blog for Microsoft Application Virtualization

App-V Support Tip: Error 29-0000001F on initial application launch after active upgrade

App-V Support Tip: Error 29-0000001F on initial application launch after active upgrade

  • Comments 1
  • Likes

Tools_thumb2_thumb 

Here’s a quick heads up on an issue we ran into recently. When you open a Microsoft Application Virtualization (App-V) app for active upgrade and make a minor change, it is possible that the application will fail to start the first time it is imported on the App-V Management Server. On a client, users will see the error specified below upon the first launch attempt (any other launch will work fine, it only happens for the first launch)

clip_image002

The Application Virtualization Client could not launch. A device attached to the system is not functioning. Error code xxxxxxxx-xxxxxx29-0000001F

They key factor here is the size of the update you are performing. If the size of the package does not change, or it changes too little, you will run into this issue.

Workaround

You can use the steps to work around this behavior and ensure that the package launches after adding it to the App-V Management Server:

  • On the Sequencer, open the package for package upgrade.
  • During the monitoring phase, be sure to add a dummy file to the Virtual File system. Usually something about 50 KB will do.
  • If you need to replace an existing file from the VFS, ensure you have this file ready in an unmonitored location.
  • Delete the original file.
  • Copy the new file over.
  • Save the package.

Now you should not see the error.

Good luck sequencing!

Sebastian Gernert | App-V Escalation Engineer

Madelinde Walraven | App-V Support Escalation Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

 

 

Tools_thumb4_thumb

Comments
  • Error 0000729-0000001F

    Hello, this problem I do not resolv this note upper, but add information to registry in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration -- ApplicationSourceRoot value: http://servername_FQDN/content/

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