ERROR – Unable to connect to SQL Server '(local)' | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

ERROR – Unable to connect to SQL Server ‘(local)’

We have been facing this error for the past few days. There is an automated job which gives READ access to a database, running @ 6 AM everyday. The job keeps on failing with the message :
<<< Unable to connect to SQL Server ‘(local)’. The step failed.>>>
The wierd part is When i run that job manually just after it failed it is running to success Please let me know your opinion guyzz
[email protected] "What would you attempt to do if you knew that you could never fail"
-Robert Schuller

check the sql server registration properties.
U can even add thats erver alias in client network utility.
Set remote server connection timeout to 0.
also check the connection used if the server is on mixed mode then instead of windows authentication check it with sa login if that helps.
Is this a SQL Server job, or some batch job you have setup? If it’s a SQL Server job, what username is it running under? Does that user have access to the particular database to set the permissions properly? If it’s a SQL Server user, have you ran EXEC sp_change_users_login ‘REPORT’ to see if there are any issues with orphaned users? Is there more information in the SQL Server error log or eventvwr log? Also, this is the default instance, not a named instance. Correct? MeanOldDBA
[email protected] When life gives you a lemon, fire the DBA.