April 12, 2012 at 10:30 am
Hi,
I'm able to connect to the sql instance but when I click database properties it's not responding. No backups happening.
Application using this sql instance is alos NOT working.
We are having SQL Server 2008 with SP1 on Windows Server 2008 64 bit. It's 2 node active/passive cluster setup.
I have noticed the below error in error log:
012-04-11 21:00:11.94 Backup Log was backed up. Database: CF_AQS_Repository_PROD, creation date(time): 2010/10/23(11:21:22), first LSN: 9913:43:1, last LSN: 9913:57:1, number of dump devices: 3, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'VDI_8AACE742-1EB5-46F9-A557-283594E29493_0', 'VDI_8AACE742-1EB5-46F9-A557-283594E29493_1', 'VDI_8AACE742-1EB5-46F9-A557-283594E29493_2'}). This is an informational message only. No user action is required.
2012-04-11 21:01:17.60 Server Using 'dbghelp.dll' version '4.0.5'
2012-04-11 21:01:17.64 Server ***Unable to get thread context for spid 0
2012-04-11 21:01:17.64 Server * *******************************************************************************
2012-04-11 21:01:17.64 Server *
2012-04-11 21:01:17.64 Server * BEGIN STACK DUMP:
2012-04-11 21:01:17.64 Server * 04/11/12 21:01:17 spid 2844
2012-04-11 21:01:17.64 Server *
2012-04-11 21:01:17.64 Server * Non-yielding Scheduler
2012-04-11 21:01:17.64 Server *
2012-04-11 21:01:17.64 Server * *******************************************************************************
2012-04-11 21:01:17.64 Server Stack Signature for the dump is 0x0000000000000380
2012-04-11 21:01:19.96 Server External dump process return code 0x20000001.
External dump process returned no errors.
2012-04-11 21:01:19.96 Server Process 0:0:0 (0x20f4) Worker 0x00000000067E21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12978646201553. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 98%. Interval: 70075 ms.
2012-04-11 21:02:20.00 Server Process 0:0:0 (0x20f4) Worker 0x00000000067E21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12978646201553. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 98%. Interval: 132544 ms.
2012-04-11 21:03:20.03 Server Process 0:0:0 (0x20f4) Worker 0x00000000067E21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12978646201553. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 98%. Interval: 192580 ms.
2012-04-11 21:04:20.07 Server Process 0:0:0 (0x20f4) Worker 0x00000000067E21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12978646201553. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 98%. Interval: 252616 ms.
2012-04-11 21:05:20.11 Server Process 0:0:0 (0x20f4) Worker 0x00000000067E21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12978646201553. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 98%. Interval: 312652 ms.
2012-04-11 21:06:20.14 Server Process 0:0:0 (0x20f4) Worker 0x00000000067E21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12978646201553. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 99%. Interval: 372688 ms.
2012-04-11 21:07:20.18 Server Process 0:0:0 (0x20f4) Worker 0x00000000067E21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12978646201553. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 99%. Interval: 432725 ms.
2012-04-11 21:08:20.22 Server Process 0:0:0 (0x20f4) Worker 0x00000000067E21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12978646201553. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 99%. Interval: 492762 ms.
2012-04-11 21:09:20.25 Server Process 0:0:0 (0x20f4) Worker 0x00000000067E21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12978646201553. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 99%. Interval: 552798 ms.
2012-04-11 21:10:20.29 Server Process 0:0:0 (0x20f4) Worker 0x00000000067E21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12978646201553. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 99%. Interval: 612834 ms.
2012-04-11 21:11:20.33 Server Process 0:0:0 (0x20f4) Worker 0x00000000067E21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12978646201553. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 99%. Interval: 672871 ms.
2012-04-11 21:12:20.36 Server Process 0:0:0 (0x20f4) Worker 0x00000000067E21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12978646201553. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 99%. Interval: 732908 ms.
2012-04-11 21:13:20.40 Server Process 0:0:0 (0x20f4) Worker 0x00000000067E21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12978646201553. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 99%. Interval: 792944 ms.
2012-04-11 21:14:20.44 Server Process 0:0:0 (0x20f4) Worker 0x00000000067E21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12978646201553. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 99%. Interval: 852981 ms.
2012-04-11 21:15:20.47 Server Process 0:0:0 (0x20f4) Worker 0x00000000067E21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12978646201553. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 99%. Interval: 913017 ms.
2012-04-11 21:16:20.51 Server Process 0:0:0 (0x20f4) Worker 0x00000000067E21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12978646201553. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 99%. Interval: 973053 ms.
2012-04-11 21:17:20.54 Server Process 0:0:0 (0x20f4) Worker 0x00000000067E21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12978646201553. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 99%. Interval: 1033090 ms.
:crying:
Please advice..
April 12, 2012 at 10:33 am
I would try restarting the instance and see if that resolves the issue.
April 12, 2012 at 10:38 am
Thanks,
I restarted the service and its working fine.
But I want to know why the error occurred..
Thanks
April 12, 2012 at 10:41 am
a quick through the DMVs would have been helpful but to late now
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 12, 2012 at 11:03 am
You mean there is no way to find out why the error occurred once we restart the service?
Thanks
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply