Server Error / Error: 17883, Severity: 1, State: 0

Question

Post reply

Server Error / Error: 17883, Severity: 1, State: 0

EsterCool

Old Hand

Points: 373
More actions
May 2, 2005 at 2:30 am

#88858

Occasionally we get an error on a Server with SQL Server:
We get an msgbox error with a message similar to: (..) DLL Error, unable to .. OLEDB Provider (...). Sorry we don't have now the exact error, we post it next time.
In the registry of errors of SQL Server the following entrances are generated:
- Error: 17883, Severity: 1, State: 0
- The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x00FA2CC0.
- Stack Signature for the dump is 0x00000000
And then the following ones:
- Error: 17883, Severity: 1, State: 0
- The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x00FA2CC0.
- Error: 17883, Severity: 1, State: 0
- The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x00FA2CC0.
(...)
Until we did not accept the msgbox of error in the server, the SQL server does not work and the connections are hung.
We do not know that to do. We did not find anything of information on the matter.
How we can contact with Microsoft and what we would have to send to them so that they helped us?
Version of SQL:
Microsoft SQL Server 2000 - 8,00,818 (Intel X86) Window Version: Servant NT4 Enterprise SP6. Thanks for your time...
Versión de SQL:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
Versión Window:
Servidor NT4 Enterprise SP6.
Thanks for your time

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Frank Kalis SSC Guru Points: 111183 More actions · Answer 1

First off, severity level 1 is not the most severe you can get. Actually it's an informational level.

For contacting MS, this might help: http://support.microsoft.com/gp/profsup

Though I think, depending on your country where you live, there might be a local MS support branch available for you.

--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

mcurnutt Ten Centuries Points: 1222 More actions · Answer 2

Two new fixes came out in the last couple of months that address this error message:

SQL Version .996.

FIX: You receive a 17883 error message and SQL Server 2000 may stop responding to other requests when you perform large in-memory sort operations

http://support.microsoft.com/default.aspx?scid=kb;en-us;891268

SQL version .988

FIX: A 17883 error is written to the SQL Server 2000 error log and the LogWriter component does not yield correctly

http://support.microsoft.com/default.aspx?scid=kb;en-us;890637

Mindy

Frank Kalis SSC Guru Points: 111183 More actions · Answer 3

Mindy,

this is a very nice homepage you have. I like especially this gallery:

http://www.stampola.com/asp/gallerytype.asp?gallerytype=14

--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

mcurnutt Ten Centuries Points: 1222 More actions · Answer 4

Frank,

Thanks so much. The baby gallery huh? The site used to be a lot larger before we started our own family. I had to scale things back severely and all that really remains of the former glory of the site is the gallery. Glad you enjoyed.

Mindy

EsterCool Old Hand Points: 373 More actions · Answer 5

You may think I'm stupid but I'm not able to understand how to install these upgrades...

There is not a package to install over my SQL Version?

Thanks for your time.

mcurnutt Ten Centuries Points: 1222 More actions · Answer 6

I believe you need to request the upgrades from your Microsoft TAM. They are noted in the KB, but not publicly available. That is what I understand.

Mindy