none
non-yielding on Scheduler related issues found in log file

    Question

  • Hi there,

    I found below in error log file, Kindly tell me the reason.

    2018-02-20 00:00:40.35 spid22s     This instance of SQL Server has been using a process ID of 5592 since 2/16/2018 10:21:37 AM (local) 2/16/2018 4:51:37 AM (UTC). This is an informational message only; no user action is required.
    2018-02-20 02:04:15.52 spid5s      SQL Server has encountered 31 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\abc_2.ldf] in database [abc] (7).  The OS file handle is 0x0000000000000CA8.  The offset of the latest long I/O is: 0x0000039193ae00
    2018-02-20 02:04:47.36 spid5s      SQL Server has encountered 3 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\abc_1.ndf] in database [abc] (7).  The OS file handle is 0x0000000000000C8C.  The offset of the latest long I/O is: 0x00001b11024000
    2018-02-20 02:08:30.87 Server      Process 386:0:15 (0x63ec) Worker 0x00000002636DC1A0 appears to be non-yielding on Scheduler 6. Thread creation time: 13163475328746. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 2%. System Idle 93%. Interval: 70321 ms.
    2018-02-20 02:09:10.66 spid5s      SQL Server has encountered 150 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\abc.mdf] in database [abc] (7).  The OS file handle is 0x0000000000000CC8.  The offset of the latest long I/O is: 0x00006005450000
    2018-02-20 02:16:29.49 spid5s      SQL Server has encountered 138 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\abc.mdf] in database [abc] (7).  The OS file handle is 0x0000000000000CC8.  The offset of the latest long I/O is: 0x000090bb4d0000
    2018-02-20 02:17:39.47 Server      Process 386:0:5 (0x6af0) Worker 0x0000000571C601A0 appears to be non-yielding on Scheduler 12. Thread creation time: 13163542222266. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 97%. Interval: 70297 ms.
    2018-02-20 05:09:38.41 Server      Process 0:0:0 (0x1758) Worker 0x0000000005AB01A0 appears to be non-yielding on Scheduler 0. Thread creation time: 13163230252500. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 97%. Interval: 70302 ms.
    2018-02-20 05:10:03.65 Server      Process 57:0:3 (0x48c4) Worker 0x00000000F2F3C1A0 appears to be non-yielding on Scheduler 8. Thread creation time: 13163555732632. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 96%. Interval: 70552 ms.
    2018-02-20 05:10:39.20 Server      Process 0:0:0 (0x1758) Worker 0x0000000005AB01A0 appears to be non-yielding on Scheduler 0. Thread creation time: 13163230252500. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 96%. Interval: 131092 ms.
    2018-02-20 05:11:04.21 Server      Process 57:0:3 (0x48c4) Worker 0x00000000F2F3C1A0 appears to be non-yielding on Scheduler 8. Thread creation time: 13163555732632. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 96%. Interval: 131347 ms.
    2018-02-20 05:11:11.84 Server      Process 57:0:17 (0x7ba4) Worker 0x00000000E73A81A0 appears to be non-yielding on Scheduler 17. Thread creation time: 13163545871750. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 96%. Interval: 70304 ms.
    2018-02-20 05:11:39.51 Server      Process 0:0:0 (0x1758) Worker 0x0000000005AB01A0 appears to be non-yielding on Scheduler 0. Thread creation time: 13163230252500. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 96%. Interval: 191653 ms.
    2018-02-20 05:11:59.86 Server      Process 57:0:7 (0x4d68) Worker 0x00000001E20901A0 appears to be non-yielding on Scheduler 10. Thread creation time: 13163545826747. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 93%. Interval: 70343 ms.
    2018-02-20 05:13:13.38 spid5s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\abc.mdf] in database [abc] (7).  The OS file handle is 0x0000000000000CC8.  The offset of the latest long I/O is: 0x00008730e12000
    2018-02-20 05:21:40.70 spid5s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\abc_2.ldf] in database [abc] (7).  The OS file handle is 0x0000000000000CA8.  The offset of the latest long I/O is: 0x00000493a52400
    2018-02-20 05:22:38.32 Logon       Error: 18456, Severity: 14, State: 46.
    2018-02-20 05:22:38.32 Logon       Login failed for user 'abc'. Reason: Failed to open the database configured in the login object while revalidating the login on the connection. [CLIENT: 172.16.0.1]
    2018-02-20 05:22:38.33 spid1001    Error: 18056, Severity: 20, State: 46.
    2018-02-20 05:22:38.33 spid1001    The client was unable to reuse a session with SPID 1001, which had been reset for connection pooling. The failure ID is 46. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.


    • Edited by Amita Tyagi Tuesday, February 20, 2018 6:29 AM
    Thursday, February 08, 2018 4:44 AM

