I've Googled myself silly on this and I'm not sure what I should do to fix
it. Will SP4 do it? These errors happen every day at 8:00 PM yet there are
no SQL Server Agent jobs running during that time. Any ideas?
2006-05-21 12:25:36.71 server Microsoft SQL Server 2000 - 8.00.760 (Intel
X86)
.
.
2006-05-21 20:20:09.00 server Error: 17883, Severity: 1, State: 0
2006-05-21 20:20:09.00 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D0E28.
2006-05-22 01:10:07.29 spid63 DBCC CHECKDB (iGreentree, noindex) executed
by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
2006-05-22 01:36:50.81 backup Database backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), pages dumped: 667205, first LSN:
789963:13179:1, last LSN: 789963:19503:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK:
{'F:\SQL_BAK\iGreentree\iGreentree_db_200605220130.BAK'}).
2006-05-22 12:02:03.96 backup Log backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), first LSN: 789814:10524:1, last
LSN: 789966:19764:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'F:\SQL_BAK\iGreentree\iGreentree_tlog_200605221200.TRN'}).
2006-05-22 20:11:08.85 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:11:08.85 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039C3D10.
2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:12:08.86 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039C3D10.
2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:12:08.86 server The Scheduler 1 appears to be hung. SPID
59, ECID 0, UMS Context 0x039D27E8.
2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:12:08.86 server The Scheduler 3 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039C5A68.
2006-05-23 01:10:06.00 spid52 DBCC CHECKDB (iGreentree, noindex) executed
by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
2006-05-23 01:37:12.34 backup Database backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), pages dumped: 668013, first LSN:
790081:6357:1, last LSN: 790081:12597:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK:
{'F:\SQL_BAK\iGreentree\iGreentree_db_200605230130.BAK'}).
2006-05-23 12:01:04.71 backup Log backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), first LSN: 789966:19764:1, last
LSN: 790091:2027:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'F:\SQL_BAK\iGreentree\iGreentree_tlog_200605231200.TRN'}).
2006-05-23 20:22:08.77 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:22:08.77 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D3548.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D3548.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 1 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D7AA8.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 2 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D6F60.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 3 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039DCD98.Scagnetti,
Try refresh on the jobs collection also take a look at your Database
Maintenance Plans. Is this a target server for a master server?
HTH
Jerry
"Scagnetti" <Scagnetti@.discussions.microsoft.com> wrote in message
news:6635ACAF-0BD1-48BE-BFD4-4D459F34786E@.microsoft.com...
> I've Googled myself silly on this and I'm not sure what I should do to fix
> it. Will SP4 do it? These errors happen every day at 8:00 PM yet there
> are
> no SQL Server Agent jobs running during that time. Any ideas?
> 2006-05-21 12:25:36.71 server Microsoft SQL Server 2000 - 8.00.760 (Intel
> X86)
> .
> .
> 2006-05-21 20:20:09.00 server Error: 17883, Severity: 1, State: 0
> 2006-05-21 20:20:09.00 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D0E28.
> 2006-05-22 01:10:07.29 spid63 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-22 01:36:50.81 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 667205, first
> LSN:
> 789963:13179:1, last LSN: 789963:19503:1, number of dump devices: 1,
> device
> information: (FILE=1, TYPE=DISK:
> {'F:\SQL_BAK\iGreentree\iGreentree_db_200605220130.BAK'}).
> 2006-05-22 12:02:03.96 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789814:10524:1, last
> LSN: 789966:19764:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: {'F:\SQL_BAK\iGreentree\iGreentree_tlog_200605221200.TRN'}).
> 2006-05-22 20:11:08.85 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:11:08.85 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 1 appears to be hung. SPID
> 59, ECID 0, UMS Context 0x039D27E8.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C5A68.
> 2006-05-23 01:10:06.00 spid52 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-23 01:37:12.34 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 668013, first
> LSN:
> 790081:6357:1, last LSN: 790081:12597:1, number of dump devices: 1, device
> information: (FILE=1, TYPE=DISK:
> {'F:\SQL_BAK\iGreentree\iGreentree_db_200605230130.BAK'}).
> 2006-05-23 12:01:04.71 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789966:19764:1, last
> LSN: 790091:2027:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: {'F:\SQL_BAK\iGreentree\iGreentree_tlog_200605231200.TRN'}).
> 2006-05-23 20:22:08.77 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:22:08.77 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 1 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D7AA8.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 2 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D6F60.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039DCD98.
>|||The scheduler referenced in the error message isn't SQL Agent - it's the
internal task scheduler UMS - User Mode Scheduler. This basically means
that a thread became stuck. Here are a few possible causes:
http://support.microsoft.com/search/default.aspx?catalog=LCID%3D1033&spid=global&query=17883&adv=&mode=r&cat=False
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Scagnetti" <Scagnetti@.discussions.microsoft.com> wrote in message
news:6635ACAF-0BD1-48BE-BFD4-4D459F34786E@.microsoft.com...
> I've Googled myself silly on this and I'm not sure what I should do to fix
> it. Will SP4 do it? These errors happen every day at 8:00 PM yet there
> are
> no SQL Server Agent jobs running during that time. Any ideas?
> 2006-05-21 12:25:36.71 server Microsoft SQL Server 2000 - 8.00.760 (Intel
> X86)
> .
> .
> 2006-05-21 20:20:09.00 server Error: 17883, Severity: 1, State: 0
> 2006-05-21 20:20:09.00 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D0E28.
> 2006-05-22 01:10:07.29 spid63 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-22 01:36:50.81 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 667205, first
> LSN:
> 789963:13179:1, last LSN: 789963:19503:1, number of dump devices: 1,
> device
> information: (FILE=1, TYPE=DISK:
> {'F:\SQL_BAK\iGreentree\iGreentree_db_200605220130.BAK'}).
> 2006-05-22 12:02:03.96 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789814:10524:1, last
> LSN: 789966:19764:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: {'F:\SQL_BAK\iGreentree\iGreentree_tlog_200605221200.TRN'}).
> 2006-05-22 20:11:08.85 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:11:08.85 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 1 appears to be hung. SPID
> 59, ECID 0, UMS Context 0x039D27E8.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C5A68.
> 2006-05-23 01:10:06.00 spid52 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-23 01:37:12.34 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 668013, first
> LSN:
> 790081:6357:1, last LSN: 790081:12597:1, number of dump devices: 1, device
> information: (FILE=1, TYPE=DISK:
> {'F:\SQL_BAK\iGreentree\iGreentree_db_200605230130.BAK'}).
> 2006-05-23 12:01:04.71 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789966:19764:1, last
> LSN: 790091:2027:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: {'F:\SQL_BAK\iGreentree\iGreentree_tlog_200605231200.TRN'}).
> 2006-05-23 20:22:08.77 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:22:08.77 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 1 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D7AA8.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 2 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D6F60.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039DCD98.
>
Showing posts with label hung. Show all posts
Showing posts with label hung. Show all posts
Wednesday, March 21, 2012
Error: 17883, The Scheduler 0 appears to be hung...
I've Googled myself silly on this and I'm not sure what I should do to fix
it. Will SP4 do it? These errors happen every day at 8:00 PM yet there are
no SQL Server Agent jobs running during that time. Any ideas?
2006-05-21 12:25:36.71 server Microsoft SQL Server 2000 - 8.00.760 (Intel
X86)
.
.
2006-05-21 20:20:09.00 server Error: 17883, Severity: 1, State: 0
2006-05-21 20:20:09.00 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D0E28.
2006-05-22 01:10:07.29 spid63 DBCC CHECKDB (iGreentree, noindex) executed
by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
2006-05-22 01:36:50.81 backup Database backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), pages dumped: 667205, first LSN:
789963:13179:1, last LSN: 789963:19503:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK:
& #123;'F:\SQL_BAK\iGreentree\iGreentree_d
b_200605220130.BAK'}).
2006-05-22 12:02:03.96 backup Log backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), first LSN: 789814:10524:1, last
LSN: 789966:19764:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: & #123;'F:\SQL_BAK\iGreentree\iGreentree_t
log_200605221200.TRN'}).
2006-05-22 20:11:08.85 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:11:08.85 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039C3D10.
2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:12:08.86 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039C3D10.
2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:12:08.86 server The Scheduler 1 appears to be hung. SPID
59, ECID 0, UMS Context 0x039D27E8.
2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:12:08.86 server The Scheduler 3 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039C5A68.
2006-05-23 01:10:06.00 spid52 DBCC CHECKDB (iGreentree, noindex) executed
by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
2006-05-23 01:37:12.34 backup Database backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), pages dumped: 668013, first LSN:
790081:6357:1, last LSN: 790081:12597:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK:
& #123;'F:\SQL_BAK\iGreentree\iGreentree_d
b_200605230130.BAK'}).
2006-05-23 12:01:04.71 backup Log backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), first LSN: 789966:19764:1, last
LSN: 790091:2027:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: & #123;'F:\SQL_BAK\iGreentree\iGreentree_t
log_200605231200.TRN'}).
2006-05-23 20:22:08.77 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:22:08.77 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D3548.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D3548.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 1 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D7AA8.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 2 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D6F60.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 3 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039DCD98.Scagnetti,
Try refresh on the jobs collection also take a look at your Database
Maintenance Plans. Is this a target server for a master server?
HTH
Jerry
"Scagnetti" <Scagnetti@.discussions.microsoft.com> wrote in message
news:6635ACAF-0BD1-48BE-BFD4-4D459F34786E@.microsoft.com...
> I've Googled myself silly on this and I'm not sure what I should do to fix
> it. Will SP4 do it? These errors happen every day at 8:00 PM yet there
> are
> no SQL Server Agent jobs running during that time. Any ideas?
> 2006-05-21 12:25:36.71 server Microsoft SQL Server 2000 - 8.00.760 (Intel
> X86)
> .
> .
> 2006-05-21 20:20:09.00 server Error: 17883, Severity: 1, State: 0
> 2006-05-21 20:20:09.00 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D0E28.
> 2006-05-22 01:10:07.29 spid63 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-22 01:36:50.81 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 667205, first
> LSN:
> 789963:13179:1, last LSN: 789963:19503:1, number of dump devices: 1,
> device
> information: (FILE=1, TYPE=DISK:
> & #123;'F:\SQL_BAK\iGreentree\iGreentree_d
b_200605220130.BAK'}).
> 2006-05-22 12:02:03.96 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789814:10524:1, last
> LSN: 789966:19764:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: & #123;'F:\SQL_BAK\iGreentree\iGreentree_t
log_200605221200.TRN'}
).
> 2006-05-22 20:11:08.85 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:11:08.85 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 1 appears to be hung. SPID
> 59, ECID 0, UMS Context 0x039D27E8.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C5A68.
> 2006-05-23 01:10:06.00 spid52 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-23 01:37:12.34 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 668013, first
> LSN:
> 790081:6357:1, last LSN: 790081:12597:1, number of dump devices: 1, device
> information: (FILE=1, TYPE=DISK:
> & #123;'F:\SQL_BAK\iGreentree\iGreentree_d
b_200605230130.BAK'}).
> 2006-05-23 12:01:04.71 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789966:19764:1, last
> LSN: 790091:2027:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: & #123;'F:\SQL_BAK\iGreentree\iGreentree_t
log_200605231200.TRN'}
).
> 2006-05-23 20:22:08.77 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:22:08.77 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 1 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D7AA8.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 2 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D6F60.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039DCD98.
>|||The scheduler referenced in the error message isn't SQL Agent - it's the
internal task scheduler UMS - User Mode Scheduler. This basically means
that a thread became stuck. Here are a few possible causes:
http://support.microsoft.com/search...ode=r&cat=False
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Scagnetti" <Scagnetti@.discussions.microsoft.com> wrote in message
news:6635ACAF-0BD1-48BE-BFD4-4D459F34786E@.microsoft.com...
> I've Googled myself silly on this and I'm not sure what I should do to fix
> it. Will SP4 do it? These errors happen every day at 8:00 PM yet there
> are
> no SQL Server Agent jobs running during that time. Any ideas?
> 2006-05-21 12:25:36.71 server Microsoft SQL Server 2000 - 8.00.760 (Intel
> X86)
> .
> .
> 2006-05-21 20:20:09.00 server Error: 17883, Severity: 1, State: 0
> 2006-05-21 20:20:09.00 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D0E28.
> 2006-05-22 01:10:07.29 spid63 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-22 01:36:50.81 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 667205, first
> LSN:
> 789963:13179:1, last LSN: 789963:19503:1, number of dump devices: 1,
> device
> information: (FILE=1, TYPE=DISK:
> & #123;'F:\SQL_BAK\iGreentree\iGreentree_d
b_200605220130.BAK'}).
> 2006-05-22 12:02:03.96 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789814:10524:1, last
> LSN: 789966:19764:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: & #123;'F:\SQL_BAK\iGreentree\iGreentree_t
log_200605221200.TRN'}
).
> 2006-05-22 20:11:08.85 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:11:08.85 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 1 appears to be hung. SPID
> 59, ECID 0, UMS Context 0x039D27E8.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C5A68.
> 2006-05-23 01:10:06.00 spid52 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-23 01:37:12.34 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 668013, first
> LSN:
> 790081:6357:1, last LSN: 790081:12597:1, number of dump devices: 1, device
> information: (FILE=1, TYPE=DISK:
> & #123;'F:\SQL_BAK\iGreentree\iGreentree_d
b_200605230130.BAK'}).
> 2006-05-23 12:01:04.71 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789966:19764:1, last
> LSN: 790091:2027:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: & #123;'F:\SQL_BAK\iGreentree\iGreentree_t
log_200605231200.TRN'}
).
> 2006-05-23 20:22:08.77 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:22:08.77 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 1 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D7AA8.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 2 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D6F60.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039DCD98.
>
it. Will SP4 do it? These errors happen every day at 8:00 PM yet there are
no SQL Server Agent jobs running during that time. Any ideas?
2006-05-21 12:25:36.71 server Microsoft SQL Server 2000 - 8.00.760 (Intel
X86)
.
.
2006-05-21 20:20:09.00 server Error: 17883, Severity: 1, State: 0
2006-05-21 20:20:09.00 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D0E28.
2006-05-22 01:10:07.29 spid63 DBCC CHECKDB (iGreentree, noindex) executed
by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
2006-05-22 01:36:50.81 backup Database backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), pages dumped: 667205, first LSN:
789963:13179:1, last LSN: 789963:19503:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK:
& #123;'F:\SQL_BAK\iGreentree\iGreentree_d
b_200605220130.BAK'}).
2006-05-22 12:02:03.96 backup Log backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), first LSN: 789814:10524:1, last
LSN: 789966:19764:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: & #123;'F:\SQL_BAK\iGreentree\iGreentree_t
log_200605221200.TRN'}).
2006-05-22 20:11:08.85 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:11:08.85 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039C3D10.
2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:12:08.86 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039C3D10.
2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:12:08.86 server The Scheduler 1 appears to be hung. SPID
59, ECID 0, UMS Context 0x039D27E8.
2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:12:08.86 server The Scheduler 3 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039C5A68.
2006-05-23 01:10:06.00 spid52 DBCC CHECKDB (iGreentree, noindex) executed
by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
2006-05-23 01:37:12.34 backup Database backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), pages dumped: 668013, first LSN:
790081:6357:1, last LSN: 790081:12597:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK:
& #123;'F:\SQL_BAK\iGreentree\iGreentree_d
b_200605230130.BAK'}).
2006-05-23 12:01:04.71 backup Log backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), first LSN: 789966:19764:1, last
LSN: 790091:2027:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: & #123;'F:\SQL_BAK\iGreentree\iGreentree_t
log_200605231200.TRN'}).
2006-05-23 20:22:08.77 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:22:08.77 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D3548.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D3548.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 1 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D7AA8.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 2 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D6F60.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 3 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039DCD98.Scagnetti,
Try refresh on the jobs collection also take a look at your Database
Maintenance Plans. Is this a target server for a master server?
HTH
Jerry
"Scagnetti" <Scagnetti@.discussions.microsoft.com> wrote in message
news:6635ACAF-0BD1-48BE-BFD4-4D459F34786E@.microsoft.com...
> I've Googled myself silly on this and I'm not sure what I should do to fix
> it. Will SP4 do it? These errors happen every day at 8:00 PM yet there
> are
> no SQL Server Agent jobs running during that time. Any ideas?
> 2006-05-21 12:25:36.71 server Microsoft SQL Server 2000 - 8.00.760 (Intel
> X86)
> .
> .
> 2006-05-21 20:20:09.00 server Error: 17883, Severity: 1, State: 0
> 2006-05-21 20:20:09.00 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D0E28.
> 2006-05-22 01:10:07.29 spid63 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-22 01:36:50.81 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 667205, first
> LSN:
> 789963:13179:1, last LSN: 789963:19503:1, number of dump devices: 1,
> device
> information: (FILE=1, TYPE=DISK:
> & #123;'F:\SQL_BAK\iGreentree\iGreentree_d
b_200605220130.BAK'}).
> 2006-05-22 12:02:03.96 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789814:10524:1, last
> LSN: 789966:19764:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: & #123;'F:\SQL_BAK\iGreentree\iGreentree_t
log_200605221200.TRN'}
).
> 2006-05-22 20:11:08.85 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:11:08.85 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 1 appears to be hung. SPID
> 59, ECID 0, UMS Context 0x039D27E8.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C5A68.
> 2006-05-23 01:10:06.00 spid52 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-23 01:37:12.34 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 668013, first
> LSN:
> 790081:6357:1, last LSN: 790081:12597:1, number of dump devices: 1, device
> information: (FILE=1, TYPE=DISK:
> & #123;'F:\SQL_BAK\iGreentree\iGreentree_d
b_200605230130.BAK'}).
> 2006-05-23 12:01:04.71 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789966:19764:1, last
> LSN: 790091:2027:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: & #123;'F:\SQL_BAK\iGreentree\iGreentree_t
log_200605231200.TRN'}
).
> 2006-05-23 20:22:08.77 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:22:08.77 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 1 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D7AA8.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 2 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D6F60.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039DCD98.
>|||The scheduler referenced in the error message isn't SQL Agent - it's the
internal task scheduler UMS - User Mode Scheduler. This basically means
that a thread became stuck. Here are a few possible causes:
http://support.microsoft.com/search...ode=r&cat=False
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Scagnetti" <Scagnetti@.discussions.microsoft.com> wrote in message
news:6635ACAF-0BD1-48BE-BFD4-4D459F34786E@.microsoft.com...
> I've Googled myself silly on this and I'm not sure what I should do to fix
> it. Will SP4 do it? These errors happen every day at 8:00 PM yet there
> are
> no SQL Server Agent jobs running during that time. Any ideas?
> 2006-05-21 12:25:36.71 server Microsoft SQL Server 2000 - 8.00.760 (Intel
> X86)
> .
> .
> 2006-05-21 20:20:09.00 server Error: 17883, Severity: 1, State: 0
> 2006-05-21 20:20:09.00 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D0E28.
> 2006-05-22 01:10:07.29 spid63 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-22 01:36:50.81 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 667205, first
> LSN:
> 789963:13179:1, last LSN: 789963:19503:1, number of dump devices: 1,
> device
> information: (FILE=1, TYPE=DISK:
> & #123;'F:\SQL_BAK\iGreentree\iGreentree_d
b_200605220130.BAK'}).
> 2006-05-22 12:02:03.96 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789814:10524:1, last
> LSN: 789966:19764:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: & #123;'F:\SQL_BAK\iGreentree\iGreentree_t
log_200605221200.TRN'}
).
> 2006-05-22 20:11:08.85 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:11:08.85 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 1 appears to be hung. SPID
> 59, ECID 0, UMS Context 0x039D27E8.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C5A68.
> 2006-05-23 01:10:06.00 spid52 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-23 01:37:12.34 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 668013, first
> LSN:
> 790081:6357:1, last LSN: 790081:12597:1, number of dump devices: 1, device
> information: (FILE=1, TYPE=DISK:
> & #123;'F:\SQL_BAK\iGreentree\iGreentree_d
b_200605230130.BAK'}).
> 2006-05-23 12:01:04.71 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789966:19764:1, last
> LSN: 790091:2027:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: & #123;'F:\SQL_BAK\iGreentree\iGreentree_t
log_200605231200.TRN'}
).
> 2006-05-23 20:22:08.77 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:22:08.77 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 1 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D7AA8.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 2 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D6F60.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039DCD98.
>
Error: 17883 - The scheduler 0 appears to be hung...
Environment:
Clustered SQL Server 2K sp3a (single instance)
Product version: 8.00.760
Problem:
I end up in error 17883.
I am aware that the solution is to apply this patch:
821277 MS03-031:Security Patch for SQL Server 2000 Service
Pack 3.
I am also aware that after you install this cumulative
patch you will end up in this problem:
826161 FIX: You are prompted for password after you change
a standard SQL Server login.
After reading this one I found that there are 2
possibility to solve this problem, one if you have already
installed the security patch from MS03-031 and another one
if you do NOT have installed this patch.
Question:
Do I only need to apply this last one (is it also
cumulative?) or do I need to first apply MS03-031 and then
later the FIX 826161?
Please advise.
Kind regards.
You will need to follow the instructions in the section "If you have not
installed the security patch for Microsoft Security Bulletin
MS03-031,Q826161..." . This will include the
fix for the Enterprise Manager issue.
Additionally, this will not fix the cause of the 17883. This will only
provide additional diagnostic information for Microsoft Support should a
17883 occur which was not available in previous builds. If you believe you
are seeing performance issues at the time the 17883's are being recorded, I
urge you to open a case with Microsoft Support for assistance.
Regards,
Farooq Mahmud [MS SQL Support]
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
|||Thank you so much for your answer.
I still don't understand why, when you read MS KB article
810885,under resolution, you find the reference for MS03-
031 Cumulative Security Patch for SQL Server.
What does this cumulative patch solve?
I was sure that it will solve many problems, most of them
security related, but also the 17883 problem.
If this cumulative patch does not solve the 17883 problem
so I don't need to install any patch, right?
Am I wrong?
Please advise.
Clustered SQL Server 2K sp3a (single instance)
Product version: 8.00.760
Problem:
I end up in error 17883.
I am aware that the solution is to apply this patch:
821277 MS03-031:Security Patch for SQL Server 2000 Service
Pack 3.
I am also aware that after you install this cumulative
patch you will end up in this problem:
826161 FIX: You are prompted for password after you change
a standard SQL Server login.
After reading this one I found that there are 2
possibility to solve this problem, one if you have already
installed the security patch from MS03-031 and another one
if you do NOT have installed this patch.
Question:
Do I only need to apply this last one (is it also
cumulative?) or do I need to first apply MS03-031 and then
later the FIX 826161?
Please advise.
Kind regards.
You will need to follow the instructions in the section "If you have not
installed the security patch for Microsoft Security Bulletin
MS03-031,Q826161..." . This will include the
fix for the Enterprise Manager issue.
Additionally, this will not fix the cause of the 17883. This will only
provide additional diagnostic information for Microsoft Support should a
17883 occur which was not available in previous builds. If you believe you
are seeing performance issues at the time the 17883's are being recorded, I
urge you to open a case with Microsoft Support for assistance.
Regards,
Farooq Mahmud [MS SQL Support]
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
|||Thank you so much for your answer.
I still don't understand why, when you read MS KB article
810885,under resolution, you find the reference for MS03-
031 Cumulative Security Patch for SQL Server.
What does this cumulative patch solve?
I was sure that it will solve many problems, most of them
security related, but also the 17883 problem.
If this cumulative patch does not solve the 17883 problem
so I don't need to install any patch, right?
Am I wrong?
Please advise.
Subscribe to:
Posts (Atom)