Не удалось запустить службу sql server код ошибки 1053

I am running Windows 7 32 bit and I have IIS, Visual Studio 2008, 2010 installed. I am haunted by this error in SQL Server 2008 which is:

Windows could not start the SQL Server (SQLEXPRESS) service on local computer. Error 1053: The service did not respond to the start or control request in a timely fashion

I have Googled and visited many other sites.

I have tried following:

• changed Account permission to Local System Account and no luck.
• uninstalled and re-installed: no luck.
• checked the port in Client Protocols and it is set 1433.
• added Network Service account to the Microsoft SQL Server folder in program files.

I cant check the log file because it doesn’t exist in the LOG folder of MS SQL folder.
I have changed registry information from fix articles about this issue but no luck from those sites.

It is really annoying because i installed SQL Server 2005 Express earlier and I got the same error message so that’s why I uninstalled this and decided to give SQL Server 2008 Express a go and I receive the same error.

This is really slowing me down because I have developed a lot of the web pages in my website and now I want to add functionality to the site and I need SQL Server and this has really stopped me from working.

Can someone help please? I really need to get this fixed i have tried everything that the sites provide in Google. If you require more information ill be glad to give you the feedback to get this solved as soon as possible.

I am running Windows 7 32 bit and I have IIS, Visual Studio 2008, 2010 installed. I am haunted by this error in SQL Server 2008 which is:

Windows could not start the SQL Server (SQLEXPRESS) service on local computer. Error 1053: The service did not respond to the start or control request in a timely fashion

I have Googled and visited many other sites.

I have tried following:

• changed Account permission to Local System Account and no luck.
• uninstalled and re-installed: no luck.
• checked the port in Client Protocols and it is set 1433.
• added Network Service account to the Microsoft SQL Server folder in program files.

I cant check the log file because it doesn’t exist in the LOG folder of MS SQL folder.
I have changed registry information from fix articles about this issue but no luck from those sites.

It is really annoying because i installed SQL Server 2005 Express earlier and I got the same error message so that’s why I uninstalled this and decided to give SQL Server 2008 Express a go and I receive the same error.

This is really slowing me down because I have developed a lot of the web pages in my website and now I want to add functionality to the site and I need SQL Server and this has really stopped me from working.

Can someone help please? I really need to get this fixed i have tried everything that the sites provide in Google. If you require more information ill be glad to give you the feedback to get this solved as soon as possible.

Error 1053 SQL server occurs when attempting to pause or stop the SQL Server service in the Windows Services Console.

Here at Bobcares, we have seen several such SQL related issues as part of our Server Management Services for web hosts and online service providers.

Today we’ll take a look at the cause for this error and how to fix it.

What causes error 1053 SQL server to occur

The Microsoft Windows Service Control Manager controls the start, stop, and pause state of all installed Windows services. If the system times out before the stop or pause has completed then this error occurs.

By default, the Service Control Manager waits for 30 seconds until a service responds. However, certain configurations, technical restrictions, or performance issues may delay the service to respond and may take longer than 30 seconds.

By editing or creating the ServicesPipeTimeout DWORD value, the Service Control Manager timeout period can be overridden, thereby giving the service more time to start up and report ready to the Service.

For instance, the error appears as below.

How we fix error 1053 SQL server

Here are a couple of steps that our Support Engineers provide to our customers to resolve this error.

1. Process monitor usage

• Run process monitor and then run SQL service from the command line (copy path and syntax from services properties)
  Find the file location in process monitor running as the service attempted to run
  C:WINDOWSWinSxSx86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.4053_x-ww_e69679MSVCP80.dll
• Open that directory and check whether file size and date for MSVCP80.dll is different than the one in SQL setup and install directory. Replace it.

2. Ending the process that is causing the error is the best solution to get rid of this error. Here are the steps to end the process.

• Initially, open the Windows Task Manager and go to the Processes tab
• Then select sqlservr.exe and click End Process
• When prompted to confirm that you wish to end the process, click End process

3. Restarting the computer is the easiest way to fix this error. After restarting attempt to stop the service again to test

4. The SQLServerAgent service startup account may not have the correct folder permissions that contain SQLAgent.out files.
In such cases, make sure that the 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.

5. Few executable .dll files may be corrupted or damaged.

In this case, try to start SQL Server Agent from the command prompt by running the following command:

For Default Instance

sqlagent -c -v

For 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

Then replace the SQLAgent.dll and SQLAgent.rll files with different copies of these files (SQLAgent.dll and SQLAgent.rll).

[Need any further assistance in fixing SQL errors? – We’re available 24*7]

Conclusion

In short, this error occurs when attempting to pause or stop the SQL Server service in the Windows Services Console. Today, we saw the resolution to this SQL error.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;