none
This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem. APP-V 4.6 issues

    Question

  • I am getting this issue since the introduction of APP-V 4.6 (build 1523 and build 20200). I have seen that with both version the FTA has not been set during installation, I have therefor also set this manualy although I do not think that is the issue. At this moment it only happends with Adobe Reader 9.3.2 It hasn't gave this issues before and we are already working with it since the release of the adobe version.

    The problems are happening randomly on our TS and only with Adobe, strangely the problem doesn't affect everyone on the server. The error message is no where to be found so I cannot see what it means.

     

    Error code: 4604EE8-1B401F2C-000036B1

    Any help is appreciated!

     

    Wednesday, May 26, 2010 7:02 AM

Answers

All replies

  • Hi,

    Are there an (human readable) additional information in the log file?


    Falko
    Wednesday, May 26, 2010 2:55 PM
    Moderator
  • I have the following information in the log.  The error on virtual registry is there often but it seems more informational, I think I read something somewhere that MS will remove this error because it is not important. this seems to be the real error Unable to CreateProcess (rc 1B401F2C-000036B1). Strange thing is that other people on the same server do not have problems before or after.

    [05/28/2010 10:37:17:568 OMGR INF] {tid=45EC:usr=****}
    The client updated the OSD file for 'Adobe Reader 9.3 9.3.2.163' with a version from Fri, 28 May 2010 08:37:17 GMT.


    [05/28/2010 10:37:17:818 ???? INF] {tid=34F4:usr=****}
    An error occurred while opening the virtual registry (section: 9), rc: 07B01F0C-0000004A


    [05/28/2010 10:37:17:849 ???? INF] {tid=34F4}
    An error occurred while opening the virtual registry (section: 9), rc: 07B01F0C-0000004A


    [05/28/2010 10:37:17:849 SWAP INF] {hap=AF4:app=Adobe Reader 9.3 9.3.2.163:tid=34F4:usr=****}
    Elapsed time for upload: 0.125 seconds


    [05/28/2010 10:37:18:333 OSDF INF] {hap=AF4:app=Adobe Reader 9.3 9.3.2.163:tid=34F4:usr=****}
    Elapsed time for script C:\DOCUME~1\****\LOCALS~1\APPLIC~1\SOFTGR~1\4DF52F~1.BAT: 0.468 seconds
    Script type: sync
    Script trigger time: pre-launch

     

    [05/28/2010 10:37:18:349 ???? ERR] {tid=34F4:usr=****}
    Unable to CreateProcess (rc 1B401F2C-000036B1)


    [05/28/2010 10:37:18:349 SWAP ERR] {hap=AF4:app=Adobe Reader 9.3 9.3.2.163:tid=34F4:usr=****}
    The client could not launch Q:\ar_93.p03\Adobe\Reader 9.0\Reader\AcroRd32.exe (rc 1B401F2C-000036B1, last error 87).


    [05/28/2010 10:37:18:537 TRAY ERR] {tid=3CBC:usr=****}
    The Application Virtualization Client could not launch Adobe Reader 9.3 9.3.2.163.

    This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.


    Error code: 4604EE8-1B401F2C-000036B1

    Friday, May 28, 2010 8:59 AM
  • Hello,


    Try without antivirus and see if that makes a difference.

    /znack

    Friday, May 28, 2010 9:21 AM
  • No it doesn't because all directories and files concerning APP-V are already excluded from the virus scanner.

     

    What I did do in one case was unload the cache and then the person(s) who had the problem could also work again with the same sequence. If it would be the cache like a corruption, then why would it then work for other people without problems?

    The problem was non-existent with APP-V 4.5

    Friday, May 28, 2010 10:42 AM
  • Hello,

    when we noticed problems like this - it had nothing todo with what was excluded from real-time scanning - but other functions of the antivirus software.

    /Znack

    Friday, May 28, 2010 12:15 PM
  • Which virus scan do you use?
    Friday, May 28, 2010 1:23 PM
  • Hello,

    I am a consultant - so I get just about anything. What I did learn is that everyone call their feature something else than the next one - so when troubleshooting antivirus I always start by entirely removing it. This gives me a good sense if that is the path to troubleshoot.


    /Znack

    Friday, May 28, 2010 2:01 PM
  • I love this generic error message.

    This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.

    This is an application error bubbling up through the App-V client. As to how you would fix it I'm not sure I can offer much help there. Resetting the virtual environment for the application and all users may help also re-sequencing the application using a newer sequencer may help (assuming the application was sequenced using an older sequencer).

    If you could run Dependency Walker inside modern versions of App-V you might see some side-by-side dll issues. But since you can't you can check your eventlog for side by side errors that may be related to the sequence.


    www.bighatgroup.com
    Monday, May 31, 2010 2:49 AM
    Answerer
  • We have the some problem (1B401F2C-000036B1, last error 87). Does anyone have a solution for this problem?

     

    Monday, August 01, 2011 12:12 PM
  • Hello,

    I suggest creating your own thread - where you in much greater detail explain your problem, your environment and what steps you have investigated so far
    /Znack
    Tuesday, August 02, 2011 4:32 AM
  • This may be a SxS configuration issue with your sequenced application.  You can use the sxstrace command to get additional information about the failure.
    Steve Morin
    Tuesday, September 20, 2011 12:01 AM
  • What happens if you re-sequence the application with the 4.6 SP1 sequencer?
    Steve Thomas, SSEE, Microsoft
    App-V/MED-V/SCVMM/SCCM/AppCompat
    http://madvirtualizer.wordpress.com/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”
    Sunday, October 16, 2011 4:25 AM
  • We are experiencing the same issue (& error) randomly with 4.6 SP1-sequenced Adober Reader 10.1.0.534.  The only way we have found to fix it is to delete it via the Application Virtualization Client console on the affected PC.  Then after refresh, it typically will work again.  This does not happen to everyone nor does it happen to the same person every time - very random.  Is it possible the package on the virtualized Q: drive is getting corrupted?

    We have a few other sequenced apps, but this error only seems to occur with Reader.

    Thanks,

    Eldon Wagner

    Thursday, October 27, 2011 7:29 PM
  • Hello, 

     

    Have you investigated what happens if only removing the users PKG?


    /Znack
    Thursday, October 27, 2011 8:21 PM
  • If you repair the application, does the issue reappear?
    Steve Thomas, SSEE, Microsoft
    App-V/MED-V/SCVMM/SCCM/AppCompat
    http://madvirtualizer.wordpress.com/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”
    Friday, November 04, 2011 2:05 AM
  • Hello,

    Have you verified the application-log?

    Usually this will tell you which file is wrong - see this as a sample suggestion;

    This error indicates that certain components that needs to available to the application are not when running a virtualized application within App-V.

    VC++ 2005: http://www.microsoft.com/download/en/details.aspx?id=3387
    VC++ 2005 SP1: http://www.microsoft.com/download/en/details.aspx?id=5638
    VC++ 2005 SP1 ATL security update: http://www.microsoft.com/download/en/details.aspx?id=14431
    VC++ 2008: http://www.microsoft.com/downloads/details.aspx?familyid=9b2da534-3e03-4391-8a4d-074b9f2bc1bf
    VC++ 2008 SP1: http://www.microsoft.com/download/en/details.aspx?id=5582
    VC++ 2008 SP1 with ATL security update: http://www.microsoft.com/download/en/details.aspx?id=15303
    VC++ 2010: http://www.microsoft.com/download/en/details.aspx?id=5555
    VC++ 2010 SP1: http://www.microsoft.com/download/en/details.aspx?id=8328
    Visual J# 2.0: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=4712
    VS 2010 F# 2.0 SP1: http://www.microsoft.com/download/en/details.aspx?id=15834

    Incase installing one of the above does not remedy the problem - you can manually setup the missing sidebyside-component. Review the error
    message from the Application Log - see example below;

     
    Log Name: Application 
    Source: SideBySide 
    Level: Error 
    Keywords: Classic 
    Description: 
    Activation context generation failed for "Q:\ecowin.002\VFS\CSIDL_PROGRAM_FILES\EcoWin\EcoWin.exe". Dependent Assembly Vinga.vscom90u,processorArchitecture="X86",publicKeyToken="e520fe831c9439c8",type="Win32",version="1.0.0.55" could not be found. Please use sxstrace.exe for detailed diagnosis. 
    

     

     

    Locate the referenced file within the package and copy it to the same folder as the application.
    Create the first manifest to tell Ecowin where it should get its above Vinga.vscom90u (named ecowin.exe.manifest)

     

     
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?> 
    <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> 
    <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3"> 
    <security> 
    <requestedPrivileges> 
    <requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel> 
    </requestedPrivileges> 
    </security> 
    </trustInfo> 
    <dependency> 
    <dependentAssembly> 
    <assemblyIdentity type="win32" name="Vinga.vscom90u" version="1.0.0.55" processorArchitecture="x86"></assemblyIdentity> 
    </dependentAssembly> 
    </dependency> 
    </assembly>
    
    


     


     

     
    The second manifest telling Ecowin where VScom90u.dll was (named Vinga.vscom90u.manifest)

     
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?> 
    <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> 
    <noInheritable /> 
    <assemblyIdentity type="win32" name="Vinga.vscom90u" publicKeyToken="e520fe831c9439c8" version="1.0.0.55" processorArchitecture="x86" /> 
    <file name="vscom90u.dll" /> 
    </assembly>
    



    The version, name, type, processorArchitecture, publicKeyToken are all picked up from the original error message.
    Nicke Källén | The Knack| Twitter: @Znackattack
    Tuesday, November 22, 2011 9:29 AM