September 15, 2008 at 10:58 am
I have a situation in which all of the SQL Server Agent Jobs are failing with the message "Unable to connect to SQL Server (local). The step failed."
I have never seen this before, and I am wondering what could be causing it.
I tried creating a new job, created it successfully, it parsed successfully, but when I ran it, I got the same error.
The service is running under a local system account (as is the server)
There is nothing particularly unusual about the installation, no clustering or anything like that.
Any ideas?
Thanks,
Bill Mell
September 15, 2008 at 11:02 am
- did you change e.g. sqlagent service account recently ?
- did you remove e.g. builtin\administrators from you sql instance before altering sqlagent service account ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
September 15, 2008 at 11:10 am
It's running under the local service account not a domain account.
The Domain Admins are still in the Administrators account.
September 15, 2008 at 11:20 am
Issue might be related to the account that "owns" the job rather than to the account you have set for SQL Server Agent.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.September 15, 2008 at 11:23 am
the sa account owns all the jobs
September 15, 2008 at 11:28 am
Also check each job to see who it "Runs As"
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
September 15, 2008 at 11:31 am
The "Run as" is blank on everything
September 15, 2008 at 12:07 pm
If the jobs have TSQL steps, check that the database in the job step is accessible. Check that the SQL command can be executed outside of the job, from the database specified in the job.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
September 15, 2008 at 12:14 pm
Already done,
I think something is seriously hosed on the server.
all the components of the jobs (at least the TSQL based steps) have all been successfully tested in the appropriate databases.
September 15, 2008 at 12:17 pm
We've decided that we are just going to run the steps manually until such time as we can take the server down and re-install.
I've run out of ideas of things to test.
Fortunately there are not too many jobs to worry about.
If anyone runs into this kind of situation and finds a solution, I'd love to hear about it tho.
Thanks,
Bill
September 15, 2008 at 12:26 pm
Have you tried just stopping and restarting SQL Server Agent?
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
September 16, 2008 at 1:06 am
Have you renamed any of the referenced databases ?
You can script the job and check all the databases references to see if everything is ok.
September 16, 2008 at 4:11 am
I have tried stopping and starting the sql agent.
And I have also tried scripting the jobs, and found them all to be just fine.
September 16, 2008 at 4:42 am
Can you post version information of your sqlserver .
Select @@version
or
Select Serverproperty( 'BuildClrVersion' ) as BuildClrVersion
, Serverproperty( 'Collation' ) as Collation
, Serverproperty( 'CollationID' ) as CollationID
, Serverproperty( 'ComparisonStyle' ) as ComparisonStyle
, Serverproperty( 'ComputerNamePhysicalNetBIOS' ) as ComputerNamePhysicalNetBIOS
, Serverproperty( 'Edition' ) as Edition
, Serverproperty( 'EditionID' ) as EditionID
, Serverproperty( 'EngineEdition' ) as EngineEdition
, Serverproperty( 'InstanceName' ) as InstanceName
, Serverproperty( 'IsClustered' ) as IsClustered
, Serverproperty( 'IsFullTextInstalled' ) as IsFullTextInstalled
, Serverproperty( 'IsIntegratedSecurityOnly' ) as IsIntegratedSecurityOnly
, Serverproperty( 'IsSingleUser' ) as IsSingleUser
, Serverproperty( 'LCID' ) as LCID
, Serverproperty( 'LicenseType' ) as LicenseType
, Serverproperty( 'MachineName' ) as MachineName
, Serverproperty( 'NumLicenses' ) as NumLicenses
, Serverproperty( 'ProcessID' ) as ProcessID
, Serverproperty( 'ProductVersion' ) as ProductVersion
, Serverproperty( 'ProductLevel' ) as ProductLevel
, Serverproperty( 'ResourceLastUpdateDateTime' ) as ResourceLastUpdateDateTime
, Serverproperty( 'ResourceVersion' ) as ResourceVersion
, Serverproperty( 'ServerName' ) as ServerName
, Serverproperty( 'SqlCharSet' ) as SqlCharSet
, Serverproperty( 'SqlCharSetName' ) as SqlCharSetName
, Serverproperty( 'SqlSortOrder' ) as SqlSortOrder
, Serverproperty( 'SqlSortOrderName' ) as SqlSortOrderName
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply