Microsoft KB Archive/839091

= Startup may take longer than usual and you may receive an &quot;At least one of services failed to start&quot; error message =

Article ID: 839091

Article Last Modified on 1/23/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)

-





Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
In Microsoft Windows Server 2003, startup may take longer than usual and you may receive the following error message:

At least one of services or driver failed during system startup. Use Event Viewer to examine the event log for details.

Note If Microsoft Background Intelligent Transfer Service (BITS) has any pending jobs, BITS will be set to automatically start at startup, and you may notice this behavior.



CAUSE
This behavior occurs because of a race condition. In Windows Server 2003, BITS depends on the EventSystem service. Therefore, if BITS starts before the EventSystem service starts, BITS tries to start the EventSystem service and then waits until the EventSystem service starts. However, even after the timeout period (typically, 80 seconds), if the EventSystem service does not start, the Service Control Manager (SCM) causes BITS to timeout and then adds a message in the event log. Then, you receive the &quot;At least one of services failed to start&quot; error message in the SCM that is mentioned in the &quot;Symptoms&quot; section. After you receive this error message, the EventSystem service may start, and BITS may enter the &quot;Running&quot; state. Because of this behavior, startup may take longer (typically, two minutes more) than usual.



RESOLUTION
To resolve this behavior, add the EventSystem service to the list of dependencies for BITS. If you add the EventSystem service to the list of dependencies for BITS, BITS will start only after the EventSystem service starts. To use the Service Control utility (Sc.exe) to add the EventSystem service to the list of dependencies for BITS, follow these steps:  Log on to your computer as an administrator. Click Start, and then click Run. The Run dialog box appears. In the Open box, type cmd, and then click OK. At the command prompt, run the following command:

sc config bits depend= rpcss/eventsystem

Note By default, in Windows Server 2003, the list of dependencies for BITS includes the RpcSs service. Therefore, when you run this command, you must specify &quot;rpcss&quot; as an OptionValue parameter for the depend OptionName parameter. To verify the contents of the list of dependencies for BITS, run the following command at the command prompt:

sc qc bits

Note This command will display the service settings for BITS. The list of dependencies is one of the service settings.</ol>

For more information about the changes that Sc.exe makes to your Windows registry if you run the command that is mentioned in step 4, see the &quot;Changes that Sc.exe makes to the Windows registry&quot; subsection of the &quot;More Information&quot; section.

<div class="status_section">

STATUS
This behavior is by design. This behavior does occur in Windows Server 2003 Service Pack 1 (SP1).

<div class="moreinformation_section">

BITS
BITS is a service that asynchronously transfers files between a client and an HTTP server. BITS transfers files in the background.

Changes that Sc.exe makes to the Windows registry
To add the EventSystem service to the list of dependencies for BITS, run the following command at the command prompt:

sc config bits depend= rpcss/eventsystem

When you run this command, Sc.exe changes the value of the following REG_MULT_SZ type registry entry:

The new value of this registry entry is as follows: rpcss Eventsystem Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

If you use Registry Editor to make these changes to your Windows registry, type one dependent service on each line in the Value data box of the Edit Multi-String dialog box.

Note If you use Registry Editor to make these changes, you must restart your computer for the changes to take effect.

<div class="references_section">