• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1012
  • Last Modified:

Volume Shadow Copy keeps dying.

I have an SBS2003 box on which for no readily apparent reason the VSC service Microsoft Software Shadow Copy Provider service both keep stopping.

The log file just shows they "entered the stopped state" i.e. its as if someone has clicked on the Stop Service button.

Clicking on the Start Service button re-starts them good as gold.

1) Any idea what could be stopping them?

2) Will the VSC "catch up", i.e. if the service is down for a while then comes back on line, do I still have full roll-back capability on the file system or will changes and deletions which took place whilst the service was down be un-roll-back-able?

0
ccomley
Asked:
ccomley
1 Solution
 
ccomleyAuthor Commented:
Well, what you lot seemed unable to help otu with is...

It isn't *supposed* to be "Automatic" it's supposed to be "Manual", the sheduled process starts and stops teh service on demand. It just mustnt be set to "Disabled".

0
 
wlfsCommented:
Hi ccomley,

I came along your question because I am encountering exactly the same problem as you did (also SBS2003).
Since your question is 5 month old, I was wondering whether you figured out the problem and some solution yet.
If so, I will open the same question again and happily reward you the 500 points.

I might add that the problem appeared only after installing the latest service pack 4 weeks ago.

Thanks in advance,
woolf
0
 
tspaCommented:
I am having the same issue. I have read a few Microsoft KB articles & still no luck...
0
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

 
tspaCommented:
A Volume Shadow Copy Service (VSS) update package is available for Windows Server 2003
http://support.microsoft.com/?id=833167
Give that link a try, I will report back my results
0
 
ccomleyAuthor Commented:
tspa, wlfs, if you look at my *comment* to my original question, you'll see that the problem was not that the service keeps dying, but that it isn't supposed to be running all the time at *all*. This was the mistake someone made to the system config.

The service is started when needed, runs, exits, and then waits to be called again. It isn't supposed to be running 24x7.

0
 
DarthModCommented:
PAQed with points (500) refunded

DarthMod
Community Support Moderator
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now