June 4, 2012 at 9:47 pm
Today, Our sql server was unresponsive and below is the error from errolog.
We restarted the sql service o resolve the issue.
Do you know what will be the reason for the below error?
2012-06-04 13:44:10.25 spid169 Timeout occurred while waiting for latch: class 'LOG_MANAGER', id 00000000055709F8, type 4, Task 0x000000027C458988 : 0, waittime 600, flags 0x1a, owning task 0x0000000005627948. Continuing to wait.
2012-06-04 13:44:26.76 spid223 Timeout occurred while waiting for latch: class 'LOG_MANAGER', id 00000000055709F8, type 4, Task 0x00000001D8C4F288 : 0, waittime 300, flags 0x1a, owning task 0x0000000005627948. Continuing to wait.
2012-06-04 13:44:28.44 Server Process 0:0:0 (0x2018) Worker 0x00000000059981A0 appears to be non-yielding on Scheduler 2. Thread creation time: 12983225402244. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 98%. Interval: 856742 ms.
2012-06-04 13:44:44.28 spid175 Timeout occurred while waiting for latch: class 'LOG_MANAGER', id 00000000055709F8, type 4, Task 0x00000001EBE4D048 : 0, waittime 600, flags 0x1a, owning task 0x0000000005627948. Continuing to wait.
2012-06-04 13:44:56.07 spid178 Timeout occurred while waiting for latch: class 'LOG_MANAGER', id 00000000055709F8, type 4, Task 0x00000001EBE4D4C8 : 0, waittime 600, flags 0x1a, owning task 0x0000000005627948. Continuing to wait.
2012-06-04 13:45:00.46 spid177 Timeout occurred while waiting for latch: class 'LOG_MANAGER', id 00000000055709F8, type 4, Task 0x00000001EBE4CBC8 : 0, waittime 600, flags 0x1a, owning task 0x0000000005627948. Continuing to wait.
2012-06-04 13:45:02.59 spid93 Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT', id 00000001ED866978, type 4, Task 0x0000000005609DC8 : 4, waittime 900, flags 0x1a, owning task 0x000000000561D708. Continuing to wait.
2012-06-04 13:45:02.59 spid93 Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT', id 00000001ED866978, type 4, Task 0x0000000005613948 : 1, waittime 900, flags 0x1a, owning task 0x000000000561D708. Continuing to wait.
2012-06-04 13:45:02.60 spid93 Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT', id 00000001ED866978, type 4, Task 0x0000000005627B88 : 2, waittime 900, flags 0x1a, owning task 0x000000000561D708. Continuing to wait.
2012-06-04 13:45:18.89 spid224 Timeout occurred while waiting for latch: class 'LOG_MANAGER', id 00000000055709F8, type 4, Task 0x00000001C184E2C8 : 0, waittime 300, flags 0x1a, owning task 0x0000000005627948. Continuing to wait.
2012-06-04 13:45:19.08 spid230 Timeout occurred while waiting for latch: class 'LOG_MANAGER', id 00000000055709F8, type 4, Task 0x000000012C7454C8 : 0, waittime 300, flags 0x1a, owning task 0x0000000005627948. Continuing to wait.
2012-06-04 13:45:28.48 Server Process 0:0:0 (0x2018) Worker 0x00000000059981A0 appears to be non-yielding on Scheduler 2. Thread creation time: 12983225402244. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 98%. Interval: 916781 ms.
June 4, 2012 at 10:48 pm
A non-yielding scheduler is generally a pretty bad issue. You probably have some memory dumps in your SQL Server log directory. I would recommend contacting Microsoft support and working with them.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply