SQL2000 crashes randomly at various times of the day

Hi folks,

I have SQL2000 sp3a running on the same machine as IIS (server is a
dedicated server hosted remotely), the machine is a few years old a PIV 2ghz
,
with 1gb of ram.

The SQL Server is solely there to run 2 DB's a teenie tiny 5mb db for my
main website http://www.vb4all.net/ and a bigger 200 - 600mb database for an
online browser based game I run at http://www.vb4all.net/fh2/

My problem is that every so often usually about once a month at various
times of the day or server loads MS SQL will crash, it will take out Termina
l
Services preventing me from connecting, IIS will still work fine, FTP and
accessing other ports works great too its just MS SQL and Terminal Services
that go down.

When this happens I have to request a reboot from my host which can take
anywhere from 20 minutes to a couple of hours as they do not have what I
would call 24/7 support.

Now this month we have turned a corner and not in a good way, it has crashed
3 times in the last four days ... it has gotten to the point where I have no
w
coded an automatic reboot application which sits on the server and
periodically polls SQL and if it is no longer up it auto-reboots the server.

I would seriously love to fix this problem as it is frustrating, as I am
sure many of you can imagine.

Typically when it crashes there are several dumps in the log file, usually
three memory dumps and associated logs, it would seem that perhaps this is
the cause ...

Now that said sometimes SQL will produce a memory dump after hitting an
error, but these are non fatal and SQL resumes just fine without needing a
reboot, it only seems to be when it has 3 of these errors in quick successio
n.

We reboot the server daily, at midnight and sometimes it will have this
problem in the early morning like today it had it at 7:15am our busiest time
s
are usually in the afternoon/evening and it doesnt often crash then. So I
dont think it is load related.

The last three errors from the logs are:

First error

*   Exception Address = 004028C9

*   Exception Code    = c0000005  EXCEPTION_ACCESS_VIO
LATION

*   Access Violation occurred reading address D4FBBE80

Second error had no text whatsoever but was in the same spid 13.

Cant say I have ever seen the following before, but that is the third error.

* ex_terminator - Last chance exception handling

For those who wish to read the full logs I have uploaded them to my HTTP
server.

http://www.fho2.com/downloads/Logs.zip

Thanks, Daniel

You need to contact PSS. Looking at the logs I can see the following assert
"lckmgr.cpp:5602.Expression:. NULL == m_lockList.Head ()" this indicates
either a bug in SQL or some underlying hardware issue. Looking through
google I can see that this has sometimes been caused by issues with memory.
Run a DBCC CHECKDB on your database to check for any corruption but my guess
would be that it may well be hardware. Just to check, you haven't got any
trace flags switched on have you? I've seen this error when trace flag 1200
is turned on.

--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com


"Daniel Paull" < DanielPaull@discussi
ons.microsoft.com> wrote in message
news:40FE5228-411B-4B96-BDEA- 57225FAC378A@microso
ft.com...
> Hi folks,
>
> I have SQL2000 sp3a running on the same machine as IIS (server is a
> dedicated server hosted remotely), the machine is a few years old a PIV
> 2ghz,
> with 1gb of ram.
>
> The SQL Server is solely there to run 2 DB's a teenie tiny 5mb db for my
> main website http://www.vb4all.net/ and a bigger 200 - 600mb database for
> an
> online browser based game I run at http://www.vb4all.net/fh2/
>
> My problem is that every so often usually about once a month at various
> times of the day or server loads MS SQL will crash, it will take out
> Terminal
> Services preventing me from connecting, IIS will still work fine, FTP and
> accessing other ports works great too its just MS SQL and Terminal
> Services
> that go down.
>
> When this happens I have to request a reboot from my host which can take
> anywhere from 20 minutes to a couple of hours as they do not have what I
> would call 24/7 support.
>
> Now this month we have turned a corner and not in a good way, it has
> crashed
> 3 times in the last four days ... it has gotten to the point where I have
> now
> coded an automatic reboot application which sits on the server and
> periodically polls SQL and if it is no longer up it auto-reboots the
> server.
>
> I would seriously love to fix this problem as it is frustrating, as I am
> sure many of you can imagine.
>
> Typically when it crashes there are several dumps in the log file, usually
> three memory dumps and associated logs, it would seem that perhaps this is
> the cause ...
>
> Now that said sometimes SQL will produce a memory dump after hitting an
> error, but these are non fatal and SQL resumes just fine without needing a
> reboot, it only seems to be when it has 3 of these errors in quick
> succession.
>
> We reboot the server daily, at midnight and sometimes it will have this
> problem in the early morning like today it had it at 7:15am our busiest
> times
> are usually in the afternoon/evening and it doesnt often crash then. So I
> dont think it is load related.
>
> The last three errors from the logs are:
>
> First error
>
> *   Exception Address = 004028C9
>
> *   Exception Code    = c0000005  EXCEPTION_ACCESS_VIO
LATION
>
> *   Access Violation occurred reading address D4FBBE80
>
> Second error had no text whatsoever but was in the same spid 13.
>
> Cant say I have ever seen the following before, but that is the third
> error.
>
> * ex_terminator - Last chance exception handling
>
> For those who wish to read the full logs I have uploaded them to my HTTP
> server.
>
> http://www.fho2.com/downloads/Logs.zip
>
> Thanks, Daniel

Hello Jasper,

No there are no trace flags, I guess I will contact PSS thanks for the reply
.


"Jasper Smith" wrote:

> You need to contact PSS. Looking at the logs I can see the following asser
t
> "lckmgr.cpp:5602.Expression:. NULL == m_lockList.Head ()" this indicates
> either a bug in SQL or some underlying hardware issue. Looking through
> google I can see that this has sometimes been caused by issues with memory
.
> Run a DBCC CHECKDB on your database to check for any corruption but my gue
ss
> would be that it may well be hardware. Just to check, you haven't got any
> trace flags switched on have you? I've seen this error when trace flag 120
0
> is turned on.
>
> --
> HTH,
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
>
>
> "Daniel Paull" < DanielPaull@discussi
ons.microsoft.com> wrote in message
> news:40FE5228-411B-4B96-BDEA- 57225FAC378A@microso
ft.com... 
>
>
>