Main Forum > Tweaking.com Support & Help
Registry Backup Beta
Shane:
Ztruker,
I was able to reproduce why it isn't working for you. It had to do with the bat files in the windows\temp folder not getting over written. I locked them on my machine and tried and got the same problem you did.
I have updated the program to handle this and I have my fingers crossed that this will get you fixed. :cheesy:
Still the same version for now, just download the setup again and install over the one installed now.
Try it and let me know how it goes :wink:
http://www.tweaking.com/content/page/registry_backup.html
Shane
Ztruker:
Same failure. It did create new bat files this time though but still got the same failure. Trying to attach a zip file with the two log files in it.
Event Viewer has two errors:
--- Code: ---Log Name: Application
Source: Application Error
Date: 23/05/2012 7:54:02 PM
Event ID: 1005
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Dell-P370
Description:
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program SeaMonkey because of this error.
Program: SeaMonkey
File:
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
Additional Data
Error value: 00000000
Disk type: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="49152">1005</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-05-23T23:54:02.000000000Z" />
<EventRecordID>69770</EventRecordID>
<Channel>Application</Channel>
<Computer>Dell-P370</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>SeaMonkey</Data>
<Data>00000000</Data>
<Data>0</Data>
</EventData>
</Event>/code]
[code]Log Name: Application
Source: Application Error
Date: 23/05/2012 7:54:02 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Dell-P370
Description:
Faulting application name: seamonkey.exe, version: 12.0.0.4502, time stamp: 0x4f9d0caa
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000001d
Fault offset: 0x1d16f814
Faulting process id: 0x2f8
Faulting application start time: 0x01cd393a76fea7e6
Faulting application path: C:\Program Files (x86)\SeaMonkey\seamonkey.exe
Faulting module path: unknown
Report Id: 91e5f965-a532-11e1-909c-080027009859
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-05-23T23:54:02.000000000Z" />
<EventRecordID>69769</EventRecordID>
<Channel>Application</Channel>
<Computer>Dell-P370</Computer>
<Security />
</System>
<EventData>
<Data>seamonkey.exe</Data>
<Data>12.0.0.4502</Data>
<Data>4f9d0caa</Data>
<Data>unknown</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>c000001d</Data>
<Data>1d16f814</Data>
<Data>2f8</Data>
<Data>01cd393a76fea7e6</Data>
<Data>C:\Program Files (x86)\SeaMonkey\seamonkey.exe</Data>
<Data>unknown</Data>
<Data>91e5f965-a532-11e1-909c-080027009859</Data>
</EventData>
</Event>
--- End code ---
Shane:
I wonder if it has anything to do with the fact that you have other snap shots at the same time.
This was in your log.
SET SHADOW_DEVICE_1=\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy8
When I had it deleting old snap shots it worked for you. Ever since I took it out it has stopped.
Lets test that. :wink:
Open a cmd.exe window
use vssadmin to view and then delete any snap shots. Once they are cleared try the backup again. Does it still fail?
Shane
Shane:
Come to think of it I bet that is the problem.
Looking further down your vss log I found this
--- Quote ---* SNAPSHOT ID = {eb6a5058-61fe-41cb-b660-61017f9cef7c} ...
- Shadow copy Set: {f7a0dfc1-87cc-4a97-a8cd-d3fc7bdef6be}
- Original count of shadow copies = 1
- Original Volume name: \\?\Volume{bcbe9ee2-e6d1-11de-8e59-806e6f6e6963}\ [C:\]
- Creation Time: 5/23/2012 7:48:19 PM
- Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9
- Originating machine: Dell-P370
- Service machine: Dell-P370
- Not Exposed
- Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
- Attributes: Auto_Release Differential
Generating the SETVAR script (C:\Windows\temp\vss-setvar.cmd) ...
--- End quote ---
It made \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9
But told the vss.bat that it was \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy8
Which would explain why it is failing.
I am not sure why it is passing the wrong one though.
Try removing the other snap shots and test. If it does work then I found the problem and will work on a fix :-)
Shane
Ztruker:
What will deleting shadows do to me? I have other software that uses Shadow Copy, especially Acronis True Image and I don't want to mess with it. (Can you tell I'm not up to speed on Shadow Copy :tongue:)
Also, I use Shadow Explore to browse Shadow Copies to sometimes recover files that Windows has backed up. What kind of an effect does it have on that?
I just did a vssadmin list shadows and this is the response:
--- Code: ---C:\Users\rrkurtz>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Contents of shadow copy set ID: {7b188938-d370-4feb-9a9e-8b9c62084dfa}
Contained 3 shadow copies at creation time: 5/21/2012 4:29:00 PM
Shadow Copy ID: {aa946877-595a-4179-8992-2b7f5b3df833}
Original Volume: (D:)\\?\Volume{bcbe9ede-e6d1-11de-8e59-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
Originating Machine: Dell-P370
Service Machine: Dell-P370
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered
Shadow Copy ID: {086270b9-c5e0-4b78-bf00-27171d8911c4}
Original Volume: (E:)\\?\Volume{bcbe9edf-e6d1-11de-8e59-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3
Originating Machine: Dell-P370
Service Machine: Dell-P370
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered
Shadow Copy ID: {9d7b82a4-de52-4b41-b823-52245a2754bc}
Original Volume: (C:)\\?\Volume{bcbe9ee2-e6d1-11de-8e59-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy5
Originating Machine: Dell-P370
Service Machine: Dell-P370
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered
Contents of shadow copy set ID: {6d0d06be-076f-4d75-a04d-fc0a0fe0c3ad}
Contained 3 shadow copies at creation time: 5/22/2012 3:06:09 PM
Shadow Copy ID: {d43b6a93-6928-49d4-b488-ffa072df21fa}
Original Volume: (D:)\\?\Volume{bcbe9ede-e6d1-11de-8e59-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2
Originating Machine: Dell-P370
Service Machine: Dell-P370
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered
Shadow Copy ID: {1a114272-e9f0-40a6-a3ca-31f985b5c373}
Original Volume: (E:)\\?\Volume{bcbe9edf-e6d1-11de-8e59-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4
Originating Machine: Dell-P370
Service Machine: Dell-P370
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered
Shadow Copy ID: {02b7b622-cf97-48f8-9ecf-f554dd4e4abf}
Original Volume: (C:)\\?\Volume{bcbe9ee2-e6d1-11de-8e59-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy7
Originating Machine: Dell-P370
Service Machine: Dell-P370
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered
--- End code ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version