VSS error

Error come up when i try to do ntbackup to file or tape. I tried diffrent ideas form microsoft but i am stuck.

Thanks for any suggestions

Event Type:      Error
Event Source:      VSS
Event Category:      None
Event ID:      20
Date:            30/03/2006
Time:            11:37:23
User:            N/A
Computer:      SERVER01
Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered.  This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider.  The error returned from CoCreateInstance on class with CLSID {faf53cc4-bd73-4e36-83f1-2b23f46e513e} and Name VSSEvent is [0x80040154].

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0000: 2d 20 43 6f 64 65 3a 20   - Code:
0008: 42 55 45 43 58 4d 4c 43   BUECXMLC
0010: 30 30 30 30 33 32 38 31   00003281
0018: 2d 20 43 61 6c 6c 3a 20   - Call:
0020: 42 55 45 43 58 4d 4c 43   BUECXMLC
0028: 30 30 30 30 37 30 39 36   00007096
0030: 2d 20 50 49 44 3a 20 20   - PID:  
0038: 30 30 30 30 35 30 37 32   00005072
0040: 2d 20 54 49 44 3a 20 20   - TID:  
0048: 30 30 30 30 34 35 38 38   00004588
0050: 2d 20 43 4d 44 3a 20 20   - CMD:  
0058: 22 43 3a 5c 57 49 4e 44   "C:\WIND
0060: 4f 57 53 5c 73 79 73 74   OWS\syst
0068: 65 6d 33 32 5c 6e 74 62   em32\ntb
0070: 61 63 6b 75 70 2e 65 78   ackup.ex
0078: 65 22 20 20 20 20 20 20   e"      
0080: 2d 20 55 73 65 72 3a 20   - User:
0088: 54 41 59 4c 4f 52 42 55   company
0090: 43 48 41 4c 54 45 52 5c   name\
0098: 61 64 6d 69 6e 69 73 74   administ
00a0: 72 61 74 6f 72 20 20 20   rator  
00a8: 2d 20 53 69 64 3a 20 20   - Sid:  
00b0: 53 2d 31 2d 35 2d 32 31   S-1-5-21
00b8: 2d 32 31 35 31 39 30 32   -2151902
00c0: 36 2d 31 30 37 36 31 31   6-107611
00c8: 36 35 39 38 2d 37 37 35   6598-775
00d0: 36 31 35 38 38 34 2d 35   615884-5
00d8: 30 30 20 20 20 20 20 20   00      
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hi mickinoz2005,

do you have SQL installed on the machine?


maybe also try running this

regsvr32 vss_ps.dll

taken from
Have you installed SP1 and all of the latest patches...?  There was a bug in SP1 that dealt directly withi ntbackup and VSS, here is the fix that MS gave another user:


:It is a bug with SP1.  The resolution is as follows.

Option 1 or Option 2.  I found option 2 easier as option 1 requires a server
restart and will mean AD DB & Log are both on C: drive.

1. Moving the AD log files back to the default location (“C:”).

2. Select “D:” (or a file in that volume) to force a shadow copy on it.
This, in turn will suppress the NTDS writer error.  (I created a dummy text
file on the drive where my NTDS Log files were and included in the backup

The likely reason behind those error messages is that AD is configured such
that it keeps the databases and the logs on separate volumes.
The AD writer (NTDS) will report an error if you try to create a shadow copy
set that has one of the volumes but not the other.
The problem is that in this configuration (AD databases and logs are on a
different volume) NTBackup doesn't pick up the correct set of volumes.
By selecting system state, NTBackup requests for a shadow copy to be created
on the boot volume.
By the time NTBackup requests for the location of the AD database and logs,
the shadow copy has already been created.
Thus, NTBackup will not create a snapshot on “D:”.
This throws the NTDS writer off, thinking that NTBackup is not going to pick
up all its data on D: thus causing an error.
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

mickinoz2005Author Commented:

Thanks for all tips but it still doesn’t work. In my sbs I have all ntds files in default location. I have re-registered all dll:
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

plus one for a sql. Restart a server and still nothing. I tried to compare these registry key from error ({faf53cc4-bd73-4e36-83f1-2b23f46e513e}) with other working sbs server and everything seems to be ok (the name, value, and permission on this key).

So if any other ideas I am looking forward to hear it.

Thanks guys for your time 
mickinoz2005Author Commented:
Just wondering if anybody has any more ideas on this one as the problem still exists and we need to get it fixed.

If we backup the server without system state we have no problem just when we include system state we have the above prob.
When you re-registered the DLL's did you first **stop** the volume shadow copy service, go to a cmd prompt navigate to c:\windows\system32??

in command shell-
---net stop vss
 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

Also, if the above steps do not resolve the issue, you may have to
reinstall the 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
install the COM+ Rollup from:

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

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.

oops forgot to add when in the cmd shell to navigate to c:\windows\system32, very important
mickinoz2005Author Commented:
Hi there,

The problem has not been solved, the guy looking after it has been away. i will get him back on to this.

So please keep this question open.


mickinoz2005Author Commented:
Hi all,

The solution to this problem was found at


Mazaraat you comment was close but it is missing some information thanks for your help anyway.

As this was solved by myself I would like a refund off the points please.



Hi mickinoz2005

Since you found the solution by yourself, and experts here gave valuable information, my suggestion will now be :

PAQ with points refunded


EE Cleanup Volunteer
Glad you were able to solve the problem
PAQed with points refunded (500)

Community Support Moderator

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.