SQL Server Fix : The semaphore timeout period has expired

Sometime you may see this unusual error message in job history.

Exact Error Message:

Write on
““\\server-name\e$\SQLBackup\user_db_full.bak” failed: 121(The semaphore timeout period has expired.) [SQLSTATE 42000] (Error 3202) A nonrecoverable I/O error occurred on file “\\server-name\e$\SQLBackup\user_db_full.bak:” 59(An unexpected network error occurred.). [SQLSTATE 42000] (Error 3271) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013).

You may have to rerun the job step taking backup if it doesn’t help, please ensure the network location is accessible where backup is being performed. If a batch job is scheduled through scheduled tasks increase the time limit in Scheduled tasks (which runs that bat file) with a couple of hours and then the backup should run without any errors.

Just one of those error messages that are hard to determine the right solution for….




2 Responses

  1. Hey Amit,

    I am facing the same issue of “The semaphore timeout period has expired” while taking full db backup to remote location. Its failing after sometime, not immediately. Network location is accessible. What would be the probable reasons and its solution?


    • Hi Vivek,

      Please check your network connectivity.

      Please ping and see if continuous reply you are getting for that server. eg. ping serverip -t

      Let me know your response..

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: