Event Log Opening Problem Causes Services.exe Failure

View products that this article applies to.

This article was previously published under Q178741

Expand all | Collapse all

SYMPTOMS

Windows NT server Services.exe may cause an access violation during an event log update. An "RPC Server is too busy..." message may appear, indicating that Services.exe failed. A Dr. Watson log may be written to the %SystemRoot% directory. Sessions provided by the server through NET USE may remain active. You may also be able to establish new sessions.

The following messages may be returned to client requests using RPC services:

Error 1723: The RPC server is too busy to complete this operation.

Back to the top

CAUSE

The pointer to the next event is miscalculated or the beginning of the log is corrupt and causing Services.exe to have an access violation. After Services.exe exits, other service wait indefinitely.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 (http://support.microsoft.com/kb/152734/EN-US/ ) How to Obtain the Latest Windows NT 4.0 Service Pack

Back to the top

STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

Back to the top