Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

EXCEPTION_ACCESS_VIOLATION error

Status
Not open for further replies.

freshegg

IS-IT--Management
Feb 22, 2005
37
GB
Error: 0, Severity: 19, State: 0
SqlDumpExceptionHandler: Process 75 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

I am getting this error in event viewer every time we run a certain action. when set nocount property is not explicitly turned on and off at the start and end of stored procedures there can be problems, have tried adding that into the Store Procedure but we don't get the desired response returned from the execute!
anyone got any ideas?

thanks
 
What action are you running that causes the error?

Have you looked up the error on yet?



Catadmin - MCDBA, MCSA
Remember, "Work" is a four letter word. And you know what your mother told you about using four letter words!
 
i will look at the site and get back to u if need be, thanks for your help
 
i have looked this up on and can't seem to find anything specific to this error. the page executing the store procedure is throwing up an error as well.
i have found this but am not sure of its relevance. will continue to investigate but if u think of anything else i would be v grateful.

Many exception errors are not processed by applications. The most common exception error is EXCEPTION_ACCESS_VIOLATION (c0000005). It occurs when a pointer is dereferenced and the pointer points to inaccessible memory or a write operation is attempted on read-only memory. If an application does not trap an exception, the Win32 module, UnhandledExceptionFilter, will do one of the following: display a message box, invoke Dr. Watson, or attach your application to a debugger.
 
in case anyone is interested this was a microsoft bug inside SQL Server 2000- it was scheduled to be fixed in sp4 but i got a hotfix off them before its release and it worked! plus we got our £200 back from MS that we initially paid them - good deal! i have more information on this issue should it concern anyone - let me know
 
I just got this error today. I would love to hear what you found out about it. Thanks.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top