May 5, 2014 at 9:05 am
Occasionally I'm seeing the following error when tranlog or full backup maintenance plan is executing.
Failed:(-1073573396) Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection.
What is strange is that it goes away without any action from myself. We have a tranlog backup that is scheduled every hour. I had this error happen once in the middle of the night. It looks like the job was running fine because almost all the backups are there. I've searched and not found a resolution to this error. I checked the event log and don't see any issues and even tried rebuilding the maintenance plans. Any help is appreciated.
May 5, 2014 at 10:26 am
That's usually an indication of one of two things, the login running the job, whatever it might be, doesn't have access to the server, or, it has the server connection configured wrong. Are you sure you don't have other jobs that are failing instead of one job failing on an intermittent fashion? Are there other automated processes that might interfere?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 5, 2014 at 11:42 am
The only 2 jobs that have failed are tranlog backup and full back. Reindex, statistics, and integrity check all ran without errors. The tranlog backup has only failed once in a week and it had that error. That job runs every hour so there are numerous accounts of it running without any issues. The backup failed the same day the tranlog did and that was the only time in 7 days it failed. It appears something happened that day but an hour later the tranlog job was running fine.
May 5, 2014 at 12:02 pm
Are there two different servers involved? Are you in a failover situation or something along those lines? It could be that it was failed over during that period.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 5, 2014 at 2:48 pm
It is a standalone server. No failover.
November 4, 2014 at 1:32 am
has anyone been able to resolve this problem, please let me know Thanks.
November 4, 2014 at 7:18 am
I never did figure out why this was happening. It went away on its own and did not occur again.
May 8, 2015 at 11:10 am
Did you ever get this resolved. I am experiencing the same problem
August 2, 2016 at 5:35 pm
I actually experienced this problem just the other day. It was while the CPU usage was pegged at 100% on the SQL Server from an application that uses it. Once the CPU usage went back to normal the error stopped. It only happened twice in about 12 hours all the rest of the hourly T_Log backups went fine.
Jeff
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply