E
Eric
I am unable to get the Volume Shadow Copy feature to work correctly. When I
first noticed the problem, I was getting both COM+ and VSS errors (together)
and couldn't even manually start the COM+ System Application service. I
searched around a lot and figured out that I needed to reinstall COM+, and I
did that following the instructions in
http://support.microsoft.com/default.aspx?scid=kb;en-us;315296. That got
rid of the COM+ errors, but VSS is still not working. I'm at a loss as to
what to do now.
If I try to do a backup using ntbackup I get the following in ntbackup's
log:
" Error returned while creating the volume shadow copy:8004230f
Reverting to non-shadow copy backup mode."
I also get (7 times if I was trying to backup the system state) the
following event in the Application Log:
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 12292
Date: 11/18/2004
Time: 4:29:18 PM
User: N/A
Computer: COMPNAME
Description:
Volume Shadow Copy Service error: Error creating the Shadow Copy Provider
COM class with CLSID {65ee1dba-8ff4-4a58-ac1c-3470ee2f376a} [0x80040154].
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 43 4f 52 53 4f 46 54 43 CORSOFTC
0008: 37 30 00 00 00 00 00 00 70......
0010: 43 4f 52 53 4f 46 54 43 CORSOFTC
0018: 36 30 00 00 00 00 00 00 60......
I figured out that the CLSID corresponds to swprv.dll. My system is on an
NTFS partition, and am backup up from it to a directory on the same
partition, and have close to 3 GB free. I also have other partitions, both
FAT and NTFS, but they aren't involved.
Other information:
If I try running "vssadmin list shadows", I get:
"vssadmin 1.0 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.
Error: 0x8000ffff"
and I wind up with an event in the Application log that is identical to the
ones from ntbackup.
If I run "vssadmin list providers" I get:
"vssadmin 1.0 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.
Provider name: 'MS Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
and no errors. FWIW, the value of
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}\CLSID
is {65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}, which corresponds to the CLSID in
the Application Log event.
If I run "vssadmin list writers" I get:
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'Microsoft Writer (Service State)'
Writer Id: {e38c2e3c-d4fb-4f4d-9550-fcafda8aae9a}
Writer Instance Id: {7d991ab0-6105-48cf-ae14-8acc7c83e45a}
State: [1] Stable
Writer name: 'Microsoft Writer (Bootable State)'
Writer Id: {f2436e37-09f5-41af-9b2a-4ca2435dbfd5}
Writer Instance Id: {b4782007-66cb-4ff8-bea6-db8cdb6f08e4}
State: [1] Stable
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {1fefd6c7-55f3-4f8f-8313-3e48e03c7686}
State: [1] Stable
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {8662ab03-c4c5-4892-a50d-6acc66031664}
State: [1] Stable
which honestly means very little to me. But again, this doesn't cause an
error and I hope it might be useful to someone else.
I'm not including information about the COM+ errors because they seem to
have completely gone away. But if there is any more information that would
be helpful in diagnosing this, I would be glad to provide it.
If someone can help me figure out how to get VSS working again, I would
certainly appreciate it.
Eric
first noticed the problem, I was getting both COM+ and VSS errors (together)
and couldn't even manually start the COM+ System Application service. I
searched around a lot and figured out that I needed to reinstall COM+, and I
did that following the instructions in
http://support.microsoft.com/default.aspx?scid=kb;en-us;315296. That got
rid of the COM+ errors, but VSS is still not working. I'm at a loss as to
what to do now.
If I try to do a backup using ntbackup I get the following in ntbackup's
log:
" Error returned while creating the volume shadow copy:8004230f
Reverting to non-shadow copy backup mode."
I also get (7 times if I was trying to backup the system state) the
following event in the Application Log:
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 12292
Date: 11/18/2004
Time: 4:29:18 PM
User: N/A
Computer: COMPNAME
Description:
Volume Shadow Copy Service error: Error creating the Shadow Copy Provider
COM class with CLSID {65ee1dba-8ff4-4a58-ac1c-3470ee2f376a} [0x80040154].
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 43 4f 52 53 4f 46 54 43 CORSOFTC
0008: 37 30 00 00 00 00 00 00 70......
0010: 43 4f 52 53 4f 46 54 43 CORSOFTC
0018: 36 30 00 00 00 00 00 00 60......
I figured out that the CLSID corresponds to swprv.dll. My system is on an
NTFS partition, and am backup up from it to a directory on the same
partition, and have close to 3 GB free. I also have other partitions, both
FAT and NTFS, but they aren't involved.
Other information:
If I try running "vssadmin list shadows", I get:
"vssadmin 1.0 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.
Error: 0x8000ffff"
and I wind up with an event in the Application log that is identical to the
ones from ntbackup.
If I run "vssadmin list providers" I get:
"vssadmin 1.0 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.
Provider name: 'MS Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
and no errors. FWIW, the value of
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}\CLSID
is {65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}, which corresponds to the CLSID in
the Application Log event.
If I run "vssadmin list writers" I get:
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'Microsoft Writer (Service State)'
Writer Id: {e38c2e3c-d4fb-4f4d-9550-fcafda8aae9a}
Writer Instance Id: {7d991ab0-6105-48cf-ae14-8acc7c83e45a}
State: [1] Stable
Writer name: 'Microsoft Writer (Bootable State)'
Writer Id: {f2436e37-09f5-41af-9b2a-4ca2435dbfd5}
Writer Instance Id: {b4782007-66cb-4ff8-bea6-db8cdb6f08e4}
State: [1] Stable
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {1fefd6c7-55f3-4f8f-8313-3e48e03c7686}
State: [1] Stable
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {8662ab03-c4c5-4892-a50d-6acc66031664}
State: [1] Stable
which honestly means very little to me. But again, this doesn't cause an
error and I hope it might be useful to someone else.
I'm not including information about the COM+ errors because they seem to
have completely gone away. But if there is any more information that would
be helpful in diagnosing this, I would be glad to provide it.
If someone can help me figure out how to get VSS working again, I would
certainly appreciate it.
Eric