COM failure

[Ryan Olf]

I'm trying to run shadowspawn with robocopy on Windows XP. I am getting the following (verbose output). The program claims a "COM failure," and robocopy command never runs.

Here is the output:

ShadowSpawn (c) 2011 Craig Andera. shado...@wangdera.com

Argument 0: C:\backup\shadowspawn.exe

Argument 1: /verbosity=4

Argument 2: C:\data

Argument 3: Q:

Argument 4: robocopy

Argument 5: Q:\

Argument 6: Z:\e4main-current\backup\data

Argument 7: /COPYALL

Argument 8: /MIR

Argument 9: /B

Argument 10: /FFT

Argument 11: /R:1

Argument 12: /W:1

Argument 13: /LOG+:robocopy_backup20111025.log

Argument 14: /NFL

Argument 15: /NDL

Calling CoInitialize

Shadowing C:\data at Q:

Calling CreateVssBackupComponents in GetSystemProviderId

Calling InitializeForBackup in GetSystemProviderId

Looking for the system VSS provider

Calling backupComponents->Query(enum providers)

Calling IVssEnumObject::Next

Examining provider MS Software Shadow Copy provider 1.0 to see if it's the system provider...

...and it is.

Calling CreateVssBackupComponents again

Calling InitializeForBackup again

Calling GatherWriterMetadata

Waiting for call to GatherWriterMetadata to finish...

Calling QueryStatus for GatherWriterMetadata

Call to GatherWriterMetadata finished.

Calling GetWriterMetadataCount

Calling GetWriterMetadata

Writer 0 named MSDEWriter

Writer has 3 components

Component 0 is named master, has a path of E4MAIN\SQLEXPRESS, and is not selectable for backup. 0 files, 0 databases, 2 log files.

Database log file 0 has path c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf

Database log file 1 has path c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf

Component 1 is named model, has a path of E4MAIN\SQLEXPRESS, and is not selectable for backup. 0 files, 0 databases, 2 log files.

Database log file 0 has path c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\model.mdf

Database log file 1 has path c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\modellog.ldf

Component 2 is named msdb, has a path of E4MAIN\SQLEXPRESS, and is not selectable for backup. 0 files, 0 databases, 2 log files.

Database log file 0 has path c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf

Database log file 1 has path c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf

Component 0 has name master, path E4MAIN\SQLEXPRESS, is not selectable for backup, and has parent (no parent)

Component 1 has name model, path E4MAIN\SQLEXPRESS, is not selectable for backup, and has parent (no parent)

Component 2 has name msdb, path E4MAIN\SQLEXPRESS, is not selectable for backup, and has parent (no parent)

Calling GetWriterMetadata

Writer 1 named Microsoft Writer (Service State)

Writer has 3 components

Component 0 is named Content Indexing Service, has a path of (null), and is not selectable for backup. 0 files, 0 databases, 0 log files.

Component 1 is named Config Directory, has a path of (null), and is not selectable for backup. 1 files, 0 databases, 0 log files.

File 0 has path %SystemRoot%\Repair\Backup\ServiceState\ConfigDirectory\*

Component 2 is named Event Logs, has a path of (null), and is not selectable for backup. 1 files, 0 databases, 0 log files.

File 0 has path %SystemRoot%\Repair\Backup\ServiceState\EventLogs\*

Component 0 has name Content Indexing Service, path , is not selectable for backup, and has parent (no parent)

Component 1 has name Config Directory, path , is not selectable for backup, and has parent (no parent)

Component 2 has name Event Logs, path , is not selectable for backup, and has parent (no parent)

Calling GetWriterMetadata

Writer 2 named Microsoft Writer (Bootable State)

Writer has 2 components

Component 0 is named COM+ Registration Database, has a path of (null), and is not selectable for backup. 1 files, 0 databases, 0 log files.

File 0 has path %SystemRoot%\Repair\Backup\BootableSystemState\ComRegistrationDatabase\*

Component 1 is named Registry, has a path of (null), and is not selectable for backup. 1 files, 0 databases, 0 log files.

File 0 has path %SystemRoot%\Repair\Backup\BootableSystemState\Registry\*

Component 0 has name COM+ Registration Database, path , is not selectable for backup, and has parent (no parent)

Component 1 has name Registry, path , is not selectable for backup, and has parent (no parent)

Calling GetWriterMetadata

Writer 3 named WMI Writer

Writer has 1 components

Component 0 is named WMI, has a path of (null), and is not selectable for backup. 1 files, 0 databases, 0 log files.

File 0 has path C:\WINDOWS\system32\WBEM\Repository\*.*

Component 0 has name WMI, path , is not selectable for backup, and has parent (no parent)

Calling StartSnapshotSet

Calling GetVolumePathName

Calling AddToSnapshotSet

Aborting backup.

There was a COM failure 0x80042317 - ShadowSpawn.cpp (301)

Any advice? Thanks,

Ryan

[Craig Andera]

This link [1] suggests you may have hit the maximum number of
allowable snapshots, and suggests a resolution. Give that a try and
ping us back if that doesn't fix the problem. Good luck!

[1] http://kb.backupassist.com/articles.php?aid=2979

[Ryan Olf]

I don't know what solved the problem, but it works now. I was unable to follow the instructions in that article, as in XP it appears there are no options to view shadow copies. Rebooting (again..) seemed to help. I may have installed some VSS tools in the meantime.... Anyway, all is well.
Ryan

[Craig Andera]

> I don't know what solved the problem, but it works now. I was unable to
> follow the instructions in that article, as in XP it appears there are no
> options to view shadow copies. Rebooting (again..) seemed to help. I may
> have installed some VSS tools in the meantime.... Anyway, all is well.

Glad you got it working. I suspect it was the reboot - that probably
cleared out some old shadow copies, which can be created by a bunch of
different things.