SQL Server (MSSQLSERVER) service on Local Computer ERROR 1053

Question

Hello,

I'll try to describe what I've done so far:

• Installed SQL Server 2008 Developer Edition With all features enabled. 
• Used Default Instance MSSQLSERVER as it is
•  Give following passwords:
• SQL Server browser NT AUTHORITY\Local ; startup type Disable; which i later on set as automatic
• SQL Server (MSSQLSERVER) = SQL Server Analysis = SS reporting S =SSIntegration S = NT AUTHORITY\ SYSTEM ; Automatic; Use the same account for all option. I remmber it was not accepting \Local that is why i select it.
• Selected Windows authontication mode and Add current user Umema-VAIO\Umema in to SQL server administrators
• Install the native mode default configuration
• In RebootMessageAction it was showing Databse Engine Services and Replication services as FAILED.
• Then i Opened Management Studio and tried to connect to Database Engine MSSQLSERVER (as that is the server's name) with Windows Authentication method.

This results in the following error:

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

Cannot connect to mssqlserver.

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

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=53&LinkId=20476

------------------------------
Error Number: 53
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()

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

IF i try to connect to Database Engine "." Or my computer name (Umema-VAIO\Umema) with Windows Authentication method.

This results in the following error:

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

Cannot connect to ..

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

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()

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

• If i enable SQL Server (MSSQLSERVER) from Computer-Manger-SQL Server Config - SQL Server Service it shows this alert
• The request failed or ther service did not respond in a timely manners Consult the event Log Or other application error logs for detail
• If i enable SQL Server (MSSQLSERVER) from Computer-Manger-Services and Applications- Services, Then alert appears:
  Windows could not start the SQL Server (MSSQLSERVER) service on Local Computer
  ERROR 1053: The service did not respond to start or control request in a timely fashion.

I'm running on Windows 7 Home. I have enables TCP/IP e If there's more information you need, I'll be glad to provide it. I hope you can help me fix this.

Answer 1

Is it SQL Server Service Up and running?

---

http://uk.linkedin.com/in/ramjaddu

Answer 2

means ? please elaborate ?

SQLSERVER(MSSQLSERVER) service is showing no status when i try to start it it gives me error:1053

SERVER AGENT , Error:1068

rest of the four services are runing.

 

I am runing SQL on my laptop local machine, although i enabled TCP/IP

 

---

Faculty, www.ssuet.edu.pk/~suhani

Answer 3

1. Confirm SQL Server is up and running.

1. Go to START, RUN , type services.msc

        2. Locate the "SQL Server (MSSQLSERVER)" and the check the status.

2. You already said that you enabled TCP/IP, check and confirm once more.

3. Check your windows firewall setting and open the port no 1433 by using the "ADD Port" button.

---

Thanks
Manish

Answer 4

Check following link http://support.microsoft.com/kb/322140

Answer 5

1. Confirm SQL Server is up and running.

 1. Go to START, RUN , type services.msc

        2. Locate the "SQL Server (MSSQLSERVER)" and the check the status. (SQLSERVER(MSSQLSERVER) service is showing no status when i try to start it it gives me error:1053 The service did not respond tp start or control request in a timely fashion)

2. You already said that you enabled TCP/IP, check and confirm once more. (Done already through Cliconfg.exe)

3. Check your windows firewall setting and open the port no 1433 by using the "ADD Port" button. (Done already through Cliconfg.exe)

---

Faculty, www.ssuet.edu.pk/~suhani

Answer 6

Hi Umena,

As you told you are having Windows 7 Home, is it updated with the latest service pack and hot fixes ? As per the following two links of MS 

http://support.microsoft.com/kb/839174

http://support.microsoft.com/kb/886695

Have a look to the resolution section. 

Also I suggest, please confirm the TCP/IP status using the SQL SERVER CONFIGURATION MANAGER  by Go to START, RUN , type SQLServerManager10.msc 

Select SQL SERVER NETWORK CONFIGURATION 

Select Protocols for MSSQLSERVER

Check the TCP/IP status is enabled or not.

 

 

 

---

Thanks
Manish

Please use Mark as Answer if my post solved your problem and use Vote As Helpful if a post was useful.

Answer 7

@Mitchpe please find my findings in Bold: I found this on url ttp://support.microsoft.com/kb/322140

This issue occurs because of one of the following reasons:

• The SQLServerAgent service startup account may not have the correct permissions on the folder that contains SQLAgent.out files.
• The SQL Server Agent error log may include a path or a file name that is not correct.
• Some executable .dll files may be corrupted or damaged.
• The SQLServerAgent service startup account may not have the correct permissions to use the registry.

To resolve this issue, use one of the following methods, as appropriate to your circumstances:

• The SQLServerAgent service startup account may not have the correct permissions on the folder that contains SQLAgent.out files.
  
  In this case, make sure that the specified SQLServerAgent service account has full control permissions to the folder in which the SQLAgent.out, SQLAgent.1, SQLAgent.2, and other SQL Server files are located. These files are typically stored in the LOG folder, which is in the SQL Server installation path. (Intallation folder: Microsoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL\LOG is empty. I check this folder's right it was Read only i removed it and applied it to all sub folders and files) 
• The SQL Server Agent error log may include a path or a file name that is not correct.
  
  In this case, verify that the path and file name for SQLAgent.out is valid: (This file is no where, if i search foler for SQLAgent*.* then i found many files in MSSQL folder but not the MSSQL\LOG which is empty as i told you)

  SQLAGENT.exe Microsoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL

• sqlagentctr100.dll Microsoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL\Binn

• sqlagentLOG.dllMicrosoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL

• SALagentmail.dllMicrosoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL

• SQLagent.rllMicrosoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL\Binn\Resources

• SQLagentLOG.RLLMicrosoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL\Binn\Resources

• SQLAgentMail.rllMicrosoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL\Binn\Resources

• SQLagent100_msdb_upgradeMicrosoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL\Binn

• SQLagent100_msdb_upgradeMicrosoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL

• SQLagent100_upgradeMicrosoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL

• perf-SQLSERVERAGENTsqlagtctrMicrosoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL

• instdistMicrosoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL

• instmsdbMicrosoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL

• sqlagtctrMicrosoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL

• sysdbpgMicrosoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL

• sysdbpgMicrosoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL

• procsystMicrosoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL

• procsystMicrosoft SQL Server\MSSQL10.MSSQLSERVER \MSSQL

  1. In SQL Server Enterprise Manager, expand the Management folder. (Where it is ? do you mean 1. configuration manager  for services Or the Server mangement Studio?)
  2. Right-click SQL Server Agent, and then click Properties.
  3. Under Error Log, make sure that the path that is specified next to File Name is valid.
  4. Make sure that the file name is SQLAGENT.out.
• FAILED TO FIND THIS FILE
• Some executable .dll files may be corrupted or damaged.
  
  In this case, try starting SQL Server Agent from the command prompt by running the following command:
  
  Default Instance

  sqlagent -c -v 

  Named Instance

  sqlagent -i[Instance Name] -c -v 

  If you receive the following error message
  execution can't continue as the language resource file sqlagent.rll could not be loaded
  replace the SQLAgent.dll and SQLAgent.rll files with different copies of these files (SQLAgent.dll and SQLAgent.rll).

(I AM RECEIVING MESSAGE ON COMMAND PROMPT: You must start sql server agent as a service using the SQL Service Manager )

• The SQLServerAgent service startup account may not have the correct permissions to use the registry.
  
  In this case, make sure that the MSSQLSERVER startup account, the SQL Server Agent startup account, and the Microsoft Distributed Transaction Coordinator (MS DTC) startup account have full control of the following keys in the registry:
  
  
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDTC 
• (When i regedit and locate them They are showing ObjectName: NT AUTHORITY\NetworkService and show requiredPrivilages:SeChangeNotifyPrivilege and SeCreateGlobalPrivilege)
  
  
  The following keys are for the default instance:
  
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLSERVER
• (ObjectName:LocalSystem, ImagePath:"C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn\sqlservr.exe" -sMSSQLSERVER )
• when i directly run "C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn\sqlservr.exe"; it gives alert SQL Server NT-64 Bit has stopped working: Aproblem caused the program to stop working correctly. Windows will close the program and notif you if a solution is available.)
• 
  
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlset\Services\SQLSERVERAGENT
• (ObjectName:LocalSystem, ImagePath:"C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn\SQLAGENT.EXE" -i MSSQLSERVER)
• When i click it it gives same message run through Service Manager
  
  The following keys are for the named instance:
  
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQL$<INSTANCE>
• Not found
• 
  
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlset\Services\SQLAgent$<INSTANCE>
• Not found
• instead hace MSSQLServerADHelper100 and MSSQLServerOLAPService
  
  Note The placeholder <var>INSTANCE</var> is replaced with the actual name of an instance of SQL Server.

---

Faculty, www.ssuet.edu.pk/~suhani

Answer 8

Hi Umema,

The various causes fall into five categories:
1. Incorrect connection string, such as using SqlExpress.
2. NP was not enabled on the SQL instance.
3. Remote connection was not enabled.
4. Server not started, or point to not a real server in your connection string.
5. Other reasons such as incorrect security context.

For more information, you could refer to http://blogs.msdn.com/b/sql_protocols/archive/2007/03/31/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server.aspx.

 Thanks,
Maggie

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.

Answer 9

Thanks Dear all, Problem retains as it is.

---

Faculty, www.ssuet.edu.pk/~suhani

Answer 10

Hi Umema,

Since you have installed a default instance, you need to use the computer name to connect database engine. I think your computer name is Umema-VAIO not Umema-VAIO\Umema with Windows Authentication method.

If you have any problem, please feel free to let me know.

Thanks,
Maggie

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.

Answer 11

Dear Maggie, Yes i know.

 

Problem is as it is. It has not been resolved. I have not come to any solution even Windows has already updated its so many updates BUT  still Database engine is unable to locate both "MSSQLSERVER" or "UMEMA-VIO".

---

Faculty, www.ssuet.edu.pk/~suhani

Answer 12

Hi,

I had sort of this problem with SQL Server 2008 and did all things and wasted my times!  The problem was that I was entering MSSQLServer for the instanace name, where I should have entered the name of the computer!  Because thie instance was the default instance name and so it should be the name of the computer! Stupid SQL Server Team, it should be the instance name which is in windows services namely MSSQLServer!

---

Mike

Answer 13

Hi,

I had sort of this problem with SQL Server 2008 and did all things and wasted my times!  The problem was that I was entering MSSQLServer for the instanace name, where I should have entered the name of the computer!  Because thie instance was the default instance name and so it should be the name of the computer! Stupid SQL Server Team, it should be the instance name which is in windows services namely MSSQLServer!

---

Mike

http://sqlserver-help.com/2011/06/19/help-whats-my-sql-server-name/

---

Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
--------------------------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------------------------------------------------------------------
My Blog | Team Blog | @Twitter