Error 17883 - Scheduler appears to be hung - related to linked server or HT??

We have been getting the following errors on our production environment
lately.
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x021B55C0
It appears that this error shows whenever we run a query with a linked
server. This error appears concurrently with an application popup on the
SQL server.
Application popup: SQL Server OLEDB provider support error : Unable to load
SQL Server OLEDB provider resource DLL. The application cannot continue.
We had this issue earlier with another machine which had parallelization
turned on. We turned it off because we believed the Hyperthreading w/
Parallelization was confusing this. Our old servers never had these issues
and were not HT enabled. The one box that was experiencing the problems
was/is behaving normally. However another box (same CPU, same no
parallelization settings) is having the issue when running a query using a
linked server to another SQL Server.
Our servers are SQL Server 2000 SP3, on Windows2000 SP4. With 2 3.2Ghz, HT
Enabled and 1.5GB RAM.
Thanks,
DanWe've seen the 17883 happen for a variety of reasons and symptoms.
It almost always comes down to disk i/o - contention issues. We had a
msde show this after being bombarded with query requests and with an 8
concurrent query limit.
Check to make sure that SQL Server is the ONLY one messing with
its' files. Make sure that on-access virus scan is off. As well as
backups or anything that might be going after the data and log files.
The last time this happened was because of virus scan and a policy set
that kept re-enabling on access scan.
Frankm
dan wrote:
> We have been getting the following errors on our production environment
> lately.
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x021B55C0
> It appears that this error shows whenever we run a query with a linked
> server. This error appears concurrently with an application popup on the
> SQL server.
> Application popup: SQL Server OLEDB provider support error : Unable to load
> SQL Server OLEDB provider resource DLL. The application cannot continue.
> We had this issue earlier with another machine which had parallelization
> turned on. We turned it off because we believed the Hyperthreading w/
> Parallelization was confusing this. Our old servers never had these issues
> and were not HT enabled. The one box that was experiencing the problems
> was/is behaving normally. However another box (same CPU, same no
> parallelization settings) is having the issue when running a query using a
> linked server to another SQL Server.
> Our servers are SQL Server 2000 SP3, on Windows2000 SP4. With 2 3.2Ghz, HT
> Enabled and 1.5GB RAM.
> Thanks,
> Dan
>|||Hey Dan,
Your problem is almost exactly what we are facing.
I did not know you had posted your question when I posted
mine ( I usually do a search before posting questions, but
I missed doing it this time). Check out 'my' thread on the
21st & 22nd with 17883 in the subject line.
Did you resolve your problem?
Did you go through any of the suggestions in my thread?
Hotfix to get a more precise indication?
Thanks very much.
Sam
>--Original Message--
>We have been getting the following errors on our
production environment
>lately.
>Error: 17883, Severity: 1, State: 0
>The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS
Context 0x021B55C0
>It appears that this error shows whenever we run a query
with a linked
>server. This error appears concurrently with an
application popup on the
>SQL server.
>Application popup: SQL Server OLEDB provider support
error : Unable to load
>SQL Server OLEDB provider resource DLL. The application
cannot continue.
>We had this issue earlier with another machine which had
parallelization
>turned on. We turned it off because we believed the
Hyperthreading w/
>Parallelization was confusing this. Our old servers
never had these issues
>and were not HT enabled. The one box that was
experiencing the problems
>was/is behaving normally. However another box (same CPU,
same no
>parallelization settings) is having the issue when
running a query using a
>linked server to another SQL Server.
>Our servers are SQL Server 2000 SP3, on Windows2000 SP4.
With 2 3.2Ghz, HT
>Enabled and 1.5GB RAM.
>Thanks,
>Dan
>
>.
>