New
#51
Windows NO LONGER backing up
-
-
New #52
Sh*t....; problems remain same!
direct backup: can read shadow copy,
wireless back: path not correct
this is getting quite desperate...?
-
-
-
New #55
overnight i did a full backup, including system image: (IE DIRECT BACKUP VIA USB)
these are the massages in order of appearance:
1)
The backup was not successful. The error is: Windows Backup failed while trying to read from the shadow copy on one of the volumes being backed up. Please check in the event logs for any relevant errors. (0x81000037).
2)
Fault bucket 1084420110, type 5
Event Name: WindowsBackupFailure
Response: Not available
Cab Id: 0
Problem signature:
P1: Backup
P2: 6.1.7601
P3: 0x81000037
P4: 11
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\WINDOWS\Logs\WindowsBackup\WindowsBackup.1.etl
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_Backup_37c94a3f7f9dc50e1a69c36b71e2cc befec74cf_22ec2ca2
Analysis symbol:
Rechecking for solution: 0
Report Id: 97049d07-db90-11e1-adaa-00217063082d
Report Status: 0
3)
The VSS service is shutting down due to idle timeout.
4)
The Block Level Backup Engine service has stopped.
5)
Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0
Problem signature:
P1: 7.6.7600.256
P2: 80072ee2
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7:
P8:
P9:
P10:
Attached files:
These files may be available here:
Analysis symbol:
Rechecking for solution: 0
Report Id: 01946a6f-db99-11e1-adaa-00217063082d
Report Status: 0
6)
Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0
Problem signature:
P1: 7.6.7600.256
P2: 80072ee2
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7:
P8:
P9:
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.6.7600.256_d657698cc2203130accf771c18 dbe77b92e59fa7_cab_1daf4744
Analysis symbol:
Rechecking for solution: 0
Report Id: 01946a6f-db99-11e1-adaa-00217063082d
Report Status: 4
7)
Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0
Problem signature:
P1: 7.6.7600.256
P2: 80072ee2
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7:
P8:
P9:
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.6.7600.256_d657698cc2203130accf771c18 dbe77b92e59fa7_cab_1daf4744
Analysis symbol:
Rechecking for solution: 0
Report Id: 01946a6f-db99-11e1-adaa-00217063082d
Report Status: 0
8)
-
New #56
Yes correct.
i can ALWAYS access the wireless drive directly via my pc using this path,
so i i know 100pct sure it's correct.
like i mentioned before, when i want to setup a backup to this drive,
windows sometimes immediately says path not valid & sometimes says this
during the backup...
-
New #57
All failures you posted are almost on same time so related?
1) is the oldest enrty in event log, then 2 then 3 etc?
-
New #58
1: it says somethig about VSS error
2,3,4 just a result of problem 1
windows update... hmmm maybe also a vss problem ... don't know can you install updates succesfully now without errors?
If attached directly to win7 backup is always succesfully now?
-
New #59
My native language is not english... but if I read corrrect it refers to the source of backup so C? Do I read it right?1)
The backup was not successful. The error is: Windows Backup failed while trying to read from the shadow copy on one of the volumes being backed up. Please check in the event logs for any relevant errors. (0x81000037).
-
New #60
started teh backup around midnight & these errors appeared between 06.20-07.20hrs this morning
1 is the 1st that appeared & 7 the last (forget the no 8 i mentioned in my previous post)
Quote
Related Discussions