locked
Every single client backup attempt fails RRS feed

  • Question

  • Quote

     Backup Did Not Complete Because A Problem Interrupted The Connection

     

    That's all it ever says.  Sometimes it gets to 2%, sometimes it gets to 82%, but in dozens of tries over the past two weeks, not a single backup has ever succeeded.

     

    I have an Acer EasyStore h340. It used to run Windows Home Server 2003 (v1). I had a crash on my Win 7 client PC and restored from backup on this server, and everything was peachy. Except, I couldn't backup the client any more. It kept saying the connection to the server was interrupted, even though both are hardwired to the same router (Linksys WRT54G running DDWRT), and I sat and watched both the client and the server (via remote desktop) to make sure none of them slept, hibernated, or lost connection to the network at anytime.  I ran chkdsk on every hard drive on both the client and server, and everything came back perfect.

     

    I followed every "Help" guide I could find for fixing this in WHSv1, including uninstalling / reinstalling .NET frameworks. Eventually, I gave up and decided I should just reformat and reinstall. So I bought a new HDD, installed Windows Home Server 2011 (yeah, upgraded the OS) and fully updated it. I've tried to backup the client again, and it failed for the same reason.  I noticed (don't know why I didn't know this ahead of time) that my client partitions are GPT, not MBR, so I found and applied the hotfix to WHS2011, removed my computer from the Dashboard, and rebooted.  I uninstalled the Connector software from the client, rebooted, and went through the /connect process again.

     

    Same thing.  Nothing changed.

     

    Here are the two client Error Events that are logged whenever the backup fails:

     

    Quote

     Log Name:      Application
    Source:        Application Error
    Date:          7/11/2015 11:15:26 PM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      TONGA.WORKGROUP.local
    Description:
    Faulting application name: SharedServiceHost.exe, version: 6.1.1839.0, time stamp: 0x4d38a956
    Faulting module name: guard64.dll, version: 8.2.0.4591, time stamp: 0x55719f78
    Exception code: 0xc0000409
    Fault offset: 0x0000000000002cc1
    Faulting process id: 0x8c8
    Faulting application start time: 0x01d0bc65e8977a36
    Faulting application path: C:\Program Files\Windows Server\Bin\SharedServiceHost.exe
    Faulting module path: C:\Windows\system32\guard64.dll
    Report Id: 6273f784-285d-11e5-9420-f46d04e4bf5e
    Event Xml:
    <Event xmlns="REDACTED">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-07-12T06:15:26.000000000Z" />
        <EventRecordID>11327</EventRecordID>
        <Channel>Application</Channel>
        <Computer>TONGA.WORKGROUP.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>SharedServiceHost.exe</Data>
        <Data>6.1.1839.0</Data>
        <Data>4d38a956</Data>
        <Data>guard64.dll</Data>
        <Data>8.2.0.4591</Data>
        <Data>55719f78</Data>
        <Data>c0000409</Data>
        <Data>0000000000002cc1</Data>
        <Data>8c8</Data>
        <Data>01d0bc65e8977a36</Data>
        <Data>C:\Program Files\Windows Server\Bin\SharedServiceHost.exe</Data>
        <Data>C:\Windows\system32\guard64.dll</Data>
        <Data>6273f784-285d-11e5-9420-f46d04e4bf5e</Data>
      </EventData>
    </Event>

     

     

    Quote

     Log Name:      System
    Source:        Service Control Manager
    Date:          7/11/2015 11:15:26 PM
    Event ID:      7031
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      TONGA.WORKGROUP.local
    Description:
    The Windows Server Client Computer Backup Provider Service service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 30000 milliseconds: Restart the service.
    Event Xml:
    <Event xmlns="REDACTED">
      <System>
        <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
        <EventID Qualifiers="49152">7031</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2015-07-12T06:15:26.923522700Z" />
        <EventRecordID>17120</EventRecordID>
        <Correlation />
        <Execution ProcessID="688" ThreadID="3016" />
        <Channel>System</Channel>
        <Computer>TONGA.WORKGROUP.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">Windows Server Client Computer Backup Provider Service</Data>
        <Data Name="param2">1</Data>
        <Data Name="param3">30000</Data>
        <Data Name="param4">1</Data>
        <Data Name="param5">Restart the service</Data>
      </EventData>
    </Event>

     

     

     

    I'm completely lost.  I've tried everything I can think of, followed every "How To" guide that I've found, and nothing is making the least bit of difference.  It seems evident that the problem is with the client PC, but I can't figure out what it could possibly be.  What more can I check?



    Monday, July 13, 2015 5:35 AM

Answers

  • Just a thought: I see that guard64.dll is mentioned in the first error entry. This seems to be a component of Comodo firewall. Perhaps you could disable or uninstall it temporarily and/or replace it with the Windows firewall. Maybe there's an incompatibility between WHS and Comodo.

    Don

    • Marked as answer by Olaf Engelke Wednesday, July 22, 2015 12:43 PM
    Monday, July 13, 2015 1:37 PM

All replies

  • Just a thought: I see that guard64.dll is mentioned in the first error entry. This seems to be a component of Comodo firewall. Perhaps you could disable or uninstall it temporarily and/or replace it with the Windows firewall. Maybe there's an incompatibility between WHS and Comodo.

    Don

    • Marked as answer by Olaf Engelke Wednesday, July 22, 2015 12:43 PM
    Monday, July 13, 2015 1:37 PM
  • I disabled Comodo and ran again with the same errors.  I can see in the Process Tree though that it leaves two active processes:  cavwp.exe  and  cmdagent.exe    I'm unsure how to kill these processes (as I'm disallowed in the Task Manager and the Services panel both).  I'll try uninstalling later, just to see.
    Monday, July 13, 2015 4:49 PM
  • Well, if guard64.dll is still showing up in the error log, then it wasn't disabled.  It'll be interesting to see your results after uninstalling Comodo.

    Don

    Monday, July 13, 2015 6:02 PM
  • Lo and Behold!  I completely uninstalled Comodo (only way to disable it, it seems) and the first backup completed successfully!  First time in two months!

    Now that I know that Comodo is the beast causing the problem, I'll see what I can suss out there.  If it comes down to it, I guess I'll rely on Windows Firewall (but I really do prefer Comodo).  Thoughts?

    Monday, July 13, 2015 8:31 PM
  • FWIW, I have only ever used Windows firewall in addition to my FiOS modem/router's firewall and haven't had any problems.

    Don

    Monday, July 13, 2015 8:44 PM
  • Comodo Firewall v5.3 doesn't seem to have this issue.  I successfully completed two backups with this version installed.

    Thanks for your help!

    Monday, July 13, 2015 10:19 PM
  • Comodo firewall v8.2 looks like the latest version.  Is there a reason that you're using such an earlier version?  What version were you using when WHS failed?

    Don

    Monday, July 13, 2015 11:46 PM