RE: NTBackup Tape Errors Windows 2003

[Greg]

I have the exact same problem but with Windows 2003 SBS SP1. Backups were
working fine for 6+ months and then started failing. Any news?

"Matt" wrote:

> Hello,
>
> I have a windows 2003 server SP1 which errors when trying to backup to tape
> using NTBackup.
> The error messages are
> ----------
> Event Type: Error
> Event Source: VSS
> Event Category: None
> Event ID: 8193
> Description:
> Volume Shadow Copy Service error: Unexpected error calling routine
> CoCreateInstance. hr = 0x80070057.
>
> ---------
> Event Type: Error
> Event Source: VSS
> Event Category: None
> Event ID: 11
> Description:
> Volume Shadow Copy Service information: The COM Server with CLSID
> {faf53cc4-bd73-4e36-83f1-2b23f46e513e} and name VSSEvent cannot be started.
> [0x80070057]
>
> ----------
> Plus report from backup log is:
> Volume shadow copy creation: Attempt 1.
> Timeout before function completed
>
> Error returned while creating the volume shadow copy:0xffffffff.
>
> Error returned while creating the volume shadow copy:ffffffff
> Aborting Backup.
>
> I would be very grateful of help.
>

[Greg]

I finally found a solution to this problem. I found other articles similar
to this but the trick is to be in the c:\windows\system32 directory when
registery the DLLs. I was registering them from the 'Run' prompt and it
wasn't working. I went to a command prompt and changed directory to
c:\windows\system32 and then executed the commands. It worked!!!! Here's
the article I followed:
*****************
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.

[Benton [MSFT]@discussions.microsoft.com Jim Benton [MSFT]]

Please note that this procedure should NEVER be attempted on a system running
Vista or Windows Server 2008. The installation of these operating systems is
manifest based, not driven by binary self-registration. Unfortunately, many
binaries still contain the self-registration code, but executing the code can
actually create new problems and in some cases completely break features in
the OS. This is true of the VSS related binaries listed below.