Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Client Backup server failed PP3 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Every time I try to backup any PC (Vista Home and 7), I get the following errors in the event log on the server running Windows Home Server with Power Pack 3.

    Unexpected error 0x80041014 from IWbemLocator::ConnectServer: Unknown error 0x80041014

    Client Backup server failed at d:\wssg_src\whs_pp3\qhs\src\backup\util\sort.cpp(471)



    I ran chkdsk /x /r on the client computers and they booted normally.

    I ran the following on the home server and saw no errors in the event log.

    net stop pdl
    net stop whsbackup
    chkdsk D: /x /r 
    chkdsk C: /x /r
    for /d %%1 in (C:\fs\*) do start chkdsk /x /r %%1

    Can someone help me?  I was unable to find the feedback link on Connect, so did not file the bug there.
    Saturday, February 6, 2010 5:03 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    A damaged WMI repository can cause all kind of hassles, so this can or can not have to do with the failing backups. In this thread I described just a few days ago how I did repair this on my own WHS.
    Best greetings from Germany
    Olaf
    Sunday, February 7, 2010 4:02 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Did the server perform unexpected reboots?
    A corrupted backup database could be the reason for the behavior, especially if the backup was functioning well before.
    You can also try to delete the backup database and start from the scratch, since repairing a once corrupt backup database often does not work well.
    Best greetings from Germany
    Olaf
    Saturday, February 6, 2010 5:22 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for the response.  Yes, there was a power failure.

    Are there steps to delete the backup database and start from scratch?

    When I run repair on the Database everything completes successfully, but when I run Cleanup Now, I get the exact same errors listed above.
    Saturday, February 6, 2010 6:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    On the server open a command prompt.
    Enter following commands:
    net stop pdl
    net stop whsbackup
    d:
    cd  \folders\{00008086-058D-4C89-AB57-A7F909A47AB4}
    del *.*

    (You can also perform the deletion of all files in that folder from Windows Explorer after stopping the mentioned services, if you are not so sure about the command prompt.)
    After completing the deletion (ensure that no files did remain in the folder) restart either the services or the server.

    Good luck
    Olaf
    Saturday, February 6, 2010 8:39 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Ok, did that.  Restarted the server, went back into the Console.  Verified that there were no longer any backups under View Backups and clicked Backup Now.  Made it to 2% (same as before) and stopped.  Logged same errors to the HomeServer event log.

    The Application log shows the following every time this fails.

    Faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x000635d7.


    Any other ideas?

    Thanks
    Saturday, February 6, 2010 9:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,
    bad to hear that.
    2% is very early in the process. Did you check also the client event log for related error messages? (Although a failing shadow copy or a firewall issue on the client should not let whsbackup crash.)
    Did you also verify, that the folder was empty after deleting the files? Sometimes tombstones are surviving a normal deletion.
    The version number of WHS is 6.0.2423.0?

    Best greetings from Germany
    Olaf

    Saturday, February 6, 2010 11:21 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    When I click on Backup Details, the client says "An unexpected error occured on the server when calling an API.  IWbemLocator::ConnectServer".

    Yes, I verified the folder was empty and that there were no hidden/system files in there.

    That's the version number given in the event log, so I assume so.

    I'm not sure what else I can do at this point except get an external hard drive, copy all of my shared files to it, and reinstall WHS, but at that point I don't know how I can prevent this from happening again.  Is there a way to repair WHS while keeping all of the files I have in my shared folders in tact?

    Thanks again.
    Saturday, February 6, 2010 11:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Some other errors showing up in the event log...

    WinMgmt could not open the repository file. This could be due to insufficient security access to the "<%SystemRoot%>\System32\WBEM\Repository", insufficient disk space or insufficient memory.

    Fault bucket 1579504027.


    and every minute CqvSvc.exe gives me the follwing warning...

    Exception occurred: System.Management.ManagementException

    Message: Initialization failure

     


    I don't know if these were happening before I lost the ability to back up.

    Sunday, February 7, 2010 12:28 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    A damaged WMI repository can cause all kind of hassles, so this can or can not have to do with the failing backups. In this thread I described just a few days ago how I did repair this on my own WHS.
    Best greetings from Germany
    Olaf
    Sunday, February 7, 2010 4:02 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Olaf, I also have the Scaleo.  I created and ran the cmd file on the server.  When it rebooted, I got the following errors in the event log and after an hour the CqvSvc.exe warnings remain.

    Failed to load MOF C:\WINDOWS\SYSTEM32\INETSRV\ASP.MFL while recovering repository file.

    Failed to load MOF C:\WINDOWS\SYSTEM32\INETSRV\IISADMIN.MFL while recovering repository file.

    Failed to load MOF C:\WINDOWS\SYSTEM32\INETSRV\W3CORE.MFL while recovering repository file.

    Failed to load MOF C:\WINDOWS\SYSTEM32\INETSRV\W3DT.MFL while recovering repository file.

    Failed to load MOF C:\WINDOWS\SYSTEM32\INETSRV\W3ISAPI.MFL while recovering repository file.



    Are these errors something I need to worry about?  It appears the backup is running now, as it has now reached 18%.  I am also having another problem, where my Photos folder on the server keeps going in and out (losing and regaining access to) from the client computer.  All of the other folders (Music, Videos, etc) maintain access.  I can mark your previous post as Answer, but I'd like to know if you have any ideas on the Photos folder problem.  I did confirm File and Printer sharing is on on the client computer and I can always log in to the server and view all of the files in the photos folder.

    Thanks,
     Steve from Texas
    Sunday, February 7, 2010 7:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Steve,
    I cannot see any of the mentioned errors in my machine. They all look attached to Internet Information Services - so if Remote Access, access to the WHS internal website or the installation of the Connector software do not work properly, we would have to investigate further. Are the files available in the folder C:\WINDOWS\SYSTEM32\INETSRV on the server?

    Jumping access only from one client and only for the fotos folder sounds strange. If it would be other shares as well to which you loose temporary access I would assume a locked user account, which can happen, if a client stored that user account for accessing the server with a wrong password (Start/Run keymgr.dll) or if another client uses the same user name with a different password.
    Did you enable the guest account on the server? If so, it is recommended to disable it.

    Best greetings from Germany
    Olaf
    Sunday, February 7, 2010 9:25 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yep, all files are in the INETSRV folder.  I won't worry about it for now.  I may end up rebuilding the server once I get an external drive big enough to copy my shared files to.  I guess these little things don't handle power outages too well.  Thanks for your help.
    Monday, February 8, 2010 1:31 AM