Forum Discussion
23 Replies
- CraigVModerator
Hi Adam,
First thing to do is open a command prompt and type: vssadmin list writers. Make sure all the writers are stable & running...if not, then they're in error, and you can do 1 of 2 things:
1. Restart the server in question on which this error is happening.
2. Reregister the VSS *.dlls as per the TN below:
http://www.symantec.com/business/support/index?page=content&id=TECH70486
Thanks!
- Adam_BallLevel 4
Hi Craig,
Thanks for your reply.
All of the writers seem to be OK.
Any ideas?
Thanks
- CraigVModerator
...mmm, if not on R3 with SP2, then upgrade to that. Not guaranteed to fix your issue, but you'll be on the latest version.
What happens if you run this job manually? Does is succeed? Does your job run during a maintenance window of some application?
Thanks!
- Adam_BallLevel 4
I tried to manually start the job, however, this failed aswell!
It got to snapshot processing and stopped....
any ideas?
Thanks
- CraigVModerator
Have you selected the option to let BE choose the VSS provider? Otherwise select the Microsoft provider & make sure that AOFO isn't selected in the job.
- Adam_BallLevel 4
Yes we have tried all of this.
Its really strange!
- Adam_BallLevel 4
I have remounted the Second Storage group... could this be the cause?
- CraigVModerator
...it could very well be. Run a backup again and see how it runs.
- TheMykeyReturnsLevel 2
I have been working with adam on this and can confirm that this did not work on last night backup.
The backup failed again with the error code (0xE0008516)
Any other ideas for a solution would be greatly appreciated
Cheers
- Adam_BallLevel 4
Hi Craig,
preformed the job again after remounting the storage group, however, failed again. Myself and Micheal (Poster above) are running out of ideas!
Any more suggestions?
We are looking at preforming an upgrade to R3, but would like to ideally sort this without an upgrade as we would like to minimise the amount of down time caused.
Thanks
Related Content
- 8 years ago
- 9 months ago