none
APP-V 5 SP1 - "Application Failed to Launch. This may be due to a network failure 0x0FD01B25-0000007B"

    Question

  • Hello all,I am having some issues with APP-V 5.

    I am having particular issues with starting a packaged SIMS.net. I keep recieving:

    "Application Failed to Launch. This may be due to a network failure 0x0FD01B25-0000007B"

    ...within a second or two of clicking on the app-v created shortcut for this software.

    To clarify, I had this software working perfectly previously. I recreated this package due to a software update, but it fails to launch now. I started a new package from scratch as this is a complex piece of software with multiple installers to run etc.

    To be honest, I keep seeing this error on other applications. At one point, nearly every published app returned the same error. I spent a day trying to diagnose but the following day, everything mysteriously started working again.

    I have had a look on kirks blog & Tim Magan, but to no avail.

    Any help would be greatly appreciated, as this is a 'business critical application' (as they say).

    Quick overview of my setup:

    - Single Server configuration (Management, Publishing & SQL) on Server 2012 VM in 2012 Hyper-V

    - Win 2000 Domain with 2003 DC

    - Windows 7 Enterprise SP1

    - SIMS.net Summer 2013 sequenced on 32bit following best practice guide

    - Deploying to 32 bit machine

    - Client settings pushed by GPO. Powershell execution policy set to allsigned.

    Friday, August 16, 2013 12:20 PM

Answers

  • RESOLVED: This error is caused by the "Program Files" missing from the "C:\ProgramData\Microsoft\Windows\Start Menu\" folder.

    Firstly, a big thank you Nicke. You may not have solved the problem, but you sent me down the road to resolve this issue.

    After trying the step you mentioned, I placed the computer in an OU with inheritance disabled. From this point onwards, I deduced that it was actually a group policy issue.

    In my environment, I redirect start menus to generated start menu. This is created using a powershell script to combine locally installed items and network items. This scripts deletes the content of the 'programdata' start menu (i.e all users start menu) to prevent these items disrupting the start menu.

    Now... The app-v packages were breaking because, the 'Start Menu > Programs' folder did not exist. If an empty 'Start Menu > Programs' exists, the packages work correctly.

    I can only assume that the two packages that were working correctly - that I installed these for 'current user only', rather than 'all users'.

    It seems a little silly to me that app-v should fall over for something so simple. However, you could argue that it serves me right for playing about with system files :)

    Thanks again for the help.

    Mark

    Wednesday, August 21, 2013 8:17 AM

All replies

  • Hello,

    So, which debug logs have you been looking at?


    Nicke Källén | The Knack| Twitter: @Znackattack

    Friday, August 16, 2013 1:13 PM
  • I have just built a new image containing the app-v client and deployed to a machine using MDT.

    All the shortcuts appear for my packaged software, but interestingly, all but two fail with exactly the same error.

    I have looked at every available debug log. Most are empty, but a number contain interesting messages which I am unable to interpret. For the sake of expediency, I have the most interesting one below for the VFS:

    "Failed to get the long path from "\\?\". [Followed by the error code above]

    Thanks

    Mark

    Monday, August 19, 2013 9:24 AM
  • Hello,

    If you add them from the local disk using PowerShell cmdl:ets, do they work then?


    Nicke Källén | The Knack| Twitter: @Znackattack

    Monday, August 19, 2013 6:41 PM
  • RESOLVED: This error is caused by the "Program Files" missing from the "C:\ProgramData\Microsoft\Windows\Start Menu\" folder.

    Firstly, a big thank you Nicke. You may not have solved the problem, but you sent me down the road to resolve this issue.

    After trying the step you mentioned, I placed the computer in an OU with inheritance disabled. From this point onwards, I deduced that it was actually a group policy issue.

    In my environment, I redirect start menus to generated start menu. This is created using a powershell script to combine locally installed items and network items. This scripts deletes the content of the 'programdata' start menu (i.e all users start menu) to prevent these items disrupting the start menu.

    Now... The app-v packages were breaking because, the 'Start Menu > Programs' folder did not exist. If an empty 'Start Menu > Programs' exists, the packages work correctly.

    I can only assume that the two packages that were working correctly - that I installed these for 'current user only', rather than 'all users'.

    It seems a little silly to me that app-v should fall over for something so simple. However, you could argue that it serves me right for playing about with system files :)

    Thanks again for the help.

    Mark

    Wednesday, August 21, 2013 8:17 AM
  • I also got your same error of 0xFD01F25-0000007B.  I isolated the problem, in this particular case, to be caused by excessive desktop.ini files in the VFS.

    http://t3chn1ck.wordpress.com/2014/01/16/app-v-5-0-error-0xfd01f25-0x7b/


    Nick Moseley | http://t3chn1ck.wordpress.com

    • Proposed as answer by Click72 Thursday, June 04, 2015 7:34 PM
    Thursday, January 16, 2014 11:13 PM
  • I as well had a significant number of desktop.ini files in my App-V 5 sequence of Crystal Reports 2013, once deleted the app worked as expected. Thanks!!
    Thursday, June 04, 2015 7:35 PM