Switch Alt-Ctrl or Simulate a Mac Keyboard in a regular PC keyboard.
September 25, 2012
HOW TO: WD Sharespace RAID 5 Data Recovery and some handy notes on this device.
January 16, 2013
- Either there is no space left on –at least one of your VMs. Please note that free space for correct vss working should be at least 1GB for vhds of 100GB of space.
- Or at least one vss writer fails on one of your vms. Go back to step 1 and execute vssadmin list writers on every VM you have. At least one fails. On the one that fails (personally seen it on w2k3 Exchange VM were the Exchange Writer was on error) make a batch file containing the following (I have put some pauses in order to see who the procedure works out). Save the batch as whatever you like .bat and WATCH IT!!! Before Re-registering the vss and required dlls you have to switch your path to windows\system32!!! If you don’t, then the vss will not run actually and when you run vssadmin list writers nothing will come up. So pay attention!!!
Step1 :
Follow info on http://support.microsoft.com/kb/940349
Download and install update.
Restart
Step2:
Open Cmd and run vssadmin list writers
No error should appear.
Check if backup works (It is likely it won’t, instead of running the whole W2k8 Hypervisor backup, try backing up the current VM by it’s own NTbackup, try system state or any folder)
If it does not work proceed to step3:
Step3:
Regedit
Locate and export the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions
Export the key/folder somewhere in order to get it back if smt goes wrong
Now delete that key/folder (No worries Windows will recreate it)
Step4:
Restart each of the following services in that exact order:
– COM+ Event System
– COM+ System Application
– Microsoft Software Shadow Copy Provider
– Volume Shadow Copy
If one of the services is on stop mode, change the startup type to automatic and start the service
Step5:
Open Cmd and run vssadmin list writers
If errors still show up…go the last …step6
Step6:
Watch it you have to switch your path to windows\system32 – otherwise you will see no writes in vssadmin.
Make a batch copy-pasting the following:
net stop swprv
pause
cd..
cd windows
cd system32
pause
regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 vss_ps.dll
vssvc /Register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 vss_ps.dll
vssvc /register
regsvr32 /i swprv.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll
pause
Net Start vss
Net Start swprv
pause
vssadmin list writers
pause
The batch will list vss writers at the end. Check if all are in stable.RESTART!!!!
Go back to your HyperV and try to back up.
