question

ahesh avatar image
ahesh asked

Maintenance Plans Fail on SQL Server 2012 after applying SP2 patch

All maintenance plans on 5 failover cluster instances fail with Failed to acquire connection "Local server connection" after I applied sp2 patch. There is a 2008R2 failover instance on the same cluster that has no problem. There were a lot of security patches (windows 2008 R2) that were applied after sp2. nothing noteworthy other than .NET Framework 4.6. Any help is greatly appreciated!
sql-server-2012maintenance-plans
3 comments
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Wilfred van Dijk avatar image Wilfred van Dijk commented ·
Please post the error message / output
0 Likes 0 ·
ahesh avatar image ahesh commented ·
Error: 2015-09-11 12:47:00.15 Code: 0xC00291EC Source: {3FB6BDA0-A50C-4E2F-94E6-F8AFE1643964} Execute SQL Task Description: Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error
0 Likes 0 ·
Grant Fritchey avatar image Grant Fritchey ♦♦ commented ·
The error suggests that it's not using a named instance in the jobs, but instead is relying on default connections. It says right there "Local server connection". So how are you choosing to define the connection?
0 Likes 0 ·

1 Answer

·
Grant Fritchey avatar image
Grant Fritchey answered
If you have two instances on the server, to make the connections work correctly all the time, use the named server in your Maintenance Plans, not "Local server". Probably, the default server is the other one. Just use the instance name.
2 comments
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

ahesh avatar image ahesh commented ·
The connection property for all jobs on all instances (six) have the correct server name\instance name. I even tried to create new maintenance plans but none work.
0 Likes 0 ·
ahesh avatar image ahesh commented ·
Connection name is "Local Server Connection" but the server name in the connection property has the correct server name \instance name. I even created a new connection and changed the job to use the newly created connection but still gives the same error.
0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.