March 5, 2008 at 6:43 pm
About every 5 seconds I am getting the below errors
Source: SQLDumperEvent: 5000
Source: MSSQL$MOSSEvent: 17310
Source: SQLDumperEvent: 5001
Source: SQLDumperEvent: 1010
My MOSS 2007 implementation seems to seize up sometimes and I am not sure if I am troubleshooting this correctly. :crazy:
March 5, 2008 at 7:07 pm
Is there any error text?
Try http://www.eventid.net/search.asp
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
March 6, 2008 at 6:42 am
I'm not really seeing anything in the SQL log (unless I am looking in the wrong place). I open SQL Mngmt Studio, drill down to SQL Server Agent - Error Logs and doubleclick Current - xxxxx
All I see for that and the lastest archives is:
[408] SQL Server MOSS is clustered - AutoRestart has been disabled
[396] An idel CPU condition has not been defined - OnIdle job schedules will have no effect
[260] Unable to start mail session (reason: No mail profile defined)
[129] SQLAgent$MOSS starting under Windows NT service control
[364] The Messenger service has not been started - NetSend notifications will not be sent
Am I out to lunch?
March 6, 2008 at 6:44 am
That is the agent logs (the scheduler), you want to look at the error logs for SQL server.
SSMS - Management -> SQL Server Logs
or
sp_readerrorlog
or
Install Location\Microsoft SQL Server\MSSQL.InstanceInstallNumber\MSSQL\LOG
March 6, 2008 at 7:49 am
Sorry. Not enought coffee this morning. It looks ugly but here's what I see in the SQL Server Log. It repeats A LOT
Date,Source,Severity,Message,
spid57,Unknown,Using 'dbghelp.dll' version '4.0.5',
Server,Unknown,A user request from the session with SPID 57 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.,
Server,Unknown,Error: 17310 State: 1.,
spid57,Unknown,External dump process return code 0x20002001. The error information has been submitted to Watson error reporting.,
spid57,Unknown,Stack Signature for the dump is 0x0000000114B8F941,
spid57,Unknown,* Short Stack Dump,
spid57,Unknown,* _ M S S _ C r a w 5f 00 4d 00 53 00 53 00 5f 00 43 00 72 00 61 00 77 00,
spid57,Unknown,* d b o . p r o c 12 00 64 00 62 00 6f 00 2e 00 70 00 72 00 6f 00 63 00,
spid57,Unknown,* Input Buffer 104 bytes -,
spid57,Unknown,* Access Violation occurred reading address 0000000000000000,
spid57,Unknown,* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION,
spid57,Unknown,* Exception Address = 00000000015F7A1E Module(sqlservr+00000000005F7A1E),
spid57,Unknown,* 03/06/08 09:42:01 spid 57,
spid57,Unknown,* BEGIN STACK DUMP:,
spid57,Unknown,* *******************************************************************************,
spid57,Unknown,SqlDumpExceptionHandler: Process 57 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.,
spid57,Unknown,***Stack Dump being sent to J:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump10000.txt,
spid57,Unknown,Using 'dbghelp.dll' version '4.0.5',
Server,Unknown,A user request from the session with SPID 57 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.,
Server,Unknown,Error: 17310 State: 1.,
spid57,Unknown,External dump process return code 0x20002001. The error information has been submitted to Watson error reporting.,
spid57,Unknown,Stack Signature for the dump is 0x0000000114B8F941,
spid57,Unknown,* Short Stack Dump,
March 6, 2008 at 8:19 am
What service pack/revision are you on?
SELECT SERVERPROPERTY('ProductLevel')
SELECT SERVERPROPERTY('ProductVersion')
While I don't know exactly what those errors are eluding to, there is a good chance you can resolve this with an update.
March 6, 2008 at 8:56 am
Currently running SQL Server 2005 (9.00.1399.00), but no SP.
March 6, 2008 at 8:58 am
miltonmharper (3/6/2008)
Currently running SQL Server 2005 (9.00.1399.00), but no SP.
Oh yeah ... you need SP2 ... I googled a bit of your error and found random MSDN posts with users reporting that SP2 resolved it.
March 6, 2008 at 9:11 am
I have the attached link for doing SP2. Did you see any issues loading it in a failover clustered environment? I gather you have to install it on both servers.
March 6, 2008 at 9:14 am
miltonmharper (3/6/2008)
I know close to nothing about a clustered environment unfortunately, haven't had the privilege :(. I saw some other posts in the admin forum about installing an SP on a clustered environment. There are definitely some things to know ... You may want to create a new thread ... but after a quick Google, I found this:
3.2.5 Installing SQL Server 2005 SP2 on a Failover Cluster Instance
Note the following information before you install SP2 on a failover cluster instance:
* Do not stop the cluster service before you run the SP2 Setup program, or while the installation program is running.
* Do not end any running processes before you run the SP2 Setup program.
* Do not take the SQL Server service off line before you run the SP2 Setup program. The SP2 Setup program will stop and start the SQL Server service.
* Run the SP2 Setup program on the primary node of the failover cluster instance.
* You must restart all failover cluster nodes after SP2 is finished installing.
* Rolling upgrade is not supported for SP2.
March 6, 2008 at 6:00 pm
The 5000 Error has:
EventType sql90exception64, P1 sqlservr.exe, P2 2005.90.1399.0, P3 00000000434fa8ab, P4 sqlservr.exe, P5 2005.90.1399.0, P6 00000000434fa8ab, P7 0, P8 00000000005f7a1e, P9 0000000114b8f941, P10 NIL.
The 17310 Error has:
A user request from the 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.
The 5001 Informational has:
Bucket 157936425, bucket table 5, EventType sql90exception64, P1 sqlservr.exe, P2 2005.90.1399.0, P3 00000000434fa8ab, P4 sqlservr.exe, P5 2005.90.1399.0, P6 00000000434fa8ab, P7 0, P8 00000000005f7a1e, P9 0000000114b8f941, P10 NIL.
The 1010 Informational has:
Bucket 157936425, bucket table 5.
Not really sure what to make of these
March 6, 2008 at 6:02 pm
Sounds like SQL is dumping ... check your SQL Server Error Logs, they may contain more information.
March 7, 2008 at 6:24 am
Yep. I saw the tidbits in para 3.2.5. Sorry I couldn't reply yesterday. huge fire to put out due to a GPO push to our SQL & MOSS farm. Can you say BOOM! Priority right now is that the MOSS is getting errors and we plan on doing the MOSS SP1 upgrade tonight. Will schedule SQL SP2 probably next weekend.
March 8, 2008 at 4:49 am
Looks like SP2 corrected that issue. Good news for that since it innunudated the Application logs. Bad news is now I get to see other events to work on.:w00t:
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply