XP SP3 - Volume shadow copy

Here you can find everything you need to know about Dll-Files. You can also share your knowledge regarding the topic.

Moderators: DllAdmin, DLLADMIN ONLY

Post Reply
rd
Posts: 1
Joined: 03 Jun 2009, 23:00

XP SP3 - Volume shadow copy

Post by rd »

I have been having some trouble getting various imaging software to work.
They all hang on starting the backup. Working with "Macrium Reflect" it was
determined that I should follow this article for solution:
http://www.macrium.com/blog/2008/09/26/ ... rrors.aspx

I followed the instructions, found that VSS was on manual start. I changed
to automatic and rebooted. I then ran the batch file the article suggests it
is:
cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s /i eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll
vssvc /register
net start swprv
net start vss

The batch got stuck after:

" regsvr32 /s /i swprv.dll"

and would not progress further. The image process continues to hang at the
start of the backup.

The response was "swprv.dll is the Microsoft Volume Shadow Copy Service
software provider dll. You will need to contact MS support on this I'm
afraid."

So here I am. Suggestions?

twayne
Posts: 18
Joined: 03 Apr 2010, 23:00

Re: XP SP3 - Volume shadow copy

Post by twayne »

RD wrote:
> I have been having some trouble getting various imaging software to
> work. They all hang on starting the backup. Working with "Macrium
> Reflect" it was determined that I should follow this article for
> solution:
> http://www.macrium.com/blog/2008/09/26/ ... rrors.aspx
>
> I followed the instructions, found that VSS was on manual start. I
> changed to automatic and rebooted. I then ran the batch file the
> article suggests it is:
> cd /d %windir%\system32
> net stop vss
> net stop swprv
> regsvr32 /s ole32.dll
> regsvr32 /s oleaut32.dll
> regsvr32 /s vss_ps.dll
> vssvc /register
> regsvr32 /s /i swprv.dll
> regsvr32 /s /i eventcls.dll
> regsvr32 /s es.dll
> regsvr32 /s stdprov.dll
> regsvr32 /s vssui.dll
> regsvr32 /s msxml.dll
> regsvr32 /s msxml3.dll
> regsvr32 /s msxml4.dll
> vssvc /register
> net start swprv
> net start vss
>
> The batch got stuck after:
>


> " regsvr32 /s /i swprv.dll",,,,,,, *<=====* You might try removing
> the /s from here so you can see the messages it creates. The error
> message there might be useful/explanatory.
You could remove it from the preceding one too, to see if it says
anything useful.


>
> and would not progress further. The image process continues to hang
> at the start of the backup.
>
> The response was "swprv.dll is the Microsoft Volume Shadow Copy
> Service software provider dll. You will need to contact MS support on
> this I'm afraid."
>
> So here I am. Suggestions?

There really isn't anything wrong with setting the VSS services to auto
but manual is also OK. Manual I beleve is the default setting and mose
people leave it at manual to prevent boot-time loading of excessing
applications. But no big deal either way.
Any chance you're missing ticking a box to use shadow copy in the
program/s?

What imaging programs have you been trying? You say "various" ones but
then only mention one.

One way to determine whether shadow copy is working properly is to use
XP's own ntbackup.exe to back up a small set of files; say a System
State. It's definitely required for backing that up and it's a fairly
fast set of files to backup.
ntbackup.exe DOES have a checkbox to tick for using the shadow copy
services, in the Advanced area of settings. Unticked, it will turn them
off. Ticked, it will turn them on. Be sure it's ticked; it should be
automaticall ticked when you chose System State to back up.
If that box is ticked, and ntbackup.exe fails to back up the System
State, then there is definitely a system file problem or corruption
somewhere and it'll have nothing to do with the imaging program/s.
But if the System State is correctly created, the the program/s are
somehow at fault. I'd start by very carefully reading every screen and
watching to be sure everything is set properly. If that doesn't help
anything, then go right to the source of where you got the software and
explain to them what's happening.

You did, of course, do a Restart before performing any of this work,
right?
An additional thing you could try is to disconnect your modem from the
'net and turn off you AV during the installs.
Just remember to turn it back on and reconnect when you're done.

HTH,

Twayne`

Post Reply