locked
WHS backup failure RRS feed

  • Question

  • I have four computers connected to my WHS.  When I try to backup any of them I get an error message.  An unexpected error occured on the server when call API.IEnum When Class Object:: Next -2147221164.  When I run trouble shooter it tell me my connector does not match what is on the machines and what is on the server.  I have tried to delete connector, but it will not delete.
    Where can I go for help.
    Wednesday, January 14, 2009 7:04 PM

Answers

  • Hi,
    please run chkdsk /f /r on the client disks (or as a first attempt only on one volume and exclude the other volumes from backup).
    I'm not sure, what the GUIDs in the event log are standing for (i.e. {97735c58-7a7b-43fc-b433-a9f37a1acfb2}). Could be voume GUIDs or something else. If something else, search the clients registry for it and figure out, what is behind it. (I had similar experiences with remains of Norton Ghost in the past.)

    Other than that, reregistering the VSS components on the client as described in this thread could help you also to fix the behavior.
    Best greetings from Germany
    Olaf
    Saturday, January 31, 2009 10:48 PM
    Moderator

All replies

  • Did you try a reboot of the server already?
    Can you log in to your server locally or via Remote Desktop and check the event log for errors and warnings, which may be related?

    When I run trouble shooter it tell me my connector does not match what is on the machines and what is on the server.
    This is a bug since the November upgrade, because not all WHS components got the updated version number and te troubleshooter seems to assume that all components need to have identical numbers.

    Best greetings from Germany
    Olaf
    Wednesday, January 14, 2009 11:03 PM
    Moderator
  • I ran the trouble shooter and it told me the version on the server and the version on the computer did not match.  I uninstalled the computer versio and installed the one in Home Server Software.  Ran trouble shooter again and still recieved the same message.  The version on the server ends in .0 and the version on the computer ends in .12
    Monday, January 26, 2009 4:33 PM
  •  Woody47, I have been experiencing the same issue with two of my computers and believe in my case the issue was with running Mozy (remote backup service) from the workstations.  I turned off the functionality and now the one machine has had no issues, my other machine still has the issue and I am leaning towards it has something to do with my windows workstation settings were I put the computer into hibernate mode.  Going to turn that off and see if I can get reliable daily backups.

    Tom

     

    Monday, January 26, 2009 6:05 PM
  • Hi,

    maybe the Troubleshooter issue was already there with every update after Power Pack 1.
    The most current version of WHS should have the end number .24 for 3 of the 5 components.

    As Tom said, sometimes 3rd party software (security suites, disk cloning software etc) may also interact with the WHS services in a bad way.
    So what about the event logs on client and server?

    Best greetings from Germany
    Olaf

    Monday, January 26, 2009 6:35 PM
    Moderator
  • So have you performed a new install of the connector software that is located on the server in the Software folder? Use a browser to navigate to your home server and download the Connector software to the client.

    I have four computers running myself with no issues on any of them and they are all running the exact same version numbers. Installing from the Home Connector disk is fine the first time, but once you install PP1 then you should install from the server instead to avoid issues or having to do the same thing twice.


    PACS Technical Support Engineer
    Tuesday, January 27, 2009 3:24 AM
  • I am getting closer.  My personal machine has now been backing up without any issues after stopping the mozy service.  My other computer was getting the snapshot error a day later.  I removed the Dell support tools and the backup would run without having to run a chkdsk /f/r.  I'll get back to you in a couple of days with my results.

    Tom

    Wednesday, January 28, 2009 9:04 PM
  • OK, I give up.  I get the computer to backup for a day or 2 and then the snapshot errors.  Open to any suggestions.
    Saturday, January 31, 2009 7:36 PM
  • Tom,

    If you are having to run chkdsk prior to being able to get a backup to run, it would indicate a drive problem.
    It could be worthwhile running with the '/v' switch - this will give you a report of what it's doing.
    Also, what do the Client logs show at that point of failure?

    Colin

    If anyone answers your query successfully, please mark it as 'Helpful', to guide other users.
    Saturday, January 31, 2009 8:03 PM
    Moderator
  • I can run the chkdsk with the /v option but the thing that bothers me is that this is happening on 2 separate computers (1 dell and 1 home built and each have different hard drives.).  Having a problem believing that both drives are bad.  One other thing to point out is that I can reboot the computer and then run a manual backup with no issues.  Then the nightly will run and may go for one more day at best.  Anyway, here is what I can see in the logs from my computer.:


    Backup set 14 on WALL-E failed: Microsoft.HomeServer.Backup.VSS.ShadowVolumeException: VSS Operation timed out ---> System.TimeoutException: VSS Operation timed out
       at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet.Wait(IVssAsync va)
       at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet.CreateShadowVolume(VolumeInfo[] volumes)
       --- End of inner exception stack trace ---
       at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet.CreateShadowVolume(VolumeInfo[] volumes)
       at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet..ctor(VolumeInfo[] volumes)
       at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.RunWithoutCatch()
       at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.Run()

    Here are some VSS errors that I see:
    Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details PreFinalCommitSnapshots({97735c58-7a7b-43fc-b433-a9f37a1acfb2}, 1) [hr = 0x8000ffff].

    Operation:
       Executing Asynchronous Operation

    Context:
       Current State: DoSnapshotSet

    Log Name:      Application
    Source:        VSS
    Date:          1/30/2009 1:52:05 AM
    Event ID:      12293
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Hudson-Hornet
    Description:
    Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details PreFinalCommitSnapshots({c55a3e62-99e5-449b-8141-c53c9ecb001c}, 1) [hr = 0x8000ffff].

    Operation:
       Executing Asynchronous Operation

    Context:
       Current State: DoSnapshotSet
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="VSS" />
        <EventID Qualifiers="0">12293</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-01-30T06:52:05.000Z" />
        <EventRecordID>4362</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Hudson-Hornet</Computer>
        <Security />
      </System>
      <EventData>
        <Data>{b5946137-7b9f-4925-af80-51abd60b20d5}</Data>
        <Data>PreFinalCommitSnapshots({c55a3e62-99e5-449b-8141-c53c9ecb001c}, 1)</Data>
        <Data>0x8000ffff</Data>
        <Data>

    Operation:
       Executing Asynchronous Operation

    Context:
       Current State: DoSnapshotSet</Data>
        <Binary>2D20436F64653A20434F52534E50534330303030313233362D2043616C6C3A20434F52534E50534330303030313131372D205049443A202030303030333138342D205449443A202030303030353934342D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E5420415554484F524954595C53595354454D20202020202D205369643A2020532D312D352D3138</Binary>
      </EventData>
    </Event>


    I did have mozy installed on the computer and am wondering if that is connected to the issue.  I turned off the service and and now going to fully un-install the application.  Mozy is the common thread from both computers.

    Thanks for anyhelp you can give.

    Tom

    Saturday, January 31, 2009 8:38 PM
  • Tom,

    There is something interfering with the VSS service on the Client. Whether that is Mozy or not I don't know.
    However, the majority of these backup offerings along with quite a few disk manipulation programs like Acronis etc., can definitely cause problems.
    Personally, I would uninstall any tools like that, and have another trial.

    Good luck,

    Colin


    If anyone answers your query successfully, please mark it as 'Helpful', to guide other users.
    Saturday, January 31, 2009 8:49 PM
    Moderator
  • Hi,
    please run chkdsk /f /r on the client disks (or as a first attempt only on one volume and exclude the other volumes from backup).
    I'm not sure, what the GUIDs in the event log are standing for (i.e. {97735c58-7a7b-43fc-b433-a9f37a1acfb2}). Could be voume GUIDs or something else. If something else, search the clients registry for it and figure out, what is behind it. (I had similar experiences with remains of Norton Ghost in the past.)

    Other than that, reregistering the VSS components on the client as described in this thread could help you also to fix the behavior.
    Best greetings from Germany
    Olaf
    Saturday, January 31, 2009 10:48 PM
    Moderator