|
Home > Archive > microsoft.public.sqlserver.server > November 2002 > SqlServer2000 Terminates with AV errors 17066, 18052, 17055, etc.
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SqlServer2000 Terminates with AV errors 17066, 18052, 17055, etc.
|
|
| Padraic Lavin 2002-11-20, 4:23 pm |
| I'm having a hard time with Sql Server 2000 at the moment after over a year
of smooth operation. I hope someone here can help as I'm completely lost.
Sql Server 2000 SP2 - 8.00.534
Win2k
About 1400 databases.
After a while, sometimes 24 hours sometimes 2 hours sql server terminates
with errors like the following (in order of occurrence).
17066 :
SQL Server Assertion: File: < S:\sql\ntdbms\storeng\drs\incl
ude\record.inl>,
line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
18052 :
Error: 3624, Severity: 20, State: 1.
17066 :
SQL Server Assertion: File: < S:\sql\ntdbms\storeng\drs\incl
ude\record.inl>,
line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
I've searched the web, newsgroups and looked here -
http://support.microsoft.com/common...ft%20SQL%20Serv
er%202000%20Post-SP2%20Hotfixes&LL=&Sz=kbSQLServ2000presp3fix&Fr=&DU=&SD=GN&
LN=EN-US&CND=1&VR=&CAT=&VRL=&SG=&MaxResults=200
but cannot find a fix.
I can provide the latest *.dmp file if you need it.
Anyone have any ideas?
-----
Padraic
| |
| James Hunter Ross 2002-11-20, 4:23 pm |
| I hope somebody more knowledgeable replies, but I'll take a stab at it.
Have you run DBCC CHECKDB cleanly? Try that and see if the database
structure on all your databases is OK.
Also, check the Event Log, just in case there might be clues there.
James
| |
| Padraic Lavin 2002-11-20, 5:23 pm |
| "James Hunter Ross" <jhr@delta.net> wrote in message
news:esUv2HOkCHA.716@tkmsftngp11...
> I hope somebody more knowledgeable replies, but I'll take a stab at it.
> Have you run DBCC CHECKDB cleanly? Try that and see if the database
> structure on all your databases is OK.
>
> Also, check the Event Log, just in case there might be clues there.
>
> James
Thanks for replying,
The errors I quoted are from the event log.
I ran DBCC CHECKDB on master only, how to run on all 1400 via script?
--
Padraic.
| |
| Richard G 2002-11-21, 1:23 am |
| The following code will checkdb on all databases. Run it with the print
statement to see if it's what you want. You can pipe the output to a text
file.
Whew, 1400 databases? Hope they're not too big, or this script may run a
while. 
declare @Sql varchar(1000)
, @DbName varchar(100)
declare DbName cursor fast_forward for
select name from master.dbo.sysdatabases order by name
open DbName
fetch DbName into @DbName
while @@fetch_status = 0
begin
set @Sql = 'dbcc checkdb(''' + @DbName + ''') with no_infomsgs'
print @Sql
--exec (@Sql)
fetch DbName into @DbName
end
deallocate DbName
"Padraic Lavin" <win2k@utvinternet.com> wrote in message
news:OzISXPOkCHA.1488@tkmsftngp11...
"James Hunter Ross" <jhr@delta.net> wrote in message
news:esUv2HOkCHA.716@tkmsftngp11...
> I hope somebody more knowledgeable replies, but I'll take a stab at it.
> Have you run DBCC CHECKDB cleanly? Try that and see if the database
> structure on all your databases is OK.
>
> Also, check the Event Log, just in case there might be clues there.
>
> James
Thanks for replying,
The errors I quoted are from the event log.
I ran DBCC CHECKDB on master only, how to run on all 1400 via script?
--
Padraic.
|
|
|
|
|