Error EC8F17B7: Cannot create recovery points for job: Drive Backup of <drives> Error E7D1001F: Unable to write to file. Error EBAB03F1: The specified network name is no longer available. Error E7D10046: Unable to set file size.

Problem

Backup job fails with the following error message.

Error Message

Error EC8F17B7: Cannot create recovery points for job: Drive Backup of Error E7D1001F: Unable to write to file.
Error EBAB03F1: The specified network name is no longer available.
Error E7D10046: Unable to set file size.

Cause

On occasion, backup jobs may fail when using Symantec System Recovery (SSR) or Backup Exec System Recovery (BESR) in an environment also running Symantec Endpoint Protection (SEP), the Symantec Endpoint Protection Manager (SEPM), or other 3rd party antivirus solutions. The error "EBAB03F1: The specified network name is no longer available" is typically due to the antivirus blocking communications causing a Delayed Write Failure. The backup failures are usually at a random percentage during the job. In addition to antivirus, any firewall application can also block traffic causing job failures to occur.

 

Solution

To troubleshoot the error, perform the following steps:
  1. Ensure network issues are resolved per Technical Document TECH55684  www.symantec.com/docs/TECH55684
  2. Use NetMon and Wireshark to determine if there is packet loss, firewall blocking, etc.
  3. Open the System Log in the Windows Event Viewer and look for Delayed Write Failures.
    Example:
    Event Type: Information
    Event Source: Application Popup
    Event Category: None
    Event ID: 26

    Description:
    Application popup: Windows -Delayed Write Failed : Windows was unable to save all the data for the file \<file name>. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. 
     
  4. If a Delayed Write Failure occurs, open the Application Log in the Windows Event Viewer and verify the time the backup job failed occurred after the Delayed Write Failure.
     

 
Possible Workarounds: 
  1. Stop the Symantec Endpoint Protection services on the client / server and backup destination then rerun backup job.
  2. Add the server being backed up to the Excluded Hosts List in the Intrusion Prevention Policy for Symantec Endpoint Protection:
    www.symantec.com/docs/HOWTO27084
    www.symantec.com/docs/TECH104434
     
  3. Temporarily disable the Network Threat Protection
  4. Create a Firewall Exception in SEP 
    Allow Local/Trusted Application C:\Program Files\Symantec\Backup Exec System Recovery\Agent\VProSvc.exe
    Allow Local/Trusted Application C:\WINDOWS\system32\ntoskrnl.exe 
     
  5. Disable any firewall application.
 

 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)