December 29, 2008 at 9:41 am
A couple of days ago, the SQL Agent service on one of our instances restarted on its own. I'm showing the errors recorded in the Windows App Log. Has anyone else seen this?
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 1000
Date: 12/27/2008
Time: 10:48:41 AM
User: N/A
Computer: xxx
Description:
Faulting application sqlagent90.exe, version 2005.90.3042.0, stamp 45cd6a37, faulting module kernel32.dll, version 5.2.3790.3959, stamp 45d70ad8, debug? 0, fault address 0x0000bee7.
Event Type: Error
Event Source: MSSQL$xxx
Event Category: (2)
Event ID: 17052
Date: 12/27/2008
Time: 10:48:48 AM
User: N/A
Computer: xxx
Description:
The description for Event ID ( 17052 ) in Source ( MSSQL$xxxxx ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly..
Event Type: Warning
Event Source: MSSQL$xxxxx
Event Category: (2)
Event ID: 17052
Date: 12/27/2008
Time: 10:48:48 AM
User: N/A
Computer: xxx
Description:
The description for Event ID ( 17052 ) in Source ( MSSQL$xxxxx ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: SQLServerAgent Monitor successfully restarted SQLServerAgent after SQLServerAgent terminated unexpectedly..
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
December 29, 2008 at 12:15 pm
Anything in the SQLAGENT.1 log?
Are there any stack dumps sitting in the same folder?
Take a look through those would be your best bet.
December 29, 2008 at 12:28 pm
Nicholas Cain (12/29/2008)
Anything in the SQLAGENT.1 log?Are there any stack dumps sitting in the same folder?
Take a look through those would be your best bet.
Funny thing is, there is no SQLAGENT.1 log file. I have SQLAGENT.OUT, SQLAGENT.2, SQLAGENT.3 etc, but no SQLAGENT.1.
I also have a couple of ATLtracetool trace-settings files: log_369.trc, log_368.trc.
Not sure how these were generated.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
December 29, 2008 at 12:34 pm
That is totally random.
And nothing in the .2 log that indicates anything I expect.
Nothing in the SQL logs either?
December 29, 2008 at 12:37 pm
Nicholas Cain (12/29/2008)
That is totally random.And nothing in the .2 log that indicates anything I expect.
Nothing in the SQL logs either?
No, there is nothing in the .2 log or SQL logs to indicate a problem.
The only evidence something went wrong is from the Event Log (errors shown in the OP).
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
December 29, 2008 at 12:40 pm
Might have to chalk that one up to the SQL gremlins, unless someone else has any ideas
December 29, 2008 at 12:42 pm
Nicholas Cain (12/29/2008)
Might have to chalk that one up to the SQL gremlins, unless someone else has any ideas
Yeah, probably the ghost of Christmas past... 😉
Hopefully it's a one-of thing.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
December 29, 2008 at 1:00 pm
I'm having the same problem and can't find the cause. It started this month on two of our SQL clusters. One cluster is 32-bit and the other is 64-bit. By any chance is your issue on a cluster? I'm guessing it is not based upon your 17052 message.
The description for Event ID ( 17052 ) in Source ( MSSQLSERVER ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: SQLServerAgent Monitor failed to restart SQLServerAgent after SQLServerAgent terminated unexpectedly (reason: SQLSCMControl() returned error 5040, 'The cluster node already exists.')..
Dave
December 29, 2008 at 1:03 pm
DBADave (12/29/2008)
I'm having the same problem and can't find the cause. It started this month on two of our SQL clusters. One cluster is 32-bit and the other is 64-bit. By any chance is your issue on a cluster?Dave
No, it's on a standalone server instance, although I have seen a couple of posts on the web with a similar problem on a cluster.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
December 29, 2008 at 1:06 pm
My 32-bit cluster is running 2005 SP1 and my 64-bit cluster is running 2005 SP2. Both are Enterprise Edition. We plan on calling Microsoft in January to see if they can help, but we aren't holding out much hope.
December 29, 2008 at 1:13 pm
IF you're on a cluster the cluster logs themselves are an immense help in these kinds of situations.
December 29, 2008 at 1:14 pm
DBADave (12/29/2008)
My 32-bit cluster is running 2005 SP1 and my 64-bit cluster is running 2005 SP2. Both are Enterprise Edition. We plan on calling Microsoft in January to see if they can help, but we aren't holding out much hope.
They will probably suggest that you upgrade to SQL 2008... :hehe:
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
December 29, 2008 at 1:30 pm
I no longer have the exact log messages since the log has wrapped, but it essentially stated the SQL Server Agent had a problem and needed to be restarted. The message was very generic and didn't point to anything specific.
December 29, 2008 at 1:33 pm
DBADave (12/29/2008)
I no longer have the exact log messages since the log has wrapped, but it essentially stated the SQL Server Agent had a problem and needed to be restarted. The message was very generic and didn't point to anything specific.
I wonder if running "chkdsk" is worth it, it would slow the system down for users while running.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
December 29, 2008 at 1:37 pm
Since it's clustered the data is on a SAN. I'm guessing there is an equivelant tool to chkdsk, but I'm not sure I understand the connection. What would I be looking for in the chkdsk output?
Viewing 15 posts - 1 through 15 (of 31 total)
You must be logged in to reply to this topic. Login to reply