backup failing with error

One of the requirements for restoring Windows System State is that the backup software must restore all the services configured on the system. Since the binaries associated with the service may be running, the backup software has to take a VSS snapshot of the volume containing the service binaries. This error message is saying that there is a service running from a network share (in this case \\

If you need more information or have more questions, please don't hesitate to reply.

Hi Ian Anderson,

Thanks a lot for reply, but i didn't understand how to avoid this error and successfully complete the backup.Can you please suggest possible solution for this?

If you want to take system state backups of this system, all services need to be configured to run from local storage, not from the network. Open the services control panel and check the properties of the services listed there. There is a field in the Properties dialog for each service called "Path to executable". According to the error message, there is at least one service on this system where "Path to executable" starts with \\ \admin$. Once you know which software installed the service, look at the documentation for that software or contact the software vendor for help reconfiguring the service to run locally.

Thanks to Ian Anderson fix.

I had the same failure error, on checking services one had been installed locally with UNC path to executable.  Service was amended in regedit to follow local path c:\windows\system32\xy.exe and now system state backup works fine.

The same error message when using v6 client  "Error: Unable to determine if volume \\10.x.x.x\admin$ is supported by Microsoft system provider GUID ={b5946137-7b9f-4925-af8051abd60b20}, ",

Hi Ian,

I am having issue with the system state backup.

avtar logs give :

avvss Error <18040>: Detected a UNC Share Volume '\\d072007\fnprod\'. One of the system services is configured to use network path. Microsoft system provider does not support snapshot of network paths. Please correct the mis-configuration and re-run the backup

2014-11-13 10:26:05 avvss Error <12077>: VSS returned an error message exiting HR = 0x80004005

considering that \\d******7\fnprod\ is a path to be executable, when verified found

The Service BootReporterNET  has that path configured and is in delayed start.

although i have stopped the service & run a test system state backup it fails again.

the windows backup utility reports as :

The backup operation that started at '‎2014‎-‎11‎-‎14T01:50:12.202576200Z' has failed with following error code '2155347997' (The operation ended before completion.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

Please advice on the fix.

The fix is to ensure that the binary for this service is installed on local storage as I've outlined above.

Thank you Ian.

Ian, i have a one part question on a VSS backup issue.

I see a consistent system state failure for a windows 2k8 server, whereas the filesystems writes fine.

but the concern is... i still see the system state available for restore under the "Backup & Restore" tab selected the VSS Plugin on the date of restore.

what exactly does it mean the restore dates changing to yellow.

Backups that complete with exceptions or complete with errors (as opposed to explicitly failing) may appear in the GUI but are not guaranteed to be recoverable. Without seeing the actual completion status of the backup, I can't really tell you more.

A yellow circle appears on any day for which there was at least one completed backup. Note that backups are displayed by end time, so backups that completed after midnight may not be where you expect to find them.

Thanks Ian.

Ian, as per what was discussed.

Avamar does not run on systems which completely are managed through remote call in LAN or WAN. As there is always a service running from the local Host.

How the host is managed is irrelevant. The issue documented in this thread is that there is a system service installed to a network path and the Microsoft ASR writer does not support taking a snapshot of a network path.

I don't think I understand your question.

For example :

The systems which boot up via PXE Boot.

The ability to run an Avamar backup depends on whether or not the client agent is installed, running, and activated. If so, you can back the client up. If not, you can't.

This is straying really far from the original topic. If you have further unrelated questions, please start a new thread.