EBAB03F1: The semaphore timeout period has expired. Error E7D10046: Unable to set file size. Error EBAB03F1: The specified network name is no longer available

  • Modified Date:
  • Article ID:000041632


Backup job is failing with the following error message.

Error Message

EBAB03F1: The semaphore timeout period has expired. Error E7D10046: Unable to set file size. Error EBAB03F1: The specified network name is no longer available


On occasions, backup jobs may fail when using Backup Exec System Recovery. The error "EBAB03F1: The specified network name is no longer available" is typically due to network latency, timeouts, or the resource is no longer available.

To troubleshoot the error, perform the following steps:
1) Verify network connectivity by running PING <IP Address> to the Windows Share or remote storage device.
2) Run a backup to a locally attached device to rule out the server being backed up as the source of the problem.
3) Create a new Windows Share or folder and run a backup to the new location using \\<ip address>\<share name> instead of a drive mapping.
4) Disable any firewall applications
5) Enable Network Throttling per Technical Document HOWTO48435  http://www.symantec.com/docs/HOWTO48435
6) If saving to an array (RAID, SAN, etc), check each individual disk in the array. If there is a bad or failing block, and the operating system\controller card has not yet picked it up, SSR\BESR may attempt to read or write to that block and throw this error. Run a thorough disk check on all disks in the set using a recommended programs from the RAID controller mftr. 
Network Considerations:
 The backup speed is limited by the speed of the physical connection. The rate at which the backup runs depends on the make/model of network cards, the mode/frame type configuration for the adapter, the connectivity equipment (hubs, switches, routers, and so on), and operating system settings. Backups to a local disk can usually backup at a higher rate of speed than backing up across a network.
A common reason for slow network backups can be networking configuration. Features such as "full-duplex" and "auto-detect" may not be fully supported in every environment. Manually set the speed to 100 Mb and the duplex to half/full for the server side. Find out which Ethernet port the server is connected to on the switch, and set the SWITCH PORT setting to 100 MB and half/full duplex. Do this for the backup server switch port, and any switch ports for machines being backed up.
When a hub is in place instead of a switch, full duplex may not be supported, see the Original Equipment Manufacturer for details on device features. Also, both the switch and the network card must have matching settings, for instance, if the switch port is set to 100 half, the NIC for the server should also be set to 100 half.
Another common cause could be the NIC driver. Update the network card drivers on the server and remote machine. Also make sure that the link speed/duplex values are set properly on all machines and that networking errors are not occurring in the Windows Event Viewer logs. Check the event logs for any other warnings, errors, or normal events that may take place when the backups run.
7) As an additional troubleshooting step, Symantec has an agreement with Apparent Networks to provide a network utility called AppCritical. This utility will provide Symantec Technical Support additional information and possibly identify bottlenecks or other underlying issues in the network infrastructure. This utility can be obtained at the following site:  





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



Did this article answer your question or resolve your issue?


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


How can we make this article more helpful?

Email Address (Optional)