Showing posts with label period. Show all posts
Showing posts with label period. Show all posts

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

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

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

Error 1222 Lock Request time out period exceed

Hi, I'm getting this error when I tried to click on the Current Activity in
the Enterprise Manager. This is a SQL2000 running on Windows2000. Does
anyone know what causes this and how to fix it? I also get this error
sometimes when I run a crystal report in my C# application.
Thanks,
AlphaA transaction is being blocked to acquire a lock because another transaction
already locked the resource.
See "Customizing the Lock Time-out" in BOL.
AMB
"Alpha" wrote:
> Hi, I'm getting this error when I tried to click on the Current Activity in
> the Enterprise Manager. This is a SQL2000 running on Windows2000. Does
> anyone know what causes this and how to fix it? I also get this error
> sometimes when I run a crystal report in my C# application.
> Thanks,
> Alpha|||Do not use the GUI. Instead, get used to sp_who, sp_who2 or sp_who1 in Query
Analyzer.
"Alpha" <Alpha@.discussions.microsoft.com> wrote in message
news:16FC85B9-57C8-4906-AC47-3B9E826D9A79@.microsoft.com...
> Hi, I'm getting this error when I tried to click on the Current Activity
> in
> the Enterprise Manager. This is a SQL2000 running on Windows2000. Does
> anyone know what causes this and how to fix it? I also get this error
> sometimes when I run a crystal report in my C# application.
> Thanks,
> Alpha|||Thank you. That was very helpful.
"Alejandro Mesa" wrote:
> A transaction is being blocked to acquire a lock because another transaction
> already locked the resource.
> See "Customizing the Lock Time-out" in BOL.
>
> AMB
> "Alpha" wrote:
> > Hi, I'm getting this error when I tried to click on the Current Activity in
> > the Enterprise Manager. This is a SQL2000 running on Windows2000. Does
> > anyone know what causes this and how to fix it? I also get this error
> > sometimes when I run a crystal report in my C# application.
> >
> > Thanks,
> > Alpha

Error 1222 Lock request

I received the Error 1222 lock request time out period
when trying to open SQL Server Current Activity folder
under the Management folder to display locks.
This was caused by several locks.
This made it very difficult to resolve the locks without
the GUI.
What would cause the SQL Server GUI to be unable to
display the locks?
Thank You,
Mickey Autry
mautry@.ev1.netThat's know to happen when you have a lot of locks. You can
use Query Analyzer to execute sql statments and system
stored procedures to view the same info you look at in the
Current Activity part of Enterprise Manager. Check books
online for more information on sp_lock, sp_who, sp_who2 and
the sysprocesses table.
-Sue
On Tue, 23 Sep 2003 15:41:17 -0700, "Mickey"
<mautry@.ev1.net> wrote:
>I received the Error 1222 lock request time out period
>when trying to open SQL Server Current Activity folder
>under the Management folder to display locks.
>This was caused by several locks.
>This made it very difficult to resolve the locks without
>the GUI.
>What would cause the SQL Server GUI to be unable to
>display the locks?
>Thank You,
>Mickey Autry
>mautry@.ev1.net
>

Wednesday, March 7, 2012

Error : Timeout expired. The timeout period elapsed...

Hi,

Iget this error from our web application every once in a while. " Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding". I emailmyself when an error occurs, and once every 2-3 days I get this timeouterror emails, like 5-10 emails in a span of few minutes. Then it goesaway. I have set the command timeout for 60 secs.

Itdoesn't happen from the same stored procedure, actually I have seen ittimeout from really simple 1 or 2 line stored procedures, which shouldn't normally take 1 sec. Its likesql server just shuts down for few minutes. We have somebackups and maintenance jobs scheduled, but they run only aftermidnight. I have checked theapplication event viewer, there are no warnings orerror messages forMSSQLSERVER.

Canany one tell me how to check whats going on during that short timespanwhen timeout error occurs, and what causes it? I don't want to run sqlprofiler continuously for 2-3 days, I am afraid it will slow down theserver more.

Thanks.

It could be locking|||Sorry, that was a bit laconic. I meant it could be table (or page) locking. I don't think you can do much without running the profiler or at least a good error logging so that you would isolate the scenario. In the mean time you could be looking for concurent access to those records|||

websolutions:

Sorry, that was a bit laconic. I meant it could be table (or page) locking. I don't think you can do much without running the profiler or at least a good error logging so that you would isolate the scenario. In the mean time you could be looking for concurent access to those records

I agree read the performance tuning tips in the link below and run SQL Server profiler to find out what is causing your error. Hope this helps.

http://msdn.microsoft.com/msdnmag/issues/06/07/WebAppFollies/default.aspx