EXCEPTION_ACCESS_VIOLATION Error

Hi all,
One of our clients is using SQL7/SP4 and their database is working correctly
with our application and not producing any errors. To help locate an
intermittent problem with our application I did a backup of the database and
returned it to our office.
The backup went fine and was verified and the restore to our SQL/SP4 Server
in the office went without any errors.
However if you try and look at any Tables, SP's or Views in EM you receive
the following error msg:
SqlDumpExceptionHandler: Process 9 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
The error log shows:
****************************************
************************************
***
*
* BEGIN STACK DUMP:
* 03/24/04 08:02:31 spid 9
*
* Exception Address = 0051ACE7 (CObjectScan::LParentid + 10)
* Exception Code = c0000005 E
* Access Violation occurred reading address 00000000
* Input Buffer 1428 bytes -
* s e l e c t s 1 = o . n a m e , s 2 = u s e r _ n a m e ( o
* . u i d ) , o . c r d a t e , o . i d , N ' S y s t e m O b j ' =
* ( c a s e w h e n ( O B J E C T P R O P E R T Y ( o . i d , N ' I
* s M S S h i p p e d ' ) = 1 ) t h e n 1 e l s e O B J E C T P R
* O P E R T Y ( o . i d , N ' I s S y s t e m T a b l e ' ) e n d ) ,
* o . c a t e g o r y , 0 , O b j e c t P r o p e r t
* y ( o . i d , N ' T a b l e H a s A c t i v e F u l l t e x t I n d e
* x ' ) , O b j e c t P r o p e r t y ( o . i d , N ' T a b l e F u l
* l t e x t C a t a l o g I d ' ) , N ' F a k e T a b l e ' = ( c a
* s e w h e n ( O B J E C T P R O P E R T Y ( o . i d , N ' t a b l
* e i s f a k e ' ) = 1 ) t h e n 1 e l s e 0 e n d ) ,
* ( c a s e w h e n ( O B J E C T P R O P E R T Y ( o . i d ,
* N ' I s Q u o t e d I d e n t O n ' ) = 1 ) t h e n 1 e l s e
* 0 e n d ) , ( c a s e w h e n ( O B J E C T P R O P E R T Y ( o
* . i d , N ' I s A n s i N u l l s O n ' ) = 1 ) t h e n 1 e l s
* e 0 e n d ) f r o m d b o . s y s o b j e c t s
* o , d b o . s y s i n d e x e s i w h e r e O B J E C T P R O P
* E R T Y ( o . i d , N ' I s T a b l e ' ) = 1 a n d i . i d
* = o . i d a n d i . i n d i d < 2 a n d o . n a m e n o
* t l i k e N ' # % ' o r d e r b y s 1 , s 2
*
*
* MODULE BASE END SIZE
* sqlservr 00400000 008d2fff 004d3000
* ntdll 77f60000 77fbefff 0005f000
* KERNEL32 77f00000 77f5efff 0005f000
* ADVAPI32 77dc0000 77dfefff 0003f000
* USER32 77e70000 77ec1fff 00052000
* GDI32 77ed0000 77efbfff 0002c000
* RPCRT4 77e10000 77e66fff 00057000
* ole32 77b20000 77bd0fff 000b1000
* OLEAUT32 65340000 653dafff 0009b000
* VERSION 77a90000 77a9afff 0000b000
* SHELL32 77c40000 77d7afff 0013b000
* COMCTL32 71710000 71793fff 00084000
* LZ32 779c0000 779c7fff 00008000
* opends60 41060000 41085fff 00026000
* ums 41090000 4109cfff 0000d000
* MSVCRT 78000000 78043fff 00044000
* sqlsort 04000000 0408efff 0008f000
* MSVCIRT 780a0000 780b1fff 00012000
* sqlevn70 410a0000 410a6fff 00007000
* rpcltc1 77bf0000 77bf6fff 00007000
* COMNEVNT 410b0000 410fefff 0004f000
* ODBC32 012b0000 012e4fff 00035000
* comdlg32 77d80000 77db1fff 00032000
* SQLWOA 41100000 4110bfff 0000c000
* odbcint 013f0000 01405fff 00016000
* NDDEAPI 75a80000 75a87fff 00008000
* WINSPOOL 77c00000 77c17fff 00018000
* SQLTrace 41130000 4117dfff 0004e000
* NETAPI32 4ca00000 4ca40fff 00041000
* NETRAP 77840000 77848fff 00009000
* SAMLIB 777e0000 777ecfff 0000d000
* WSOCK32 776d0000 776d7fff 00008000
* WS2_32 776b0000 776c3fff 00014000
* WS2HELP 776a0000 776a6fff 00007000
* WLDAP32 77950000 77978fff 00029000
* SSNMPN70 41190000 41195fff 00006000
* SSMSSO70 411a0000 411aafff 0000b000
* SSMSRP70 411b0000 411b7fff 00008000
* ENUdtc 69140000 69156fff 00017000
* XOLEHLP 69360000 69368fff 00009000
* MTXCLU 69790000 6979cfff 0000d000
* ADME 69120000 69132fff 00013000
* DTCUtil 69000000 69009fff 0000a000
* DTCTRACE 68ff0000 68ff6fff 00007000
* CLUSAPI 7f230000 7f23cfff 0000d000
* RESUTILS 7f250000 7f259fff 0000a000
* msafd 77660000 7766efff 0000f000
* wshtcpip 77690000 77698fff 00009000
* rpclts1 77e00000 77e06fff 00007000
* RpcLtScm 74fa0000 74faafff 0000b000
* MSWSOCK 77670000 77686fff 00017000
* rnr20 74ff0000 74ffdfff 0000e000
* RpcLtCcm 74fc0000 74fcefff 0000f000
* security 76e70000 76e81fff 00012000
* msapsspc 24900000 24910fff 00011000
* MSVCRT40 779d0000 779e4fff 00015000
* schannel 77400000 7741dfff 0001e000
* MSOSS 5e380000 5e3a4fff 00025000
* CRYPT32 5cf00000 5cf74fff 00075000
* MSASN1 24930000 2493ffff 00010000
* digest 24940000 2494ffff 00010000
* msnsspc 716d0000 716eefff 0001f000
* SQLRGSTR 411c0000 411c4fff 00005000
* sqlmap70 415b0000 415c5fff 00016000
* ntwdblib 73320000 73363fff 00044000
* MAPI32 6fa90000 6fb6afff 000db000
* MPR 77720000 77730fff 00011000
* contab32 6eaf0000 6eb08fff 00019000
* EMSABP32 626f0000 62713fff 00024000
* EMSUI32 625d0000 625f0fff 00021000
* WMSUI32 6def0000 6e017fff 00128000
* GAPI32 6fbf0000 6fc07fff 00018000
* xpsqlbot 41820000 41825fff 00006000
* sqlboot 417f0000 417f7fff 00008000
* xpstar 411d0000 41200fff 00031000
* SQLWID 412f0000 412f5fff 00006000
* SQLSVC 415e0000 415f8fff 00019000
* odbcbcp 25510000 25516fff 00007000
* SQLRESLD 41320000 41325fff 00006000
* W95SCM 41210000 41217fff 00008000
* SQLSVC 42480000 42485fff 00006000
* sqlimage 72a00000 72a2cfff 0002d000
*
* Edi: 256CF9D4: 00100009 005f92d5 256cfa44 00000000 0078eecb 256cfb50
* Esi: 256CF944: 00000000 00000000 00000000 00000000 0000002a 1520fbc8
* Eax: 00000000:
* Ebx: 00000007:
* Ecx: 00000009:
* Edx: 0000002C:
* Eip: 0051ACE7: abe85030 c0830081 e128a150 57fc458d 5651ec8b 55c3008b
* Ebp: 256CF9E0: 00000007 1548d1f8 0bdc9e2e 00100009 005f92d5 256cfa44
* SegCs: 0000001B:
* EFlags: 00010246: 0020006d 00610072 0067006f 00720050 005c003a 0043003b
* Esp: 256CF8EC: 00000000 00000008 005f9290 256cfa10 256cfa10 005ecc26
* SegSs: 00000023:
****************************************
************************************
***
The Short Stack Dump is empty.
I've tried restoring the DB to several SQL 7 Servers but with the same
result. I have taken other backups from the clients SQL 7 Server but all
the restores to our Servers give the same result. Restores to our clients
PC work correctly.
DBCC CheckDB at our office produces the following:
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:325) with latch type SH. sysobjects failed.
Server: Msg 8944, Level 16, State 1, Line 1
Table Corrupt: Object ID 1, index ID 0, page (1:325), row 62. Test (nVarCols
&& (hdr->r_tagA & VARIABLE_COLUMNS)) failed. Values are 0 and 32.
DBCC results for 'JagTrain'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'sysobjects' (object ID 1).
CHECKDB found 0 allocation errors and 1 consistency errors in database
'JagTrain'.
repair_allow_data_loss is the minimum repair level for the errors found by
DBCC CHECKDB (JagTrain ).
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
The commands:
exec sp_dboption 'JagTrain', 'single user', 'on'
GO
DBCC CHECKDB ('JagTrain', repair_allow_data_loss)WITH NO_INFOMSGS
Produces:
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
The database is now single user.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:325) with latch type SH. sysobjects failed.
Server: Msg 8944, Level 16, State 1, Line 1
Table Corrupt: Object ID 1, index ID 0, page (1:325), row 62. Test (nVarCols
&& (hdr->r_tagA & VARIABLE_COLUMNS)) failed. Values are 0 and 32.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'sysobjects' (object ID 1).
CHECKDB found 0 allocation errors and 1 consistency errors in database
'JagTrain'.
repair_allow_data_loss is the minimum repair level for the errors found by
DBCC CHECKDB (JagTrain repair_allow_data_loss).
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
If anyone has any ideas as to what might be causing this problem it would be
appreciated.
Thanks in advance,
Greg
--
greghines@.bigfoot.com.NOSPAM
Remove NOSPAM when replyingHi Greg,
Judging from your DBCC CHECKDB output, it appears that your sysobjects
table has been corrupted. Unfortunately this is probably one of the most
important system tables in the database as it contains information for each
object in the database. The Repair option most likely will not fix the
corruption.
If the backup exhibits same problem, that means the database has been
backed up with corruption. You may have to find other ways to regenerate
your data, or go to an even older backup.
Yih-Yoon Lee
On Wed, 24 Mar 2004 08:24:39 +1100, Greg Hines wrote:

> DBCC CheckDB at our office produces the following:
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:325) with latch type SH. sysobjects faile
d.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 1, index ID 0, page (1:325), row 62. Test (nVarCo
ls
> && (hdr->r_tagA & VARIABLE_COLUMNS)) failed. Values are 0 and 32.
> DBCC results for 'JagTrain'.
> CHECKDB found 0 allocation errors and 1 consistency errors in table
> 'sysobjects' (object ID 1).
> CHECKDB found 0 allocation errors and 1 consistency errors in database
> 'JagTrain'.
> repair_allow_data_loss is the minimum repair level for the errors found by
> DBCC CHECKDB (JagTrain ).
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> The commands:
> exec sp_dboption 'JagTrain', 'single user', 'on'
> GO
> DBCC CHECKDB ('JagTrain', repair_allow_data_loss)WITH NO_INFOMSGS
> Produces:
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> The database is now single user.
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:325) with latch type SH. sysobjects faile
d.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 1, index ID 0, page (1:325), row 62. Test (nVarCo
ls
> && (hdr->r_tagA & VARIABLE_COLUMNS)) failed. Values are 0 and 32.
> CHECKDB found 0 allocation errors and 1 consistency errors in table
> 'sysobjects' (object ID 1).
> CHECKDB found 0 allocation errors and 1 consistency errors in database
> 'JagTrain'.
> repair_allow_data_loss is the minimum repair level for the errors found by
> DBCC CHECKDB (JagTrain repair_allow_data_loss).
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
>
> If anyone has any ideas as to what might be causing this problem it would
be
> appreciated.
> Thanks in advance,
> Greg|||Hi Yih-Yoon Lee,
You maybe correct but DBCC CheckDB on our clients computer (ie where the
backup came from) comes up clean. And I've done the backup and restore
several times all with the same result. Plus all backups pass verification.
Any other information you can provide would be appreciated.
Greg
--
greghines@.bigfoot.com.NOSPAM
Remove NOSPAM when replying
"Yih-Yoon Lee" <lee@.yihyoon.com> wrote in message
news:1avgpv091zsvt.1gwr1xbhp2fh7.dlg@.40tude.net...
> Hi Greg,
> Judging from your DBCC CHECKDB output, it appears that your sysobjects
> table has been corrupted. Unfortunately this is probably one of the most
> important system tables in the database as it contains information for
each
> object in the database. The Repair option most likely will not fix the
> corruption.
> If the backup exhibits same problem, that means the database has been
> backed up with corruption. You may have to find other ways to regenerate
> your data, or go to an even older backup.
> Yih-Yoon Lee
> On Wed, 24 Mar 2004 08:24:39 +1100, Greg Hines wrote:
>
failed.
(nVarCols
by
failed.
(nVarCols
by
would be