Scheduler is hung

I have a SQL 2000 with sp3 recently connected to the NetApps filer. For
the last two days the SQL Server keeps hanging. I can't even log on to
the machine, can't open enterprise manager. We have to bounce the
server. The errorlog indicates:
2004-03-01 17:07:20.38 server Error: 17883, Severity: 1, State: 0
2004-03-01 17:07:20.38 server The Scheduler 0 appears to be hung.
SPID 0, ECID 0, UMS Context 0x03469860.
2004-03-01 17:07:20.38 server Error: 17883, Severity: 1, State: 0
2004-03-01 17:07:20.38 server The Scheduler 1 appears to be hung.
SPID 59, ECID 0, UMS Context 0x0346BC48.
2004-03-01 17:08:20.39 server Error: 17883, Severity: 1, State: 0
2004
What does it mean by the scheduler? Is this where the Enterprise
manager runs all the scheduled jobs?
Have any ideas as to what's going on?
Thanks,
Raziq.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!It could be:
FIX: The Checkpoint Process Can Delay SQL Server Database Activity and Does
Not Yield Scheduler Correctly Causing Error: 17883 to Occur
http://support.microsoft.com/defaul...6&Product=sql2k
Known bug. Call PSS to confirm and get the hotfix.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Raziq Shekha" <raziq_shekha@.anadarko.com> wrote in message
news:uluFM4GAEHA.2432@.TK2MSFTNGP11.phx.gbl...
> I have a SQL 2000 with sp3 recently connected to the NetApps filer. For
> the last two days the SQL Server keeps hanging. I can't even log on to
> the machine, can't open enterprise manager. We have to bounce the
> server. The errorlog indicates:
>
> 2004-03-01 17:07:20.38 server Error: 17883, Severity: 1, State: 0
> 2004-03-01 17:07:20.38 server The Scheduler 0 appears to be hung.
> SPID 0, ECID 0, UMS Context 0x03469860.
> 2004-03-01 17:07:20.38 server Error: 17883, Severity: 1, State: 0
> 2004-03-01 17:07:20.38 server The Scheduler 1 appears to be hung.
> SPID 59, ECID 0, UMS Context 0x0346BC48.
> 2004-03-01 17:08:20.39 server Error: 17883, Severity: 1, State: 0
> 2004
> What does it mean by the scheduler? Is this where the Enterprise
> manager runs all the scheduled jobs?
> Have any ideas as to what's going on?
> Thanks,
> Raziq.
>
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!

Scheduler is hung

I have a SQL 2000 with sp3 recently connected to the NetApps filer. For
the last two days the SQL Server keeps hanging. I can't even log on to
the machine, can't open enterprise manager. We have to bounce the
server. The errorlog indicates:
2004-03-01 17:07:20.38 server Error: 17883, Severity: 1, State: 0
2004-03-01 17:07:20.38 server The Scheduler 0 appears to be hung.
SPID 0, ECID 0, UMS Context 0x03469860.
2004-03-01 17:07:20.38 server Error: 17883, Severity: 1, State: 0
2004-03-01 17:07:20.38 server The Scheduler 1 appears to be hung.
SPID 59, ECID 0, UMS Context 0x0346BC48.
2004-03-01 17:08:20.39 server Error: 17883, Severity: 1, State: 0
2004
What does it mean by the scheduler? Is this where the Enterprise
manager runs all the scheduled jobs?
Have any ideas as to what's going on?
Thanks,
Raziq.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!It could be:
FIX: The Checkpoint Process Can Delay SQL Server Database Activity and Does
Not Yield Scheduler Correctly Causing Error: 17883 to Occur
http://support.microsoft.com/default.aspx?scid=kb;en-us;815056&Product=sql2k
Known bug. Call PSS to confirm and get the hotfix.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Raziq Shekha" <raziq_shekha@.anadarko.com> wrote in message
news:uluFM4GAEHA.2432@.TK2MSFTNGP11.phx.gbl...
> I have a SQL 2000 with sp3 recently connected to the NetApps filer. For
> the last two days the SQL Server keeps hanging. I can't even log on to
> the machine, can't open enterprise manager. We have to bounce the
> server. The errorlog indicates:
>
> 2004-03-01 17:07:20.38 server Error: 17883, Severity: 1, State: 0
> 2004-03-01 17:07:20.38 server The Scheduler 0 appears to be hung.
> SPID 0, ECID 0, UMS Context 0x03469860.
> 2004-03-01 17:07:20.38 server Error: 17883, Severity: 1, State: 0
> 2004-03-01 17:07:20.38 server The Scheduler 1 appears to be hung.
> SPID 59, ECID 0, UMS Context 0x0346BC48.
> 2004-03-01 17:08:20.39 server Error: 17883, Severity: 1, State: 0
> 2004
> What does it mean by the scheduler? Is this where the Enterprise
> manager runs all the scheduled jobs?
> Have any ideas as to what's going on?
> Thanks,
> Raziq.
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!

Scheduler appears to be hung ...

SQL 7.0 SP4 logging this message :
The Scheduler 0 appears to be hung. PSS 0x652E50D0, EC 0x652E5280, UMS Context 0x2FB7E0A0

While SQL is logging these messages SQL is blocked
This is hapening 5-10 times in week.
In traced file I found that there is no same query from application that causes this blocking.
What this qould be ?!
Is it SQL engine or is it hardware on underlaying-server ?
What with combination beetwen SQL 7.0 and Windows Server 2000.
Or even is it problems with queries from application ?HTH

http://www.eweek.com/article2/0,3959,920568,00.asp|||Thanks for linksql

