Discussion Locked

SQL Server 6.5 Daily errors with no expl

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have recently been experiencing errors on our SQL Server and the errors have no good answers in any of our Tech guides. These errors include:

1. "# Number of users exceeded" errors in the middle of the night with no one on, this locks the DB down and no one can access it until it is rebooted. This usually occurs after a "General network error, problem sending results to front end" error, although we are getting no errors anywhere else and after using a sniffer are seeing no network errors. There also appears to be a Dr. Watson that will not write out a log when trying to reboot after these errors.

2. This morning I finally caught the Dr. Watson Error, it references a (pid139) and a (pid171) in the log and these show in TechNet as being associated errors with SNA Server and Terminal server but not with SQL Server. The exception error is associated with a SQLSERVR.DBG application. Today the SQLEXEC and SQLServer were shut down when I came in. Looking at the applicationevent log it appears

13 replies

by gutridgesj

what service pack are you running? we had a simliar problem. it seemed to go away but then we upgraded to 7.0

by richard jones

We have been running 6.5 SP5a since it came out, since I posted this I have have even replace/upgraded the Server that this is running on. Completely reloading from scratch and reloading the data. We ran fine for about a month and now it has started doing it again. No real explication..

by rwscc

You would think that the con artists that post "If you solve a question, you should close it" would be disqualified from recieving points. If anyone else feels these freeloaders should be disqualified please give techrepublic the feedback on this matter. They are stealing points from people who try to give valid answers.

This discussion is closed to new replies.