May 21, 2014 at 6:33 am
Hello masters,
we are facing one issue from last 3 days.
During job execution (SSIS) we are getting Login TimeOut. with the following error. Request your master help.
Error:
SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
ource: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Login timeout expired". Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Unable to complete login process due to delay in login response". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "TCP Provider: Timeout error [258]. ". End Error
Your help will be very helpful.
Thanks
PK.
May 23, 2014 at 7:57 am
pxt_ce (5/21/2014)
Hello masters,we are facing one issue from last 3 days.
During job execution (SSIS) we are getting Login TimeOut. with the following error. Request your master help.
Error:
SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
ource: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Login timeout expired". Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Unable to complete login process due to delay in login response". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "TCP Provider: Timeout error [258]. ". End Error
Your help will be very helpful.
Thanks
PK.
Did it run before and you have not changed anything after that? If that's true, sounds like network issues, latency maybe?
May 23, 2014 at 8:11 am
Here are a few things I'd consider:
* Can you ping the target server from the computer the package is running on? If not, the server may be down or there may be routing or DNS issues
* Is SQL Server Browser running on the target computer, or did you supply the port number in the connection string?
* Can you get a telnet session to the server using the port number? If not, SQL Server may not be running
* Have you spelled the server and instance name correctly?
* Does the target server have TCP enabled in SQL Server Configuration Manager?
* Can you connect to the server from anywhere else?
John
May 3, 2017 at 2:31 am
John Mitchell-245523 - Friday, May 23, 2014 8:11 AMHere are a few things I'd consider:* Can you ping the target server from the computer the package is running on? If not, the server may be down or there may be routing or DNS issues* Is SQL Server Browser running on the target computer, or did you supply the port number in the connection string?* Can you get a telnet session to the server using the port number? If not, SQL Server may not be running* Have you spelled the server and instance name correctly?* Does the target server have TCP enabled in SQL Server Configuration Manager?* Can you connect to the server from anywhere else?John
Hi John,
As listed by you, I am able to connect to the server from anywhere else.
regards,
Thulasi
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply