edwalt's - Things I Wish I'd known about SBS 2003....
The Volume Shadow Copy Service (VSS) component of Windows Server 2003 (This includes SBS 2003) coordinates the activities of providers, writers and requestors for creating and using shadow copies. During a backup operation the requestor uses VSS along with other components to define the type of backup operations in progress. Wow...sounds cool, so what does all of this mean? In a nutshell; If VSS isn't happy...backups arent happy.
So how do I know if there is an issue with VSS anyway?
Some of the symptoms we were seeing:
C:\VSSADMIN LIST WRITERS <enter> WARNING: This can take a while to run!
So whats the fix....
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:
Then register the following dlls and services (be sure you're still in the windows\system32 directory at your command prompt):
regsvr32 ole32.dllregsvr32 vss_ps.dllvssvc /Registerregsvr32 /i swprv.dllregsvr32 /i eventcls.dllregsvr32 es.dllregsvr32 stdprov.dllregsvr32 vssui.dllregsvr32 msxml.dllregsvr32 msxml3.dllregsvr32 msxml4.dll
Test the backup... If the issue still remains you may want to see if COM+ could also be an issue.
How do I check COM+ integrity?
If they all open without error, COM+ should be good. If they don't please see the instructions below:
Be sure the system account you are using is a member of the SQL Administrators group.
On a post SP1 Systems to Reinstall COM+
If you have Windows Server 2003 SP1 files available during this step. Sometimes you will receive errors when installing, you can safely ignore them.