Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

logon trigger and EXCEPTION_ACCESS_VIOLATION Expand / Collapse
Posted Wednesday, July 23, 2014 8:26 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, February 24, 2016 10:22 AM
Points: 53, Visits: 176
Hello. My production sql server is running Microsoft SQL Server 2005 - 9.00.4035.00 (X64)
Nov 24 2008 16:17:31
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2) on a windows server 2003 standard edition machine.
We have a logon trigger running, and one user was updating all the views, and got a login failed due to trigger execution, and a stack dump in the log due to EXCEPTION_ACCESS_VIOLATION.
I tried copying the crash dump to my workstation and downloaded the debugger, but wasn't able to debug it due to all the other files not being present.
Is there any potential issue with me downloading the debugger to our prod server and running it there during non-prime time?
Or has anyone got any suggestions or information on what could have caused the exception, and next steps?
Thanks very much.
Post #1595506
Posted Friday, September 19, 2014 10:12 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, October 29, 2014 1:09 AM
Points: 33, Visits: 54
SQL server 2005 SP3 which you have as of now(9.00.4035.00 ) is out of support. So first thing you should do is apply SP4. Access violation exception generally means some bug in SQL Server and its best to get this stack dump analyzed by Microsoft Engineer. You might get lucky with debugger but you would not be able to draw correct inference from it.

Even if you open case with MS they would first ask you to install latest SP and if the issue occurs then revert to them. So instead first apply SP4 and see if this issue subsides.

You are also using Old Version of windows Server, windows server 2003 you should consider upgrading both SQL Server and windows Server to supported versions and editions.
Post #1615484
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse