Home Forums SQL Server 2012 SQL 2012 - General Job Step Failure RE: Job Step Failure

  • March 13, 2018 at 9:51 am

    #1982966

    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.