Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Completed status: Completed with exception

Created: 19 Nov 2012 • Updated: 21 Nov 2012 | 5 comments

Hi,

 

We are currently experiencing "completed with exceptions" on our backup job status, on job logs, here are the exceptions

 

Backup- \\"servername"\System?State \\"servername"\System?State
VSS Snapshot warning. File c:\windows\system32\wsmprov.dll is not present on the snapshot.
VSS Snapshot warning. File c:\windows\system32\wsmcl.dll is not present on the snapshot.
VSS Snapshot warning. File c:\windows\system32\corpol.dll is not present on the snapshot.
VSS Snapshot warning. File c:\windows\system32\mstime.dll is not present on the snapshot.

As a workaround, we created a blank file using the filenames listed above. This method worked and completed the backup job but creating those files caused the server to hang up on reboot. Is there any other options to fix this error? thank you very much for replies in advance.

Comments 5 CommentsJump to latest comment

Donald Eady's picture

You have already done the suggested work around. You might try recreating the job and verifying that the files in questions are not in the selection list. Additionally you may want to contact the venders that the files belong to for removal / cleanup instructions ... view reading below 

 

http://www.symantec.com/docs/TECH126412

 

I hope this posting was helpful

  

pkh's picture

 you may want to contact the venders that the files belong to for removal / cleanup instructions

If you have done some research, you would have known that the missing files are Windows components.  How do you propose that they be removed?

droidz_b20's picture

Thanks for your replies, I have recreated the job, recreated selections, but this 4 exceptions still occur, this 4 files are i think Windows components which are removed after windows update. This issue is still not resolved, any other suggestions? thanks in advanced

pkh's picture

You can try searching the registry and delete any references to these modules.

Mayuresh Thule's picture

Hi,

This problem occurs if registry entries remain from a program that was uninstalled. If the program was not uninstalled successfully, the System Writer may list files to be backed up even though the files have been deleted.