VSS event 12293

All replies

• 

  

  0

  Sign in to vote

  Please check the clients event log first. This gives often more info for troubleshooting than the server log.
  Best greetings from Germany
  Olaf

  Saturday, January 10, 2009 10:01 PM

  Moderator
• 

  

  0

  Sign in to vote

  This was from the client's event log. Sorry for the confusion.

  Saturday, January 10, 2009 11:57 PM
• 

  

  0

  Sign in to vote

  Hi Bob,
  was the same client joined to the other server before and backed up successfully?
  Often VSS errors are caused by disk errors (logical or physical). Therefore a first step would be checking the disk.
  On the client open a command prompt and run
  chkdsk /f /r c:
  (if more disks are there, you would have to repeat this for the other drives).
  
  Other than that 3rd party software on your client could be a reason, especially imaging software.
  Or components of the VSS service are not properly registered any more. You could try following lines in a batch file:
  cd %windir%\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
  Net start swprv
  Net start vss
  
  Good luck
  Olaf

  Sunday, January 11, 2009 12:09 AM

  Moderator
• 

  

  0

  Sign in to vote

  Thanks,
  
  Tried the chkdsk route to no avail. I will try what you suggest.
  
  Bob
  

  Sunday, January 11, 2009 4:33 AM
• 

  

  0

  Sign in to vote

  Tried your commands. The lkine with vssui.dll failed. The rest worked, but the backup failed as before with the same error. I appreciate your input. Do you have any other ideas?
  
  Bob
  

  Sunday, January 11, 2009 4:45 AM
• 

  

  0

  Sign in to vote

  Hi,
  you didn't answer my questions - if the client was joined to the other server before and backed up successfully? And if you installed/uninstalled 3rd party disk imaging software (Acronis, Norton) on that system?
  Which operating system is on the client?
  
  That the vssui.dll register did not work, may be, since the batch has been taken from a KB article for a server OS.
  Did you also reboot the client after executing the commands?
  
  Has the volume you are trying to backup been converted from FAT32 to NTFS in the past or is it still FAT32?
  On the client please open a command prompt and type
  vssadmin list providers
  Copy and paste the output into your answer.
  
  Best greetings from Germany
  Olaf

  Sunday, January 11, 2009 10:02 AM

  Moderator
• 

  

  0

  Sign in to vote

  Olaf,
  
  First, thanks for your assistance.
  
  Both systems are independent. Each has a WHS and one client. I live in two different places. Where I am right now is the WHS I build. This machine has never executed a successful backup because of the VSS problem. Yes, I have used Acronis on that system, but I have removed it (at least as far as I can tell). All the drives were brought up as NTFS volumes. I never used acronis to clone a drive. And I have this problem on all my drives. I do have several raid drives in this system, but C: and D: are straight single piece drives.
  
  I did not reboot after executing the list of commands you gave me. I did them one at a time at a command prompt. I will try that now.
  
  Thanks again,
  Bob
  
  
  
  Microsoft(R) Windows DOS
  (C)Copyright Microsoft Corp 1990-2001.
  
  C:\DOCUME~1\ROBERT~1.HA~>vssadmin list providers
  vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
  (C) Copyright 2001 Microsoft Corp.
  
  Provider name: 'MS Software Shadow Copy provider 1.0'
  Provider type: System
  Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
  Version: 1.0.0.7
  
  
  C:\DOCUME~1\ROBERT~1.HA~>
  
  Event log error
  
  Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details Cannot ask provider {00000000-0000-0000-0000-000000000000} if volume is supported. [0x8000ffff] [hr = 0x8000ffff].
  
  
  

  Sunday, January 11, 2009 4:27 PM
• 

  

  0

  Sign in to vote

  Olaf,
  
  Rebooting made no difference. Same error.
  
  Bob
  

  Sunday, January 11, 2009 4:33 PM
