Startup may take longer than usual and you may receive an "At least one of services failed to start" error message (839091)
The information in this article applies to:
- the operating system: Microsoft Windows Server 2003
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 SYMPTOMSIn 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. CAUSEThis 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 "At least one
of services failed to start" error message in the SCM that is mentioned in the "Symptoms"
section. After you receive this error message, the EventSystem
service may start, and BITS may enter the "Running" state. Because of this behavior, startup may take longer (typically, two minutes more)
than usual.RESOLUTIONTo 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 "rpcss" 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:Note This command will display the service settings for BITS. The list
of dependencies is one of the service settings.
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
" Changes that Sc.exe makes to the Windows registry" subsection of the "More
Information" section. STATUS This
behavior is by design. This behavior does occur in
Windows Server 2003 Service Pack 1 (SP1).REFERENCES
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
818746
Background Intelligent Transfer Service in Windows Server 2003 white paper
331716 List of known issues for Background Intelligent Transfer Service (BITS)
For more information, visit the following Microsoft
Developer Network (MSDN) Web sites:
Modification Type: | Major | Last Reviewed: | 12/22/2004 |
---|
Keywords: | kbSCM kberrmsg kbServiceProcess kbService kbprb KB839091 kbAudEndUser |
---|
|