Hi Experts,

We have a log backup job in the mirrored instance which was succeeding till yesterday and today it started to fail with the following error:

Executed as user: ABC\Dba. Microsoft (R) SQL Server Execute Package Utility  Version 11.0.2100.60 for 64-bit  Copyright (C) Microsoft Corporation. All rights reserved.    Started:  12:00:00 PM  Error: 2015-05-25 12:00:15.34     Code: 0xC00291EC     Source: {017DEABA-663B-4843-B849-5E7FFAEC180F} 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  Warning: 2015-05-25 12:00:15.34     Code: 0x80019002     Source: OnPreExecute      Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED.  The Execution method succeeded, but the number of errors raised (1) 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: 2015-05-25 12:00:30.09     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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)). The Execute method must succeed, and indicate the result using an "out" parameter.  End Error  Error: 2015-05-25 12:00:44.82     Code: 0xC0024104     Source: {468FE3BB-3A58-42EF-8A4F-BCAD7E38FAA7}      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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)). The Execute method must succeed, and indicate the result using an "out" parameter.  End Error  Warning: 2015-05-25 12:00:44.82     Code: 0x80019002     Source: OnPostExecute      Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED.  The Execution method succeeded, 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  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  12:00:00 PM  Finished: 12:00:44 PM  Elapsed:  44.422 seconds.  The package execution failed.  The step failed.

I am thinking it as a network error but I could access server with no issues and I know that the backups are not necessary in mirrored instance and I do not want to disable these job as they were runnig fine till yesterday.

Can you please advice me where I am wrong apart from this network error?

Thanks in advance.

Are you running the job, or is it scheduled?

If it's scheduled, check the permissions for the user that is executing it. Has that users password expired?

Does the job still fail if executed now? perhaps it was an intermittent issue?

Hi Patrick,

Thanks for your reply, yes this job is scheduled.

User is a windows domain login, hence no password expiration policy.

yes it failed at current run at 2:00 pm.

User is a windows domain login, hence no password expiration policy.

I'd check just to make sure. While you're in there you can check it wasn't disabled or anything crazy.

Good, nothing is more annoying than problems that fix themselves, leaving you nothing to diagnose.

Can that user access the directory in question? 

user is not disabled .

Do you mean folder by directory? if so yes user can access that one too.

checked SQL Browser, it is not running, will that be the cause of failure?

Thanks.

• Edited by venkatesh1985 12 hours 2 minutes ago

https://technet.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx in short, no.

The error message you received happened because the package failed to connect to "Local server connection". It would be helpful to know what "Local server connection" is. 

user is not disabled .

Do you mean folder by directory? if so yes user can access that one too.

checked SQL Browser, it is not running, will that be the cause of failure?

Thanks.

• Edited by venkatesh1985 Monday, May 25, 2015 7:04 PM

1)Maint Plan - Failed to acquire connection "Local server connection"
That sounds like a permission issue. Check that the account running 
the SQL Server agent have access to the resources specified in the 
connection managers. Check the way the authentication mode in 
connection manager. This KB article describe common issues when 
running packages via SQL Server agent
:: http://support.microsoft.com/kb/918760

2)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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)).

http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/

Check and let me know.

• Edited by Dinesh Vishe 6 hours 58 minutes ago

1)Maint Plan - Failed to acquire connection "Local server connection"
That sounds like a permission issue. Check that the account running 
the SQL Server agent have access to the resources specified in the 
connection managers. Check the way the authentication mode in 
connection manager. This KB article describe common issues when 
running packages via SQL Server agent
:: http://support.microsoft.com/kb/918760

2)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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)).

http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/

Check and let me know.

• Edited by Dinesh Vishe Tuesday, May 26, 2015 12:08 AM

Good day venkatesh,

Is this is still an issue?

* If not then please close the thread. If it is, then please clarify :-)