• 

  

  0

  Sign in to vote

  Hi Bob,
  seems something has removed some information from your registry (maybe uninstalling software), since a provider {0...} is not normal.
  If you run regedit, what is the value of HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}\CLSID?
  
  KB940184 delivers some more informations about what you could try (together with above batch) for Windows Server 2003.
  
  Check also, if there are COM or DCOM errors and warnings in the event log.
  
  In worst case only a repair installation of your Windows may fix this behavior. If you do so, you should prepare a Windows XP CD with slipstreamed SP3.
  Best greetings from Germany
  Olaf

  Sunday, January 11, 2009 6:53 PM

  Moderator
• 

  

  0

  Sign in to vote

  I only have controlset002,003,004 and currentcontrolset
  
  Value for controlset002 is {65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}
  Value for controlset003 is {65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}
  Same for controlset004, but that one has a key ENUM under VSS as well.
  
  Currentcontrolset looks like 004.
  
  I forget, will a repair installation require me to re-install all my applications. That might not be worth it.
  
  I find this strange as the OTHER system worked for a while and then starting showing this exact same beahavior. The clints on each system are VERY different and used completely differently. It's odd that I would get this on two different systems like this. I never put acronis on the other system. Why would it work and then stop. Both machines WERE running SP2. I just upgraded on this machine yesterday. I wonder if there was an SP2 update that wiped out the values I need? The other system stopped working after I applied some updates to it. hmmm
  
  Thanks again for your time,
  Bob
  

  Monday, January 12, 2009 1:40 AM
• 

  

  0

  Sign in to vote

  Hi Bob,
  that's also not normal. In a normal acting Windows you have ControlSet001 and ControlSet002, and ControlSet001 is linked by CurrentControlSet here.
  A repair installation will not require to install all applications, but usually triggers product activation.
  
  Exactly the same behavior I could only explain, if you installed or removed the same piece of software from both systems, interacting with VSS or its components.
  
  Best greetings from Germany
  Olaf

  Monday, January 12, 2009 4:55 AM

  Moderator
• 

  

  0

  Sign in to vote

  Olaf.
  
  I created a slip streamed windows disk and started to do the repair installation/in place upgrade. It loaded all the files and went to reboot and nothing happens. just get a blinking cursor in the upper left. I've tried using recovery console to repair the boot sector and the boot.ini file but still get the same thing. THe c drive looks fine when I boot from my Ultimate Boot CD. I have an image backup of the drive butit ison the Windows home server and I can't get at it.
  
  At this point, I'd like to forget the repair (and WHS) and just go back to the way things were.
  
  Any ideas?
  
  Bob Haines
  

  Saturday, January 17, 2009 10:51 PM
• 

  

  0

  Sign in to vote

  Don't know how helpful this will be, but here's some info I wrote up on another forum. I may give you some ideas to diagnose the issue.
  
  Also, here's a link to some info on this event id 12293 : http://technet.microsoft.com/en-us/library/cc734302.aspx
  
  I just built and setup my server a week ago. One of my primary reasons for getting the server was to backup two laptops and two desktop computers in my home. I had no issues with backing up the laptops (one with WinXP Pro SP2, the other with WinXP MCE SP3). However, I had back up issues with the two desktop machines. Both are running Win XP Home SP3. Both had Volume Shadow Service (VSS) issues, given as a cyptic 0x8000FFFF error. I spent about 3 evenings researching VSS issues. It seems to be a common enough problem, but no specific fixes were in any of the WHS sites/forums. I finally resolved the issue and thought I'd write up the fix to help others. Note that the solution does require registry edits on your client computer.
  
  1. Click Start, click Run, type cmd, and then click OK.This brings up a command prompt window.
  
  2. At the command line type vssadmin list writers, then press enter.If you get an 0x8000FFFF error or other error, proceed with the rest of this solution.
  
  3. Next, make sure the correct services are running. Click Start, Control Panel, Administrative Tools, Component Services. In the Component Services window, click Services (local) and you'll get a list of the services on the client computer.
  
  4.For each of the following services check that the start up type is set to manual. This can be changed in the properties if it is not. Then, right-click the following services one at a time. For each service, click Restart:
  • COM+ Event System
  • COM+ System Application
  • Distributed Transactions Coordinator
  • Microsoft Software Shadow Copy Provider
  • Volume Shadow Copy
  
  5. Next, we'll check if there are any errors with the VSS services. In the Component Services window, click Event Viewer (local), Application. Look for errors with VSS under the Source column. I had two:
  
  Event ID 5013
  Volume Shadow Copy Service error: Shadow Copy writer ContentIndexingService called routine RegQueryValueExW which failed with status 0x80070002 (converted to 0x800423f4).
  
  Event ID 12302
  Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers. Please check to see that the Event Service and Volume Shadow Copy Service are operating properly.
  
  6. Look up the error at support.microsoft.com. The 0x80070002 error, directed me to Article ID 907574. On my client computers, the default registry subkeys were not set correctly. I edited the registry exactly as directed in this article.
  
  7. Look up the 0x8000FFFF error. This takes you to Article ID 940184. My procedures differs a little bit from this article. First, follow steps 1 - 4 to edit the registry.
  
  8. Reboot the computer.
  
  9. Bring up a command prompt window again - Click Start, click Run, type cmd, and then click OK. Type the following list of commands to register the VSS dll's.
  
  • cd /d %windir%\system32
  • net stop vss
  • net stop swprv
  • regsvr32 ole32.dll
  • regsvr32 oleaut32.dll
  • regsvr32 vss_ps.dll
  • vssvc /register
  • regsvr32 /i swprv.dll
  • regsvr32 /i eventcls.dll
  • regsvr32 es.dll
  • regsvr32 stdprov.dll
  • regsvr32 msxml.dll
  • regsvr32 msxml3.dll
  • regsvr32 msxml4.dll
  
  10. At the command prompt, type vssadmin list writers, and then press ENTER. You should see of the Writer names, Id, Instance ID and state. If you get this, your VSS problems should be solved, the VSS service should be running and you should be able to back up the client computer to your WHS.
  
  Regards,
  Scott
  
  

  Saturday, January 17, 2009 11:11 PM
• 

  

  0

  Sign in to vote

  BobH57 said:

  Olaf.
  
  I created a slip streamed windows disk and started to do the repair installation/in place upgrade. It loaded all the files and went to reboot and nothing happens. just get a blinking cursor in the upper left. I've tried using recovery console to repair the boot sector and the boot.ini file but still get the same thing. THe c drive looks fine when I boot from my Ultimate Boot CD. I have an image backup of the drive butit ison the Windows home server and I can't get at it.
  
  At this point, I'd like to forget the repair (and WHS) and just go back to the way things were.
  
  Any ideas?
  
  Bob Haines
  

  
  Hi Bob,
  why not slipstreamed with SP3?
  Would have saved some work with later upgrading. From what you describe, either some files on the disk are not copied correctly (did you try chkdsk from your Vista-DVD?) or the files on the CD are not ok or something else (memory or what ever) may affect your system. Hard to say from the distance, so all assumptions can only remain speculative.
  Boot sequence in Bios is still correct?
  Once a repair install is started, it cannot be reverted.
  
  If you boot from the CD and try another install, is a repair install still offered or is the Windows installation not found any more?
  What do you mean with "image backup on the WHS"?
  Is it a former backup done with Windows Home Server?
  If this is the case, what is the problem to restore?
  
  Or a backup made with Acronis?
  If the last and you have still a second volume on the client, you could try to copy the image directly from the server. In the Vista DVD use startnet.cmd (may work or not, depending from driver support for your network card in the Vista DVD). IF you get a successfull start:
  Map a network drive to a share on the server, i.e.
  net use x: \\server\public /user:server\administrator password
  and copy the file using copy or xcopy.
  (Or use an USB drive to put the data back.)
  After that start the Acronis recovery disk to write the image back.
  
  Best greetings from Germany
  Olaf

  Saturday, January 17, 2009 11:51 PM

  Moderator
• 

  

  0

  Sign in to vote

  The slipstream disk is SP3. I tried the install with the original SP2 disk with the same result.
  If I had to guess I think it may be a problem with the size of my C; drive? It is a solid state drive that is 64 meg. It is only 2/3 full as I have all my programs installed on the D: drive. Pretty much all that's on the C: drive is the Windows XP installation.
  
  THe backup I did was with the Windows XP backup It made an image backup of the C: drive. I copied that to a share on the WHS. Unfortunately, I cannot access that with the recovery console OR my ultimate boot CD. Unless I'm missing something. Networking on the Ultimate Boot CD is very primitive. It will not allow me to see WHS because I made the disk BEFORE I installed WHS. (Yeah, a mistake!) I will work on that some more as it is one ray of hope.
  
  If the problem is the size of the C: drive, I could find another machine and clone the C: to another larger, drive install that, and try again. If it is a size issue, I would have thought the install program would have told me there is not enough space?
  
  It is very strange because it looks like it's not loading ANYTHING from the C: drive on boot. There is one VERY quick access and that's it. I get nothing on the screen. Yet, the drive has all the required files and Boot.ini looks okay. When the install does the reboot, how does it change the boot sequence so the install program boots instead of the operating system?
  
  Thanks again,
  Bob
  

  Sunday, January 18, 2009 2:42 PM
• 

  

  0

  Sign in to vote

  WHen I try to re-start the repair, it does find the windows install and tells me that it has already attempted a repair.

  Sunday, January 18, 2009 2:44 PM
• 

  

  0

  Sign in to vote

  Olaf,
  
  I've got two SATA slots in my WHS machine. Is there a way I can put my existing C: drive and a larger drive in those two slots and clone one from the other without WHS grabbing them and adding them to its storage pool? I might even be able to restore the image backup from the WHS to the C: drive if I could do this. Right now, its' the only extra machine I have with available SATA slots. The machine with th e problem has no extra SATA slots for me to use. (Well, maybe I could take out the D: drive. but the rest are set up as raid.)
  
  Thanks again for all your help. It is truly appreciated.
  
  Bob Haines
  

  Sunday, January 18, 2009 3:36 PM
• 

  

  0

  Sign in to vote

  Hi Bob,
  WHS does not automatically add drives to the storage pool.
  The problem is, that the recovery software may not run well on the server OS (installation rejected, because it is not made for server or may even interact that deep with the server OS, that it destroys the core WHS components).
  If you can create a recovery CD from your imaging software, which allows you to boot from it on the server hardware and to access the disks, this would be less a problem and could work.
  Best greetings from Germany
  Olaf
  

  Sunday, January 18, 2009 9:40 PM

  Moderator
• 

  

  0

  Sign in to vote

  The backup image was made with Windows Backup.
  
  Can I install a copy of XP on the WHS machine and make it a multiple boot machine? COuld I still get to the copy of the backup I have on the WHS public space?
  
  Do you have any ideas on why my repair is having these problems? It is very frustrating to have something that simple fail like this? Could it bee the solid state drive or the fact that it is only 64 meg? Setup does not complain about disk space. I could also try copying the solid state drive to a larger standard SATA drive. Maybe the repair would work then?
  

  Monday, January 19, 2009 9:52 PM
• 

  

  0

  Sign in to vote

  Hi Bob,
  I have personally tested an SSD as Windows system volume and also found situations, in which setup was simpy stuck - so yes, this could be a reason (especially the timing may be too sensitive for some tasks).
  Windows Backup is also part of Windows Server 2003 OS (although not supported in Windows Home Server), so it would be worth a try, if a restore works directly to that disk.
  
  A multi boot installation cannot be recommended, since this may mess up the WHS core components (you would have to ad a disk or misuse a drive, which is part of the storage pool). While this could function in theory, I would not recommend this on a non test machine.
  
  If you have a spare disk, install XP to that disk.

  • Proposed as answer by kariya21Moderator Friday, February 6, 2009 2:40 PM
  • Marked as answer by Lara JonesModerator Saturday, February 14, 2009 7:40 PM

  Monday, January 19, 2009 10:20 PM

  Moderator