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

[Angelos Pitsos]

Hello there!

I'm trying to run shadowspawn with robocopy on Windows XP, like Ryan
Olf here (http://groups.google.com/group/shadowspawn-tool/
browse_thread/thread/dacb69b66d359663) and I am getting the following
(verbose output). The program claims a "COM failure," and robocopy
command looks that never runs, exactly like Ryan's issue. The
difference is that the problem didn't solve after the computer's
restart.

The batch file I have created and I am running is the following:
<quote>
Net use B: \\antoniou\c$\PST /Persistent:NO
E:
CD\

E:\special_commands\ShadowSpawn.exe /verbosity=4 B:\ Q: robocopy Q:\ F:
\PST_Backups\Weekly\m.antoniou /s

Net use B: /delete
<unquote>


An here is the output:
<quote>
E:\>E:\special_commands\ShadowSpawn.exe /verbosity=4 \\antoniou\c$\PST
Q: roboco
py Q:\ F:\PST_Backups\Weekly\m.antoniou /s
ShadowSpawn (c) 2011 Craig Andera. shado...@wangdera.com

Argument 0: E:\special_commands\ShadowSpawn.exe
Argument 1: /verbosity=4
Argument 2: \\antoniou\c$\PST
Argument 3: Q:
Argument 4: robocopy
Argument 5: Q:\
Argument 6: F:\PST_Backups\Weekly\m.antoniou
Argument 7: /s
Calling CoInitialize
Shadowing \\antoniou\c$\PST 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 syste
m 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 Microsoft Writer (Bootable State)
Writer has 2 components
Component 0 is named COM+ Registration Database, has a path of (null),
and is no
t selectable for backup. 1 files, 0 databases, 0 log files.
File 0 has path %SystemRoot%\Repair\Backup\BootableSystemState
\ComRegistrationDa
tabase\*
Component 1 is named Registry, has a path of (null), and is not
selectable for b
ackup. 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 ba
ckup, and has parent (no parent)
Component 1 has name Registry, path , is not selectable for backup,
and has pare
nt (no parent)
Calling GetWriterMetadata
Writer 1 named MSDEWriter
Writer has 0 components
Calling GetWriterMetadata
Writer 2 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 (n
o parent)
Calling GetWriterMetadata
Writer 3 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 selectab
le 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 back
up, 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 pa
rent (no parent)
Calling StartSnapshotSet
Calling GetVolumePathName
Calling AddToSnapshotSet
Aborting backup.
There was a COM failure 0x80042308 - ShadowSpawn.cpp (301)

E:\>
<unquote>

I am looking forward for your lights...!

Thanks a lot in advance for your prompt attention.


Best regards,
Angelos Pitsos

[Craig Andera]

Hmm. Have you tried running chkdsk /r? This link [1] suggests that it
may fix the problem.

[1] http://social.microsoft.com/Forums/en-US/whssoftware/thread/9967a751-aa13-4f96-842c-13c44953ed48