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