locked
AppV5 SP3 - First launch (or two) of an application fails with Error 0x3E501405-0x90001 RRS feed

  • Question

  • We have a few large applications that have a >30MB registry (as captured by the AppV5 sequencer).  All was fine with AppV 5SP2 HF4, but after upgrading to AppV5 SP3 we get an error on startup:

    Process 1832 failed to start due to Virtual Filesystem subsystem failure. Package ID {aef1abd8-2ac1-4300-856a-31abbf90d70c}. Version ID {89c14a0a-fb18-4488-a240-368bfaaf3bed}. Error: 0x3E501405-0x90001

    Microsoft has documentation on this here.  Essentially, it says:

    This can occur if the path to the .appv container file is incorrect in the client package. Normally this is seen if the content was moved or renamed.

    In our environment we use the full infrastructure.  We have not upgraded the database to SP3 yet, running at the previous level.  For all other applications that are not large we do not have this issue, and it will resolve itself if you try launching the application a couple of times; which tells me the MS documentation is missing something.  I did try the fix as noted in the documentation, removing the package and readding it to ensure the path was good.  That did not work.  I also re-sequenced the application in case it was sequenced with SP2, but the issue persists.

    I think my next step is to try and upgrade the database and see if that resolves it, but I'm open to other suggestions.  Anyone else have any more thoughts on this?

    Thursday, March 12, 2015 3:17 AM

Answers

  • We are aware of this issue and this is being addressed soon.


    Steve Thomas, Senior Consultant, Microsoft

    App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat

    http://blogs.technet.com/gladiatormsft/
    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.”

    • Marked as answer by TrententMVP Tuesday, October 20, 2015 6:39 PM
    Tuesday, October 20, 2015 2:18 AM

All replies

  • Some addition details:

    Enabling debug logs details the following:

    Microsoft-AppV-Subsystems-VFS/Debug : ID 611
    Failed to load filesystem metadata for package/group {aef1abd8-2ac1-4300-856a-31abbf90d70c} version {89c14a0a-fb18-4488-a240-368bfaaf3bed}. Error code: 0x3E501405-0x90001


    Streaming-Filter : Event ID 51,52,50
    Send message to the streaming engine failed. Status 0x102

    Bad stream fault message. File name: D:\AppVData\PackageInstallationRoot\AEF1ABD8-2AC1-4300-856A-31ABBF90D70C\89C14A0A-FB18-4488-A240-368BFAAF3BED\FilesystemMetadata.xml, Offset: 0x0 , Length 0x10000, Status 0x102.

    Stream fault failed. File name: D:\AppVData\PackageInstallationRoot\AEF1ABD8-2AC1-4300-856A-31ABBF90D70C\89C14A0A-FB18-4488-A240-368BFAAF3BED\FilesystemMetadata.xml, Offset: 0x0 , Length 0x800, Status 0xc000000d.

    Service Log: Event ID 1:

    2015-Mar-11 22:37:26.628 - Catalog: [5452].[5276]: INFO: AppV::Client::Catalog::UserCatalogImpl::GetPackage(), 513: Package {AEF1ABD8-2AC1-4300-856A-31ABBF90D70C} - {89C14A0A-FB18-4488-A240-368BFAAF3BED} was not found in the 2 Catalog.
    2015-Mar-11 22:37:26.628 - Catalog: [5452].[5276]: INFO: AppV::Client::Catalog::MachineCatalogImpl::GetPackageGroup(), 264: Package group {AEF1ABD8-2AC1-4300-856A-31ABBF90D70C} - {89C14A0A-FB18-4488-A240-368BFAAF3BED} was not found in the 1 catalog.
    2015-Mar-11 22:37:26.628 - Catalog: [5452].[5276]: INFO: AppV::Client::Catalog::UserCatalogImpl::GetPackage(), 513: Package {AEF1ABD8-2AC1-4300-856A-31ABBF90D70C} - {89C14A0A-FB18-4488-A240-368BFAAF3BED} was not found in the 2 Catalog.
    2015-Mar-11 22:37:31.665 - StrmDrv: [4].[1728]: DEBUG: UserCommunication::SendMessage() - SendMessage() returned with STATUS_TIMEOUT.2015-Mar-11 22:37:31.665 - FileSystemMetadata: [5452].[5276]: ERROR: FileSystemMetadataImpl::LogLoadError() - Failed to load filesystem metadata xml.
    DOM Error: -2147023897
    Reason: Error performing inpage operation.

    Line: 1
    Column: 0
    Offset: 0
    2015-Mar-11 22:37:31.665 - Orchestrator: [5452].[5276]: ERROR: ClientActivity::ExecuteActivity() - Activity VirtualEnvironmentCreated #495 failed on component SubsystemController (error: 1045435397-589825).
    2015-Mar-11 22:37:31.665 - Orchestrator: [5452].[5276]: ERROR: ActivityManagerImpl::RequestActivity() - VirtualEnvironmentCreated activity #495 failed with error code 1435503874-1281.
    2015-Mar-11 22:37:31.696 - VEMgrDrv: [4700].[8752]: ERROR: VirtualEnvironmentManager::VECreatedNotificationUpcall() - VE created notification failed. Package moniker AEF1ABD8-2AC1-4300-856A-31ABBF90D70C_89C14A0A-FB18-4488-A240-368BFAAF3BED. User SID S-1-5-21-38857442-2693285798-3636612711-15060318. Error -1073741823.

    Client-SubsystemController: EventID 100

    2015-Mar-11 22:37:26.628 - Catalog: [5452].[5276]: INFO: AppV::Client::Catalog::UserCatalogImpl::GetPackage(), 513: Package {AEF1ABD8-2AC1-4300-856A-31ABBF90D70C} - {89C14A0A-FB18-4488-A240-368BFAAF3BED} was not found in the 2 Catalog.
    2015-Mar-11 22:37:26.628 - Catalog: [5452].[5276]: INFO: AppV::Client::Catalog::MachineCatalogImpl::GetPackageGroup(), 264: Package group {AEF1ABD8-2AC1-4300-856A-31ABBF90D70C} - {89C14A0A-FB18-4488-A240-368BFAAF3BED} was not found in the 1 catalog.
    2015-Mar-11 22:37:26.628 - Catalog: [5452].[5276]: INFO: AppV::Client::Catalog::UserCatalogImpl::GetPackage(), 513: Package {AEF1ABD8-2AC1-4300-856A-31ABBF90D70C} - {89C14A0A-FB18-4488-A240-368BFAAF3BED} was not found in the 2 Catalog.
    2015-Mar-11 22:37:31.665 - StrmDrv: [4].[1728]: DEBUG: UserCommunication::SendMessage() - SendMessage() returned with STATUS_TIMEOUT.2015-Mar-11 22:37:31.665 - FileSystemMetadata: [5452].[5276]: ERROR: FileSystemMetadataImpl::LogLoadError() - Failed to load filesystem metadata xml.
    DOM Error: -2147023897
    Reason: Error performing inpage operation.

    Line: 1
    Column: 0
    Offset: 0
    2015-Mar-11 22:37:31.665 - Orchestrator: [5452].[5276]: ERROR: ClientActivity::ExecuteActivity() - Activity VirtualEnvironmentCreated #495 failed on component SubsystemController (error: 1045435397-589825).
    2015-Mar-11 22:37:31.665 - Orchestrator: [5452].[5276]: ERROR: ActivityManagerImpl::RequestActivity() - VirtualEnvironmentCreated activity #495 failed with error code 1435503874-1281.
    2015-Mar-11 22:37:31.696 - VEMgrDrv: [4700].[8752]: ERROR: VirtualEnvironmentManager::VECreatedNotificationUpcall() - VE created notification failed. Package moniker AEF1ABD8-2AC1-4300-856A-31ABBF90D70C_89C14A0A-FB18-4488-A240-368BFAAF3BED. User SID S-1-5-21-38857442-2693285798-3636612711-15060318. Error -1073741823.

    Client-StreamingUX: Event ID 1,80

    An attempt to create the streaming UX process failed. Path = C:\Program Files\Microsoft Application Virtualization\Client\AppVStreamingUX.exe ErrorCode = 10759111679578406914
    An attempt to launch the process is the current user's sesssion failed. ErrorCode = 10759111679578406914

    Seemingly, it's pointing to the FilesystemMetadata.xml file as failing to stream when it errors.  The file in this package is 1,687KB

    Thursday, March 12, 2015 5:06 AM
  • 

    I think I forgot to mention that my infrastructure is also a Shared Content Store.

    If I fully mount the package, FilesystemMetadata.xml will stream, loads and launches without any errors the first time.  So it appears to be with something on how AppV5 SP3 handles shared content store...  I am still suspecting it has to do with the size of the FilesystemMetadata.xml file though.

    Thursday, March 12, 2015 5:22 AM
  • Hello,

    What happens if you try the latest version of the App-V client?

    What happens if you disable SCS?


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

    Thursday, March 12, 2015 10:28 PM
  • What type of networking are you using? Have you checked for dropped packets?


    Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually answer your question). This can be beneficial to other community members reading the thread.


    This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or other MVPs.

    Twitter: @stealthpuppy | Blog: stealthpuppy.com | The Definitive Guide to Delivering Microsoft Office with App-V

    Friday, March 13, 2015 4:54 AM
    Moderator
  • Networking is good, no dropped packets.  The fact that this error is consistent on this one package for every reboot/first launch but not other packages is telling.
    Friday, March 13, 2015 3:55 PM
  • Hello,

    What happens if you try the latest version of the App-V client?

    What happens if you disable SCS?


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

    I will try AppV5 SP3 HF1 later.

    With SCS disabled I can confirm I do NOT get this error.  It only occurs during a SCS enabled first-launch.

    Friday, March 13, 2015 4:36 PM
  • Installed SP3 HF1 and am still encountering the error on first launch.  Definitely seems related to SCS.  Maybe it's some of the new features of SP3 detailed here:

    http://blogs.technet.com/b/gladiatormsft/archive/2015/01/09/app-v-5-on-the-locationprovider-and-the-ignorelocationprovider-feature.aspx

    http://blogs.technet.com/b/gladiatormsft/archive/2014/12/10/app-v-5-on-the-packagesourceroot.aspx

    I'll have to play around with those settings maybe, but again, we publish a couple dozen packages and it's just this one overly large package that has this issue...  Hm.

    Friday, March 13, 2015 10:11 PM
  • Hello,

    So workaround is (obviously) to mount this package, and I would assume that you open a ticket with Microsoft to resolve the error?


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

    Saturday, March 14, 2015 9:10 AM
  • Hello,
    same error popup & events are logged to "Application and Services Logs>Microsoft>AppV" log.

    Content required by an application could not be retrieved from the network. A request for file C:\ProgramData\App-V\7B35353A-304F-4A7E-B7D7-54B9BB5AA063\D647A03D-C5E6-4D3F-B47C-4C71F2B78C48\FilesystemMetadata.xml from package version {00000000-0000-0000-0000-000000000000} failed with error Le fichier spécifié est introuvable..  Check your network connection and try again.

    Environment :
    - 4 RDS 2012 R2 with app-v 5.0 sp3 already installed
    - App-V packages are pushed using SCCM
    - SharedContentStoreMode was always set to 0

    I noticed :

    1/
    - 0x3E501405-0x90001 Error was thrown/popping while trying to launch a remoteApp (witch then fails to start)
    - this happened on only one of the 4 servers of the RDS collection

    2/

    the error shown only when trying to launch that particular app-v package, the other could start with no issue

    3/
    I did 'Repair-AppvClientPackage' on that particular appv pkg
    => it didn't fixed the issue

    Get-AppvClientPackage commandlet returned apps info :
    -
    PercentLoaded  and  Path  parameters took my attention though

    Where :
     
    percent loaded was < 100 %
      => I thought I had to mount it first and started Mount-AppvClientPackage -Name theAppvApp’sName
     but had
    Mount-AppvClientPackage : Application Virtualization Service failed to complete requested operation.
    Operation attempted: Mount Package.
    Windows Error: 0x80070002 - Le fichier spécifié est introuvable
    Error module: Streaming Manager. Internal error detail: 74F02C2C80070002.
    Please consult AppV Client Event Log for more details.
    Au caractère Ligne:1 : 1
    + Mount-AppvClientPackage -Name ESSBase
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidResult : (:) [Mount-AppvClientPackage], ClientException
        + FullyQualifiedErrorId : MountPackageError,Microsoft.AppV.AppvClientPowerShell.MountAppvPackage

    and
    Path was pointing to C:\Windows\ccmcache\m\NameOfTheApp….appv
    => SO I went to that folder and found completely other stuff (Microsoft KBs for .Net…) ?!

    I searched same path for *.appv under one of the other server’s
    c:\windows\ccmcache folder
    and found my package, copied it locally and pushed
    Mount-AppvClientPackage -Name theAppvApp’sName
    again – the mount package operation this time succeeded.

    The application started correctly after that !

    I’m not saying this is ‘THE’ solution but for me it worked.

    Thanks.

     
     


    MCTS Windows Server Virtualization, Configuration

    • Proposed as answer by Yassine Souabni Thursday, March 19, 2015 2:35 PM
    • Unproposed as answer by TrententMVP Monday, March 30, 2015 10:04 PM
    Thursday, March 19, 2015 2:33 PM
  • Hi Nicke,

    I was going to contact Microsoft but I know their first suggestion would be to bring everything up to AppV5SP3 level, so I was going to do that first.  :)

    I had the AppV5 SP3 client installed, but my infrastructure was AppV5 SP1 level. (Database, publishing and management servers).

    Anyways, I've updated the DB to AppV5SP3, then updated the backend to coincide with it, and now my infrastructure is AppV5SP3 level all over.

    And I no longer get this error for the first (or second) launch of an AppV5 SP3 application.

    Funky that the DB/infrastructure update would resolve it as the error doesn't appear to point to it, but I've confirmed it.

    DB update was at 2:00PM my time in the screenshot, infrastructure update completed around 3:00PM, server was rebooted several times which always generated an error message, then server was online around 3:30PM with numerous users launching the application without issue for the first launch.  As you can see, no more error messages after the update.

    • Marked as answer by TrententMVP Monday, March 30, 2015 10:04 PM
    • Unmarked as answer by TrententMVP Tuesday, March 31, 2015 3:40 PM
    Monday, March 30, 2015 10:03 PM
  • Nope...  I take it back...  we are still getting the errors this today.  I will open a call to Microsoft.
    Tuesday, March 31, 2015 3:41 PM
  • Just an update to this case...  

    The original logs are pointing to this cause:

    Bad stream fault message. File name: D:\AppVData\PackageInstallationRoot\AEF1ABD8-2AC1-4300-856A-31ABBF90D70C\89C14A0A-FB18-4488-A240-368BFAAF3BED\FilesystemMetadata.xml, Offset: 0x0 , Length 0x10000, Status 0x102.

    Stream fault failed. File name: D:\AppVData\PackageInstallationRoot\AEF1ABD8-2AC1-4300-856A-31ABBF90D70C\89C14A0A-FB18-4488-A240-368BFAAF3BED\FilesystemMetadata.xml, Offset: 0x0 , Length 0x800, Status 0xc000000d.

    The stream fault fails with a length of 0x800 (2048).

    Procmon reports that the IN PAGE ERROR occurs at 2048 (bytes?)...

    Of all my packages the ones highlighted have exhibit this issue:

    Long story short, size is definitely a factor.  MS is still investigating this internally.

    Friday, July 3, 2015 8:20 AM
  • Hi Trentent, any update to this issue. we have the same error...
    Friday, July 17, 2015 4:02 PM
  • Hi I have a further update.

    I have found I can replicate this issue when launching an application via the /appvve switch or via powershell:

    Start-AppvVirtualProcess -AppvClientObject (Get-AppvClientPackage *APPNAME*) cmd.exe

    If I create a shortcut direct to the .exe with my parameters hard-coded I do NOT get this error.  So, the specific way the *scripted* methods open the virtual environment appear to be causing an issue.  I have confirmed this error exists in 5.1 as well.  5.1 now displays an error message instead of hiding it in the logs.


    Sunday, September 27, 2015 4:55 AM
  • Can I get some clarification - If the package is mounted - does it still reproduce?


    Steve Thomas, Senior Consultant, Microsoft

    App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat

    http://blogs.technet.com/gladiatormsft/
    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 18, 2015 4:44 AM
  • Hi Steve,

    If the package is fully mounted then there is no error.  Issue only occurs with Shared Content Store.

    Trentent

    Monday, October 19, 2015 8:50 PM
  • We are aware of this issue and this is being addressed soon.


    Steve Thomas, Senior Consultant, Microsoft

    App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat

    http://blogs.technet.com/gladiatormsft/
    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.”

    • Marked as answer by TrententMVP Tuesday, October 20, 2015 6:39 PM
    Tuesday, October 20, 2015 2:18 AM
  • Awesome news Steve.  Any timeline?  I imagine as a hotfix for SP1?
    Tuesday, October 20, 2015 6:39 PM
  • Well, I jumped the gun, again.  It is not fixed.  I still have this issue with AppV 5.1 HF1

    I get these messages in the log:

    Log Name:      Microsoft-AppV-Client/Operational
    Source:        Microsoft-AppV-Client
    Date:          12/1/2015 10:24:42 AM
    Event ID:      13003
    Task Category: Application Launch
    Level:         Error
    Keywords:      Virtual Application Launch
    User:          HEALTHY\trententtye
    Computer:      wsctxepic401t.healthy.bewell.ca
    Description:
    C:\Windows\System32\cmd.exe application from package ID {79D156F3-BE65-47B7-BC97-72D5516B02B6} failed to launch. process ID 2392, error 0x55900D02-0x501.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-AppV-Client" Guid="{E4F68870-5AE8-4E5B-9CE7-CA9ED75B0245}" />
        <EventID>13003</EventID>
        <Version>1</Version>
        <Level>2</Level>
        <Task>23</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4000000000100000</Keywords>
        <TimeCreated SystemTime="2015-12-01T17:24:42.727284700Z" />
        <EventRecordID>1118593</EventRecordID>
        <Correlation />
        <Execution ProcessID="5876" ThreadID="6688" />
        <Channel>Microsoft-AppV-Client/Operational</Channel>
        <Computer>wsctxepic401t.healthy.bewell.ca</Computer>
        <Security UserID="S-1-5-21-38857442-2693285798-3636612711-15138285" />
      </System>
      <EventData>
        <Data Name="ProcessName">C:\Windows\System32\cmd.exe</Data>
        <Data Name="Package">{79D156F3-BE65-47B7-BC97-72D5516B02B6}</Data>
        <Data Name="Pid">2392</Data>
        <Data Name="ErrorHigh">1435503874</Data>
        <Data Name="ErrorLow">1281</Data>
      </EventData>
    </Event>

    Log Name:      Microsoft-AppV-Client/Operational
    Source:        Microsoft-AppV-Client
    Date:          12/1/2015 10:24:42 AM
    Event ID:      13003
    Task Category: Application Launch
    Level:         Error
    Keywords:      Virtual Application Launch
    User:          HEALTHY\trententtye
    Computer:      wsctxepic401t.healthy.bewell.ca
    Description:
    C:\Windows\System32\cmd.exe application from package ID {79D156F3-BE65-47B7-BC97-72D5516B02B6} failed to launch. process ID 2392, error 0x3E501405-0x90001.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-AppV-Client" Guid="{E4F68870-5AE8-4E5B-9CE7-CA9ED75B0245}" />
        <EventID>13003</EventID>
        <Version>1</Version>
        <Level>2</Level>
        <Task>23</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4000000000100000</Keywords>
        <TimeCreated SystemTime="2015-12-01T17:24:42.727284700Z" />
        <EventRecordID>1118592</EventRecordID>
        <Correlation />
        <Execution ProcessID="5876" ThreadID="6688" />
        <Channel>Microsoft-AppV-Client/Operational</Channel>
        <Computer>wsctxepic401t.healthy.bewell.ca</Computer>
        <Security UserID="S-1-5-21-38857442-2693285798-3636612711-15138285" />
      </System>
      <EventData>
        <Data Name="ProcessName">C:\Windows\System32\cmd.exe</Data>
        <Data Name="Package">{79D156F3-BE65-47B7-BC97-72D5516B02B6}</Data>
        <Data Name="Pid">2392</Data>
        <Data Name="ErrorHigh">1045435397</Data>
        <Data Name="ErrorLow">589825</Data>
      </EventData>
    </Event>

    Log Name:      Microsoft-AppV-Client/Operational
    Source:        Microsoft-AppV-Client
    Date:          12/1/2015 10:24:42 AM
    Event ID:      23001
    Task Category: Streaming
    Level:         Error
    Keywords:      Streaming
    User:          SYSTEM
    Computer:      wsctxepic401t.healthy.bewell.ca
    Description:
    A timeout occurred while streaming an application, which may have prevented the application from running. The application should start successfully the next time it is launched.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-AppV-Client" Guid="{E4F68870-5AE8-4E5B-9CE7-CA9ED75B0245}" />
        <EventID>23001</EventID>
        <Version>1</Version>
        <Level>2</Level>
        <Task>33</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4000000000040000</Keywords>
        <TimeCreated SystemTime="2015-12-01T17:24:42.727284700Z" />
        <EventRecordID>1118591</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="7148" />
        <Channel>Microsoft-AppV-Client/Operational</Channel>
        <Computer>wsctxepic401t.healthy.bewell.ca</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
      </EventData>
    </Event>

    I also got these messages in the service log:

    Log Name:      Microsoft-AppV-Client/Debug
    Source:        Microsoft-AppV-ServiceLog
    Date:          12/1/2015 10:24:37 AM
    Event ID:      3
    Task Category: Debug AppV Client
    Level:         Information
    Keywords:      Debug Out Messages.
    User:          HEALTHY\trententtye
    Computer:      wsctxepic401t.healthy.bewell.ca
    Description:
    2015-Dec-01 10:24:37.539 - VirtualizationManager: [5876].[6688]: INFO: AppData mapping cofiguration for user S-1-5-21-38857442-2693285798-3636612711-15138285, package 79d156f3-be65-47b7-bc97-72d5516b02b6: mapping target C:\Users\trententtye\AppData\Roaming\Microsoft\AppV\Client\VFS\79D156F3-BE65-47B7-BC97-72D5516B02B6\AppData; local cache C:\Users\trententtye\AppData\Local\Microsoft\AppV\Client\VFS\79D156F3-BE65-47B7-BC97-72D5516B02B6\AppData; need to copy: 1
     [AppV::Client::Virtualization::FolderRedirectionTask::FolderRedirectionTask; 76]
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-AppV-ServiceLog" Guid="{9cc69d1c-7917-4acd-8066-6bf8b63e551b}" />
        <EventID>3</EventID>
        <Version>0</Version>
        <Level>4</Level>
        <Task>1</Task>
        <Opcode>10</Opcode>
        <Keywords>0x8000000000000001</Keywords>
        <TimeCreated SystemTime="2015-12-01T17:24:37.539751500Z" />
        <EventRecordID>236</EventRecordID>
        <Correlation />
        <Execution ProcessID="5876" ThreadID="6688" ProcessorID="3" KernelTime="93" UserTime="26" />
        <Channel>Microsoft-AppV-Client/Debug</Channel>
        <Computer>wsctxepic401t.healthy.bewell.ca</Computer>
        <Security UserID="S-1-5-21-38857442-2693285798-3636612711-15138285" />
      </System>
      <EventData>
        <Data Name="Message">2015-Dec-01 10:24:37.539 - VirtualizationManager: [5876].[6688]: INFO: AppData mapping cofiguration for user S-1-5-21-38857442-2693285798-3636612711-15138285, package 79d156f3-be65-47b7-bc97-72d5516b02b6: mapping target C:\Users\trententtye\AppData\Roaming\Microsoft\AppV\Client\VFS\79D156F3-BE65-47B7-BC97-72D5516B02B6\AppData; local cache C:\Users\trententtye\AppData\Local\Microsoft\AppV\Client\VFS\79D156F3-BE65-47B7-BC97-72D5516B02B6\AppData; need to copy: 1
    </Data>
        <Data Name="Function">AppV::Client::Virtualization::FolderRedirectionTask::FolderRedirectionTask</Data>
        <Data Name="Line">76</Data>
      </EventData>
    </Event>

    Log Name:      Microsoft-AppV-Client/Debug
    Source:        Microsoft-AppV-ServiceLog
    Date:          12/1/2015 10:24:37 AM
    Event ID:      3
    Task Category: Debug AppV Client
    Level:         Error
    Keywords:      Debug Out Messages.
    User:          HEALTHY\trententtye
    Computer:      wsctxepic401t.healthy.bewell.ca
    Description:
    2015-Dec-01 10:24:37.539 - VirtualizationManager: [5876].[6688]: ERROR: AppData download task failed. Error 12330893182463574018; user S-1-5-21-38857442-2693285798-3636612711-15138285; package 79d156f3-be65-47b7-bc97-72d5516b02b6.
     [AppV::Client::Virtualization::VirtualizationManager::HandleVeCreated; 810]
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-AppV-ServiceLog" Guid="{9cc69d1c-7917-4acd-8066-6bf8b63e551b}" />
        <EventID>3</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>1</Task>
        <Opcode>10</Opcode>
        <Keywords>0x8000000000000001</Keywords>
        <TimeCreated SystemTime="2015-12-01T17:24:37.539751500Z" />
        <EventRecordID>237</EventRecordID>
        <Correlation />
        <Execution ProcessID="5876" ThreadID="6688" ProcessorID="3" KernelTime="93" UserTime="26" />
        <Channel>Microsoft-AppV-Client/Debug</Channel>
        <Computer>wsctxepic401t.healthy.bewell.ca</Computer>
        <Security UserID="S-1-5-21-38857442-2693285798-3636612711-15138285" />
      </System>
      <EventData>
        <Data Name="Message">2015-Dec-01 10:24:37.539 - VirtualizationManager: [5876].[6688]: ERROR: AppData download task failed. Error 12330893182463574018; user S-1-5-21-38857442-2693285798-3636612711-15138285; package 79d156f3-be65-47b7-bc97-72d5516b02b6.
    </Data>
        <Data Name="Function">AppV::Client::Virtualization::VirtualizationManager::HandleVeCreated</Data>
        <Data Name="Line">810</Data>
      </EventData>
    </Event>

    Log Name:      Microsoft-AppV-Client/Debug
    Source:        Microsoft-AppV-ServiceLog
    Date:          12/1/2015 10:24:37 AM
    Event ID:      1
    Task Category: None
    Level:         Information
    Keywords:      Debug Out Messages.
    User:          HEALTHY\trententtye
    Computer:      wsctxepic401t.healthy.bewell.ca
    Description:
    2015-Dec-01 10:24:37.727 - StrmDrv: [5876].[6688]: INFO: Reader::ReadFile() - New stream fault requested. File name: D:\AppVData\PackageInstallationRoot\79D156F3-BE65-47B7-BC97-72D5516B02B6\96A8BC01-1610-4157-B256-9C01262983F3\FilesystemMetadata.xml, Offset: 0 , Length 2048, Status 0x00000000.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-AppV-ServiceLog" Guid="{9cc69d1c-7917-4acd-8066-6bf8b63e551b}" />
        <EventID>1</EventID>
        <Version>0</Version>
        <Level>4</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000001</Keywords>
        <TimeCreated SystemTime="2015-12-01T17:24:37.727252700Z" />
        <EventRecordID>249</EventRecordID>
        <Correlation />
        <Execution ProcessID="5876" ThreadID="6688" ProcessorID="3" KernelTime="100" UserTime="30" />
        <Channel>Microsoft-AppV-Client/Debug</Channel>
        <Computer>wsctxepic401t.healthy.bewell.ca</Computer>
        <Security UserID="S-1-5-21-38857442-2693285798-3636612711-15138285" />
      </System>
      <EventData>
        <Data Name="stringValue1">2015-Dec-01 10:24:37.727 - StrmDrv: [5876].[6688]: INFO: Reader::ReadFile() - New stream fault requested. File name: D:\AppVData\PackageInstallationRoot\79D156F3-BE65-47B7-BC97-72D5516B02B6\96A8BC01-1610-4157-B256-9C01262983F3\FilesystemMetadata.xml, Offset: 0 , Length 2048, Status 0x00000000.</Data>
      </EventData>
    </Event>

    Log Name:      Microsoft-AppV-Client/Debug
    Source:        Microsoft-AppV-ServiceLog
    Date:          12/1/2015 10:24:37 AM
    Event ID:      3
    Task Category: Debug AppV Client
    Level:         Information
    Keywords:      Debug Out Messages.
    User:          HEALTHY\trententtye
    Computer:      wsctxepic401t.healthy.bewell.ca
    Description:
    2015-Dec-01 10:24:37.727 - StreamingManager: [5876].[6692]: INFO: Microsoft AppV Streaming Manager StreamFault initiated: Package Version 00000000-0000-0000-0000-000000000000, file D:\AppVData\PackageInstallationRoot\79D156F3-BE65-47B7-BC97-72D5516B02B6\96A8BC01-1610-4157-B256-9C01262983F3\FilesystemMetadata.xml
     [Streaming::StreamingManager<struct strategy::enterprise::streaming_strategy>::StreamFault; 533]
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-AppV-ServiceLog" Guid="{9cc69d1c-7917-4acd-8066-6bf8b63e551b}" />
        <EventID>3</EventID>
        <Version>0</Version>
        <Level>4</Level>
        <Task>1</Task>
        <Opcode>10</Opcode>
        <Keywords>0x8000000000000001</Keywords>
        <TimeCreated SystemTime="2015-12-01T17:24:37.727252700Z" />
        <EventRecordID>250</EventRecordID>
        <Correlation ActivityID="{01B11C58-F800-0003-53BD-9D39502CD101}" />
        <Execution ProcessID="5876" ThreadID="6692" ProcessorID="2" KernelTime="10" UserTime="14" />
        <Channel>Microsoft-AppV-Client/Debug</Channel>
        <Computer>wsctxepic401t.healthy.bewell.ca</Computer>
        <Security UserID="S-1-5-21-38857442-2693285798-3636612711-15138285" />
      </System>
      <EventData>
        <Data Name="Message">2015-Dec-01 10:24:37.727 - StreamingManager: [5876].[6692]: INFO: Microsoft AppV Streaming Manager StreamFault initiated: Package Version 00000000-0000-0000-0000-000000000000, file D:\AppVData\PackageInstallationRoot\79D156F3-BE65-47B7-BC97-72D5516B02B6\96A8BC01-1610-4157-B256-9C01262983F3\FilesystemMetadata.xml
    </Data>
        <Data Name="Function">Streaming::StreamingManager&lt;struct strategy::enterprise::streaming_strategy&gt;::StreamFault</Data>
        <Data Name="Line">533</Data>
      </EventData>
    </Event>

    Log Name:      Microsoft-AppV-Client/Debug
    Source:        Microsoft-AppV-ServiceLog
    Date:          12/1/2015 10:24:37 AM
    Event ID:      3
    Task Category: Debug AppV Client
    Level:         Error
    Keywords:      Debug Out Messages.
    User:          HEALTHY\trententtye
    Computer:      wsctxepic401t.healthy.bewell.ca
    Description:
    2015-Dec-01 10:24:37.727 - StreamingManager: [5876].[6692]: ERROR: Failed to parse uri provider guid, result = -2147023886.
     [AppV::Client::Streaming::SCCMURIConfig::GetConfigURIInterface; 131]
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-AppV-ServiceLog" Guid="{9cc69d1c-7917-4acd-8066-6bf8b63e551b}" />
        <EventID>3</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>1</Task>
        <Opcode>10</Opcode>
        <Keywords>0x8000000000000001</Keywords>
        <TimeCreated SystemTime="2015-12-01T17:24:37.727252700Z" />
        <EventRecordID>251</EventRecordID>
        <Correlation ActivityID="{01B11C58-F800-0003-53BD-9D39502CD101}" />
        <Execution ProcessID="5876" ThreadID="6692" ProcessorID="2" KernelTime="10" UserTime="14" />
        <Channel>Microsoft-AppV-Client/Debug</Channel>
        <Computer>wsctxepic401t.healthy.bewell.ca</Computer>
        <Security UserID="S-1-5-21-38857442-2693285798-3636612711-15138285" />
      </System>
      <EventData>
        <Data Name="Message">2015-Dec-01 10:24:37.727 - StreamingManager: [5876].[6692]: ERROR: Failed to parse uri provider guid, result = -2147023886.
    </Data>
        <Data Name="Function">AppV::Client::Streaming::SCCMURIConfig::GetConfigURIInterface</Data>
        <Data Name="Line">131</Data>
      </EventData>
    </Event>

    Tuesday, December 1, 2015 5:32 PM
  • We are also experiencing this issue. What is interesting is that the "Package ID" and "Version ID" reported in our log is actually a Connection Group, not a Package.

    This is occurring on our largest package.

    Thursday, December 3, 2015 4:43 PM
  • hi, do you know if it was fixed with hotfix 2 by any chance?

    thanks

    Thursday, February 25, 2016 7:31 PM
  • I have not had the opportunity to test 5.1HF2 yet due to other issues that prevent us from moving forward with it.  I will test it and update here once I get a chance.
    Wednesday, March 2, 2016 9:27 PM
  • I can confirm this issue still exists with AppV 5.1HF2, again, only with SCS.

    Our solution thus far, is to have a prelaunch script 'start' the application, check to see if it's started and if not, restart it.

    :STARTAPP
    START "" C:\<path to application>\App.exe
    
    ping 127.0.0.1 -n 5 >NUL
    tasklist /fi "username eq %username%" | findstr /i /c:"app.exe"
    if [%ERRORLEVEL%] EQU [1] GOTO STARTAPP

    The issue we have with this check is that it's very CPU expensive when you have a lot of processes.  Fortunately, our PROD environment is full mount so we check the %COMPUTERNAME% to see if it's a prod system so we don't have to run this.

    The application, per the issue, restarts without issue when executed the second time.

    Thursday, April 14, 2016 3:12 AM
  • Can anyone confirm if this is fixed in the latest hotfix (hotfix 3 or 4 / 5.1.104 / 5.1.106)? 
    Wednesday, June 29, 2016 2:04 PM
  • This still happens in HF3.  I have not tried HF4.

    Wednesday, June 29, 2016 2:07 PM
  • Same issue here with the June 2016 servicing release (which I assume is HF4, it's the latest version).

    We have a connection group with several small Office add-ins which works fine, however, whenever I add the SAP client to that group (which is ~1 GB in size) then suddenly this error starts popping up. We run these add-ins using RunVirtual on locally installed applications. Now whenever a user logs on to our XenApp environment Outlook 2013 automatically launches which is when the error pops up and Outlook fails to start. If the user then manually clicks on the Outlook icon it will launch without any issues so it looks like some timing issue where App-V is not ready yet and the application already wants to start.

    This is indeed with SCS mode only, this does not happen when you mount the package but that kinda destroys the entire purpose of App-V 5 especially on our provisioned servers so that's no option.

    We get the error on the connection group as well, not on the package. If I remove the SAP package everything is fine again. I also did a full package cleanup, manually removing all unwanted files and registry entries from the package but it still fails. Anyway size has definitely to do with it I'm sure.

    Next step I'll try is to sequence SAP using PVAD, see if that makes any difference.

    Update: If I  enable the debug logs it shows this error:

    2016-Sep-01 13:21:46.982 - StreamingManager: [4304].[4532]: ERROR: Failed to parse uri provider guid, result = -2147023886.
     [AppV::Client::Streaming::SCCMURIConfig::GetConfigURIInterface; 131]


    2016-Sep-01 13:11:15.600 - VirtualizationManager: [4304].[4572]: ERROR: AppData download task failed. Error 12330893182463574018; user S-1-5-21-1294535232-1600342054-1232828436-26805; package 977c4946-3c4f-4c4f-b07f-d6a860546955.
     [AppV::Client::Virtualization::VirtualizationManager::HandleVeCreated; 810]

    The GUID matches the user getting the error, the package ID is the connection group. I will try to get rid of the Appdata from the SAP package and try again

    Thursday, September 1, 2016 11:10 AM