Event Id | 17 |
Source | SNA Server |
Description | APPC session activation failure: BIND negative response sent. Sense data = <data> Connection = <connection> Session ID = <ID> LFSID = <ID>. |
Event Information | According to Microsoft: CAUSE: If the host Bind request does not contain an APPC mode name, and the SNA Server configuration does not specify one of the following: • If the Local APPC LU and the Remote APPC LU is not partnered with the "BLANK" mode name (the BLANK mode name needs to be reconfigured to support a single session for use as a mode for dependent LUs). -or- • If the Remote APPC LU does not have an Implicit Incoming Mode name defined. Then SNA Server will reject the bind request due to an unrecognized APPC mode name. The xx offset in the sense code may point to the Session Instance Identifier instead of the mode name, because the mode name is not present in the Bind request. Resolution: To solve the problem, define SNA Server appropriately to accept a Bind that does not contain an APPC mode name, using one of the methods described above. |
Reference Links | event id:17 and source:SNA SERVER |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.