MS SQL Server Enterprise Edition (64-bit) v9.00.1399.06
MS Windows NT 5.2 (3790)
14334 MB RAM
8 CPU
Not clustered
serves MS SharePoint 2007 instance
My SharePoint goes down twice a day due to SQL Server connection errors. A reboot of the DB server and SP server resolves the incident.
In the SQL Server error logs are continuous stack dumps that started a few days ago. Excepts from the dump:
Using 'dbghelp.dll' version '4.0.5'
A user request from session with SPID 56 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
Error: 17310, Severity: 20, State: 1.
blah, blah, blah...
Input Buffer 104 bytes -
Access Viaolation occured reading address 000000000000000000
Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
Exception Address = 00000000015F7A1E Module(sqlserver+00000000015F7A1E)
This error does not seem to bring down the server, as the stack dumps are logged one after the other at ~5 second intervals.
The LOG directory has 6 files that are continuously updated:
- ERRORLOG
- SQLDUMPER_ERRORLOG.log
- SQLDmpr10000.mdmp
- SQLDmpr10000.log
- exception.log
- SQLDump10000.txt <-- over 7 GB!
The server has > 4GB RAM available and > 90 GB disk space available.
At the time that SharePoint generates SQL Server connection errors, nothing new is logged in the SQL Server error logs. I can still access SQL Server and run simple queries, but even if the connection error is temporary, SharePoint never seems able to reconnect.
TIA