ViceVersa/VSS ceases to function after some time

[Nimral]

Hi TGRMN,

after ViceVersa had been working a while, successfully replicating files, things *somehow* went very bad. Nobody touched anything (they say), nobody installed or deinstalled anything (they say), so there are no clues where to start searching. Facts is: the source files do not get replicated to the target server any more. All I have is this: normally the replication job runs scheduled with vvlauncher. If I start the very same job manually, I get the following message on the Viceversa console:

Adding volume \\?\Volume{c73fbf11-fbbc-11dd-9b88-806e6f6e6963}\ [C:\] to the shadow set...
ERROR: COM call "m_pVssObject->AddToSnapshotSet((LPWSTR)volume.c_str(), GUID_NULL, &SnapshotID)" failed.
- Returned HRESULT = 0x8004230f
- Error text: VSS_E_UNEXPECTED_PROVIDER_ERROR [Volume Shadow Copy creation failed for c:\. VSS_E_UNEXPECTED_PROVIDER_ERROR]
[Volume Shadow Copy creation failed for c:\. VSS_E_UNEXPECTED_PROVIDER_ERROR] Error.

Furthermore, examining the application eventlog, I noticed that beginning yesterday there is an error logged every 3-4 seconds:

Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details Cannot ask provider {b5946137-7b9f-4925-af80-51abd60b20d5} if volume is supported. [0x8000ffff] [hr = 0x8000ffff].

Restarting the Volume Shadow Copy service or rebooting the server does not help in any way. Can you use this vague info to help me tracking the problem? Any hints/leads welcome.

OS is Windows 2003 R2, Viceversa Version is 2.5 (2500).

Thanks

AL.

[TGRMN Software]

Hello

Problem seems to be related to the Microsoft VSS Exchange Writer. On Google there are many results if you search for << Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details Cannot ask provider {b5946137-7b9f-4925-af80-51abd60b20d5} if volume is supported >>

To solve, try listing all the shadows present in the system with command

vssadmin list shadows

and then delete the most recent shadows... they could be the problem.

Also verify that all the writers are OK, with

vssadmin list providers

thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[TGRMN Software]

There's also a recent VSS update for Windows Server 2003 on the Microsoft site

http://support.microsoft.com/default.aspx?kbid=833167
and this one too
http://www.microsoft.com/downloads/details.aspx?FamilyID=ae17b7ef-3c02-496a-bb46-770c04e42b5c&displaylang=en

but I do not know if they solve this issue. thanks

--
www.tgrmn.com
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com