Fun Windows Service series & mdash; Windows Service Startup timeout, windows timeout

Fun Windows Service series-Windows Service Startup timeout and windows timeout

Recently, some customers reported that the data center was powered off and the database service failed to start itself after the server system was restarted. The first time this problem occurs, in order to check whether the database file is damaged due to power failure, the customer's server obtains the database log for analysis.

Database Working Mechanism

To analyze the cause of database startup failure, first describe the working mechanism of the database service.

Databases are divided into six major services:

Event ID 7022 suspended when the snapshot service starts.

There is an event ID and Event Description, Google, but no corresponding solution is found. There is no way, but it can only be analyzed from database logs.

Analyze the log again to see the following situation:

Go to the Windows Service series-create a Windows Service

How to register and uninstall the Debug and Release versions of the Windows Service series

Go to the Windows Service series -- Why Windows service fails to be started without the COM interface and the Solution

Go to the Windows Service series-analysis of service running and stopping Processes

Turn to the Windows Service series-Tips for Windows Services

Go to Windows Service series-command line management for Windows Services

Fun with Windows Service series-Windows Service Startup timeout

Windows Time Service cannot be started in windows 7.

I remember this situation when I used Windows 7. It seems that I don't need to worry about it. I closed this window. After you open it later, the synchronization will be displayed. I also saw manual synchronization.

Windows time cannot be started. The computer time cannot be synchronized.

Start rpc-related services, start Windows Time, And then synchronize.
How to start a service: Right-click my computer and choose manage. On the left-side menu, click Services under services and applications, and start Windows Time and Remote Procedure Call (RPC) on the right) remote Procedure Call (RPC) Locator. it is best to start DCOM Server Process Launcher and Application Management together, and set the Startup Type to automatic in their respective properties, which should solve the problem.