xuewei shi
asked on
SQL Server connection timeout issue
We have a SQL job scheduled a SSIS package each day, it reads data from a remote SQL Server, across AP region to AM region.
Sometimes it executes successfully, but sometimes it fails after executing for about 20 seconds (refer to attached screen shot).
The error message is same each time:
Hresult: 0x80004005 Description: "Login timeout expired". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Unable to complete login process due to delay in prelogin response". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: Timeout error [258]. "
Does anyone know what might be caused such error? We looked the sql logs on destination SQL Server, and there is nothing relavant logged when job executes. Both source and destination SQL Server timeout setting is 10 minutes. SSIS package has timeout setting as 0 which is never timeout.
Thanks a lot!
job-history-screenshot.png
Sometimes it executes successfully, but sometimes it fails after executing for about 20 seconds (refer to attached screen shot).
The error message is same each time:
Hresult: 0x80004005 Description: "Login timeout expired". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Unable to complete login process due to delay in prelogin response". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: Timeout error [258]. "
Does anyone know what might be caused such error? We looked the sql logs on destination SQL Server, and there is nothing relavant logged when job executes. Both source and destination SQL Server timeout setting is 10 minutes. SSIS package has timeout setting as 0 which is never timeout.
Thanks a lot!
job-history-screenshot.png
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes it was due to the network problem and network team has solved that already.
Thanks again!