Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Backup failed due to unexpected error on the server when calling an API RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
     The scheduled backup of my client pc failed with the following (from the Windows Home Server Console) Failure Detail for Volume (Local Disk):

    An unexpeced error occurde on the server when calling an API.
    IEnumWbemClassObject::Next
    -2147221163

    There are two volumes on the client pc to be backed up.
    The WHS has 4 identical SAMSUNG HD103UJ (1TB) disks, and they are reported healthy in the WHS Console | Server Storage.

    Backup has been working fine for a month or so. When noticing the error message, I tried to run the backup manually but it failed with the same error message:

    Backup starts with determining changed files and clsuters on one of the drives. At 2% completion it says "The backup failed because of a problem with Windows Home Server software. The event log on the server contains more details."

    I rebooted the WHS and startet the backup from the WHS Connector tray icon. Same result and same error message.
    I suspected the error to occur after a security update from Microsoft which arrived and was installed a few hrs before the problem started. I removed the last pack of security updates on the client pc and retried the backup. Same result. Security updates are now installed again.
    A tip from a user at We Got Served suggested that the error message could be related to the disk at the client pc. I ran the chdsk utility but it did not report any issues. The scheduled backup which ran after the chkdsk did also fail.

    Any ideas where to continue next? Are there any alternatives to the chkdsk utility?

    soe




    Friday, December 12, 2008 7:09 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Problem solved!

    With help from Olaf I dived into the Event log of the WHS.

    Found this reference several times: Unexpected error 0x80040155 from IEnumWbemClassObject::Next: Interface not registered

    I googled the 0x80040155 and arrived at this article:
    http://support.microsoft.com/kb/318956/en-us

    Followed the instruction in the article and ran the batch file which registered the dll's, and presto. Last night's scheduled backup went as planned.
    • Marked as answer by me.soe Tuesday, December 16, 2008 9:34 PM
    Tuesday, December 16, 2008 9:32 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Soe,
    to take a look into the event log of your home server, you need to log in locally or via Remote Desktop to the home server.
    Use account name Administrator and the console passwort to get access to the server desktop.
    Click on Start/Control Panel/Administrative Tools/Event Viewer.
    Check the logs especially for red and yellow messages during the time of the backup failure.
    Be also aware, that the console may still think the disks are ok, if one is already affected by faulty sectors. Such details you will find in the vent log.
    Sometimes a backup failure can be caused by the client as well, so maybe check it's event log too.
    Best greetings from Germany
    Olaf
    Friday, December 12, 2008 7:13 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Olaf, thanx.

    Did a check in teh event log and, yes, there are lots of messages both red and yellow ones..

    I found these connected to the last manual backup:

    Date 12.12.2008 19:57:00, Category: Backup
    Backup of SOE E:\ has started.

    Date 12.12.2008 19:57:38, Category: Backup
    Unexpected error 0x80040155 from IEnumWbemClassObject::Next: Interface not registered

    Date 12.12.2008 19:57:38, Category: Backup
    Client Backup server failed at d:\wssg_src\whs_pp1\qhs\src\backup\util\sort.cpp(500)

    I don't know if this is useful.

    Friday, December 12, 2008 7:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Soe,
    what happens, if you exclude E: from the backup? Is that an external drive? Those seem to make trouble sometimes.

    Searching for your error in the Web gives a lot of hits, often related to some not registered DLLs.

    In the event log, are there also DCOM errors?
    If we see those, check for details. Usually they have a long key in {} brackets. For this key you can search in the registry of your WHS to see, which service or file is behind it.
    Knowing this, you could adjust the necessary permissions in the DCOM configuration on the server.

    Best greetings from Germany
    Olaf
    Friday, December 12, 2008 9:08 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi again,

    I removed the E-drive from the backup job and had a go. Same problem only now the disk being examined is the C-drive.

    Will dig into the event log tomorrow and look for the DCOM errors as you suggest.

    Regards from Oslo, Norway

    soe
    Friday, December 12, 2008 10:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Problem solved!

    With help from Olaf I dived into the Event log of the WHS.

    Found this reference several times: Unexpected error 0x80040155 from IEnumWbemClassObject::Next: Interface not registered

    I googled the 0x80040155 and arrived at this article:
    http://support.microsoft.com/kb/318956/en-us

    Followed the instruction in the article and ran the batch file which registered the dll's, and presto. Last night's scheduled backup went as planned.
    • Marked as answer by me.soe Tuesday, December 16, 2008 9:34 PM
    Tuesday, December 16, 2008 9:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have tried everthing I can find in all the forums and knowledges bases and I still can't backup one of my clients.  I am running PP1 on WHS and the client is Windows XP SP3.  I get the following errors in the event log.  If anyone has any other ideas, I would appreciate it.

    Source:  VSS
    Event ID:  12289
    Volume Shadow Copy Service error: Unexpected error CreateFileW(\\?
    \Volume{672f96d8-b460-11db-93c0-
    806d6172696f},0xc0000000,0x00000003,...).  hr = 0x80070005.

    Source:  VSS
    Event ID:  5013
    Volume Shadow Copy Service error: Shadow Copy writer
    RemovableStorageManager called routine OpenNtmsSessionW which
    failed with status 0x80070015 (converted to 0x800423f3).

    Source:  HomeServer
    Event ID:  771
    Backup of volume C: to STEUVERHSVR started.

    Source:  HomeServer
    Event ID:  773
    Backup of volume C: to STEUVERHSVR failed:
    Microsoft.HomeServer.Backup.NTFS.NtfsReaderException:
    FileRecord 118620 has an invalid magic number
       at Microsoft.HomeServer.Backup.NTFS.FileRecord..ctor(Byte* pData, Volume volume, Int64 index, Boolean inUse)
       at Microsoft.HomeServer.Backup.NTFS.FileRecordReader.Next()
       at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.DoFileRecordPass()
       at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.RunWithoutCatch()
       at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.Run()

    Source:  HomeServer
    Event ID:  770
    Backup set 25 on STEUVERHSVR failed:
    Microsoft.HomeServer.Backup.NTFS.NtfsReaderException:
    FileRecord 118620 has an invalid magic number
       at Microsoft.HomeServer.Backup.NTFS.FileRecord..ctor(Byte* pData, Volume volume, Int64 index, Boolean inUse)
       at Microsoft.HomeServer.Backup.NTFS.FileRecordReader.Next()
       at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.DoFileRecordPass()
       at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.RunWithoutCatch()
       at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.Run()
       at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.RunWithoutCatch()
       at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.Run()



    Thomas Steuver
    Wednesday, December 17, 2008 1:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Thomas,
    are there any other errors or warnings in the event log of the client?
    Is there any external disk attached to that client?
    Did you run chkdsk /f /r on each of the client disks to fix potential file system errors and discover damaged sectors, if there are any?

    Please try also, to reregister the VSS components, as outlined in this thread.
    Best greetings from Germany
    Olaf
    Wednesday, December 17, 2008 2:21 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Olaf,

    Those are the only event logs on the client at the time of the backup.
    Both drives are internal drives.
    I ran chkdsk /f /r several times on both drives.
    I did the reregister before I submitted the last post.

    Thanks,
    Tom

     

    Thomas Steuver
    Wednesday, December 17, 2008 3:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Thomas,
    do you have any other imaging software installed on that client?
    I have seen Symantec Ghost (after uninstall) leaving some remains in the registry, effectively blocking the creation of shadow copies.

    Maybe you can try to disable all unnecessary startup programs and services (besides connector, of course):
    • Click Start/Run and type msconfig. Click OK.
    • On the Services tab, click Hide All Microsoft Services and then Disable All. (This may also disable your Virus scanner temporary.)
    • In the Startup tab, click Disable All. Click OK. (This will temporarily prevent third-party programs from running automatically during start-up.) 
    • Check the Connector again if you wish to keep it start automatically.
    • Restart the computer and check whether the problem still persists by running a manual backup. 
    If the problem does no longer occur, it indicates that the problem is related to one application or service you have disabled. You can use the MSCONFIG tool again to re-enable the disabled items one by one (or group wise like Services first) to find out the causing application.

    Some more troubleshooting steps for VSS can also be found here.

    Best greetings from Germany
    Olaf
    Wednesday, December 17, 2008 7:21 PM
    Moderator