Asked by:
Backup Error

Question
-
Hello: My XP client had been backing up just fine and then several weeks ago stopping backing up. The client error says there's a problem with the connector software; when I go into the console and click on the failed backup details, it says there was a problem reading or writing from server storage. I also just bought a vista laptop, and successfully installed the connector software, but it too failed to backup. I have no problems reading or writing to the shared folders, and everything else seems to work fine.Reading these forums, I'm having trouble understanding where to begin and how to correct this. I tried wiping out all my backups, clean up, etc and that did not help. Does anyone know where I should begin for this? Thank you in advance for your help. I enjoy tinkering with the home server, but with this one I just feel over my head.Tuesday, October 27, 2009 3:52 AM
All replies
-
i to have a similar problem, at first i suspected a quetionable system drive, replaced this and installed (recover) whs, still having the same issue, backup fails with a msg WHS connecter failed, still looking but any tips appretiated ? cheers roy found this, see below... Event Type: Error Event Source: Application Error Event Category: (100) Event ID: 1000 Date: 10/27/2009 Time: 7:01:00 PM User: N/A Computer: xxxxxxxxx Description: Faulting application whsbackup.exe, version 6.0.2030.0, faulting module whsbackup.exe, version 6.0.2030.0, fault address 0x0003ce1c.Tuesday, October 27, 2009 9:58 AM
-
If all your home computers are failing to back up, I would look for an issue on the server. Could you start by running chkdsk on all the disks in your server?
I'm not on the WHS team, I just post a lot. :)Tuesday, October 27, 2009 3:31 PMModerator -
Roy, could you create a new thread, as it's not at all obvious that your problem is the same as the original poster's?
I'm not on the WHS team, I just post a lot. :)Tuesday, October 27, 2009 3:32 PMModerator -
Hi Ken: I ran your check disk batch file and it seemed to run fine. I couldn't really see the report because the command line windows would close when the process concluded. Is t6he next step to try a backup and see what happens? Thanks again for your help on this, I really appreciate it. -KevinWednesday, October 28, 2009 11:20 AM
-
You can try a backup, yes.
I'm not on the WHS team, I just post a lot. :)Wednesday, October 28, 2009 2:52 PMModerator -
Thanks Ken. I tried to run a backup and it failed again. I have the toolkit, and when you look into the error log, the following two error items were under the homserver category. Do you know what these mean? Any guidance here that you may have (or from anyone else!) would be greatly appreciated. -Kevin"Client Backup server failed at d:\wssg_src\whs_pp2\qhs\src\backup\util\diskfile.cpp(483)""Unexpected error 0x79 from WriteFile on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\Data.4096.0.new: The semaphore timeout period has expired."Thursday, October 29, 2009 12:51 AM
-
Did anyone by chance have any thoughts on this issue? At this point I'm totally stuck and I was thinking maybe I should just reinstall WHS and start fro scratch and see if that fixes it, but obviously I'd like to avoid that if possible. Would calling the MS helpline (for a fee) help here? Thanks in advance for any help.Saturday, October 31, 2009 1:17 PM
-
Did anyone by chance have any thoughts on this issue?
Your backup database might be corrupted (which chkdsk might have fixed the problem). Incidentally, you should be able to see the results of your chkdsk in the event logs on the server. In any event, if your database is corrupted, you should try repairing it through the Console. If it still doesn't work, you might have to delete the entire backup database and start a new one.
At this point I'm totally stuck and I was thinking maybe I should just reinstall WHS and start fro scratch and see if that fixes it, but obviously I'd like to avoid that if possible.
I wouldn't try that (at least not yet).
Would calling the MS helpline (for a fee) help here?
Honestly, probably not.
Thanks in advance for any help.
Saturday, October 31, 2009 4:31 PMModerator -
Thank you, Kariya. This is helpful. I earlier deleted the entire database by following the tech guidelines from MS and going to the folder in the command prompt and deleting everything. Should I try that again? Chkdsk didn't seem to change anything, should I try it again? Thanks again for your help.Sunday, November 1, 2009 3:51 AM
-
Thank you, Kariya. This is helpful. I earlier deleted the entire database by following the tech guidelines from MS and going to the folder in the command prompt and deleting everything. Should I try that again?
It couldn't hurt. How many clients total do you have? Are any of them able to backup successfully? It's possible (although extremely unlikely) that the hard drives of the 2 clients you previously mentioned both have hard drive issues (in which case you could try running chkdsk /r on those hard drives as well).
Chkdsk didn't seem to change anything, should I try it again?
I would suggest looking at the event logs on the server first for the results of your last chkdsk (which should be in the Application section of the Event Logs).
Thanks again for your help.
Monday, November 2, 2009 12:22 AMModerator -
Thank you Kariya. I (finally) had time to try the steps you suggested and backup did not work. I also tried removing the computers from the list on the server (i.e. deleting all backups), deleting the connector software on the client, and reconnecting them with the server and trying to backup -- that didn't work either. Looking at the event log as you suggested, below is the latest error. Do you (or anyone else!) have any advice as to where to go from here? Again, I really appreciate the help here...the server is otherwise working great except for backup.Event Type: ErrorEvent Source: Application ErrorEvent Category: (100)Event ID: 1000Date: 11/8/2009Time: 12:44:06 AMUser: N/AComputer: SERVERDescription: Faulting application whsbackup.exe, version 6.0.2030.0, faulting module whsbackup.exe, version 6.0.2030.0, fault address 0x000620fe.Sunday, November 8, 2009 4:29 PM
-
Thank you Kariya. I (finally) had time to try the steps you suggested and backup did not work. I also tried removing the computers from the list on the server (i.e. deleting all backups), deleting the connector software on the client, and reconnecting them with the server and trying to backup -- that didn't work either. Looking at the event log as you suggested, below is the latest error. Do you (or anyone else!) have any advice as to where to go from here? Again, I really appreciate the help here...the server is otherwise working great except for backup.
Event Type: ErrorEvent Source: Application ErrorEvent Category: (100)Event ID: 1000Date: 11/8/2009Time: 12:44:06 AMUser: N/AComputer: SERVERDescription: Faulting application whsbackup.exe, version 6.0.2030.0, faulting module whsbackup.exe, version 6.0.2030.0, fault address 0x000620fe.
How about the questions I asked in my last post (how many clients do you have and do any of them backup successfully)? Did you find the results of the chkdsk in the Application logs?- Edited by kariya21Moderator Thursday, November 12, 2009 2:52 AM
Monday, November 9, 2009 12:02 AMModerator -
Thanks Kariya. I have two clients on the home server -- he first is an XP client that backed up fine for over a year until suddenly it stopped. The second is a Windows 7 laptop that is brand new and hasn't worked since I got it. When I got it it was vista and didn't work as that either. I rank a checkdisk/r on the clients and no issue there. When I look at the logs for the chkdisk, I didn't see an error, only that the application performed. Is there somewhere else I should look? Thanks again for your help.Tuesday, November 10, 2009 2:08 AM
-
Hello: I also found the below error on the event log of the client. Does anyone have any advice on this? Thank you for all the help to date.Log Name: ApplicationSource: HomeServerDate: 11/10/2009 1:47:12 AMEvent ID: 773Task Category: HomeBackupLevel: ErrorKeywords: ClassicUser: N/AComputer: RedDescription:Backup of volume C: to SERVER failed: Microsoft.HomeServer.Backup.Protocol.ProtocolException: Client / Server connection lostat Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.TryReconnect(Int32 localGeneration)at Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.WriteWithReconnect(Int32 count)at Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.Write(Byte[] buffer, Int32 offset, Int32 count)at Microsoft.HomeServer.Common.Client.BinaryWriterEx.Write(Byte[] value, Int32 offset, Int32 length)at Microsoft.HomeServer.Backup.Protocol.BackupProtocol.SendClusterData(Int64 clusterIndex, Byte[] data, Int32 offset, Int32 length)at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.DoClusterPass2()at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.RunWithoutCatch()at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.Run()Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="HomeServer" /><EventID Qualifiers="53247">773</EventID><Level>2</Level><Task>3</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2009-11-10T07:47:12.000000000Z" /><EventRecordID>2262</EventRecordID><Channel>Application</Channel><Computer>Red</Computer><Security /></System><EventData><Data>4</Data><Data>C:</Data><Data>SERVER</Data><Data>Microsoft.HomeServer.Backup.Protocol.ProtocolException: Client / Server connection lostat Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.TryReconnect(Int32 localGeneration)at Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.WriteWithReconnect(Int32 count)at Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.Write(Byte[] buffer, Int32 offset, Int32 count)at Microsoft.HomeServer.Common.Client.BinaryWriterEx.Write(Byte[] value, Int32 offset, Int32 length)at Microsoft.HomeServer.Backup.Protocol.BackupProtocol.SendClusterData(Int64 clusterIndex, Byte[] data, Int32 offset, Int32 length)at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.DoClusterPass2()at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.RunWithoutCatch()at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.Run()</Data></EventData></Event>Wednesday, November 11, 2009 4:17 AM
-
Hello: I also found the below error on the event log of the client. Does anyone have any advice on this? Thank you for all the help to date.
Log Name: ApplicationSource: HomeServerDate: 11/10/2009 1:47:12 AMEvent ID: 773Task Category: HomeBackupLevel: ErrorKeywords: ClassicUser: N/AComputer: RedDescription:Backup of volume C: to SERVER failed: Microsoft.HomeServer.Backup.Protocol.ProtocolException: Client / Server connection lostat Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.TryReconnect(Int32 localGeneration)at Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.WriteWithReconnect(Int32 count)at Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.Write(Byte[] buffer, Int32 offset, Int32 count)at Microsoft.HomeServer.Common.Client.BinaryWriterEx.Write(Byte[] value, Int32 offset, Int32 length)at Microsoft.HomeServer.Backup.Protocol.BackupProtocol.SendClusterData(Int64 clusterIndex, Byte[] data, Int32 offset, Int32 length)at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.DoClusterPass2()at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.RunWithoutCatch()at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.Run()Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="HomeServer" /><EventID Qualifiers="53247">773</EventID><Level>2</Level><Task>3</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2009-11-10T07:47:12.000000000Z" /><EventRecordID>2262</EventRecordID><Channel>Application</Channel><Computer>Red</Computer><Security /></System><EventData><Data>4</Data><Data>C:</Data><Data>SERVER</Data><Data>Microsoft.HomeServer.Backup.Protocol.ProtocolException: Client / Server connection lostat Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.TryReconnect(Int32 localGeneration)at Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.WriteWithReconnect(Int32 count)at Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.Write(Byte[] buffer, Int32 offset, Int32 count)at Microsoft.HomeServer.Common.Client.BinaryWriterEx.Write(Byte[] value, Int32 offset, Int32 length)at Microsoft.HomeServer.Backup.Protocol.BackupProtocol.SendClusterData(Int64 clusterIndex, Byte[] data, Int32 offset, Int32 length)at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.DoClusterPass2()at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.RunWithoutCatch()at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.Run()</Data></EventData></Event>
At this point, I think your best bet is to file a bug report on Connect.Thursday, November 12, 2009 2:53 AMModerator -
Hi Everyone: Regarding the below, I finally had some spare time and tried completely reinstalling the home server software on the machine (it is a home built WHS) (I used the "new installation" option from the install DVD). I successfully reinstalled the software after backing up my files, installed all the updates and power packs, etc. When I tried to back up my client again, I ran into the same error. At this point I am at a complete loss -- I just can't figure out this error. Everything on WHS works fine, except it won't back up client machines. I had thought that starting from scratch would solve the issue even if it was a pain, but I'm right back where I started.Any advice on what I can do? Is there anyone on the WHS team who I can contact? The client back up worked totally fine until a few months ao, and then just stopped working. Thanks everyone for your help.Saturday, January 2, 2010 9:18 PM
-
Hi Everyone: Regarding the below, I finally had some spare time and tried completely reinstalling the home server software on the machine (it is a home built WHS) (I used the "new installation" option from the install DVD). I successfully reinstalled the software after backing up my files, installed all the updates and power packs, etc. When I tried to back up my client again, I ran into the same error. At this point I am at a complete loss -- I just can't figure out this error. Everything on WHS works fine, except it won't back up client machines. I had thought that starting from scratch would solve the issue even if it was a pain, but I'm right back where I started.
Did you install anything except the updates after your New Installation (add-ins or apps)? Did you use the Console to install the updates (or did you do it from the server desktop)?
Any advice on what I can do? Is there anyone on the WHS team who I can contact?
The client back up worked totally fine until a few months ao, and then just stopped working. Thanks everyone for your help.
Saturday, January 2, 2010 9:35 PMModerator -
Thanks Kariya. I installed the updates from the sever desktop. Basically, I just initiated windows update and click restart when asked. Does that make a difference?Saturday, January 2, 2010 11:39 PM
-
Thanks Kariya. I installed the updates from the sever desktop. Basically, I just initiated windows update and click restart when asked. Does that make a difference?
First, logging into the desktop is unsupported. Second, did you install any Software, Optional updates from the server desktop? If so, that is probably your problem as other users that have done that have had all sorts of issues afterwards. In any event, you should always use the Console to install updates (because it won't install any of the Software, Optional or Hardware, Optional updates).Sunday, January 3, 2010 1:48 AMModerator