Article ID: 908232
Article Last Modified on 12/4/2007
APPLIES TO
- Microsoft Host Integration Server 2004 Standard Edition
SYMPTOMS
When TN3270 emulators are connecting through the TN3270 server (Tn3servr.exe) to a host session, the TN3270 emulators may not reconnect automatically if the session ends because of inactivity. This problem occurs when Microsoft Host Integration Server 2004 is running on Microsoft Windows Server 2003.
When a TN3270 session ends because of inactivity, the following event message is logged:
Event ID: 603
Source: TN3270 Server
Description:
TN3270(E) session with client at TCP/IP Address (port TCP/IP port) using LU TN3270 LU Name terminated abnormally because: TN3270E Service Error 503 Session terminated due to inactivity.
Also, when you are using the TN3270 server that is included with Host Integration Server 2004, the following event message is logged fifteen seconds after the Event 603 message is logged:
Event ID: 902
Source: TN3270 Server
Description:
Logic error in module CompletionRoutineRead identified by: CompletionRoutineErrorNotZero
When the TN3270 server ends the session because of inactivity, you may receive the following error message in the TN3270 emulator window:
Note This message may not appear the same way in all TN3270 emulators.
CAUSE
After a TN3270 session ends because of inactivity, the TN3270 server expects to receive one of the following error messages when the TN3270 server calls the GetQueuedCompletionStatus function:
- ERROR_NETNAME_DELETED (error 64)
- ERROR_UNEXP_NET_ERR (error 59)
When the TN3270 server is running on Windows Server 2003, the TN3270 server receives the following error message in response to the GetQueuedCompletionStatus function call:
ERROR_CONNECTION_ABORTED (error 1236)
The TN3270 server does not expect to receive an Error 1236 error message after the TN3270 session ends because of inactivity. Therefore, the TN3270 server does not correctly release the TN3270 session for use.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ----------------------------------------------------- 11-Oct-2005 18:29 6.0.1990.0 241,664 Tn3servr.exe
Note Because of file dependencies, the most recent hotfix that contains these files may contain additional files.
WORKAROUND
To work around this problem, change the TN3270 server Idle timeout setting to Infinite. If you use this setting, the TN3270 server will not disconnect inactive TN3270 clients.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
This hotfix enables the TN3270 server to look for the ERROR_CONNECTION_ABORTED error that the GetQueuedCompletionStatus function returns when the TN3270 server is running on Windows Server 2003.
The following is an excerpt of a TN3270 server internal trace (Tn3int1.atf) that was captured when the problem occurred. The trace was captured by using the SNA Trace utility (SNATrace.exe).
The following is an excerpt of a TN3270 server internal trace that was captured when the problem did not occur. For this trace, Host Integration Server 2004 was running on Microsoft Windows 2000 Server Service Pack 4 (SP4).
Additional query words: HIS 2004
Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver kbhis2004 KB908232
