June 19, 2018 at 5:24 am
SSIS packages are being triggered throughout the day from the SQL Server Agent. We have an ongoing issue of Intermittent failures of SSIS packages, the failures only see to occur between 8:00-17:00 and started about 1 month ago with between 5-10 per day. This impacts different packages between these times.
Integration Services Catalog Errors:
1) SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager"x" failed with error code 0xC0202009.
2) 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. Microsoft SQL Server Native Client 11" Hresult: 0x80004005
Description: "Unable to complete login process due to delay in prelogin response".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "TCP Provider: Timeout error [258].
Any guidance / support with resolving this would be appreciated?..
June 19, 2018 at 5:28 am
mark.headley - Tuesday, June 19, 2018 5:24 AMSSIS packages are being triggered throughout the day from the SQL Server Agent. We have an ongoing issue of Intermittent failures of SSIS packages, the failures only see to occur between 8:00-17:00 and started about 1 month ago with between 5-10 per day. This impacts different packages between these times.Integration Services Catalog Errors:
1) SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager"x" failed with error code 0xC0202009.
2) 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. Microsoft SQL Server Native Client 11" Hresult: 0x80004005
Description: "Unable to complete login process due to delay in prelogin response".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "TCP Provider: Timeout error [258].
I cannot see a question here.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
June 19, 2018 at 5:35 am
Phil Parkin - Tuesday, June 19, 2018 5:28 AMmark.headley - Tuesday, June 19, 2018 5:24 AMSSIS packages are being triggered throughout the day from the SQL Server Agent. We have an ongoing issue of Intermittent failures of SSIS packages, the failures only see to occur between 8:00-17:00 and started about 1 month ago with between 5-10 per day. This impacts different packages between these times.Integration Services Catalog Errors:
1) SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager"x" failed with error code 0xC0202009.
2) 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. Microsoft SQL Server Native Client 11" Hresult: 0x80004005
Description: "Unable to complete login process due to delay in prelogin response".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "TCP Provider: Timeout error [258].I cannot see a question here.
We need try and understand the root cause of these errors to build a solution as currently we are spending a lot of time re-running packages due to this failure. As above, if anyone can help it would be greatly appreciated.
June 19, 2018 at 6:07 am
mark.headley - Tuesday, June 19, 2018 5:35 AMPhil Parkin - Tuesday, June 19, 2018 5:28 AMmark.headley - Tuesday, June 19, 2018 5:24 AMSSIS packages are being triggered throughout the day from the SQL Server Agent. We have an ongoing issue of Intermittent failures of SSIS packages, the failures only see to occur between 8:00-17:00 and started about 1 month ago with between 5-10 per day. This impacts different packages between these times.Integration Services Catalog Errors:
1) SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager"x" failed with error code 0xC0202009.
2) 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. Microsoft SQL Server Native Client 11" Hresult: 0x80004005
Description: "Unable to complete login process due to delay in prelogin response".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "TCP Provider: Timeout error [258].I cannot see a question here.
We need try and understand the root cause of these errors to build a solution as currently we are spending a lot of time re-running packages due to this failure. As above, if anyone can help it would be greatly appreciated.
Sounds like the server is running at full capacity and cannot service the SSIS login requests before the timeout period elapses.
Do you have monitoring in place which lets you compare the times of failure with server activity?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
June 19, 2018 at 6:27 am
We have just started monitoring, however knowing which metric and threshold to monitor that would cause this needs to be understood as there is so much data. So far we can see repetitive longing for the following events although not able to tie to the exact time of the SSIS failure (yet) or know if related.
RING BUFFER Security:
Notification_Time SPID Error_Code CallingAPIName APIName Record Id Type
2018-06-11b12:39:45.723 80 0x534 LookupAccountSidInternal LookupAccountSid 33177 RING_BUFFER_SECURITY_ERROR
RING_BUFFER_CONNECTIVITY:
<RecordType>ConnectionClose</RecordType>
<TdsBuffersInformation>
<TdsInputBufferError>10054</TdsInputBufferError>
<TdsOutputBufferError>0</TdsOutputBufferError>
<TdsInputBufferBytes>100</TdsInputBufferBytes>
</TdsBuffersInformation>
<TdsDisconnectFlags>
<PhysicalConnectionIsKilled>0</PhysicalConnectionIsKilled>
<DisconnectDueToReadError>0</DisconnectDueToReadError>
<NetworkErrorFoundInInputStream>0</NetworkErrorFoundInInputStream>
<ErrorFoundBeforeLogin>1</ErrorFoundBeforeLogin>
<SessionIsKilled>1</SessionIsKilled>
<RoutingCompleted>0</RoutingCompleted>
<NormalDisconnect>0</NormalDisconnect>
<NormalLogout>0</NormalLogout>
</TdsDisconnectFlags>
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply