SNA Server Knowledge Base Articles
Back to the list.
SNA Server KB Article(s)   189">SNA Server?

1  ....  4  5  6  7  [ 8 ]  9  10  11  12  .... ....  115  116 
Previous Page    Page 8 of 116    Next Page



There are 1728 KB Article(s).

106) 6/26/2004 195010195010  195010.html">Activate_session/Deactivate_session Unavailable in SNA Server
(195010) - The following APPC verbs are not available for use with SNA Server: Activate_session Deactivate_session Please refer to the APPC Programmer's Guide included with the SNA Server Software Development Kit for information on the APPC verbs supported by...

107) 6/26/2004 186053186053  186053.html">Removing DLS Removes Application Event Log Registry Keys
(186053) - When you remove a Distributed Link Service from a computer running SNA Server 2.11 SP1 or SP2, or you remove a Distributed Link Service from a computer running SNA Server 3.0 (SP1, SP2, or SP3) that had been upgraded from 2.11 SP1 or SP2, the...

108) 6/26/2004 180868180868  180868.html">SFGW May Trap When Creating New Devices in SQL Manager
(180868) - When using SQL Manager to look for volumes to use for databases on a drive mounted by the Shared Folders Gateway (SFGW), Windows NT may generate a STOP 0x23 (FAT_FILE_SYSTEM) error.

109) 6/26/2004 180863180863  180863.html">Print Server May Experience Occasional Performance Degradation
(180863) - When a print job is sent to a printer attached to a workstation that has been unplugged from the network or has encountered a blue screen STOP screen, all SNA Server printer sessions start printing very slowly (for example, five minutes per page)...

110) 6/26/2004 180789180789  180789.html">Cancelling APPC RECEIVE_AND_POST Causes SNA Event ID 95
(180789) - The following event may occur when an APPC application cancels a [MC_]RECEIVE_AND_POST function by calling TP_ENDED: Source: SNA APPC Application Event ID: 95 Description: APPC given bad event handle or callback address 00000006 The following SNA...

111) 6/26/2004 177898177898  177898.html">Dragging LUs Between Pools of the Same Type Does Not Work
(177898) - When you drag LUs from either an LUA or Downstream LU pool to another pool of the same type, the operation fails, which causes an SNAOLE error to be generated indicating that the Target record already has an owner. NOTE: The same behavior can occur...

112) 6/26/2004 180701180701  180701.html">CPIC Application CMINIT May Stop on SNA Windows NT Client
(180701) - A Win32 CPIC application's call to Initialize_Conversation (CMINIT) may never complete on an SNA Server Windows NT client if the client is unable to communicate to the SNA Server.

113) 6/26/2004 180705180705  180705.html">APPC DISPLAY Call May Return AP_COMM_SUBSYSTEM_ABENDED.
(180705) - If a Win32 APPC application calls the SNA Server DISPLAY function to retrieve a list of all configured remote APPC LU's (in other words, sets the plu_def_info option), the following symptoms may occur: the DISPLAY call may return with the following...

114) 6/26/2004 182574182574  182574.html">Event 60, SNA Server Stops Forwarding FMH-5 Attach Messages
(182574) - SNA Server may unexpectedly stop forwarding FMH-5 Attach messages to a specific branch-based SNA Server client computer (where the invokable transaction program [TP] is registered or running). When this occurs, SNA Server reports an Event 60 (DLOAD...

115) 6/26/2004 177639177639  177639.html">Internal Error - Allocation Failed
(177639) - When you configure SNA Server Manager with more than 250 Local or Remote APPC LUs, an internal error in MngAgent (Event id: 5137) may be logged in the Windows NT event log. The entry in the event log indicates that MngAgent was unable to allocate any...

116) 6/26/2004 180415180415  180415.html">Sense Code in FMH-7 Message Is Not Returned to APPC Application
(180415) - There may be certain cases where an APPC or CPI-C application does not receive an error message sent to it by a remote application or host. LU 6.2 errors are generally reported across an LU 6.2 session or conversation by FMH-7 messages. If the error...

117) 6/26/2004 183238183238  183238.html">SNARAS Logs Events 101, 102, and 201 When Dialing Out
(183238) - An SNA Server using SNARAS may log the following errors in the Windows NT Application event log when dialing out to establish an SNARAS connection: Event ID: 101 Description: SNARAS - Bad in use count in correlator. Got 0x200000 expected 0x0. Event...

118) 6/26/2004 182266182266  182266.html">SNA APPC Event 93 Should Log Fully Qualified PLU Name
(182266) - If a CPIC or APPC application attempts to allocate a conversation and specifies a fully qualified Primary (that is, Remote) APPC LU name (instead of the Remote LU alias), and the allocation attempt fails, the SNA Server APPC interface logs Event 93,...

119) 6/26/2004 176432176432  176432.html">HOWTO: How to Determine if APPC LU Partnerships are Required
(176432) - When using SNA Server 3.0, which supports dynamic partnership of local and remote APPC LU's to an APPC mode (in other words, LU/LU/mode partnership), it's not necessary to preconfigure LU/LU/mode partnership in the SNA Server configuration file in...

120) 6/26/2004 178256178256  178256.html">LUA Program Hangs After Receiving Exception Request (EXR)
(178256) - An SNA Server LUA application may hang indefinately after receiving an exception request (EXR) message on a session, which SNA Server sends to the client after it has detected a bad RU in an outbound message from the host.


1  ....  4  5  6  7  [ 8 ]  9  10  11  12  .... ....  115  116 
Previous Page    Page 8 of 116    Next Page