Hi Community
We have several SSIS packages transferring data from a local SQL server to an Azure server. The packages are executed after each other by an SQL agent job, which is scheduled hourly.
The job is configured to re-execute a package if it fails after 3 minutes for 3 times before moving to the next step.
Unfortunately we face very inconsistent login timeout issues with these packages. There is not much else running on the azure server but still we receive the following errors several times a day, in a row or sometimes for hours:
Message
Executed as user: NT Service\SQLSERVERAGENT.
Microsoft (R) SQL Server Execute Package Utility Version 12.0.2000.8 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved.
Started: 4:00:00 AM
Error: 2016-01-15 04:03:05.82
Code: 0xC0202009
Source: RVVDataTransfer_Material Connection manager "OneBitAzureDB" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available.
Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description:"Login timeout expired". An OLE DB record is available.
Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description:"A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow
remote connections. For more information see SQL Server Books Online.". An OLE DB record is available.
Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Named Pipes Provider: Could not open a connection to SQL Server [53]. ".
End Error
Error: 2016-01-15 04:03:05.83
Code: 0xC020801C
Source: Transfer Material Data Destination tbl_Material [11] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "OneBitAzureDB"
failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
End Error
Error: 2016-01-15 04:03:05.83
Code: 0xC0047017
Source: Transfer Material Data SSIS.Pipeline Description: Destination tbl_Material failed validation and returned error code 0xC020801C.
End Error
Error: 2016-01-15 04:03:05.83
Code: 0xC004700C
Source: Transfer Material Data SSIS.Pipeline Description: One or more component failed validation.
End Error
Error: 2016-01-15 04:03:05.84
Code: 0xC0024107
Source: Transfer Material Data Description: There were errors during task validation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 4:00:00 AM
Finished: 4:03:05 AM
Elapsed: 185.579 seconds.
The package execution failed.
Sometimes the packages can be executed without any issues, than from one minute to another the login timeout expired error occurs and disappears suddenly after hours, minutes or even seconds.
While packages raise this error we are still able to login to the azure server with the management studio without any recognizable delay or even error message.
We have also already changed the provider used for the connection from ADO to OLE without success.
Any further hint would be very much appreciated.