August 20, 2018 at 8:03 am
Over the weekend we installed SP2-CU2 and KB293807 on our SQL Server failover cluster. Now maintenance plans aren't work on our SQL 2012 instances or our SQL 2016 instances. It's getting an error - unable to connect to local server.
This security patch has since been retracted (Saturday evening), but for different reasons than we are experiencing. Has anyone else experienced this?
We are about to open a case with MS after we do some additional testing.
Thanks,
Cindy
August 20, 2018 at 8:47 am
Did you fail over and back in the process of applying the patch? How often do you fail these over? Was it fixed after retracting the patch? Also, could you look at your SQL log and paste the full error here, assuming you're running these via SQL Agent?
It does sound odd
August 20, 2018 at 9:39 am
We now have a case open with Microsoft, but since you asked... I will post the solution provided by MS when we get one.
All instances on the nodes were failed-over to other nodes prior to patching. We fail over to other nodes monthly for Windows 2012 patching. We have a 6 node, active-active configuration. The maintenance plans fail on all three nodes that were patched. The same maintenance plans work on the three nodes that have not yet been patched.
We have uninstalled the security patch on one node. Maintenance plans still fail. Next, we will be uninstalling SP2-CU2. We could not recreate this problem on our test cluster, which is OS Windows 2016 and only SQL 2016 instances.
We use a third party tool (litespeed) for backups, so we've been creating native maintenance plans for trouble-shooting. Backups, themselves, work - just not via a maintenance plan. We are concurrently creating backups jobs not using maintenance plans until we get this resolved.
There are no errors in the SQL log or Agent log. This is the error associated with the step and in the log file created with the step.
Date 8/20/2018 11:18:11 AM
Log Job History (MP-csc-New-MP.Subplan_1)
Step ID 1
Server APLDBCL4-DV4\DEV4
Job Name MP-csc-New-MP.Subplan_1
Step Name Subplan_1
Duration 00:01:29
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Microsoft (R) SQL Server Execute Package Utility
Version 12.0.5579.0 for 64-bit
Copyright (C) Microsoft Corporation. All rights reserved.
Started: 11:18:11 AM
Error: 2018-08-20 11:18:40.94
Code: 0xC00291EC
Source: {9F007BE7-6D99-400D-8030-5CFCD9FDB0F2} 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
Error: 2018-08-20 11:19:10.49
Code: 0xC0024104
Source: Back Up Database Task
Description: The Execute method on the task returned error code 0x80131904 (A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)). The Execute method must succeed, and indicate the result using an "out" parameter.
End Error
Error: 2018-08-20 11:19:40.03
Code: 0xC0024104
Source: {44A92E2C-8E12-4923-93BD-E772E871F192}
Description: The Execute method on the task returned error code 0x80131904 (A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)). The Execute method must succeed, and indicate the result using an "out" parameter.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 11:18:11 AM
Finished: 11:19:40 AM
Elapsed: 88.921 seconds
August 20, 2018 at 1:46 pm
I see. How are you managing authentication to the DB within the maintenance plan? SSO with windows authentication or is utilizing a SQL user with encrypted password?
I've had weird and similar issues with mainenance plans in past, and I've had to essentially export and reimport them back in.
What happens if you export one and run manually outside of litespeed and from SSIS?
August 21, 2018 at 6:41 am
My co-worker resolved the issue before Microsoft returned the call on the case. This issue was with a wrong version of .NET. We still don't know the "how" of what happened, but he downloaded/installed .NET 4.6.2 and that fixed the problem. All maintenance plans are now running. Nothing was changed with the maintenance plans themselves.
The .NET issue was not a result of SP2-CU2 or the now-retracted security KB. Looking at timestamps, it happened when the "add to node" to add an existing SQL 2016 instance to our SQL cluster was done. We had previously done the "add to node" on other nodes and didn't have a problem. Again, we don't know the "why" or "how", yet, but the "what happened" is resolved.
Thank-you for you input and assistance.
Cindy
August 22, 2018 at 9:51 am
HI, just a question, your maintenance plans no longer work, as a small experiment have you tried installing Ola Hallengren's backup scripts and see if they work? (They run via scheduled jobs and not maint plans).
qh
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply