DISPLAY or CNOS Calls Fail with UNEXPECTED_DOS_ERROR

 Last reviewed: March 19, 1998
Article ID: Q170289

The information in this article applies to:

  • Microsoft SNA Server, versions 2.11 Service Pack 2 (SP2), 3.0, and 3.0 SP1

SYMPTOMS

When calling the DISPLAY or CNOS functions on Windows NT (over the SNA Server Windows NT client software), these functions may eventually fail with the following error: 

   primary_rc = 0xF011 (UNEXPECTED_DOS_ERROR)
   secondary_rc = 593 (internal error - maximum routing procs defined)
NOTE: The 593 secondary return code is shown in decimal. This corresponds to a hexadecimal value of 0x251, or in Intel dword format, 0x51020000.

CAUSE

This problem can occur when an APPC application calls WinAPPCStartup and WinAPPCCleanup a number of times without being terminated. The APPC library registers an internal routing procedure for each call to WinAPPCStartup, but fails to deregister the routing procedure when the application calls WinAPPCCleanup. This causes the internal routing procedure table to fill, leading to the above error.

STATUS

Microsoft has confirmed this to be a problem in SNA Server versions 2.11 SP2, 3.0, and 3.0 SP1. This problem was corrected in the latest SNA Server version 3.0 U.S. Service Pack. For information on obtaining this Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

Additional query words: SAS
Keywords : snaprog kbfix3.00.sp2 kbnetwork kbprg
Version : 2.11,3.0
Platform : winnt

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: March 19, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.