|
| | | | Post in reply to: Post in reply to: Rick
Are there any event log entries relating to VSS at the time you get the
error? What do they say (and what EventID do they show)?
Just yesterday I had a user with a VSS failure (on XP, not Vista); the
problem was caused by a bug in the UNinstaller for Visio, which when
removing the program left behind inconsistent Registry entries which
confused the poor little mind of VSS. (Clearly, whoever wrote the VSS code
never heard of the strange concepts of either defensive programming or
useful error messages...but what else is new?)
Joe Morris
|
| |
| | | | | Post in reply to: Joe Morris
Yes, here's the VSS error, Event ID 12293:
Volume Shadow Copy Service error: Error calling a routine on a Shadow
Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details
PreFinalCommitSnapshots({8e323fb6-edac-468b-9276-08fdf4656cac}, 1) [hr =
0x8000ffff].
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet
Immediately thereafter this generated the Windows Backup error, Event ID
4100:
File backup failed because a shadow copy could not be created. The
system might be low on resources. The error is: The shadow copy provider
had an unexpected error while trying to process the specified operation.
(0x8004230F).
Thanks for any help.
|
| |
| | | | | Post in reply to: Rick
Even if you have an Administrator account, you normally operate with the
powers of a normal user.
You still need to invoke your superpowers when needed, like Popeye and his
spinach.
1. On the Start menu, click "All Programs".
2. Click "Accessories".
3. Right-click "Command Prompt" and choose "Run as Administrator" from the
shortcut menu.
4. When the User Account Control dialog appears, click "Continue".
5. Now run VSSADMIN
--
Vista Home Premium 32 SP1
http://get.live.com/wlmail/overview
news:zbueqJ4IHA.4856@TK2MSFTNGP02.phx.gbl...
l2h41w2IHA.5024@TK2MSFTNGP03.phx.gbl>,
|
| |
| | | | | Post in reply to: Rick
In article <6S77DP4IHA.3624@TK2MSFTNGP05.phx.gbl>,
That's caused by exceeding the maximum number (not size) of shadow
copies per volume. I don't know of a way to set this but if you delete a
shadow copy then backup should proceed. Maybe call vssadmin and
ntbackup from a script so that one vss is always deleted before backup runs??
|
| |
| |
|