Scheduler appears to be hung

Hi,
I have a SQL Server 2000 SP3 running on Windows Server 2000. I have moved
two databases that are used continously about two months back to this server
and since then I have noticed this error coming up every 10 to 15 days.
The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x023339C0.
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233C8D8.
Error: 17883, Severity: 1, State: 0
The SQL Server just freezes and becomes non-responsive. The above error was
present for almost 8 minutes before it started responding. At one time, I
wasn't even able to do a Remote Desktop to the server to check why the server
is not responding and later on I found that it had the same error. Any
information regarding this will be highly appreciated.How many processors do you have running? This implies two, or at least one
with hyperthreading. You might try turning one off completely.
"sharman" wrote:
> Hi,
> I have a SQL Server 2000 SP3 running on Windows Server 2000. I have moved
> two databases that are used continously about two months back to this server
> and since then I have noticed this error coming up every 10 to 15 days.
> The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x023339C0.
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233C8D8.
> Error: 17883, Severity: 1, State: 0
> The SQL Server just freezes and becomes non-responsive. The above error was
> present for almost 8 minutes before it started responding. At one time, I
> wasn't even able to do a Remote Desktop to the server to check why the server
> is not responding and later on I found that it had the same error. Any
> information regarding this will be highly appreciated.|||For starters, just set SQL Server to use a single processor under the
instance properties. Also, you might want to apply SP4...
"sharman" wrote:
> Thanks for the information. It has 2 processors. How do I turn off
> hyperthreading and what are the implications of turning it off? Thanks.
> "James Luetkehoelter" wrote:
> > How many processors do you have running? This implies two, or at least one
> > with hyperthreading. You might try turning one off completely.
> >
> > "sharman" wrote:
> >
> > > Hi,
> > >
> > > I have a SQL Server 2000 SP3 running on Windows Server 2000. I have moved
> > > two databases that are used continously about two months back to this server
> > > and since then I have noticed this error coming up every 10 to 15 days.
> > >
> > > The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x023339C0.
> > > Error: 17883, Severity: 1, State: 0
> > > The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233C8D8.
> > > Error: 17883, Severity: 1, State: 0
> > >
> > > The SQL Server just freezes and becomes non-responsive. The above error was
> > > present for almost 8 minutes before it started responding. At one time, I
> > > wasn't even able to do a Remote Desktop to the server to check why the server
> > > is not responding and later on I found that it had the same error. Any
> > > information regarding this will be highly appreciated.|||Thanks for the information. It has 2 processors. How do I turn off
hyperthreading and what are the implications of turning it off? Thanks.
"James Luetkehoelter" wrote:
> How many processors do you have running? This implies two, or at least one
> with hyperthreading. You might try turning one off completely.
> "sharman" wrote:
> > Hi,
> >
> > I have a SQL Server 2000 SP3 running on Windows Server 2000. I have moved
> > two databases that are used continously about two months back to this server
> > and since then I have noticed this error coming up every 10 to 15 days.
> >
> > The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x023339C0.
> > Error: 17883, Severity: 1, State: 0
> > The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233C8D8.
> > Error: 17883, Severity: 1, State: 0
> >
> > The SQL Server just freezes and becomes non-responsive. The above error was
> > present for almost 8 minutes before it started responding. At one time, I
> > wasn't even able to do a Remote Desktop to the server to check why the server
> > is not responding and later on I found that it had the same error. Any
> > information regarding this will be highly appreciated.|||Hyperthreading can be diabled at the BIOS level. Most database applications
will experience an increase in performance with HT disabled. Test in your
environment.
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:0AEF20A0-A529-42BE-888B-C86BD6957F88@.microsoft.com...
> Thanks for the information. It has 2 processors. How do I turn off
> hyperthreading and what are the implications of turning it off? Thanks.
> "James Luetkehoelter" wrote:
>> How many processors do you have running? This implies two, or at least
>> one
>> with hyperthreading. You might try turning one off completely.
>> "sharman" wrote:
>> > Hi,
>> >
>> > I have a SQL Server 2000 SP3 running on Windows Server 2000. I have
>> > moved
>> > two databases that are used continously about two months back to this
>> > server
>> > and since then I have noticed this error coming up every 10 to 15 days.
>> >
>> > The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context
>> > 0x023339C0.
>> > Error: 17883, Severity: 1, State: 0
>> > The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context
>> > 0x0233C8D8.
>> > Error: 17883, Severity: 1, State: 0
>> >
>> > The SQL Server just freezes and becomes non-responsive. The above error
>> > was
>> > present for almost 8 minutes before it started responding. At one time,
>> > I
>> > wasn't even able to do a Remote Desktop to the server to check why the
>> > server
>> > is not responding and later on I found that it had the same error. Any
>> > information regarding this will be highly appreciated.|||Take a look at this excellent MS whitepaper:
http://www.microsoft.com/technet/prodtechnol/sql/2005/diagandcorrecterrs.mspx
Linchi
"sharman" wrote:
> Hi,
> I have a SQL Server 2000 SP3 running on Windows Server 2000. I have moved
> two databases that are used continously about two months back to this server
> and since then I have noticed this error coming up every 10 to 15 days.
> The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x023339C0.
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233C8D8.
> Error: 17883, Severity: 1, State: 0
> The SQL Server just freezes and becomes non-responsive. The above error was
> present for almost 8 minutes before it started responding. At one time, I
> wasn't even able to do a Remote Desktop to the server to check why the server
> is not responding and later on I found that it had the same error. Any
> information regarding this will be highly appreciated.