Problems with VHD resurfacing RRS feed

  • Question

  • I am running Server 2008r2 serving up published desktops to multiple users.

    I am using an application called FSLogix to Mount and dismount VHD files for each user. The files are stored on Server 2012r2 file cluster.

    When the cluster fails over, the 2008r2 Server looses connection to the VHD. This is recorded in the VHDMP log as a Failed surface event (event 3). When the cluster finishes failing over, sometimes the VHD will resurface automatically with-in 10 minutes, other times the VHD will fail to resurface with event 4 (attempt cancelled)

    Log Name:      Microsoft-Windows-VHDMP/Operational
    Source:        Microsoft-Windows-VHDMP
    Date:          5/4/2017 3:27:56 PM
    Event ID:      4
    Task Category: None
    Level:         Error
    User:          SYSTEM
    Computer:      tst-xd-desks-01.crcnet.crc
    Failed to surface VHD \\devxdprofiles\profiles\S-1-5-21-2222050994-748329336-4036839477-1389_DPBrant\Profile_DPBrant.vhd. Surface attempt was cancelled.
    Event Xml:
    <Event xmlns="">
        <Provider Name="Microsoft-Windows-VHDMP" Guid="{E2816346-87F4-4F85-95C3-0C79409AA89D}" />
        <TimeCreated SystemTime="2017-05-04T20:27:56.486633200Z" />
        <Correlation />
        <Execution ProcessID="4" ThreadID="180" />
        <Security UserID="S-1-5-18" />
        <Data Name="VhdFileName">\\devxdprofiles\profiles\S-1-5-21-2222050994-748329336-4036839477-1389_DPBrant\Profile_DPBrant.vhd</Data>
    - System
    - Provider
    [ Name] Microsoft-Windows-VHDMP
    [ Guid] {E2816346-87F4-4F85-95C3-0C79409AA89D}
    EventID 4
    Version 0
    Level 2
    Task 0
    Opcode 0
    Keywords 0x8000000000000000
    - TimeCreated
    [ SystemTime] 2017-05-04T20:27:56.486633200Z
    EventRecordID 15
    - Execution
    [ ProcessID] 4
    [ ThreadID] 180
    Channel Microsoft-Windows-VHDMP/Operational
    Computer tst-xd-desks-01.crcnet.crc
    - Security
    [ UserID] S-1-5-18
    - EventData
    VhdFileName \\devxdprofiles\profiles\S-1-5-21-2222050994-748329336-4036839477-1389_DPBrant\Profile_DPBrant.vhd

    When I investigated the error, the recommendation was to look at the offending PID for the cause, but each time VHD fails it references a different process.

    I am struggling to figure out why it works sometimes but fails in other instances. Are there any registry entries to handle timeouts and reconnections?

    Any insight into this process is appreciated.

    • Edited by Derek Benak Friday, May 5, 2017 3:09 PM grammar fix
    Friday, May 5, 2017 3:08 PM