Event Error 2000 Logged Repeatedly Due to Illegal Command

 Last reviewed: July 25, 1997
Article ID: Q130120
3.50 WINDOWS kbnetwork kbbug3.50 kbfix3.50.sp2

The information in this article applies to:

  • Microsoft Windows NT Workstation version 3.5
  • Microsoft Windows NT Server version 3.5

SYMPTOMS

Windows NT file servers may log error 2000 in the event log with the following data: 

   0000: 00040000 00540001 00000000 c00007d0
   0010: 00000000 c000000d 00000000 00000000
   0020: 00000000 00000000 00000bcd

CAUSE

If a user application request is submitted illegally by a client application, the server logs the failure. The server is failing a SrvQueryBasicAndStandardInformation() call, with an "Invalid Parameter" status. The following commands result in the same error: 

   dir \\servername\ipc$
   dir \\servername\pipe

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.5. This problem was corrected in the latest US Service Pack for Windows NT. For information on obtaining this update, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K
SRV.SYS has been modified so that these messages are no longer logged and the smbs are discarded resulting in an application error.

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2
KBSubcategory: ntnetserv NTSrvWkst
Additional reference words: prodnt 3.50
Keywords : ntnetserv NTSrvWkst kbbug3.50 kbfix3.50.sp2 kbnetwork
Version : 3.50
Platform : WINDOWS
Issue type : kberrmsg
Solution Type : kbcode

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 25, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.