c0000005 EXCEPTION_ACCESS_VIOLATION

"Mike Smith" <msmith@.larrymethvin.com> wrote in message
news:OS7pVV9sFHA.3752@.TK2MSFTNGP09.phx.gbl...
> I have searched this newsgroup and Google. It seems that with this error I
> should just call PSS? The SQL (see error.log attached) runs fine from
Query
> Analyzer, but not from my application (other queries run fine though). It
> worked up until yesterday. I rebooted the server. I had an associate apply
> SP4, but it still throws this exception. I'm having my partner run Dell
> diags on it during lunch. The server is in California, I'm in Tennessee.
> I also get this Events in the Event Log when the query is fired:
> Event 17052, SOURCE: MSSQLSERVER
> Error: 0, Severity: 19, State: 0
> language_exec: Process 57 generated an access violation. SQL Server is
> terminating this process.
> AND
> Event 17052, SOURCE: MSSQLSERVER
> Error: 0, Severity: 19, State: 0
> SqlDumpExceptionHandler: Process 57 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
>
Sorry, specs:
Dell PowerEdge, Windows 2003 SP1, SQL2000 SP4.
The only change I am aware of is SP4, previously (yesterday), it had SP3a.
Regards,
Mike Smith
msmith@.larrymethvin.com"Mike Smith" <msmith@.larrymethvin.com> wrote in message
news:OS7pVV9sFHA.3752@.TK2MSFTNGP09.phx.gbl...
>I have searched this newsgroup and Google. It seems that with this error I
> should just call PSS?
Yes.
David|||"Mike Smith" <msmith@.larrymethvin.com> wrote in message
news:OS7pVV9sFHA.3752@.TK2MSFTNGP09.phx.gbl...
> I have searched this newsgroup and Google. It seems that with this error I
> should just call PSS? The SQL (see error.log attached) runs fine from
Query
> Analyzer, but not from my application (other queries run fine though). It
> worked up until yesterday. I rebooted the server. I had an associate apply
> SP4, but it still throws this exception. I'm having my partner run Dell
> diags on it during lunch. The server is in California, I'm in Tennessee.
> I also get this Events in the Event Log when the query is fired:
> Event 17052, SOURCE: MSSQLSERVER
> Error: 0, Severity: 19, State: 0
> language_exec: Process 57 generated an access violation. SQL Server is
> terminating this process.
> AND
> Event 17052, SOURCE: MSSQLSERVER
> Error: 0, Severity: 19, State: 0
> SqlDumpExceptionHandler: Process 57 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
>
For the sake of the list, and anyone else that may have this problem. I
checked my log files, they were HUGE! We had moved servers, and whoever
setup the backups didn't back up the logs. I shrank the logs using the
method in: http://support.microsoft.com/kb/272318