Sense Code 080E0000 Trying to Connect to an AS/400

 Last reviewed: November 6, 1997
Article ID: Q163517
The information in this article applies to:
  • Microsoft SNA Server, versions 2.0, 2.1, 2.11, and 3.0

SYMPTOMS

Any attempt to connect to an AS/400 fails even when the appropriate device and controllers exist. The Windows NT Server Event Viewer Application log records the following event: 

   Event 18
   APPC session activation failure:
   BIND negative response or UNBIND request received
   Sense data   = 080E0000
The AS/400 will show a status on the line and the controller, but will not show a corresponding device, even if it has been created manually. If the device has not been created manually, the System Operator message queue on the AS/400 will record errors related to the creation of the device.

CAUSE

IBM implemented a directory search filter in OS/400 V3R2. This feature, if not properly configured, will reject connection attempts and will return the 080E0000 sense code.

MORE INFORMATION

The command WRKCFGL (Work with Configuration Lists) will have entries for the directory search filter. If a particular entry is set for *REJECT, it must be changed to *ACCEPT to allow connections.

The following IBM AS/400 book describes this feature in detail: 

  SC41-3300   Tips and Tools for securing the AS/400
The International Business Machines (IBM) products discussed here are manufactured by IBM a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

Additional query words: as400 as/400 appc
Keywords : snaappc kb3rdparty
Version : 2.0 2.1 2.11 3.0
Platform : WINDOWS

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