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.