Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1744
  • Last Modified:

Shadow Copy Problem

I'm having a problem with Shadow Copy and subsequently failing backups.  I first noticed something was wrong when the backups made of the servers C drive failed.  Further investigation revealed a problem with the VSS on the C drive.  When I check the Shadow Copies tab under the drive it shows as disabled.  When I click to enable it I get this error:
"Failed to create a shadow copy of volume c:\. Error 0x80042308: The specified Volume was not found."
If I click the settings button on the same screen I get this error:
"Failed to initialize the Settings dialog for volume c:\.  Error 0x80042308: The specified volume was not found."
Several fixes have been attempted which are detailed here:
http://kb.backupassist.com/articles.php?aid=2965
So far nothing has worked and I have the same problem.  Any suggestions?
0
First Last
Asked:
First Last
  • 9
  • 7
1 Solution
 
alro613Commented:
I had something similar happen on my Exchange 2007 server ..
At command prompt type: vssadmin list writers.

It should display all the writers as "State 1 - Stable"
If it's State 0 - Failed... a simple reboot may be all that's needed to get the VSSAdmin back to a working state.  
I've pasted what's displayed on my server below..  May help...


C:\Users\admin>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Waiting for responses.
These may be delayed if a shadow copy is being prepared.

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {0205275b-5e71-4e4c-a069-94093643bc39}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {9142e65e-92e7-4780-ad93-99eecde00b0c}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {62c16100-469f-4cbb-b7dd-c70c1726afdc}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {61f72a0e-1ead-43ba-a6ba-16a0085d4494}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {0de23c6c-1f24-43df-b8b2-4b69b221c86c}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {776396a7-4fdb-4ffd-9124-5c68e58a114d}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {8434085b-688f-49d8-95b0-9ff51d1edaaf}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {473701be-4367-4930-95a4-5c15894b26e3}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {c5d6865e-864a-48d9-b941-a34d49fa89e3}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {21ffb7e9-4a51-4810-acf0-4f01fbbc89bc}
   State: [1] Stable
   Last error: No error
0
 
First LastAuthor Commented:
I tried that earlier alro613, it shows no errors.  I have rebooted several times but there has been no change:

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {7b4dbfc0-8e01-41bb-ad86-27b1919f3464}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {4d3f353d-9bc5-4883-8c77-f9f38b331ea7}
   State: [1] Stable
   Last error: No error

Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {49d6f270-01b2-4757-8876-0575692505fa}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {f7ab9da6-71b3-4d8b-86a1-8364acf44fd0}
   State: [1] Stable
   Last error: No error

Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {49a0147d-8981-4187-b184-b5686230da37}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {4fec0405-7b49-4d41-96d2-5c163108ed1f}
   State: [1] Stable
   Last error: No error
0
 
alro613Commented:
Do you have the snapshot rollup package installed?

http://support.microsoft.com/kb/940349

0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
First LastAuthor Commented:
I did see that update but it didn't quite seem to detail my exact problem so I never applied it.  Can't hurt to give that a try, right?  I'll patch it tonight and let you know if that does the trick, thanks!
0
 
alro613Commented:
That was my thinking as well.  at this stage, it's not working anyway, and the patch details are close enough that i'd give it a shot if i was in your predicament.
Good luck.
I look forward to hearing how it works out.
0
 
First LastAuthor Commented:
Ok, no dice with the patch.  I also re-ran chkdsk and it finds no errors now.  I checked the event log and saw a VSS error at just after 8am this morning:

Event ID 12290
Volume Shadow Copy Service warning: RegQueryValueExW(0x0000018c((null)),MaxDiffSpace,0,[0],0,[0]) => ERROR_FILE_NOT_FOUND.  hr = 0x00000000.

It appears three times in a row with slightly different numbers after the "RegQueryValueExW" portion of the error.

The C drive is 12GB total with a 4Gb swap file and 2.6GB of remaining space.  The wording of that error contains the phrase "MaxDiffSpace" which makes me think there could be a problem with the available space on the drive...perhaps there is not enough to perform an operation?  I have removed everything I can from the drive so all that is left would be the swap file.  Do you think its worth trying to move it to another partition or do you think the space available is sufficient?
0
 
alro613Commented:
I would -- it's simple and safe to do.  I don't see why not.  It'll only cost you a reboot to try.
0
 
First LastAuthor Commented:
Ok, I can give that a try tonight.  If getting more space also fails to work do you know of anything else I can try?  This is a really weird and persistent problem.
0
 
alro613Commented:
well.. the File_not_found part also suggests that there's a file that was once part of the scope of your back up that's no longer there.
Recently, I cleared some space on one of my remote servers and backups would finish with a failed state ... only because there was a directory missing.

I ended up having to go into the backup job - and remove the directory from the scope.  after that, i had no more errors...

So when i see that file_not_found .. it's either something is missing, or permissions are set so that the backup service has a deny on it.

According to stuff i've read, "RegQueryValueExW" is used to declare a service in the registry.   Some articles suggest that this failing could be related to permissions set in the registry.  But I wouldn't even investigate that yet... muckin' about in the registry - especially when we haven't really found the issue yet is too dangerous.  So - i put it here only as a thing to think about... but i doubt, at this point, that it has anything to do with the registry.

I'm supposing that this worked before?? And something has changed before it broke?  or has it never worked?
0
 
First LastAuthor Commented:
It worked up until about a week ago with no trouble.  I can't think of any system level changes that were done in the last couple of weeks, not even windows updates.  I had thought the file_not_found might be referencing the volume shadow file that can no longer be accessed on the C drive.
0
 
alro613Commented:
did you try re-registering all the VSS writers?
I know you mentioned an article above that had this as part of it's steps..
just curious...

1.   From command prompt:
 
Cd windows\system32
Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 vss_ps.dll
Vssvc /Register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll
 
2.         After completing the registration of the DLL’s open an command prompt and type: vssadmin list writers
3.         You should see the writers listed.
0
 
First LastAuthor Commented:
Yes, I tried everything on the list there.  I thought that one would have done the trick.
0
 
First LastAuthor Commented:
Ok, I moved the swap file and also tried another MS patch (longshot) but still have the same problem.  Can anyone offer any other suggestions I can try?
0
 
alro613Commented:
another jab here:
Dunno if this was mentioned...


Open the Windows Start menu, right click My Computer, and choose Manage.
Right click Shared Folders, choose All Tasks, and then click Manage Volume Shadow Copies.
For each volume that you are trying to backup, make sure that shadow copies are enabled. If they are not, then highlight the volume in the list and click the Enable button to enable shadow copies.

Other than that... i got nothin'.. I'll be tapped... and then would be just as curious as you to know what the fix would be.
0
 
dkikalisCommented:
I'm sure that you will have looked at this but do you have enough disk space?  Remember vas actually consumes space for the changes to the file systems during the backup so if you run out space the vas will fail.  
0
 
First LastAuthor Commented:
Hi dkikalis
Yes, I moved the swap file to another partition in order to free up another 4GB of space.  There is 9GB free on the 12GB C partition.  I should also mention that shadow copy is working fine on the other two volumes the server has, just not on C.
0
 
First LastAuthor Commented:
Solved by restoring from last backup
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 9
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now