A service does not start, and events 7000 and 7011 are logged_Windows Server 2008 R2

Symptoms

When you start a computer that is running Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2, a service does not start, and the following error events appear in the Application log:

Event 1

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000

The ServiceName service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

Event 2

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7011

Description:
Timeout (30000 milliseconds) waiting for a transaction response from the ServiceName service.

Event 3

Event Type: Error
Source: Service Control Manager
Event ID: 7009
Task Category: None

A timeout was reached (30000 milliseconds) while waiting for the ServiceName service to connect.

Workaround

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows

To work around this problem, modify the registry to increase the default time-out value for the service control manager. To increase this value to 60 seconds, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3. In the right pane, locate the ServicesPipeTimeout entry.
   
   Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
   1. On the Edit menu, point to New, and then click DWORD Value.
   2. Type ServicesPipeTimeout, and then press ENTER.
4. Right-click ServicesPipeTimeout, and then click Modify.
5. Click Decimal, type 60000, and then click OK.
   
   This value represents the time in milliseconds before a service times out.
6. Restart the computer.

Note This workaround may resolve the problem where the service does not start. However, we recommend that you research this problem to determine whether it is a symptom of another problem.

 

Source:

www.microsoft.com

 

Published By

S.G.Godwin Dinesh.MCA

Sr.System Administrator

My SQL -Hot copy

mysqlhotcopy

Format	Description
--addtodest	Do not rename target directory (if it exists); merely add files to it
--allowold	Do not abort if a target exists; rename it by adding an _old suffix
--checkpoint	Insert checkpoint entries
--chroot	Base directory of the chroot jail in which mysqld operates
--debug	Write debugging log
--dryrun	Report actions without performing them
--flushlog	Flush logs after all tables are locked
--help	Display help message and exit
--host	Connect to MySQL server on given host
--keepold	Do not delete previous (renamed) target when done
--method	The method for copying files
--noindices	Do not include full index files in the backup
--password	Password to use when connecting to server
--port	TCP/IP port number to use for connection
--quiet	Be silent except for errors
--regexp	Copy all databases with names that match the given regular expression
--resetmaster	Reset the binary log after locking all the tables
--resetslave	Reset the master.info file after locking all the tables
--socket	For connections to localhost, the Unix socket file to use
--tmpdir	The temporary directory
--user	MySQL user name to use when connecting to server