Windows Server

Jim Breit · Guest

I am using HIS 2004 on W2K3. Today one location with 10 terminals could not
establish any sessions. The following error showed in the event log:

TN3270E Service Message 529
Licensed session limit for IP address X.X.X.X has been exceeded.
EXPLANATION
A TN3270(E) client session was terminated abnormally.
ACTION
No action is necessary.

This only affected the users coming in on this one address. All other users
worked fine. The issue was finally fixed by restarting the TN3270 service. I
found an MS bulletin that mentioned a 2000 connection limit from one IP
address. This sounded promising but it applied to HIS 2000 and it was fixed
with a service pack. Is this still an issue with HIS 2004?

Charles Ezzell (MSFT) · Guest

I assume you are referring to http://support.microsoft.com/?id=814166. No it
is not an issue, but you have to add the registry entry that is mentioned in
the article.

Registry information:
Registry Location:
HKEY_LOCAL_MACHINE/system/currentcontrolset/services/tn3270/parameters
Registry Key: MaxSessionsPerUser
Registry Key Type: REG_DWORD
Default Value: 2000
Valid values: 256 - 30000

--
HTH,
Charles Ezzell
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Jim Breit" <Jim Breit@discussions.microsoft.com> wrote in message
news:3304C851-6627-49D9-A367-865327E920E2@microsoft.com...

Neil Pike · Guest

Jim,

The "fix" is probably in HIS2004, but for the fix to work you need to set the
registry entry I think.

Jim Breit · Guest

Thanks for the quick reply. Is there a way to monitor the number of sessions
per IP address? Is restarting the TN3270 service the only way to clear old
sessions?

"Charles Ezzell (MSFT)" wrote:

Charles Ezzell (MSFT) · Guest

You can sorta monitor with VBSscript, if you know the client's IP address.

*** BEGIN CUT ***
arrComputers = Array("CHARLIEE1")
For Each strComputer In arrComputers
WScript.Echo
WScript.Echo "=========================================="
WScript.Echo "Computer: " & strComputer
WScript.Echo "=========================================="

Set WmiLocator = CreateObject("WbemScripting.SWbemLocator")
Set objWMIService =
WmiLocator.ConnectServer(strComputer,"\root\MicrosoftHIS")
Set colItems = objWMIService.ExecQuery("SELECT * FROM
MsSnaStatus_TN3270Session WHERE Client = '65.53.5.54'")
WScript.Echo "Count = " & colItems.Count
For Each objItem in colItems
Wscript.Echo "-----------------------------------"
Wscript.Echo "MsSnaStatus_TN3270Session instance"
Wscript.Echo "-----------------------------------"
Wscript.Echo "Client: " & objItem.Client ' client IP address
Wscript.Echo "Name: " & objItem.Name ' lua name
Next
Next
*** END CUT ***
dumps out this:
==========================================
Computer: CHARLIEE1
==========================================
Count = 2
-----------------------------------
MsSnaStatus_TN3270Session instance
-----------------------------------
Client: 65.53.5.54
Name: SNA20002
-----------------------------------
MsSnaStatus_TN3270Session instance
-----------------------------------
Client: 65.53.5.54
Name: SNA20003

Old sessions clean up if they are disconnected properly. If the client is
not shutting down the sessions properly, then the port is left "in use".
This is part of how TCP/IP works. You can adjust our idle timeout value (in
the gui on the TN service properties), which would help, as TCP/IP has a 2
hour timer, which could leave a session "in use" for 4 hours (depending on
timing). IE: - after the idle timeout period (2 hour default), it checks to
see if any activity has happend on that session. If so, it does another
check in 2 hours. If a client sent data at the beginning of the initial
timeout window (say 5 seconds into it), then nothing for the remainder of
the time (or hit the big red "X" without properly disconnecting and the
application did not disconnect but closed down), we would NOT disconnect the
client at the 1st check. So, another 2 hours would go by, and then we would
disconnect. So, the client would have been inactive for 3 hours, 59 minutes
and 55 seconds. It's really up to the client application to shut down
properly, but the idle timeout adjustment is our way of ensuring the
customer can adjust this to their needs.

--
HTH,
Charles Ezzell
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Jim Breit" <JimBreit@discussions.microsoft.com> wrote in message
news:2C17D23A-C25A-4B4A-9D8D-12112E772EA8@microsoft.com...

Neil Pike · Guest

Jim,

	Windows Server Forum Index -> Host Integration Server	All times are GMT
Page 1 of 1