SQL Server Services in the 2008 SQL Configuration Manager FAILED

  • I was told in my book to check to status of the SQL Server Services and to start it if its stopped. Well, when i click on SQL Server Services, it says: "The remote procedure call failed."

    I'm checking windows update to see if there is an update i need to install. I do have SS2012 on my computer as well. Everything seems to be running fine on it. I don't know if there might be some conflicting issues though.

    HEre were the books instructions:

    Start the SQL Configuration Manager utility in the Configuration Tools folder, located in the Microsoft SQL Server 2008 program group. In the left pane, click SQL Server Services. In the right pane, examine the status of the SQL Server (SQLEXPRESS) service. If the status is Stopped, right-click the service, and then click Start. Wait for the status to change to Running, and then close SQL Configuration Manager.

    When i right click there is no start or stop and refreshing it means no difference. Any advice?

  • From the following two links it appears that the problem is with SS2012. They say that if i uninstall it 2008 should work. They also both seem to suggest that SS2008 R2 SP2 should fix the problem as well.

    http://stackoverflow.com/questions/11589964/sql-server-agent-gives-remote-procedure-call-failed-0x800706be

    http://www.i-m-code.com/blog/blog/2013/07/19/sql-server-2008-r2-configuration-manager-wmi-error-saga/

    as soon as this other install finishes, I'll give this a try.

  • Ok the installation worked and fixed the problem with the service running. I then followed the books instructions and ran the following installation. AdventureWorks2008_SR4.exe. Now SSMS 2008 won't connect AT ALL!

    However after running the above install and installing all the selected DBs, I'm now getting this error message:

    ===================================

    Cannot connect to Sam.

    ===================================

    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)

    ------------------------------

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

    ------------------------------

    Error Number: 2

    Severity: 20

    State: 0

    ------------------------------

    Program Location:

    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

    at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

    at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)

    at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)

    at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)

    at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)

    at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)

    at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)

    at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)

    at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)

    at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)

    at System.Data.SqlClient.SqlConnection.Open()

    at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)

    at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

  • Start "services.msc" on the host server and check if all needed SQL services are started.

    - SQL Server

    - SQL Server Agent Can not be started with SQL Express

    - SQL Server Browser

    Start SSMS on the hostserver and see if you can connect to the instance. If this is possible, you will need to check the firewall and allow SQL traffic to go through (http://social.technet.microsoft.com/Forums/en-US/operationsmanagerdeployment/thread/53fa9a6b-b9db-473f-8564-2ac4c62c3365/).

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
  • HanShi (8/28/2013)


    Start "services.msc" on the host server and check if all needed SQL services are started.

    - SQL Server

    - SQL Server Agent Can not be started with SQL Express

    - SQL Server Browser

    But i don't have SQL Express. I have at least Developers Edition. Why does my stuff say EXPRESS?

    some of my stuff says MSSQLSERVER While others say SQLEXPRESS. I've attached a screen shot

    Thanks for the link you gave. i'm checking it out.

  • HanShi, Thanks! You are worth a million!!!!

    What i did was look a little more closely and saw that there was a SQL Server (MSSQLSERVER) that as not started and a SQL Server (SQLEXPRESS) that was started. I stopped the express and ran the MSSQLSERVER.

    My question is: Do i need to start SQL Server Agent (MSSQLSERVER)? Currently it is stopped!

    Thanks so much!!!

  • SQL Agent must be started when you use scheduled jobs and/or alerts. In most systems SQL Agent is started.

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
  • Thanks Hanshi

  • HanShi (8/28/2013)


    SQL Agent must be started when you use scheduled jobs and/or alerts. In most systems SQL Agent is started.

    I'd say that on most developer/training computers (like Jacob's) Agent is not running. On a server accessed by many users it is a different story.

    [font="Times New Roman"]Erland Sommarskog, SQL Server MVP, www.sommarskog.se[/font]

  • i appreciate the info

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply