Unanswered: Jobs failing with message - Unable to connect to SQL Server
Recently this has been happening quite often. Random steps of jobs, regardless of what they're doing, fail and the job history always says "Unable to connect to SQL Server '(local)'. " It doesn't seem to matter what the specific job is or even the step. A simple stored procedure that normally takes a few seconds, or a longer one that should run for hours can both fail and give this same message. It isn't happening all the time, but probably occurs 10 times a day from a total of around 50 jobs that run throughout the day. Any ideas what could be causing this??