SQL Server 2008 – Agent Keeps Stopping for Unknown Reason

sql serversqldump

My MSSQL 2008 service keep stopping don't know why. I took the habit to just restart the service, but it's getting really annoying.

Does anyone has a clue on why it keeps shutting down ?

Sql server 2008, logged as local.

Here are 4 SQLdump from today.

09:29:36 09/28/16

10:05:42 09/28/16

10:32:18 09/28/16

10:46:14 09/28/16

found this in my event viewer :

SQL Server is terminating because of fatal exception c0000005. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).

Error when I tried to install MSSQL 2008 SP3 (x64)

The version of the instance of SQL Server Shared Component does not match the expected version of the update to SQL Server. The version of the SQL Server product installed is 10.50.1600.1 and the version of SQL Server expected is 10.0.1600.22.

SELECT @@VERSION res

Microsoft SQL Server 2008 R2 (RTM) – 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.2 (Build 9200: )

Best Answer

Installation is on RTM of SQL Server 2008 R2. Try upgrading to currently supported Service Pack 3 https://www.microsoft.com/en-ca/download/details.aspx?id=44271

Related Solutions

Sql-server – Why is script with “ xp_cmdshell ” in comment failing with a transport level error

There is a connect item discussing (well discussing...) exactly this issue, so it appears to be a bug.

Text 'xp_cmdshell' causes transport-level error: semaphore timeout period has expired from remote system

It appears that the string causes problems, not only in comments but also anywhere it's used as an exact string so even

SELECT 'xp_cmdshell'

results in the same error according to the bug report.

So it appears that the exact string xp_cmdshell is indeed the problem, unfortunately the connect item is closed as "not reproducible".
That being said, I can't reproduce it (on a local connection) on my SQL 2014 (12.0.2000.8, Windows NT 6.3 (Build 9600: )) test system either, so the operating system is probably relevant. Executing the query from a local management studio vs over the network might also be relevant as noted in the connect item.

So you could either work around it by changing the exact text (as you did) or try to reopen the connect item or file a bug report through Microsoft Support.

Sql-server – SQL Server installation errors assembly

Peter Saddow has written about this issue, and it's more likely a problem with the setup program rather than your OS (though it can't hurt to make sure you've installed all Windows updates too):

Invoke or BeginInvoke cannot be called on a control until the window handle has been created.

So instead of installing RTM from RTM media, try slipstreaming with the final service pack for 2008 R2 (Service Pack 3).

I came across this issue on Windows 7, even when slipstreaming, but in my case only a reboot was required to get past the issue (simply closing setup and re-launching was not enough).

Peter has also written about slipstreaming:

How to slipstream SQL Server 2008 R2 and a SQL Server 2008 R2 Service Pack 1 (SP1)

That post was about SP1, but you can follow the same basic steps to slipstream a newer service pack.

Related Question