Make sure VSSVC.EXE is running

runtime.org/driveimage_faq.htm#vss

Q. Why am I getting a VSS error when I try to backup a drive?

A. This error can occur if VSS (Volume Shadow Services) is not running properly on your system. This is not a DriveImage error. It is usually caused by poorly configured Windows systems.
inicio - ejecutar: services.msc
Please verify in Settings->Control Panel->Administrative Tools->Services that the following services are enabled:

MS Software Shadow Copy Provider
Volume Shadow Copy

Also make sure you are able to stop and start these services.
Possible reasons for VSS failures:
For VSS to work, at least one volume in your computer must be NTFS. If you use only FAT drives, VSS will not function.
The required NTFS volume does not need to be identical with the volume you want to image.
You should make sure that VSSVC.EXE is running in your task manager. If the problems persist, registering "oleaut.dll" and "oleaut32.dll" using "regsvr32" might help.
Without VSS you still can make images with locking or without locking.
Source
DriveXML is returning:

Could not initialize Windows Volume Shadow Service (VSS). ERROR C:\Program Files (x86)\Runtime Software\Drivelmage XML\vss64.exe failed to start. ERROR TIMEOUT Make sure VSSVC.EXE is running in your task manager. Click Help for more information.

VSSVC.EXE is running in Task Manager, as is VSS64.exe. Looking at the FAQ on the Runtime webpage this turned up:

Please verify in Settings->Control Panel->Administrative Tools->Services that the following services are enabled:

MS Software Shadow Copy Provider
Volume Shadow Copy

Also make sure you are able to stop and start these services.

==========================
Source
As part of the problem with MS Software Shadow Copy Provider service.
Symptoms:
Component Service woudn't expand.
MS Provider service woudn't start.
Error error 0x8000ffff when trying to run regsvr32 /i swprv.dll or vssadmin list providers
-------------------
Here is how I fixed it.
1) Deleted registry entry for SwPrv. (In fact some application deleted the service before, but I've imported it from the other computer). This is to allow COM+ app import later.
2) Deleted com3 key and COM+ folders as per messages and links above. Rebooted. This is to re-install COM+
3) Re-installed COM+ as per links above and MS recommendations. Now I was able to expand Component Services down to My Computer, but there was no MS Provider application there.
4) From the working computer with the same OS version I've exported MS Software Shadow Copy Provider application. To do so, Start Component Services, expand to "COM+ Applications", right-click on "MS ... Provider" name and choose "Export" from the menu. On the next screen choose "Export user identities with roles"
It will ask you for file name and location and it will create MSI package.
Copy the package to the troubled computer.
5) On the computer-in-need:
- start component services
- expand to "my computer" node
- right-click on "COM+ Applications" and choose "new" --> "Application"
- choose "Install pre-built application" button and navigate to the MSI package. Keep all defaults.
After the process completes, there is proper COM+ application as well as the service installed.
If there is any errors during the process, there is some left-over running and it is necessary to clean the registry and reboot then repeat COM+ install.

At this point you should be able to start both Shadow Copy-ralated services.
I had correct reply yto vssadmin list providers (it was error 0x8000ffff before)
I was getting an error 0x8000ffff in reply to vssadmin list writers and Event ID 8193 was logged in the App log. Backup was working at this point but without Shadow Copy.

Then I followed the steps from
http://blogs.technet.com/sdoakes/archive/2.../03/418722.aspx

www.msfn.org/board/index...?showtopic=70962
At command prompt::
Cd windows\system32
Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 vss_ps.dll
Vssvc /Register
regsvr32 /i swprv.dll ---- I was able to register it, before Iwas getting error 0x8000ffff
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll --- I had XP, I guess this should work for 2003 only.
regsvr32 msxml.dll --- the last 3 depend on what XML versions you have installed.
regsvr32 msxml3.dll --- if you get error here, re-install corresponding XML version
regsvr32 msxml4.dll
If errors, navigate to
C:\Windows\System32 directory and try the regsvr32 commands again.
2. After completing the registration of the DLL’s  type:
vssadmin list writers
3. You should see the writers listed.
4. Open Ntbackup and attempt to backup file or systemstate.
VSS needs NT Backup to work, if I remember correctly and its twin service MS Software Shadow Copy Provider (SwPrv)
You need NT Backup, too. For services, VSS and MVSC need to be Manual. Also, don't screw with anything that toasts MMC, or you're in a world of potential hurt here. Indexing is totally unneeded as an explicit service (I haven't used ot for over year in my installs)--but there are inter-component aspects extant (that's why you keep coming across references): we can remove it, but parts we keep that we need still imprint it on various interfaces--and it's one of these part you most likely made angry. Shadow Copy would certainly qualify...

=====================
Source2
groups.google.nl/group/microsoft.pu...9a95c0ac4a7a9b2
msfn.org/board/topic/70962-restore-volume-shadow-copy-vss-and-ms-software-sha/
backupassist.com/KnowledgeBase/...olumeShadowCopy
They also indicate that I need more files (stdprov.dll, eventcls.dll) which are not on the partition with the new install.
Performing the steps of the 1st link I am able to restore and start the "MS Software Shadow Copy Provider" on my own system (where it was not installed either as I discovered today), but not the "Volume Shadow Copy" (VSS).
Furthermore "vssadmin list providers" output is OK.