BUG: You receive the "service did not respond" error message when you start a Windows service (841713)
The information in this article applies to:
- Microsoft .NET Framework 1.0
SYMPTOMSWhen you try to start a Microsoft Windows service that is built on Microsoft .NET Framework 1.0 and whose AutoLog
property is set to True, the
Windows service may stop responding if the custom event log is full. Additionally, you may receive
the following error message: Could not start the
Service Name service on Local Computer. Error 1053: The service did not respond
to the start or control request in a timely fashion. The Service Name is the Windows service that you created by using Microsoft .NET Framework 1.0. CAUSEWhen the Windows service starts, the ServiceBase class writes
the event to the custom event log. If the custom event log is full, the
ServiceBase class tries to write the response to the custom event log when the OnStart
method is called. Because the custom event log is full, the OnStart method cannot write
the response to the custom event log file, and the ServiceBase class stops responding. Therefore, the Windows service indicates that the status is
Starting.RESOLUTIONTo resolve this problem, set the AutoLog property of the
Windows service to False.STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.REFERENCESFor more information, visit the following MSDN Web
site:
For additional information about how to create a Setup project, click the following article numbers to view the articles in the Microsoft Knowledge Base:
317421
How to create a Setup project for a Windows service in Visual Basic
.NET
816169 How to create a Setup project for a Windows service application in Visual C# .NET
Modification Type: | Major | Last Reviewed: | 5/26/2004 |
---|
Keywords: | kberrmsg kbSCM kbService kbEventLog kbbug KB841713 kbAudDeveloper |
---|
|