Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

How to find and fix Expand / Collapse
Author
Message
Posted Thursday, April 10, 2014 12:38 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: 2 days ago @ 7:27 AM
Points: 311, Visits: 538
I am getting the following error, about once per day, and the server it is trying to connect to is always the same server. I would perfer not to run a wide open trace on the production server.. so trying to find a much better way of finding out what is going on.

[SQLSTATE 42000] (Error 258) OLE DB provider "SQLNCLI10" for linked server "R2D2" returned message "Login timeout expired". [SQLSTATE 01000] (Error 7412) OLE DB provider "SQLNCLI10" for linked server "R2D2" returned message "Unable to complete login process due to delay in prelogin response". [SQLSTATE 01000] (Error 7412). The step failed.
Post #1560582
Posted Friday, April 11, 2014 4:16 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Monday, July 14, 2014 2:06 PM
Points: 3,865, Visits: 7,130
What exactly are you trying to find out? The error is pretty specific: the authentication process is timing out.

Try increasing the connection timeout property on the actual linked server and increase the remote query timeout on the actual server. If it's not a timing issue, the link below may be of some assistance in determining the cause


______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1561144
Posted Monday, April 14, 2014 3:07 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 2:57 PM
Points: 1,194, Visits: 2,211
Check if there is any resource contention (CPU, Memory, Ntk ..) \ blocking on the server that's causing this ..

--
SQLBuddy
Post #1561676
Posted Tuesday, April 15, 2014 11:49 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: 2 days ago @ 7:27 AM
Points: 311, Visits: 538
It is set at 20 sec.. I would think that should be long enough...it is a SQL Auth login, so all the server has to do is process the request.
Post #1562008
Posted Tuesday, April 15, 2014 1:40 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Monday, July 14, 2014 2:06 PM
Points: 3,865, Visits: 7,130
Yes, it should, but as sqlbuddy mentioned, it could be blocked for a variety of reasons. Try extending it to 180 for testing purposes only (or zero for no timeout) and see if it connects.

______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1562039
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse