none
[298] SQLServer Error: 258, Unable to complete login process due to delay in login response [SQLSTATE 08001 RRS feed

  • Question

  • Hi Experrts,

    we are receiving below error since 1 week, 

    The below error logging in SQL AGENT LOG.

    [298] SQLServer Error: 258, Unable to complete login process due to delay in login response [SQLSTATE 08001]

    Thanks in advance.

    Tuesday, July 22, 2014 9:43 AM

Answers

  • Hello,

    Is that instance a SQL Server 2012 instance? If that is the case, please read the following article:

    http://support.microsoft.com/kb/2919863/en-us

    Could you share the output of the following query with us?

    select top 40 *

    from sys.dm_os_wait_stats

    order by wait_time_ms desc

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    Tuesday, July 22, 2014 1:19 PM
    Moderator
  • Some times, we can see this error message ([298] SQLServer Error: 258, Unable to complete login process due to delay in login response [SQLSTATE 08001]) from remote logins.

    Please connect to the SQL server from local machine and try to increase remote login time and let me know if it working or not.

    Note that "remote logins" here refers to connect to linked servers. So far, Vijay has not said anything about linked servers. As far as I understand, the problem is that SQL Server Agent reports this error, and it seems clear that it is connecting to the local server.

    It is not easy to troubleshoot with this miniscule of information, but I would guess that the job is owned by a domain user? The problem may be related to veruify that user in the AD.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
    • Marked as answer by vijay_1234 Tuesday, July 29, 2014 6:32 AM
    Wednesday, July 23, 2014 8:15 AM

All replies

  • Hi Vijay:

    From where you are connecting to the SQL Instance from local or remote.

    Thanks,


    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

    Tuesday, July 22, 2014 11:54 AM
  • Hello,

    Is that instance a SQL Server 2012 instance? If that is the case, please read the following article:

    http://support.microsoft.com/kb/2919863/en-us

    Could you share the output of the following query with us?

    select top 40 *

    from sys.dm_os_wait_stats

    order by wait_time_ms desc

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    Tuesday, July 22, 2014 1:19 PM
    Moderator
  • Thanks Alberto,

    SQL Server Version : 2008(SP2) ,WIN-2008

    i am sharing output for the above query. Could you sugest to perform next step.

     
    wait_type waiting_tasks_count wait_time_ms max_wait_time_ms signal_wait_time_ms
    BROKER_TASK_STOP 21637 104252819 10314 1934
    XE_TIMER_EVENT 3428 102783752 30182 102780478
    REQUEST_FOR_DEADLOCK_SEARCH 20557 102781113 5180 102781113
    LAZYWRITER_SLEEP 112683 102773567 1692 3060
    LOGMGR_QUEUE 1105849 102672057 285755 33864
    SQLTRACE_BUFFER_FLUSH 25662 102645166 4173 6
    CHECKPOINT_QUEUE 12098 99513619 12977235 1292
    BROKER_EVENTHANDLER 923 98372170 9020283 100
    XE_DISPATCHER_WAIT 50 77073629 71163646 0
    SLEEP_TASK 3802984 51886191 1120 28608
    BROKER_TO_FLUSH 50084 51314068 1111 807
    BACKUPIO 931160 34988998 83222 26119
    BROKER_RECEIVE_WAITFOR 451 10995041 599969 30
    BACKUPTHREAD 4643 9319868 83222 3160
    BACKUPBUFFER 2621295 6672037 2049 41990
    ASYNC_IO_COMPLETION 540 6112290 1002517 21
    WRITELOG 1097259 5154816 2264 24229
    PAGEIOLATCH_SH 163198 2500573 3032 2816
    CXPACKET 595031 1889134 65689 96148
    LATCH_EX 90160 1097250 2107 8518
    PAGEIOLATCH_EX 64215 681067 1318 567
    SLEEP_BPOOL_FLUSH 42344 403862 76 1346
    IO_COMPLETION 37482 313475 1384 296
    MSQL_XP 4173 248654 33894 0
    PREEMPTIVE_OS_GETPROCADDRESS 4173 248044 33894 0
    ASYNC_NETWORK_IO 14922 244825 2000 652
    PREEMPTIVE_OS_WAITFORSINGLEOBJECT 1999 243386 2000 0
    OLEDB 112797 117110 675 0
    PAGEIOLATCH_UP 2182 62067 2117 50
    LOGBUFFER 1435 58515 2044 115
    PREEMPTIVE_OS_FILEOPS 2227 56812 3032 0
    SLEEP_DBSTARTUP 341 34876 578 4
    PREEMPTIVE_OS_CREATEFILE 1029 33561 752 0
    PAGELATCH_EX 8249173 24710 359 12706
    PREEMPTIVE_OS_WRITEFILEGATHER 175 20834 2308 0
    PREEMPTIVE_OS_GETVOLUMEPATHNAME 808 19487 2949 0
    LCK_M_SCH_S 4 16786 6149 0
    SQLTRACE_LOCK 102 16779 1000 6
    WRITE_COMPLETION 373 16325 1086 4
    SOS_SCHEDULER_YIELD 672340 15106 557 14449
    Wednesday, July 23, 2014 6:06 AM
  • Hi Sateesh,

    it is remote server.

    Wednesday, July 23, 2014 6:11 AM
  • Hi Alberto,

    The below errors receiving  at same time

    5.03 Pm- [382] Logon to server '(local)' failed (ConnUpdateStartExecutionDate

    5.03 PM -[165] ODBC Error: 0, Unable to complete login process due to delay in 

                  opening server connection [SQLSTATE 08001]


     5.00 PM -[382] Logon to server '(local)' failed (SaveAllSchedules)

    Wednesday, July 23, 2014 6:41 AM
  • Some times, we can see this error message ([298] SQLServer Error: 258, Unable to complete login process due to delay in login response [SQLSTATE 08001]) from remote logins.

    Please connect to the SQL server from local machine and try to increase remote login time and let me know if it working or not.

    Thanks


    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)


    Wednesday, July 23, 2014 7:17 AM
  • so, is it related to network issue?
    Wednesday, July 23, 2014 7:49 AM
  • Some times, we can see this error message ([298] SQLServer Error: 258, Unable to complete login process due to delay in login response [SQLSTATE 08001]) from remote logins.

    Please connect to the SQL server from local machine and try to increase remote login time and let me know if it working or not.

    Note that "remote logins" here refers to connect to linked servers. So far, Vijay has not said anything about linked servers. As far as I understand, the problem is that SQL Server Agent reports this error, and it seems clear that it is connecting to the local server.

    It is not easy to troubleshoot with this miniscule of information, but I would guess that the job is owned by a domain user? The problem may be related to veruify that user in the AD.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
    • Marked as answer by vijay_1234 Tuesday, July 29, 2014 6:32 AM
    Wednesday, July 23, 2014 8:15 AM
  • Hi Erland,

    Thanks for your sugetion..

    I see there is linked server, there is anything pending from my end to  providing info.??

    could you provide solution.

    Thanks in Advance.

    Wednesday, July 23, 2014 10:55 AM
  • Hello,

    That instance is suffering from IO Bottleneck. It has 4 waits in the top ten related to disk storage. This system is constantly waiting for disks/storage.  It is waiting 11.3 seconds for I/O to finish in average (wait time ms vs wait task count).

    You need to troubleshoot that.

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    Wednesday, July 23, 2014 2:04 PM
    Moderator
  • I see there is linked server, there is anything pending from my end to  providing info.??

    could you provide solution.

    No, I can't provide a solution, because we need more information.

    Do you get this error with a specific job? Do you get that error if you run that job separately? Does the job start and fail? Or does the job fail to start? Does the job use a linked server?

    Or more to the point, you need to give us a better description of what is going on.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
    Wednesday, July 23, 2014 9:13 PM
  • Hi Alberto,

    problem not resolved.

    could you please sugest me.

     how  did you confirm its related to IO pressure

    Thanks in Advance.

    Tuesday, August 26, 2014 3:08 PM