-run "fixdlls"

-make sure all return success (msxml4.dll is not a must)

-if not, make sure all files exists and the batch is running from 
system32 dir

-check is successfull, if not Notice last part about re-registering com+ components:

-----------------------TXT----------------------------------------
Stefan, 


I had the same problem and had to call ms support. Here's my log from 
the support call, HTH. 


Thanks, 
Steven V. 


The problem was Volume Shadow Copy service would hang when ntbackup 
would start on a 2003 server, SP1. 
This kept us from doing an ntbackup to disk or tape. 


This is what we did: 
regsvr32 ole32.dll 
regsvr32 vss_ps.dll 
vssvc /register 
regsvr32 /i swprv.dll 
regsvr32 /i eventcls.dll 


vssadmin list providers 
vssadmin list writers 
(both of these above commands returned a list of providers and writers) 


---reboot, test backup, didn't work--- 


regsvr32 ole32.dll 
regsvr32 vss_ps.dll 


vssvc /register 


regsvr32 /i swprv.dll (got an error on this one after about 5 minutes) 
regsvr32 /i eventcls.dll 


regsvr32 es.dll 
regsvr32 stdprov.dll 
regsvr32 vssui.dll 


regsvr32 msxml.dll 


regsvr32 msxml3.dll 


regsvr32 msxml4.dll (not found) 


vssadmin list providers 
vssadmin list writers 
(this time, the list of providers and writers was blank. Oops.) 


---reboot, test backup, didn't work--- 


--reboot again---- 
net stop vss 


regsvr32 ole32.dll 
regsvr32 vss_ps.dll 


vssvc /register 


regsvr32 /i swprv.dll (successful this time) 
regsvr32 /i eventcls.dll 


vssadmin list providers 
vssadmin list writers 
(both of these above commands returned a list of providers and writers) 


----------reboot, test backup, success-------------- 


This was an email sent by the support rep: 


Resolution 


========== 


In most cases, re-registering the VSS binaries resolves the issue.  To 
re-register 
VSS binaries and services, first stop the *Volume* *Shadow* *Copy* 
Service: 


Open a command prompt and change directories to \windows\system32 (this 
is 
important when you begin registering the dlls): 


net stop vss 


Then register the following dlls and services (be sure you're still in 
the 
windows\system32 directory at your command prompt): 


regsvr32 ole32.dll 


regsvr32 vss_ps.dll 


Vssvc /Register 


regsvr32 /i swprv.dll 


rRegsvr32 /i eventcls.dll 


regsvr32 es.dll 


regsvr32 stdprov.dll 


regsvr32 vssui.dll 


regsvr32 msxml.dll 


regsvr32  msxml3.dll 


regsvr32 msxml4.dll 


Other items to check: 


On a SQL Server 


-------------- 


Be sure the system account is a member of the SQL Administrators group. 


IMPORTANT NOTE: In cases where the the above steps do not resolve, you 
may wish to 
reinstall COM+, and then re-register the services and binaries again. 


On a pre-SP1 system, you do not need to reinstall COM+.  On the Pre-SP1 
system 
install the COM+ Rollup from: 


883955 Availability of Windows Server 2003 COM+ 1.5 Rollup Package 3 
(requires a 
reboot). 


On a post SP1 System 


---------------------------------- 


Reinstall COM+ 


1. Backup and then delete HKLM\Software\Microsoft\COM3 


2. Boot to Recovery console and rename clbcatq.dll to ~clbcatq.dll.  Be 
sure to use 
the tilde. 


3. Boot to normal mode and in Control Panel, open the Add or Remove 
Programs tool, 
and then open the Add/Remove Windows Components tool. Do not make any 
changes, just 
click "Next". This reinstalls COM+. 


NOTE: You must have your Windows Server 2003 SP1 files available during 
this step.