Error: 5243, Severity: 22, State: 1
-
Hi,
We got an error in sql server 2005 EE x64 on windows 2003 EE sp2 x64.
Error: 5243, Severity: 22, State: 1. For this I found a hot fix at http://support.microsoft.com/kb/916086. But is this hot fix is for sql server having SP1? or can I apply over SP2?
plz advice me
-
Mani,
This is included in SP1 - http://support.microsoft.com/kb/913090
Sounds like this isn't the fix you were looking for. Sorry.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
-
Please post the full error message, the exact version of SQL that you are on and what seems to cause the error.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverabilityWe walk in the dark places no others will enter
We stand on the bridge and no one may pass -
Hi,
The seql server version:
Microsoft SQL Server 2005 - 9.00.3042.00 (X64)
Feb 10 2007 00:59:02
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
We got a dump file in error log, this 2nd time we got this dump file. We running sharepoint application on SQL Server.
error from eventviewer:
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:5243
Date:1/8/2009
Time:12:42:58 PM
User:ABC\spsearch
Computer:SQL
Description:
An inconsistency was detected during an internal operation. Please contact technical support. Reference number 8.
Thanks
-
I would suggest you call Microsoft's customer support for this one. We don't have the tools or knowledge to interpret a stack dump
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverabilityWe walk in the dark places no others will enter
We stand on the bridge and no one may pass -
thanks Gail,
In general, the reason for getting these kind of inconsistency in internal operation, tell me whether the following settings be the root cause:
1.SQL Server configuration: We have sql server 2005 EE x64 with SP2(No cumulative updates applied) on windows 2003 EE x64.
2.Memory settings are set to default. total memory 16GB
3.Page file size is default on C drive 2046MB
4.Lock pages in memory is not enabled
-
No way to tell.
I'm asking what appears to cause it, not the root cause. What are you generally doing when it happens?
Earlier advice still applies. The best people to contact for this are Microsoft's customer support people.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverabilityWe walk in the dark places no others will enter
We stand on the bridge and no one may pass -
-
Mani, sometime ago I asked you if you solved the problem. Could you please let me know. Thanks in advance.
-
I to just Ran into the very wierd error message. I sent of the dump and all related filed. The answers is move to SP3 + Cumulative update 5.
Start from the Guru's at Microsoft.
"We just analyzed the dump file and found this error.
Error: 5243, Severity: 22, State: 1.
An inconsistency was detected during an internal operation. Please contact technical support. Reference number 8.
This turned out to be a known issue. And the fix for this is to apply SQL Server SP3 + Cumulative update 5 (09.00.4230.00)."
-
After I installed SQL Server 2005 SP3, my problem was solved.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply