Process 52 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION
-
I'm running a stored procedure, and when it finishes I get the fatal exception error in the subject line. I have traced through the stored procedure, and it seems to complete normally, so it looks like this error is generated after the stored procedure completes, but before control returns to the calling process. The error happens when the stored procedure is called from both DTS and Query Analyzer.
Does anyone have any idea what is going on?
Thanks.
-
This error is access violation, can you post code ?
which the version of sql server?
which the service pack?
without these information it is difficult to help with the problem...
-
Generally there is very little we can suggest to solve these issues, unless it is a known bug with a Knowledge Base article related to it. I would recommend you open a case with Microsoft Support.
-
I ran into the same kind of error. It turned out that the query I sent it was just too much for poor SQL Server 2000 SP4. I called Microsoft to report the bug after I had already worked around the problem by flattening out one of the set-based operations with a cursor. Can you believe that they wanted to charge me $275.00 to report an obvious bug in their software? Although they assured me that they would refund my credit card if it were determined to be a bug (And it's clear that it's a bug because c0000005 means that the SQL Server process was trying to read or write memory that it didn't own.), I finally talked them into accepting the trace, dumps, and database without charging my credit card, but they told me that because I didn't pay, they couldn't let me know when they had a fix. (Pardon me for venting.)
The point I'm trying to make is that they have builds that are not fully regression tested that fix several access-violation problems, so you might want to give Microsoft a call.
Brian
MCDBA, MCSE+I, Master CNE -
As asked above, we need to know what version / service pack level you are on. You might also consider running a trace on all of the Errors & Warnings group, and SQL:BatchStarting, SP:StmtStarting and add in the Severity column (among the normals like TextData, SPID, etc). Try to catch the F.E. occurring, then trace the SPID of the failing execute back to the very last SP:StmtStarting / Batch and see what was going on. Are you able to share any of the details of this stored proc?
If you are unable to track it yourself, here's a couple tips for getting data ready for PSS if you decide to call them. In Query Analyzer run "DBCC DUMPTRIGGER('set', <error number being generated, like "1105" or whatever>
. Then generate the error, and clean this up with DUMPTRIGGER('clear', <error number>. Then go out and check your ERRORLOG file in the LOG folder.They'll probably want a stack dump too, which can be done with SQLDumper.exe in the ..\80\com\ folder but you will need to know the process ID of SQL Server. You can get this from task manager, but PSS should be able to walk you through this if need be.
-
It turned out to be a table that got corrupted after a new column was added to it.
-
I have the same error while running a column conversion process. Managed to remove the error by working around the conversion.
ie. initialy I had the following code which failed with the error Process 51 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION
ALTER TABLE doctor ALTER column doct_surname_uc t_name
I changed this to:
------------------
EXEC sp_rename 'doctor.doct_surname_uc', 'doct_surn_old', 'COLUMN'
GO
ALTER TABLE doctor ADD doct_surname_uc t_name
GO
UPDATE doctor SET doct_surname_uc = SUBSTRING('doct_surn_old', 1, 255)
ALTER TABLE doctor DROP COLUMN doct_surn_old
GO
and the error message stopped occuring. The problem turned out to be my attapmt to convert a Varchar(255) to a text data type.
-
Thank you but, if you notice the date, I solved this problem THREE AND-A-HALF YEARS AGO.
Have a nice day.
-
haha haha haha
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply