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.
Cynthia,
Here is an article which seems to outline your problem.
http://support.microsoft.com/default...b;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 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 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 and troubleshot by Microsoft support. I'd recommend that you engage them as soon as possible.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine.
"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message news:exv7IzyTEHA.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 troubleshooting tools for this.
Showing posts with label applied. Show all posts
Showing posts with label applied. Show all posts
Tuesday, March 27, 2012
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
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
Error 17883
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.Cynthia,
Here is an article which seems to outline your problem.
http://support.microsoft.com/default.aspx?scid=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 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'|||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'|||This is a multi-part message in MIME format.
--=_NextPart_000_001C_01C44EFA.1D839650
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
In the absence of a specific bug, this is likely going to be =best-handled and troubleshot by Microsoft support. I'd recommend that =you engage them as soon as possible.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine.
"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message =news:exv7IzyTEHA.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=3D319892
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'
--=_NextPart_000_001C_01C44EFA.1D839650
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
In the absence of a specific bug, this is likely =going to be best-handled and troubleshot by Microsoft support. I'd recommend =that you engage them as soon as possible.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine.
"Russell Fields" wrote in message news:exv7IzyTEHA.2464=@.TK2MSFTNGP10.phx.gbl...Cynthia,Although this error is "informational" in that there is no direct =actionthat you can take, I would view the message as the harbinger of =problemsthat may hurt you more in the future.Inside 810885 there is a reference = to:http://support.microsoft.com/default.aspx?kbid=3D319892">http://s=upport.microsoft.com/default.aspx?kbid=3D319892That makes the following comment: If you cannot determine the root causeimmediately, consult the error log for problems and engage in = extendedsupport efforts.Sounds like Microsoft feels that =you should be concerned.Russell Fields"cynthia" wrote in messagenews:BA5=E143F-A0EE-486B-97D7-756D71893984@.microsoft.com...> Hi,>> Thanks for the reply. Yes I do have =autogrow on all the servers and thisone that is giving the error. But =there is nothing exceptional about thisserver compared to the other servers. No high speed disk system or anythingunusual. =This is the only server that has this error and the error 17883and Q815056 =seems to identify what the problem is but the hotfix 815495didn't =resolve the problem. I am wondering if the error is informationalonly'
--=_NextPart_000_001C_01C44EFA.1D839650--|||Thanks Ryan and Russell. You're both right and I have run out of troubleshooting tools for this.
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/default.aspx?scid=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 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'|||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'|||This is a multi-part message in MIME format.
--=_NextPart_000_001C_01C44EFA.1D839650
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
In the absence of a specific bug, this is likely going to be =best-handled and troubleshot by Microsoft support. I'd recommend that =you engage them as soon as possible.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine.
"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message =news:exv7IzyTEHA.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=3D319892
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'
--=_NextPart_000_001C_01C44EFA.1D839650
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
In the absence of a specific bug, this is likely =going to be best-handled and troubleshot by Microsoft support. I'd recommend =that you engage them as soon as possible.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine.
"Russell Fields"
--=_NextPart_000_001C_01C44EFA.1D839650--|||Thanks Ryan and Russell. You're both right and I have run out of troubleshooting tools for this.
Monday, March 19, 2012
Error 1222: Lock request time out period exceeded & SP4 ?
Hi,
After Spl Server 2000 w/ 16 G memory was applied SP4 and hotfix for AWE, it
got an error "Error 1222: Lock request time out period exceeded." while
running a stored procedure. It hung the process for much longer than normal.
It worked fine with SP3a. Is this error associated with SP4? Thanks.
Chuck
Check this KB http://support.microsoft.com/?kbid=888799
There are couple of fixes related to timing /performance issues
Thanks & Rate the Postings.
-Ravi-
"Chuck" wrote:
> Hi,
> After Spl Server 2000 w/ 16 G memory was applied SP4 and hotfix for AWE, it
> got an error "Error 1222: Lock request time out period exceeded." while
> running a stored procedure. It hung the process for much longer than normal.
> It worked fine with SP3a. Is this error associated with SP4? Thanks.
>
> Chuck
After Spl Server 2000 w/ 16 G memory was applied SP4 and hotfix for AWE, it
got an error "Error 1222: Lock request time out period exceeded." while
running a stored procedure. It hung the process for much longer than normal.
It worked fine with SP3a. Is this error associated with SP4? Thanks.
Chuck
Check this KB http://support.microsoft.com/?kbid=888799
There are couple of fixes related to timing /performance issues
Thanks & Rate the Postings.
-Ravi-
"Chuck" wrote:
> Hi,
> After Spl Server 2000 w/ 16 G memory was applied SP4 and hotfix for AWE, it
> got an error "Error 1222: Lock request time out period exceeded." while
> running a stored procedure. It hung the process for much longer than normal.
> It worked fine with SP3a. Is this error associated with SP4? Thanks.
>
> Chuck
Error 1222: Lock request time out period exceeded & SP4 ?
Hi,
After Spl Server 2000 w/ 16 G memory was applied SP4 and hotfix for AWE, it
got an error "Error 1222: Lock request time out period exceeded." while
running a stored procedure. It hung the process for much longer than normal.
It worked fine with SP3a. Is this error associated with SP4? Thanks.
ChuckCheck this KB http://support.microsoft.com/?kbid=888799
There are couple of fixes related to timing /performance issues
--
Thanks & Rate the Postings.
-Ravi-
"Chuck" wrote:
> Hi,
> After Spl Server 2000 w/ 16 G memory was applied SP4 and hotfix for AWE, it
> got an error "Error 1222: Lock request time out period exceeded." while
> running a stored procedure. It hung the process for much longer than normal.
> It worked fine with SP3a. Is this error associated with SP4? Thanks.
>
> Chuck
After Spl Server 2000 w/ 16 G memory was applied SP4 and hotfix for AWE, it
got an error "Error 1222: Lock request time out period exceeded." while
running a stored procedure. It hung the process for much longer than normal.
It worked fine with SP3a. Is this error associated with SP4? Thanks.
ChuckCheck this KB http://support.microsoft.com/?kbid=888799
There are couple of fixes related to timing /performance issues
--
Thanks & Rate the Postings.
-Ravi-
"Chuck" wrote:
> Hi,
> After Spl Server 2000 w/ 16 G memory was applied SP4 and hotfix for AWE, it
> got an error "Error 1222: Lock request time out period exceeded." while
> running a stored procedure. It hung the process for much longer than normal.
> It worked fine with SP3a. Is this error associated with SP4? Thanks.
>
> Chuck
Error 1222: Lock request time out period exceeded & SP4 ?
Hi,
After Spl Server 2000 w/ 16 G memory was applied SP4 and hotfix for AWE, it
got an error "Error 1222: Lock request time out period exceeded." while
running a stored procedure. It hung the process for much longer than normal.
It worked fine with SP3a. Is this error associated with SP4? Thanks.
ChuckCheck this KB http://support.microsoft.com/?kbid=888799
There are couple of fixes related to timing /performance issues
Thanks & Rate the Postings.
-Ravi-
"Chuck" wrote:
> Hi,
> After Spl Server 2000 w/ 16 G memory was applied SP4 and hotfix for AWE, i
t
> got an error "Error 1222: Lock request time out period exceeded." while
> running a stored procedure. It hung the process for much longer than norma
l.
> It worked fine with SP3a. Is this error associated with SP4? Thanks.
>
> Chuck
After Spl Server 2000 w/ 16 G memory was applied SP4 and hotfix for AWE, it
got an error "Error 1222: Lock request time out period exceeded." while
running a stored procedure. It hung the process for much longer than normal.
It worked fine with SP3a. Is this error associated with SP4? Thanks.
ChuckCheck this KB http://support.microsoft.com/?kbid=888799
There are couple of fixes related to timing /performance issues
Thanks & Rate the Postings.
-Ravi-
"Chuck" wrote:
> Hi,
> After Spl Server 2000 w/ 16 G memory was applied SP4 and hotfix for AWE, i
t
> got an error "Error 1222: Lock request time out period exceeded." while
> running a stored procedure. It hung the process for much longer than norma
l.
> It worked fine with SP3a. Is this error associated with SP4? Thanks.
>
> Chuck
Sunday, March 11, 2012
ERROR 1141 on mySQL creating a User on NT 4.0
Hi,
I just installed mySQL on MS NT 4.0 workstation and applied Service Pack
6a. When trying to add a new user using the Control Center I get an
info message that say that user was added but this is followed by an
error message that says:
There is no such grant defined for user 'username' on host 'hostname'
Does anyone know what is going on here?
Please respond in email.
Thanks,
Paul"Paul K. McKneely" <pkmckneely@.ev1.net> wrote in message
news:41499067.C056EB65@.ev1.net...
> Hi,
> I just installed mySQL on MS NT 4.0 workstation and applied Service Pack
> 6a. When trying to add a new user using the Control Center I get an
> info message that say that user was added but this is followed by an
> error message that says:
> There is no such grant defined for user 'username' on host 'hostname'
> Does anyone know what is going on here?
> Please respond in email.
> Thanks,
> Paul
This is an MSSQL (Microsoft SQL Server) newsgroup, so you will probably get
a better response in a MySQL forum.
Simon
Subscribe to:
Posts (Atom)