Monday, March 26, 2012

Error 17883

The SQL Server is 32 bit - 2000 and I have applied SP3a with hot patch 81549
5. So it is up to version 818 but I am still getting errors sporadically wh
ich are the Process 53:0 (19f8) UMS Context 0x0D2123E8 appears to be non-yie
lding on Scheduler 0. They
are server errors and appear to be happening in the early morning and trying
to search the microsoft web site, indicates that these should be corrected.
Are there additional hot patches to correct this problem? Thanks.Cynthia,
Here is an article which seems to outline your problem.
http://support.microsoft.com/defaul...kb;en-us;810885
The circumstances for this are fairly specific and there is no hot-patch
according to the article. Do you fit the profile of this article?
Russell Fields
"Cynthia" <anonymous@.discussions.microsoft.com> wrote in message
news:803D34D5-99BD-408F-B767-A29FE8FC112C@.microsoft.com...
> The SQL Server is 32 bit - 2000 and I have applied SP3a with hot patch
815495. So it is up to version 818 but I am still getting errors
sporadically which are the Process 53:0 (19f8) UMS Context 0x0D2123E8
appears to be non-yielding on Scheduler 0. They are server errors and
appear to be happening in the early morning and trying to search the
microsoft web site, indicates that these should be corrected.
> Are there additional hot patches to correct this problem? Thanks.
>|||Hi,
Thanks for the reply. Yes I do have autogrow on all the servers and this o
ne that is giving the error. But there is nothing exceptional about this se
rver compared to the other servers. No high speed disk system or anything u
nusual. This is the only s
erver that has this error and the error 17883 and Q815056 seems to identify
what the problem is but the hotfix 815495 didn't resolve the problem. I am
wondering if the error is informational only'|||Cynthia,
Although this error is "informational" in that there is no direct action
that you can take, I would view the message as the harbinger of problems
that may hurt you more in the future.
Inside 810885 there is a reference to:
http://support.microsoft.com/default.aspx?kbid=319892
That makes the following comment: If you cannot determine the root cause
immediately, consult the error log for problems and engage in extended
support efforts.
Sounds like Microsoft feels that you should be concerned.
Russell Fields
"cynthia" <anonymous@.discussions.microsoft.com> wrote in message
news:BA5E143F-A0EE-486B-97D7-756D71893984@.microsoft.com...
> Hi,
> Thanks for the reply. Yes I do have autogrow on all the servers and this
one that is giving the error. But there is nothing exceptional about this
server compared to the other servers. No high speed disk system or anything
unusual. This is the only server that has this error and the error 17883
and Q815056 seems to identify what the problem is but the hotfix 815495
didn't resolve the problem. I am wondering if the error is informational
only'|||In the absence of a specific bug, this is likely going to be best-handled an
d troubleshot by Microsoft support. I'd recommend that you engage them as s
oon as possible.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine.
"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message news:exv7
IzyTEHA.2464@.TK2MSFTNGP10.phx.gbl...
Cynthia,
Although this error is "informational" in that there is no direct action
that you can take, I would view the message as the harbinger of problems
that may hurt you more in the future.
Inside 810885 there is a reference to:
http://support.microsoft.com/default.aspx?kbid=319892
That makes the following comment: If you cannot determine the root cause
immediately, consult the error log for problems and engage in extended
support efforts.
Sounds like Microsoft feels that you should be concerned.
Russell Fields
"cynthia" <anonymous@.discussions.microsoft.com> wrote in message
news:BA5E143F-A0EE-486B-97D7-756D71893984@.microsoft.com...
> Hi,
> Thanks for the reply. Yes I do have autogrow on all the servers and this
one that is giving the error. But there is nothing exceptional about this
server compared to the other servers. No high speed disk system or anything
unusual. This is the only server that has this error and the error 17883
and Q815056 seems to identify what the problem is but the hotfix 815495
didn't resolve the problem. I am wondering if the error is informational
only'|||Thanks Ryan and Russell. You're both right and I have run out of troubleshoo
ting tools for this.sql

No comments:

Post a Comment