March 8, 2018 at 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?
March 8, 2018 at 2:59 pm
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.
March 9, 2018 at 11:21 am
No Nothing on the server was changed.
March 9, 2018 at 12:35 pm
RayMilhon - Thursday, March 8, 2018 2:26 PMI 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) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
March 13, 2018 at 2:06 am
RayMilhon - Thursday, March 8, 2018 2:26 PMI 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?
March 13, 2018 at 9:51 am
subramaniam.chandrasekar - Tuesday, March 13, 2018 2:06 AMRayMilhon - Thursday, March 8, 2018 2:26 PMI 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.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply