Microsoft KB Archive/229764

From BetaArchive Wiki
Knowledge Base


You receive a "System error 87 has occurred. The parameter is incorrect" error message on a computer that is running Windows NT

Article ID: 229764

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Server 4.0 Enterprise Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition



This article was previously published under Q229764

SYMPTOMS

When you type the following command at an MS-DOS command prompt on a computer running Windows NT with an Alpha processor:

NET PRINT //SERVER PrintJobID# /delete
                

The following error message is displayed:

System error 87 has occurred. The parameter is incorrect.

Error 87 can be any of the following:

End of tape (end of tape when not expected). From device: name
[QIC117]
Use a different tape.

Error 87 occurred adding user ' user name '. User information:
[PORTUAS]

Error 87 indicates that PortUAS encountered an invalid parameter. The user accounts database may be corrupted.
Contact technical support.

Error 87 occurred changing user ' user name '. User information:
[PORTUAS]

Error 87 indicates that PortUAS encountered an invalid parameter. The user accounts database may be corrupted.
Contact technical support.

Error Adding Adapter Information To The Registry


RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

  • 152734 How to obtain the latest Windows NT 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:



STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows NT version 4.0 Service Pack 5.

Keywords: kbbug kbfix KB229764