locked
App-v 5.0 Error 0x80000003 (launching any executable in bubble) RRS feed

  • Question

  • Hi.

    I've sequenced OpenEdge Client 10.2 on a Windows 7 (x86) client. I keep getting this error when launching any of the application shortcuts on a test VM. The error is seen regardless of shortcut/exe.

    Our App-V infrastructure is outdated (5.0.285.0 RTM), so I tried in a test lab re-sequencing on the SP2 sequencer/client. The error persists. There is little in the event logs (i.e., nothing) of value and Procmon doesn't display anything that stands out.

    Anyone seen this before?

    Event log excerpt:

    Faulting application name: showcfg.exe, version: 0.0.0.0, time stamp: 0x4b26ce51

    Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b83b16

    Exception code: 0x80000003

    Fault offset: 0x0003491e

    Faulting process id: 0xe28

    Faulting application start time: 0x01cf9b53a642aa1b

    Faulting application path: C:\ProgramData\App-V\A127AFFE-D58C-40DC-9536-88852B2FC314\66BE6629-9907-4462-9176-F49436AA5051\Root\bin\showcfg.exe

    Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll

    Report Id: e404a15e-0746-11e4-8524-005056262ab2

    Wednesday, July 9, 2014 9:22 AM

Answers

  • Finally found the answer to this problem!

    Procmon log showed the application process was searching for Microsoft.VC80.CRT.manifest which couldn't be found. The manifest file existed in several places in the sequence but not in {AppVRoot\VFS\SystemX86}.

    I copied a manifest file into the VFS\SystemX86 folder and hey presto, the app launched.

    Quite why this file doesn't appear in Procmon logs for the natively installed app isn't clear, but I don't have the time to investigate.

    Hope this helps somebody else!

    • Marked as answer by TenBob Wednesday, July 16, 2014 1:28 PM
    Wednesday, July 16, 2014 1:28 PM

All replies

  • In http://blogs.technet.com/b/appv/archive/2013/01/22/kb-keepass-exe-fails-to-synchronize-settings-with-microsoft-user-experience-virtualization-1-0-ue-v-1-0.aspx another issue with kernelbase.dll is explained, however it's causing another error. But it might be worth a try.

    http://www.appvirtguru.com/viewtopic.php?f=9&t=3638 indicates that *not* launching the application during the sequencing phase might fix the issue (hover this hasn't validated).

    Some sources indictae that kernlbase error might be cuased by VC runtimes and/or .net. could you validate they are the same on client/sequencer.

    Finally: I suppose you tired installing it 'natively' on a test client with the same specifics and it runs there.


    Falko

    Twitter @kirk_tn   |   Blog kirxblog   |   Web kirx.org   |   Fireside appvbook.com

    • Proposed as answer by znack Wednesday, July 9, 2014 8:34 PM
    Wednesday, July 9, 2014 10:16 AM
    Moderator
  • Thanks for your help.

    Tried 'not launching'; error persists.

    App installs and runs natively without error. I even tried installing the application on the same VM as the installed sequence in case a component was missing from the sequence, without success.

    VC 2005 runtime is required for the app and is installed either in the bubble or on the client, doesn't make any difference.

    With analytic and debug logs enabled, I see an error but this may be expected?:

    Log Name:      Microsoft-AppV-Subsystems-VObjects/Debug
    Source:        Microsoft-AppV-Subsystems-VObjects
    Date:          10/07/2014 16:26:56
    Event ID:      110
    Task Category: None
    Level:         Information
    Keywords:     
    Description:
    No objects node in manifest. Error code: 0x80-0x0
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-AppV-Subsystems-VObjects" Guid="{c505d6a3-83eb-41bc-89a1-96067e0cf001}" />
        <EventID>110</EventID>
        <Version>1</Version>
        <Level>4</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2014-07-10T15:26:56.489176500Z" />
        <EventRecordID>0</EventRecordID>
        <Correlation />
        <Execution ProcessID="1820" ThreadID="672" ProcessorID="0" KernelTime="27" UserTime="41" />
        <Channel>Microsoft-AppV-Subsystems-VObjects/Debug</Channel>
        <Computer>removed</Computer>
        <Security UserID="S-1-5-21-1451040463-1185243809-324685044-12345" />
      </System>
      <EventData>
        <Data Name="ErrorHigh">128</Data>
        <Data Name="ErrorLow">0</Data>
      </EventData>
    </Event>

    Thursday, July 10, 2014 3:48 PM
  • Hello,

    What happens if you check all the boxes under the Advanced-tab in editing mode on the sequencer?


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

    Thursday, July 10, 2014 9:38 PM
  • Hello,

    What happens if you check all the boxes under the Advanced-tab in editing mode on the sequencer?


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


    Same error I'm afraid (sorry, should have mentioned I tried that).
    Friday, July 11, 2014 8:25 AM
  • Hello,

    Anything else you tried?


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

    Sunday, July 13, 2014 8:32 PM
  • If I copy the contents of the App-V application folder to it's original install location (C:\oe102b) on the client, the app launches. This tells me this isn't an application specific file (or registry issue) per se, so must be related to the VCRT.

    The version of the runtime in the sequence is 8.0.50727.42.

    I created Procmon logs from the native & virtualised installs and compared the flow of events until the failure occurred. One interesting thing to note - mfc80.dll (version 8.0.50727.42) is called from within the application folder, but then a later version (8.0.50727.6195) is called from the WinSXS location by the same process.

    The native installation never uses the private mfc80.dll, it goes straight to the WinSXS version.

    Not being from a developer background, can I play around with a manifest file to force the app to use the natively installed VCRT only?

    (Note, I sequenced the app with the VCRT installed natively (outside the bubble), but the install still drops mfc80.dll, msvcp80.dll & msvcr80.dll into the application folder!).


    • Edited by TenBob Monday, July 14, 2014 1:23 PM more info
    Monday, July 14, 2014 12:16 PM
  • Finally found the answer to this problem!

    Procmon log showed the application process was searching for Microsoft.VC80.CRT.manifest which couldn't be found. The manifest file existed in several places in the sequence but not in {AppVRoot\VFS\SystemX86}.

    I copied a manifest file into the VFS\SystemX86 folder and hey presto, the app launched.

    Quite why this file doesn't appear in Procmon logs for the natively installed app isn't clear, but I don't have the time to investigate.

    Hope this helps somebody else!

    • Marked as answer by TenBob Wednesday, July 16, 2014 1:28 PM
    Wednesday, July 16, 2014 1:28 PM
  • I'd like to thank you for sharing this.

    The file did not show up in my AppV at all but it was present in the OpenEdge 10.1C installation folder.
    My eventvwr did not show any AppV entries and I must have missed it in my procmon log.

    Adding the Microsoft.VC80.CRT.manifest does indeed now start the engine/show the logon screen

    Thanks again.

    Thursday, August 28, 2014 12:07 PM