Answered by:
Client backup unsuccessful Windows 7 32bit

Question
-
Server setup and running fine and was able to backup the server to USB Drive.
Installed connector on Windows 7 and ran backup. Kept getting unsuccessful so rebooted Windows 7 and Server. Still no luck. Going into the details of "an unknown error prevented backup from completing successfully" which is not a lot of help. Could not find anything in the event log. The time from starting the client backup to complete is about 15 Seconds. It briefly as the start shows 0%
Any help appreciated as I now have no backups since all the WHS 1 backups went in the Vail Install.
Forgot to mention I have tried starting the backup from both the client and server and I have repeated customise for this computer and made sure everything was selected, I read one bug was fixed by doing this but it did not seem to apply to my situation.
- Edited by agent86oz1 Saturday, May 8, 2010 3:04 AM Extra Information
Saturday, May 8, 2010 2:58 AM
Answers
-
It is indeed possible that backups worked on WHSv1 but now failing due to VSS writer errors. In V1 we took volume snapshots but did not invoke the VSS writers. In Vail we added the functionality and now invoke all the registered writers in the system before taking a backup. This provides more consistency of the backups themselves, the downside is we fail if the writers fail or if a particular 3rd party writer is buggy and is behaving badly. We are still fine tuning some of the error handling in this area, so could you please open a bug, attach both logs and event logs.
Thanks
-Bodhi
Bodhi Deb - MSFT- Proposed as answer by Theo van ElsbergModerator Monday, May 10, 2010 8:08 PM
- Marked as answer by Jonas Svensson -FST- Monday, May 10, 2010 10:30 PM
Monday, May 10, 2010 2:47 AM -
Ok Just worked out that Windows 7 gives the CAB file number and automaticaly sends. Vail creates ColoradoLogs.zip which seems to have event log etc in it but for some reason wont sent. I will manual upload this server file now to the connect bug.
Please read the installation/usage instructions for the log collector tool; there is a registry key that you may need to set by hand.
I'm not on the WHS team, I just post a lot. :)- Marked as answer by agent86oz1 Wednesday, May 12, 2010 11:55 PM
Wednesday, May 12, 2010 7:56 PMModerator
All replies
-
Server setup and runing fine and was able to backup the server to USB Drive.
First, you should file a bug report on Connect. Second, do other computers backup successfully? You might try running chkdsk /r on the hard drives in that client to look for errors. (I don't know how how robust the backup technology in Vail is in regards to failing client hard drives, but in v1 that would definitely cause a problem.) Also, remember that this is a beta product and that you shouldn't trust your only copy of anything on the OS at this point.Intalled connector on Windows 7 and ran backup. Kept getting unsuccessful so rebooted Windows 7 and Server. Still no luck. Going int the details of "an unknown error prevented backup from completing successfuly" which is not a lot of help. Could not find anything in the event log. The time from starting the client backup to complete is about 15 Seconds. It breifly as the start shows 0%
Any help apreciated as I now have no backups since all the WHS 1 backups went in the Vail Install.
Saturday, May 8, 2010 2:46 PMModerator -
This proble might be cause by a problem with the Volume Shadow Copy Service (VSS) on the client?
On the Windows 7 client:
1. Check the event list for errors for source "VSS".
2. Run a cmd window with admin rights and type:
C:>vssadmin list writers
Any errors listed?- Theo.
No home server like Home ServerSaturday, May 8, 2010 10:03 PMModerator -
Ok found in Windows 7 VSS Error in the application event viewer each time backup is run including overnight automatic backup. I have included it below.
There were no errors in the vssadmin list writers.
I should have tried earlier but added two other computers Vista 64bit and Windows 7 64bit and they both backup.
How would I troubleshoot what is causing the VSS security error?
Log Name: Application
Source: VSS
Date: 9/05/2010 10:46:20 AM
Event ID: 8194
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Ian-PC
Description:
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process.Operation:
Gathering Writer DataContext:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {60244bd0-20a6-4f79-8955-747dc503f58a}
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">8194</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-05-09T00:46:20.000000000Z" />
<EventRecordID>11240</EventRecordID>
<Channel>Application</Channel>
<Computer>Ian-PC</Computer>
<Security />
</System>
<EventData>
<Data>0x80070005, Access is denied.
</Data>
<Data>Operation:
Gathering Writer DataContext:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {60244bd0-20a6-4f79-8955-747dc503f58a}</Data>
<Binary>2D20436F64653A20575254575254494330303030313235312D2043616C6C3A20575254575254494330303030313230352D205049443A202030303030313337322D205449443A202030303030313430302D20434D443A2020433A5C57696E646F77735C73797374656D33325C737663686F73742E657865202D6B204E6574776F726B53657276696365202020202020202D20557365723A204E616D653A204E5420415554484F524954595C4E4554574F524B20534552564943452C205349443A532D312D352D3230</Binary>
</EventData>
</Event>Sunday, May 9, 2010 12:57 AM -
Please run chkdsk /r on all the drives in the machine having problems, then try again.
I'm not on the WHS team, I just post a lot. :)Sunday, May 9, 2010 1:10 AMModerator -
The log connect tool installs but when run from the server desktop it collects information fails on send
Failed to send Watson report. The report can be found in C:\Users\ADMINI~1\AppDa
ta\Local\Temp\3\ColoradoLogs.zip.
Finished. Please press ENTER to quit...I found the file but where do I send it to manually? On the connect site it has a lot of info about WHS1 but less on Vail. Also it does not show a cab file number like shown in the document that came with the tool. I only ever see the cmd window and none of the windows screen shots shown.
Sunday, May 9, 2010 2:46 AM -
Hi Ken
I had ruled this out as I have multiple drives on Windows 7 and I tried backing up even single directories on each drive on seperate backups just incase there was an issue with a drive. The computer is my main one in use so I will have to run it overnight as there are no other options.
Thanks
Sunday, May 9, 2010 2:50 AM -
Hi,
OK. I ran into this issue some last week when VAIL errored-out when backing up one of the partitions on a Vista client. As I did have other priorities then I did not try to repair this VSS issue: Simple recreating the partition that VSS had problems with resolved the problem for me :-)
I did however find one MS thread on the Windows 7 forum that proposes a solution that might be worth checking out?
- Theo.
No home server like Home ServerSunday, May 9, 2010 10:52 AMModerator -
Thanks Theo. I had been looking at this today. All volumes on my main computer give problems. I am seriously thinking of a reinstall as I have tried many things and it looks like VSS is broken for one reason or another.
It worked on WHS1 connector. I uninstalled the connector and installed the Launchpad for WHS2 and could not backup. The information I have is that even going back VSS issue would break my backup on WHS1
Thanks for the research though.
Sunday, May 9, 2010 12:01 PM -
Hmm...
(Will make a note of this) The system that was having trouble with VSS was also backing up succesfully to WHSv1.
For now I will assume there is no relation to installing the VAIL connector as the lastest WHSv1 backup was older then 4 weeks and external events could also have caused VSS to break.- Theo.
No home server like Home ServerSunday, May 9, 2010 2:03 PMModerator -
It is indeed possible that backups worked on WHSv1 but now failing due to VSS writer errors. In V1 we took volume snapshots but did not invoke the VSS writers. In Vail we added the functionality and now invoke all the registered writers in the system before taking a backup. This provides more consistency of the backups themselves, the downside is we fail if the writers fail or if a particular 3rd party writer is buggy and is behaving badly. We are still fine tuning some of the error handling in this area, so could you please open a bug, attach both logs and event logs.
Thanks
-Bodhi
Bodhi Deb - MSFT- Proposed as answer by Theo van ElsbergModerator Monday, May 10, 2010 8:08 PM
- Marked as answer by Jonas Svensson -FST- Monday, May 10, 2010 10:30 PM
Monday, May 10, 2010 2:47 AM -
Bodhi, As you will see above I ran the Windows Server Vail Log Collector and it gave an error and would not send. I am new to submitting bugs. I assume you want the event log from the client and the log from the server from the application I downloaded from connect. Can you point me to the exact instructions of what to do? I saw that you needed to write down a cab number but I did not see that in the process either.
Happy to help but just need pointing in the right direction, I found connect difficult to navigate and kept getting sent to WHS1 stuff.
Monday, May 10, 2010 7:14 AM -
If the log collector is not working please zip the logs folder from both server and client
C:\ProgramData\Microsoft\Windows Server\
and the event logs from the client.
thanks.
Bodhi Deb - MSFTMonday, May 10, 2010 4:56 PM -
agent86oz1 - Can you please also include the output of the following command to the bug:
(run this from an elevated prompt):
vssadmin list writersThanks,
Imran.
This post is "AS IS" and confers no rights.Monday, May 10, 2010 7:21 PM -
Looks Like I narrowed it down to computers trying to backup a second hard drive. Backing up only C: seems to work or backing up a computer with only one hard drive. Windows Visat 64bit Windows 7 32 and 64 bit. All bakcups cause the Event 8194 VSS even when C: backs up directly. I think this is a red herring.
All sent to connect but I only found log files for the Server where are the client ones? I also sent the client event logs.
Monday, May 10, 2010 9:51 PM -
Ok here are the VSS List writers ouput. I checked on all computers used in the test and all seem ok.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.C:\Windows\system32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No errorWriter name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No errorWriter name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No errorWriter name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {d820a340-e1bd-401c-a828-8cba5304e54e}
State: [5] Waiting for completion
Last error: No errorWriter name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {efb0ef7c-e066-4b44-bcd3-c17aa14ac795}
State: [1] Stable
Last error: No errorWriter name: 'MSSearch Service Writer'
Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Writer Instance Id: {898f4ca9-471c-4e91-88f2-e0f0a2087800}
State: [5] Waiting for completion
Last error: No errorWriter name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {50a32f53-9720-4f22-9c46-59c09e5dbee8}
State: [1] Stable
Last error: No errorWriter name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {01fbb854-838f-40d4-9052-c450a297bee4}
State: [1] Stable
Last error: No errorWriter name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {051ee9ae-4eba-46f3-ab14-ae1c243c62c4}
State: [1] Stable
Last error: No errorWriter name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {25b28da0-c520-4672-8b89-a6ef2e29cd8b}
State: [5] Waiting for completion
Last error: No errorWriter name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {89f560ae-f5b8-4327-b2dd-86fcff230ade}
State: [1] Stable
Last error: No errorMonday, May 10, 2010 9:53 PM -
Hi,
This looks a lot similar to what I found (first disk back-up OK, second disk giving problems).Please use the Log Collector Tool available through Connect?
Install and run on both the client and VAIL server and note the CAB numbers generated. Add the CAB numbers to you feedback/bug report.In case the Log Collector Tool is unable to send the logfiles (it will tell you, as well as were to find the logfiles) you can attach the logfiles ("ColoradoLogs.zip") to your feeback report.
Please let us know when you submit your bug-report so I can confirm your findings?
Thanks,
Theo.
No home server like Home ServerMonday, May 10, 2010 10:45 PMModerator -
Hi Theo
I submitted a bug report but only the log for the server under username seaview. I just worked out you run it on the client also. It won't automatically send from the Server but the client does work and gives a cab number CAB 850886783. So the other ColoradoLogs.zip via connect and also client event log.
Is this all you need?
Monday, May 10, 2010 11:04 PM -
Ok Just worked out that Windows 7 gives the CAB file number and automaticaly sends. Vail creates ColoradoLogs.zip which seems to have event log etc in it but for some reason wont sent. I will manual upload this server file now to the connect bug.
Tuesday, May 11, 2010 2:46 AM -
Thanks,
Confirmed your report and added a reference to info I submitted.
-Theo.PS - As you are, I am just testing. Trying to find as many ways as possible to brake wonderfull things the HSBS team is creating with WHS and VAIL ;-)
No home server like Home ServerWednesday, May 12, 2010 7:18 PMModerator -
Ok Just worked out that Windows 7 gives the CAB file number and automaticaly sends. Vail creates ColoradoLogs.zip which seems to have event log etc in it but for some reason wont sent. I will manual upload this server file now to the connect bug.
Please read the installation/usage instructions for the log collector tool; there is a registry key that you may need to set by hand.
I'm not on the WHS team, I just post a lot. :)- Marked as answer by agent86oz1 Wednesday, May 12, 2010 11:55 PM
Wednesday, May 12, 2010 7:56 PMModerator -
Ok fixed the registry and it generated and sent CAB 852411774 for the server. Windows client is CAB 850886783
Has anyone been able to get a second hard drive to backup from the client computer?
Thursday, May 13, 2010 1:31 AM