job failed for time out of connection

Question

job failed for time out of connection

sqlfriend

SSC Guru

Points: 52794
More actions
March 23, 2015 at 1:38 pm

#302337

Hello,
We have a web service job running nightly. But last night it failed with the following message.
It looks like the application server tries to connect to SQL server, but timed out at the very beginning of the job.
The only thing I know is at weekend our network team did some battery and SAN migration changes on the application server and database server, and rebooted both servers, but the order of rebooting is application server first, then database server second. So I think maybe we should restart the server in the right order- SQL server first then application server next.
But there are another web service job running early this morning too, they use both of servers and completed successfully.
So I wonder what other clues are?
The error is as below:
FATAL 2015-03-22 23:28:00,943 [8] SEASService.App_Code.BatchService - Failed
[SqlException]: hashcode { 57932624 }
{
Message : Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
StackTrace : at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

ZZartin SSC-Dedicated Points: 30921 More actions · Answer 1

Well yes if the web server was restarted before sql server and it tried to run a job that needed to connect to sql server before sql server was running then it would be expected it would time out?

sqlfriend SSC Guru Points: 52794 More actions · Answer 2

Thanks,

Both servers were rebooted on Saturday morning.

But the job rans on Sunday night when both servers have already rebooted.

Jeff Moden SSC Guru Points: 1004646 More actions · Answer 3

I guess I don't understand. Why would you think you wouldn't have a problem if the Web Service was running when you rebooted SQL Server? Disable the Web Service job until SQL Server is back up, running, and steady.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

sqlfriend SSC Guru Points: 52794 More actions · Answer 4

The web service was not running at that time. We rebooted the servers a day ago in the morning, the job only at night.