February 16, 2018 at 8:23 am
Everytime I run the Maintenance Plan in SSMS(Check DB Integrity, syspolicy purge history, Full backups, Transaction Log), and it keeps failing. I checked the History log for errors:
Check Database integrity on Local server connection
Databases: All user databases
Include indexes
Error number: -1073573396
Error Message: Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection.
I also checked the job history: EXECUTE msdb..sp...".: 100% complete End Progress Error: 2018-02-16 09:48:04.65 Code: 0xC00291EC Source: Check Database Integrity 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-02-16 09:48:04.66 Code: 0xC00291EC Source: Check Database Integrity 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-02-16 09:48:04.71 Code: 0xC00291EC Source: Check Database Integrity 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-02-16 09:48:04.71 Code: 0xC00291EC Source: Check Database Integrity 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-02-16 09:48:04.73 Code: 0xC00291EC Source: Check Database Integrity 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-02-16 09:48:04.76 Code: 0xC0024104 Source: {4280A145-8AEC-4399-A084-A8B7C3F4F833} Description: The Execute method on the task returned error code 0x80131904 (A connection was successfully established with the server<c/> but then an error occurred during the login process. (provider: Shared Memory Provider<c/> error: 0 - No process is on the other end of the pipe.)). The Execute method must succeed<c/> and indicate the result using an "out" parameter. End Error Warning: 2018-02-16 09:48:04.80 Code: 0x80019002 Source: OnPostExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded<c/> but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning Error: 2018-02-16 09:48:04.80 Code: 0xC0024104 Source: Reporting Task for subplan-{72FA8092-91B6-430B-950A-C68F37935E47} Description: The Execute method on the task returned error code 0x80131904 (Logon failed for login 'NMED\NHCNE-GRCT-DBD1$' due to trigger execution. Changed database context to 'master'. Changed language setting to us_english.). The Execute method must succeed<c/> and indicate the result using an "out" parameter. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 9:48:02 AM Finished: 9:48:04 AM Elapsed: 1.968 seconds. The package execution failed. The step failed.,
The syspolicy_purge_history runs successful however. I checked the Local Server Connection in the Maintenance Plan, and its has the correct server name listed. If the error is saying that my server doesn't exist, I would not be able to RDP into it let alone ping it. I tried changing the permissions so that the Maintenance job and the syspolicy job are both owned by me with sysadmin permissions, and that didn't work. I was going to change the OWNERSID for the Maintenance Plan to 0x01(sa), but I noticed the exact same Maintenance Plan on other servers, and that Maintenance Plan OWNERSID never change to 0x01.
So I'm totally baffled why I cannot run this Maintenance Plan on my server.
Thanks.
February 16, 2018 at 2:15 pm
WC_Admin - Friday, February 16, 2018 8:23 AMEverytime I run the Maintenance Plan in SSMS(Check DB Integrity, syspolicy purge history, Full backups, Transaction Log), and it keeps failing. I checked the History log for errors:
Check Database integrity on Local server connection
Databases: All user databases
Include indexes
Error number: -1073573396
Error Message: Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection.I also checked the job history: EXECUTE msdb..sp...".: 100% complete End Progress Error: 2018-02-16 09:48:04.65 Code: 0xC00291EC Source: Check Database Integrity 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-02-16 09:48:04.66 Code: 0xC00291EC Source: Check Database Integrity 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-02-16 09:48:04.71 Code: 0xC00291EC Source: Check Database Integrity 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-02-16 09:48:04.71 Code: 0xC00291EC Source: Check Database Integrity 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-02-16 09:48:04.73 Code: 0xC00291EC Source: Check Database Integrity 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-02-16 09:48:04.76 Code: 0xC0024104 Source: {4280A145-8AEC-4399-A084-A8B7C3F4F833} Description: The Execute method on the task returned error code 0x80131904 (A connection was successfully established with the server<c/> but then an error occurred during the login process. (provider: Shared Memory Provider<c/> error: 0 - No process is on the other end of the pipe.)). The Execute method must succeed<c/> and indicate the result using an "out" parameter. End Error Warning: 2018-02-16 09:48:04.80 Code: 0x80019002 Source: OnPostExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded<c/> but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning Error: 2018-02-16 09:48:04.80 Code: 0xC0024104 Source: Reporting Task for subplan-{72FA8092-91B6-430B-950A-C68F37935E47} Description: The Execute method on the task returned error code 0x80131904 (Logon failed for login 'NMED\NHCNE-GRCT-DBD1$' due to trigger execution. Changed database context to 'master'. Changed language setting to us_english.). The Execute method must succeed<c/> and indicate the result using an "out" parameter. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 9:48:02 AM Finished: 9:48:04 AM Elapsed: 1.968 seconds. The package execution failed. The step failed.,
The syspolicy_purge_history runs successful however. I checked the Local Server Connection in the Maintenance Plan, and its has the correct server name listed. If the error is saying that my server doesn't exist, I would not be able to RDP into it let alone ping it. I tried changing the permissions so that the Maintenance job and the syspolicy job are both owned by me with sysadmin permissions, and that didn't work. I was going to change the OWNERSID for the Maintenance Plan to 0x01(sa), but I noticed the exact same Maintenance Plan on other servers, and that Maintenance Plan OWNERSID never change to 0x01.
So I'm totally baffled why I cannot run this Maintenance Plan on my server.
Thanks.
Did you also notice this in the error message:
Logon failed for login 'NMED\NHCNE-GRCT-DBD1$' due to trigger execution.
So it looks like it's a machine account and that you likely have a logon trigger.
You also have this error in the mix of all of that:
(provider: Shared Memory Provider<c/> error: 0 - No process is on the other end of the pipe
Which often is from not having shared memory enabled.
Sue
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply