You are currently offline, waiting for your internet to reconnect

Event Log Opening Problem Causes Services.exe Failure

This article was previously published under Q178741
This article has been archived. It is offered "as is" and will no longer be updated.
Windows NT server Services.exe may cause an access violation during anevent 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 mayremain active. You may also be able to establish new sessions.

The following messages may be returned to client requests using RPCservices:

Error 1723: The RPC server is too busy to complete this operation.
The pointer to the next event is miscalculated or the beginning of the logis corrupt and causing Services.exe to have an access violation. AfterServices.exe exits, other service wait indefinitely.
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 theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

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.
drwtsn32.log system security application

Article ID: 178741 - Last Review: 02/24/2014 08:31:37 - Revision: 3.2

Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT Workstation 3.51 SP5, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT 3.51 Service Pack 5, Microsoft Windows NT Server 4.0 Standard Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug KB178741