Answers

  • So this is due to storage or it's sql server's issue?

    First of all please give proper heading to your question. Just putting "error" as name does not qualify as good question heading. 

    Now Olaf gave you links to read and I believe it has all the details to troubleshoot the issue. The issue mostly can be because of slow storage, but I have seen cases where this was also due to poor query running in sql server which was doing multiple table scans and overwhelming the I/O and thus this message. The message means an I/O request was posted by SQL Server may be for bringing page from disk into memory but that request was not satisfies even after 15 sec and this SQl server logged this message in errorlog.

    As I see this may be due to storage issue depending on how often do you see this message if you see it frequently then ask your storage team to check storage, you can say it is slow. 


    Cheers,

    Shashank

    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles

    MVP

    • Marked as answer by Amita Tyagi Monday, February 12, 2018 10:14 AM
    Monday, February 12, 2018 6:39 AM
    Moderator

All replies

  • Hello,

    That are not error, just warnings and they say, that your storage system is to slow to handle IO request for SQL Server in a fashion time.

    See
    I/O requests taking longer than 15 seconds to complete on file
    Troubleshooting SQL Server I/O requests taking longer than 15 seconds – I/O stalls & Disk latency


    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    • Marked as answer by Amita Tyagi Thursday, February 08, 2018 5:09 AM
    • Unmarked as answer by Amita Tyagi Monday, February 12, 2018 6:14 AM
    Thursday, February 08, 2018 4:53 AM
    Moderator
  • So this is due to storage or it's sql server's issue?

    First of all please give proper heading to your question. Just putting "error" as name does not qualify as good question heading. 

    Now Olaf gave you links to read and I believe it has all the details to troubleshoot the issue. The issue mostly can be because of slow storage, but I have seen cases where this was also due to poor query running in sql server which was doing multiple table scans and overwhelming the I/O and thus this message. The message means an I/O request was posted by SQL Server may be for bringing page from disk into memory but that request was not satisfies even after 15 sec and this SQl server logged this message in errorlog.

    As I see this may be due to storage issue depending on how often do you see this message if you see it frequently then ask your storage team to check storage, you can say it is slow. 


    Cheers,

    Shashank

    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles

    MVP

    • Marked as answer by Amita Tyagi Monday, February 12, 2018 10:14 AM
    Monday, February 12, 2018 6:39 AM
    Moderator
  • Found in error logs, Kindly look into:

    2018-02-10 10:39:58.37 spid318     Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
    2018-02-10 10:39:58.56 spid318     Using 'xpsqlbot.dll' version '2009.100.1600' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
    2018-02-10 10:39:59.97 spid318     Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
    2018-02-10 10:40:00.27 spid318     Using 'xplog70.dll' version '2009.100.6000' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
    2018-02-10 11:43:22.52 Server      Using 'dbghelp.dll' version '4.0.5'
    2018-02-10 11:43:24.37 Server      ***Unable to get thread context for spid 0
    2018-02-10 11:43:24.37 Server      * *******************************************************************************
    2018-02-10 11:43:24.37 Server      *
    2018-02-10 11:43:24.37 Server      * BEGIN STACK DUMP:
    2018-02-10 11:43:24.37 Server      *   02/10/18 11:43:24 spid 5420
    2018-02-10 11:43:24.37 Server      *
    2018-02-10 11:43:24.37 Server      * Non-yielding Scheduler
    2018-02-10 11:43:24.37 Server      *
    2018-02-10 11:43:24.37 Server      * *******************************************************************************
    2018-02-10 11:43:24.37 Server      Stack Signature for the dump is 0x00000000000003B6
    2018-02-10 11:43:50.08 Server      External dump process return code 0x20002001.
    The error information has been submitted to Watson error reporting.

    2018-02-10 11:43:50.08 Server      DoMiniDump () encountered error (0x80004005) - Unspecified error

    2018-02-10 11:43:50.08 Server      Process 0:0:0 (0x79d4) Worker 0x00000001DB08A1A0 appears to be non-yielding on Scheduler 9. Thread creation time: 13162714130557. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 95%. Interval: 70358 ms.
    2018-02-10 11:44:46.30 Server      Process 0:0:0 (0x15a4) Worker 0x000000000A6A61A0 appears to be non-yielding on Scheduler 12. Thread creation time: 13162633972474. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 89%. Interval: 70411 ms.
    2018-02-10 11:45:20.49 Server      Process 73:0:4 (0x4448) Worker 0x00000001399DA1A0 appears to be non-yielding on Scheduler 11. Thread creation time: 13162634579204. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 3%. System Idle 87%. Interval: 70409 ms.

    Monday, February 12, 2018 8:33 AM
  • What is output of select @@version. Stack dumps are mostly due to bug in SQL Server if applying latest SP does not fix this your only option is to raise case with MS

    Cheers,

    Shashank

    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles

    MVP

    Monday, February 12, 2018 9:42 AM
    Moderator
  • That's a dump, nothing we from community could look into.

    Which SQL Server Version and patch Level are you using? Run

    SELECT @@VERSION;

    to get Version details


    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    Monday, February 12, 2018 9:45 AM
    Moderator
  • Below is my SQL Server Version

    "Microsoft SQL Server 2008 R2 (SP3) - 10.50.6000.34 (X64)   Aug 19 2014 12:21:34   Copyright (c) Microsoft Corporation  Web Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) "

    Monday, February 12, 2018 10:10 AM
  • Microsoft SQL Server 2008 R2 (SP3) - 10.50.6000.34 (X64)

    You are already on the latest Service pack 3 for SQL Server 2008 R2; https://sqlserverbuilds.blogspot.de/

    You can try using this tool to Analyse the dump file: SQL Server Diagnostics (Preview)


    Olaf Helper

    [ Blog] [ Xing] [ MVP]


    Monday, February 12, 2018 10:44 AM
    Moderator
  • Hi there,

    I found below in error log file, Kindly tell me the reason.

    2018-02-20 00:00:40.35 spid22s     This instance of SQL Server has been using a process ID of 5592 since 2/16/2018 10:21:37 AM (local) 2/16/2018 4:51:37 AM (UTC). This is an informational message only; no user action is required.
    2018-02-20 02:04:15.52 spid5s      SQL Server has encountered 31 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\abc_2.ldf] in database [abc] (7).  The OS file handle is 0x0000000000000CA8.  The offset of the latest long I/O is: 0x0000039193ae00
    2018-02-20 02:04:47.36 spid5s      SQL Server has encountered 3 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\abc_1.ndf] in database [abc] (7).  The OS file handle is 0x0000000000000C8C.  The offset of the latest long I/O is: 0x00001b11024000
    2018-02-20 02:08:30.87 Server      Process 386:0:15 (0x63ec) Worker 0x00000002636DC1A0 appears to be non-yielding on Scheduler 6. Thread creation time: 13163475328746. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 2%. System Idle 93%. Interval: 70321 ms.
    2018-02-20 02:09:10.66 spid5s      SQL Server has encountered 150 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\abc.mdf] in database [abc] (7).  The OS file handle is 0x0000000000000CC8.  The offset of the latest long I/O is: 0x00006005450000
    2018-02-20 02:16:29.49 spid5s      SQL Server has encountered 138 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\abc.mdf] in database [abc] (7).  The OS file handle is 0x0000000000000CC8.  The offset of the latest long I/O is: 0x000090bb4d0000
    2018-02-20 02:17:39.47 Server      Process 386:0:5 (0x6af0) Worker 0x0000000571C601A0 appears to be non-yielding on Scheduler 12. Thread creation time: 13163542222266. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 97%. Interval: 70297 ms.
    2018-02-20 05:09:38.41 Server      Process 0:0:0 (0x1758) Worker 0x0000000005AB01A0 appears to be non-yielding on Scheduler 0. Thread creation time: 13163230252500. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 97%. Interval: 70302 ms.
    2018-02-20 05:10:03.65 Server      Process 57:0:3 (0x48c4) Worker 0x00000000F2F3C1A0 appears to be non-yielding on Scheduler 8. Thread creation time: 13163555732632. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 96%. Interval: 70552 ms.
    2018-02-20 05:10:39.20 Server      Process 0:0:0 (0x1758) Worker 0x0000000005AB01A0 appears to be non-yielding on Scheduler 0. Thread creation time: 13163230252500. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 96%. Interval: 131092 ms.
    2018-02-20 05:11:04.21 Server      Process 57:0:3 (0x48c4) Worker 0x00000000F2F3C1A0 appears to be non-yielding on Scheduler 8. Thread creation time: 13163555732632. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 96%. Interval: 131347 ms.
    2018-02-20 05:11:11.84 Server      Process 57:0:17 (0x7ba4) Worker 0x00000000E73A81A0 appears to be non-yielding on Scheduler 17. Thread creation time: 13163545871750. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 96%. Interval: 70304 ms.
    2018-02-20 05:11:39.51 Server      Process 0:0:0 (0x1758) Worker 0x0000000005AB01A0 appears to be non-yielding on Scheduler 0. Thread creation time: 13163230252500. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 96%. Interval: 191653 ms.
    2018-02-20 05:11:59.86 Server      Process 57:0:7 (0x4d68) Worker 0x00000001E20901A0 appears to be non-yielding on Scheduler 10. Thread creation time: 13163545826747. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 93%. Interval: 70343 ms.
    2018-02-20 05:13:13.38 spid5s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\abc.mdf] in database [abc] (7).  The OS file handle is 0x0000000000000CC8.  The offset of the latest long I/O is: 0x00008730e12000
    2018-02-20 05:21:40.70 spid5s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\abc_2.ldf] in database [abc] (7).  The OS file handle is 0x0000000000000CA8.  The offset of the latest long I/O is: 0x00000493a52400
    2018-02-20 05:22:38.32 Logon       Error: 18456, Severity: 14, State: 46.
    2018-02-20 05:22:38.32 Logon       Login failed for user 'abc'. Reason: Failed to open the database configured in the login object while revalidating the login on the connection. [CLIENT: 172.16.0.1]
    2018-02-20 05:22:38.33 spid1001    Error: 18056, Severity: 20, State: 46.
    2018-02-20 05:22:38.33 spid1001    The client was unable to reuse a session with SPID 1001, which had been reset for connection pooling. The failure ID is 46. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.

    Tuesday, February 20, 2018 7:20 AM
  • Question
    You cannot vote on your own post
    0

    Hi there,

    I found below in error log file, Kindly tell me the reason.

    2018-02-20 00:00:40.35 spid22s     This instance of SQL Server has been using a process ID of 5592 since 2/16/2018 10:21:37 AM (local) 2/16/2018 4:51:37 AM (UTC). This is an informational message only; no user action is required.
    2018-02-20 02:04:15.52 spid5s      SQL Server has encountered 31 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\abc_2.ldf] in database [abc] (7).  The OS file handle is 0x0000000000000CA8.  The offset of the latest long I/O is: 0x0000039193ae00
    2018-02-20 02:04:47.36 spid5s      SQL Server has encountered 3 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\abc_1.ndf] in database [abc] (7).  The OS file handle is 0x0000000000000C8C.  The offset of the latest long I/O is: 0x00001b11024000
    2018-02-20 02:08:30.87 Server      Process 386:0:15 (0x63ec) Worker 0x00000002636DC1A0 appears to be non-yielding on Scheduler 6. Thread creation time: 13163475328746. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 2%. System Idle 93%. Interval: 70321 ms.
    2018-02-20 02:09:10.66 spid5s      SQL Server has encountered 150 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\abc.mdf] in database [abc] (7).  The OS file handle is 0x0000000000000CC8.  The offset of the latest long I/O is: 0x00006005450000
    2018-02-20 02:16:29.49 spid5s      SQL Server has encountered 138 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\abc.mdf] in database [abc] (7).  The OS file handle is 0x0000000000000CC8.  The offset of the latest long I/O is: 0x000090bb4d0000
    2018-02-20 02:17:39.47 Server      Process 386:0:5 (0x6af0) Worker 0x0000000571C601A0 appears to be non-yielding on Scheduler 12. Thread creation time: 13163542222266. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 97%. Interval: 70297 ms.
    2018-02-20 05:09:38.41 Server      Process 0:0:0 (0x1758) Worker 0x0000000005AB01A0 appears to be non-yielding on Scheduler 0. Thread creation time: 13163230252500. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 97%. Interval: 70302 ms.
    2018-02-20 05:10:03.65 Server      Process 57:0:3 (0x48c4) Worker 0x00000000F2F3C1A0 appears to be non-yielding on Scheduler 8. Thread creation time: 13163555732632. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 96%. Interval: 70552 ms.
    2018-02-20 05:10:39.20 Server      Process 0:0:0 (0x1758) Worker 0x0000000005AB01A0 appears to be non-yielding on Scheduler 0. Thread creation time: 13163230252500. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 96%. Interval: 131092 ms.
    2018-02-20 05:11:04.21 Server      Process 57:0:3 (0x48c4) Worker 0x00000000F2F3C1A0 appears to be non-yielding on Scheduler 8. Thread creation time: 13163555732632. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 96%. Interval: 131347 ms.
    2018-02-20 05:11:11.84 Server      Process 57:0:17 (0x7ba4) Worker 0x00000000E73A81A0 appears to be non-yielding on Scheduler 17. Thread creation time: 13163545871750. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 96%. Interval: 70304 ms.
    2018-02-20 05:11:39.51 Server      Process 0:0:0 (0x1758) Worker 0x0000000005AB01A0 appears to be non-yielding on Scheduler 0. Thread creation time: 13163230252500. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 96%. Interval: 191653 ms.
    2018-02-20 05:11:59.86 Server      Process 57:0:7 (0x4d68) Worker 0x00000001E20901A0 appears to be non-yielding on Scheduler 10. Thread creation time: 13163545826747. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 1%. System Idle 93%. Interval: 70343 ms.
    2018-02-20 05:13:13.38 spid5s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\abc.mdf] in database [abc] (7).  The OS file handle is 0x0000000000000CC8.  The offset of the latest long I/O is: 0x00008730e12000
    2018-02-20 05:21:40.70 spid5s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\abc_2.ldf] in database [abc] (7).  The OS file handle is 0x0000000000000CA8.  The offset of the latest long I/O is: 0x00000493a52400
    2018-02-20 05:22:38.32 Logon       Error: 18456, Severity: 14, State: 46.
    2018-02-20 05:22:38.32 Logon       Login failed for user 'abc'. Reason: Failed to open the database configured in the login object while revalidating the login on the connection. [CLIENT: 172.16.0.1]
    2018-02-20 05:22:38.33 spid1001    Error: 18056, Severity: 20, State: 46.
    2018-02-20 05:22:38.33 spid1001    The client was unable to reuse a session with SPID 1001, which had been reset for connection pooling. The failure ID is 46. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.

    Tuesday, February 20, 2018 10:00 AM
  • Hi Amita,

    It clearly says that the error occured due to login failure for user 'abc'. Please check the credentials for this user and whether it has the access to the database.


    Cheers,

    Amit Tomar

    ---------------------------------------------------

    Please mark this as answer if it solved your query

    Please vote this as helpful if it solved your query

    ---------------------------------------------------

    My Blog My Wiki Page

    Tuesday, February 20, 2018 10:08 AM
  • Amita you have already raised similar question here and the thread you previously raised was also the same. PLEASE dont raise similar threads, this is totally not acceptable on forum. The answer has been provided to you on the old thread. 

    Cheers,

    Shashank

    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles

    MVP

    Tuesday, February 20, 2018 10:17 AM
    Moderator
  • Sorry for this I got confused and it has been posted by mistake.
    Tuesday, February 20, 2018 10:34 AM