SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Job Step Failure


Job Step Failure

Author
Message
RayMilhon
RayMilhon
SSC Journeyman
SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)

Group: General Forum Members
Points: 97 Visits: 15
I have a Job that runs 3 times per day. It's been running perfectly for 8 weeks. Today the 6:00 AM Report ran fine this morning. The 12:00 Noon Report failed with this Message: "Unable to connect to SQL Server '(local)'. The step failed."
As far as I can tell nothing on the Server has changed. I tried the above step 4 times and it failed all 4 times. Anybody have an idea?



SQLPirate
SQLPirate
SSCrazy
SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)

Group: General Forum Members
Points: 2552 Visits: 1648
Is it possible that the database it was selected to run against has been renamed or removed? Try opening the job step and reselecting the database you want and rerun it.
RayMilhon
RayMilhon
SSC Journeyman
SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)

Group: General Forum Members
Points: 97 Visits: 15
No Nothing on the server was changed.



sgmunson
sgmunson
SSC Guru
SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)

Group: General Forum Members
Points: 98409 Visits: 7265
RayMilhon - Thursday, March 8, 2018 2:26 PM
I have a Job that runs 3 times per day. It's been running perfectly for 8 weeks. Today the 6:00 AM Report ran fine this morning. The 12:00 Noon Report failed with this Message: "Unable to connect to SQL Server '(local)'. The step failed."
As far as I can tell nothing on the Server has changed. I tried the above step 4 times and it failed all 4 times. Anybody have an idea?

Maybe an account password has expired.... That kind of thing doesn't require a human to actively change something.


Steve
‌(aka sgmunson)
Smile Smile Smile
Health & Nutrition
Subramaniam Chandrasekar
Subramaniam Chandrasekar
Hall of Fame
Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)

Group: General Forum Members
Points: 3664 Visits: 531
RayMilhon - Thursday, March 8, 2018 2:26 PM
I have a Job that runs 3 times per day. It's been running perfectly for 8 weeks. Today the 6:00 AM Report ran fine this morning. The 12:00 Noon Report failed with this Message: "Unable to connect to SQL Server '(local)'. The step failed."
As far as I can tell nothing on the Server has changed. I tried the above step 4 times and it failed all 4 times. Anybody have an idea?

Yep, possibly database rename had happened in parallel to Job run?

RayMilhon
RayMilhon
SSC Journeyman
SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)SSC Journeyman (97 reputation)

Group: General Forum Members
Points: 97 Visits: 15
subramaniam.chandrasekar - Tuesday, March 13, 2018 2:06 AM
RayMilhon - Thursday, March 8, 2018 2:26 PM
I have a Job that runs 3 times per day. It's been running perfectly for 8 weeks. Today the 6:00 AM Report ran fine this morning. The 12:00 Noon Report failed with this Message: "Unable to connect to SQL Server '(local)'. The step failed."
As far as I can tell nothing on the Server has changed. I tried the above step 4 times and it failed all 4 times. Anybody have an idea?

Yep, possibly database rename had happened in parallel to Job run?


Finally found it. Looked at the job design I don't know how many times could find no reference to any other database then one I knew hadn't changed. Finally scripted the job and found a buried reference to a database that was moved from one server to another. the interesting thing is the job does not reference that database at all. No idea what happened there.



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum









































































































































































SQLServerCentral


Search