TN3270 disconnections and 'LU in use'
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
TN3270 disconnections and 'LU in use'

 
Post new topic   Reply to topic    Windows Server Forum Index -> Host Integration Server
Author Message
NATD
Guest





Posted: Sat Apr 09, 2005 1:46 pm    Post subject: TN3270 disconnections and 'LU in use' Reply with quote

Hi,

We have recently gone into production with new equipment which uses tn3270
compared to existing use which used 'Microsoft SNA'.

We're finding 3 problems:

1) unexplained (so far) disconnections
2) Inability to reconnect afterwards ("LU in use")
3) Inability to connect even whan the LU shows as available and hasn't
actually been used since a reboot ("LU in use" message)

I've pasted some events which relate to the issue;

Most are frequent. The terminals are a variety of PCs (Running the BlueZone
client), Wyse Winterms and IBM Netvistas. All work in general and if an LU is
refusing to work, it won't work from any device (ie I can't get it from my
own PC for troubleshooting):

When the client is being told 'LU in use', the SNA Manager can show it as
available. NetView shows it as ACTIVE and if I 'inact' and 'act' it, while
the status changes in SNA Manager, it still says 'in use' from the client.

Server: Windows Server 2003 (fully patched)
HIS: 2004 with one hotfix to resolve the problem with new tn3270 after a
config change.
Connection: DLC 802.2 via Token Ring.

Surely these have to be bugs? But I see no mention of it by searching Google
or Microsoft.com for the event IDs or any of the terms.

I hope someone here recognises the symptoms and can give me a hand!

NATD.


*Event Type: Warning
*Event Source: TN3270 Server
*Event Category: None
*Event ID: 902
*Date: 9/04/2005
*Time: 9:56:57 PM
*User: N/A
*Computer: AU-BU-HIS-1
*Description:
*Logic error in module CompletionRoutineRead identified by:
CompletionRoutineErrorNotZero
*
*EXPLANATION
*An unexpected logic error has occurred.
*
*ACTION
*Record message and contact technical support.


Event Type: Warning
Event Source: TN3270 Server
Event Category: None
Event ID: 902
Date: 9/04/2005
Time: 9:56:57 PM
User: N/A
Computer: AU-BU-HIS-1
Description:
Logic error in module CompletionRoutineRead identified by:
CompletionRoutineErrorNotZero

EXPLANATION
An unexpected logic error has occurred.

ACTION
Record message and contact technical support.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: d4 04 00 00 Ô...


Event Type: Error
Event Source: SNA Manage Agent
Event Category: None
Event ID: 5167
Date: 9/04/2005
Time: 8:40:53 PM
User: N/A
Computer: AU-BU-HIS-1
Description:
An internal error has occurred in the mngsna module - Dynamic update for
3270 LU failed.

Event Type: Warning
Event Source: TN3270 Server
Event Category: None
Event ID: 603
Date: 9/04/2005
Time: 6:16:27 PM
User: N/A
Computer: AU-BU-HIS-1
Description:
TN3270(E) session with client at 172.16.101.90 (port 1039) using LU <none>
terminated abnormally because:
02 Requested LU unavailable.

EXPLANATION
A TN3270(E) client session was terminated abnormally.

ACTION
No action is necessary.
Back to top
Paul Tykodi
Guest





Posted: Mon Apr 11, 2005 5:46 am    Post subject: Re: TN3270 disconnections and 'LU in use' Reply with quote

Hi,

Since you were using Microsoft SNA previously, one thing you might
want to consider would be to install the HIS Client software on
workstations needing access to the HIS server. The HIS Client converts
SNA traffice recognizable to an "SNA Aware" application (example 3270
terminal display application) into SNA wrapped inside TCP/IP for
transmission to the HIS server. This conversion makes the SNA traffic
more palatable to a typical TCP/IP network and also makes the Client
Workstation <--> HIS Server traffic routable via standard TCP/IP
methods as well.

From the description and messages in your posting, it appears that the
TN3270 service within HIS is losing the connection to some of the SNA
defined LU's it is woking with in a manner that prevents it from
recovering. To test this hypothesis, you could recycle the TN3270
Server Service (if the users could stand a short outage) to see
whether an LU in use becomes available again after simply recycling
this one HIS based process. If it does, you will at least know where
the problem is occurring in the Mainframe host to TN3270E Client
communication path.

HTH

Best Regards,

/Paul
--
Paul Tykodi
Principal Consultant
TCS - Tykodi Consulting Services LLC
E-mail: ptykodi@tykodi.com

On Sat, 9 Apr 2005 06:11:02 -0700, "NATD"
<NATD@discussions.microsoft.com> wrote:

Quote:
Hi,

We have recently gone into production with new equipment which uses tn3270
compared to existing use which used 'Microsoft SNA'.

We're finding 3 problems:

1) unexplained (so far) disconnections
2) Inability to reconnect afterwards ("LU in use")
3) Inability to connect even whan the LU shows as available and hasn't
actually been used since a reboot ("LU in use" message)

I've pasted some events which relate to the issue;

Most are frequent. The terminals are a variety of PCs (Running the BlueZone
client), Wyse Winterms and IBM Netvistas. All work in general and if an LU is
refusing to work, it won't work from any device (ie I can't get it from my
own PC for troubleshooting):

When the client is being told 'LU in use', the SNA Manager can show it as
available. NetView shows it as ACTIVE and if I 'inact' and 'act' it, while
the status changes in SNA Manager, it still says 'in use' from the client.

Server: Windows Server 2003 (fully patched)
HIS: 2004 with one hotfix to resolve the problem with new tn3270 after a
config change.
Connection: DLC 802.2 via Token Ring.

Surely these have to be bugs? But I see no mention of it by searching Google
or Microsoft.com for the event IDs or any of the terms.

I hope someone here recognises the symptoms and can give me a hand!

NATD.


*Event Type: Warning
*Event Source: TN3270 Server
*Event Category: None
*Event ID: 902
*Date: 9/04/2005
*Time: 9:56:57 PM
*User: N/A
*Computer: AU-BU-HIS-1
*Description:
*Logic error in module CompletionRoutineRead identified by:
CompletionRoutineErrorNotZero
*
*EXPLANATION
*An unexpected logic error has occurred.
*
*ACTION
*Record message and contact technical support.


Event Type: Warning
Event Source: TN3270 Server
Event Category: None
Event ID: 902
Date: 9/04/2005
Time: 9:56:57 PM
User: N/A
Computer: AU-BU-HIS-1
Description:
Logic error in module CompletionRoutineRead identified by:
CompletionRoutineErrorNotZero

EXPLANATION
An unexpected logic error has occurred.

ACTION
Record message and contact technical support.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: d4 04 00 00 Ô...


Event Type: Error
Event Source: SNA Manage Agent
Event Category: None
Event ID: 5167
Date: 9/04/2005
Time: 8:40:53 PM
User: N/A
Computer: AU-BU-HIS-1
Description:
An internal error has occurred in the mngsna module - Dynamic update for
3270 LU failed.

Event Type: Warning
Event Source: TN3270 Server
Event Category: None
Event ID: 603
Date: 9/04/2005
Time: 6:16:27 PM
User: N/A
Computer: AU-BU-HIS-1
Description:
TN3270(E) session with client at 172.16.101.90 (port 1039) using LU <none
terminated abnormally because:
02 Requested LU unavailable.

EXPLANATION
A TN3270(E) client session was terminated abnormally.

ACTION
No action is necessary.

Back to top
NATD
Guest





Posted: Mon Apr 11, 2005 1:46 pm    Post subject: Re: TN3270 disconnections and 'LU in use' Reply with quote

Thanks Paul for the reply.

I'm aware of the MS SNA option on a Windows PC, but the reason we are also
using tn3270 is for devices which don't support anything else.

While I'll still watch for more replies here, I have opted to open a support
case as this problem isn't something we can tollerate for too long.

Thanks,

NATD.
Back to top
Dwayne
Guest





Posted: Tue Apr 12, 2005 12:18 am    Post subject: Re: TN3270 disconnections and 'LU in use' Reply with quote

I was having a almost the same problem as you and this group pointed me to
here, which after I made the changes to the registry helped a great deal
with my clients disconnects.

http://support.microsoft.com/default.aspx?scid=kb;en-us;183786

I set the KeepAliveTime to 90000 decimal as suggested by one of the HIS
group members.


"NATD" <NATD@discussions.microsoft.com> wrote in message
news:C0AF2078-2526-4F02-B362-03A3A1FE96C0@microsoft.com...
Quote:
Thanks Paul for the reply.

I'm aware of the MS SNA option on a Windows PC, but the reason we are also
using tn3270 is for devices which don't support anything else.

While I'll still watch for more replies here, I have opted to open a
support
case as this problem isn't something we can tollerate for too long.

Thanks,

NATD.
Back to top
NATD
Guest





Posted: Tue Apr 12, 2005 1:47 pm    Post subject: Re: TN3270 disconnections and 'LU in use' Reply with quote

Thanks Dwayne.

That does look useful but can you tell me this (I think the wording isn't
clear).

Does setting this GENERATE a keep alive yet let tn3270 know when the client
has died?

The settign in HIS is no use to me because we need long idle times - we have
many customer facing terminals where a session might not get used for an hour
or so, but if the next customer in the queue asks for something needing that
session, it has to be ready.

Does the registry key above mean that the session stays alive if the client
is still running, but HIS times out if a problem occurs?
Back to top
Paul Tykodi
Guest





Posted: Wed Apr 13, 2005 7:16 pm    Post subject: Re: TN3270 disconnections and 'LU in use' Reply with quote

Hi,

From your initial posting, it sounds like your network looks like
this:

Mainframe Computer --> Token Ring DLC protocol - SNA traffic --> PC
Server Running Windows 2003 and Microsoft HIS configured to offer
TN3270E LU's for clients to use --> Ethernet TCP/IP to TN3270 or
TN3270E clients.

The Microsoft knowledgebase article is mentioning one of the problems,
which can be encountered when using TN3270, TN3270E, TN5250, or
TN5250E clients, to support communication with an IBM z Series or
iSeries host as opposed to SNA communication. The problem is not
unique to Microsoft but is a function of the TN3270, TN3270E, TN5250,
TN5250E protocol implementations.

When some form of unexpected connection failure occurs between a
TCP/IP enabled TN3270E or TN5250E server and a TCP/IP enabled
TN3270(E) or TN5250(E) client, the client will generally always
realize the connection has failed and the server will quite often not
realize the connection has failed for quite a long period of time.
Until the server realizes the connection has failed, a phantom session
still running at the server will block all attempts to reconnect to
the LU serviced by the phantom session.

The Microsoft knowledgebase article describes the two documented
methods contained in one of the TN3270E RFC's to provide knowledge of
an unexpected connection failure to a server. The Microsoft article
then explains that the server based recovery capability, to determine
an unexpected communication failure has occurred, is set to a default
of 2 hours (phantom session blocking reconnection would last for 2
hours before the server would clean it up) and that the value can be
changed through editing the registry.

While changing the default recovery timeout could probably be useful
to your situation, you probably need to discover the cause of the
unexpected communication failures as well.

With the long periods of inactivity that you mentioned in your
follow-up posting, any need to traverse a firewall between the HIS
server and a TN3270(E) client will most likely result in the errors
you have trapped. The reason is that there are two TCP socket
connections, which need to be available for a successful TN3270E
server <---> TN3270(E) client communication. One socket connection is
enabled at the client and is pointed towards a fixed TCP port on the
server (if you followed Microsoft suggestion for TN3270E support,
probably TCP port 24). Once a connection is established by the client
to the server, the server opens a second TCP socket connection from
itself back to the client. The ports for this second connection are
not pre-defined. They are established at the time the session is
initially started and remain in force for the duration of the client
initiated session. Unfortunately during long periods of inactivity,
firewalls will frequently cancel both of the socket connections. This
is not really much of a problem for the client as it can successfully
re-establish a connection to the server via the firewall when it has
information to transmit. Unfortunately the server will be unable to
re-establish its session based return socket connection through the
firewall once it is cancelled and the whole session at the server must
be terminated and a new session started on the server to re-establish
a successful TCP socket connection through the firewall.

Usually firewalls have tuning parameters that can be adjusted to allow
TN3270(E) and TN5250(E) communications to remain active though this
sometimes requires enabling the keepalive packets between server and
client to keep the firewall happy.

HTH

Best Regards,

/Paul
--
Paul Tykodi
Principal Consultant
TCS - Tykodi Consulting Services LLC
E-mail: ptykodi@tykodi.com


On Tue, 12 Apr 2005 05:51:04 -0700, "NATD"
<NATD@discussions.microsoft.com> wrote:

Quote:
Thanks Dwayne.

That does look useful but can you tell me this (I think the wording isn't
clear).

Does setting this GENERATE a keep alive yet let tn3270 know when the client
has died?

The settign in HIS is no use to me because we need long idle times - we have
many customer facing terminals where a session might not get used for an hour
or so, but if the next customer in the queue asks for something needing that
session, it has to be ready.

Does the registry key above mean that the session stays alive if the client
is still running, but HIS times out if a problem occurs?
Back to top
Charles Ezzell (MSFT)
Guest





Posted: Fri Apr 15, 2005 5:46 am    Post subject: Re: TN3270 disconnections and 'LU in use' Reply with quote

Matthew,

This is going to require tn3270 traces (and probably a network sniff) to
resolve the problem. Please contact PSS and be ready to do the traces in
order to resolve the problem. The problem is some type of <unknown> network
error that is happening. Without tracing and a sniff, we will not be able to
resolve the problem.

Thanks,
Charles

"R. Matthew Cole" <R. Matthew Cole@discussions.microsoft.com> wrote in
message news:8D1C0CC3-A220-4970-90BD-B52607632B0D@microsoft.com...
Quote:
Have you found a resolution to this problem? We are having a similar
issue.
We are using a HIS 2004 box that have the sessions set to log off and log
on
every 24 hours to keep the sessions from expiring on the host. This has
been
in production for some time without any issues. We only started having
problems after applying SP1 for Windows 2003 on the HIS server. Ever since
the host connection dies with the following error:

Event Type: Warning
Event Source: TN3270 Server
Event Category: None
Event ID: 902
Date: 4/12/2005
Time: 10:52:12 PM
User: N/A
Computer: PIPC3
Description:
Logic error in module CompletionRoutineRead identified by:
CompletionRoutineErrorNotZero

EXPLANATION
An unexpected logic error has occurred.

ACTION
Record message and contact technical support.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: d4 04 00 00 Ô...

We can temporarly work around the solution by rebooting the client machine
that is talking to the HIS box, or by stopping and restarting the SNA
services on the HIS box itself. Is your machine running 2003 SP1?

"NATD" wrote:

Hi,

We have recently gone into production with new equipment which uses
tn3270
compared to existing use which used 'Microsoft SNA'.

We're finding 3 problems:

1) unexplained (so far) disconnections
2) Inability to reconnect afterwards ("LU in use")
3) Inability to connect even whan the LU shows as available and hasn't
actually been used since a reboot ("LU in use" message)

I've pasted some events which relate to the issue;

Most are frequent. The terminals are a variety of PCs (Running the
BlueZone
client), Wyse Winterms and IBM Netvistas. All work in general and if an
LU is
refusing to work, it won't work from any device (ie I can't get it from
my
own PC for troubleshooting):

When the client is being told 'LU in use', the SNA Manager can show it as
available. NetView shows it as ACTIVE and if I 'inact' and 'act' it,
while
the status changes in SNA Manager, it still says 'in use' from the
client.

Server: Windows Server 2003 (fully patched)
HIS: 2004 with one hotfix to resolve the problem with new tn3270 after a
config change.
Connection: DLC 802.2 via Token Ring.

Surely these have to be bugs? But I see no mention of it by searching
Google
or Microsoft.com for the event IDs or any of the terms.

I hope someone here recognises the symptoms and can give me a hand!

NATD.


*Event Type: Warning
*Event Source: TN3270 Server
*Event Category: None
*Event ID: 902
*Date: 9/04/2005
*Time: 9:56:57 PM
*User: N/A
*Computer: AU-BU-HIS-1
*Description:
*Logic error in module CompletionRoutineRead identified by:
CompletionRoutineErrorNotZero
*
*EXPLANATION
*An unexpected logic error has occurred.
*
*ACTION
*Record message and contact technical support.


Event Type: Warning
Event Source: TN3270 Server
Event Category: None
Event ID: 902
Date: 9/04/2005
Time: 9:56:57 PM
User: N/A
Computer: AU-BU-HIS-1
Description:
Logic error in module CompletionRoutineRead identified by:
CompletionRoutineErrorNotZero

EXPLANATION
An unexpected logic error has occurred.

ACTION
Record message and contact technical support.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: d4 04 00 00 Ô...


Event Type: Error
Event Source: SNA Manage Agent
Event Category: None
Event ID: 5167
Date: 9/04/2005
Time: 8:40:53 PM
User: N/A
Computer: AU-BU-HIS-1
Description:
An internal error has occurred in the mngsna module - Dynamic update for
3270 LU failed.

Event Type: Warning
Event Source: TN3270 Server
Event Category: None
Event ID: 603
Date: 9/04/2005
Time: 6:16:27 PM
User: N/A
Computer: AU-BU-HIS-1
Description:
TN3270(E) session with client at 172.16.101.90 (port 1039) using LU
none
terminated abnormally because:
02 Requested LU unavailable.

EXPLANATION
A TN3270(E) client session was terminated abnormally.

ACTION
No action is necessary.


Back to top
Charles Ezzell (MSFT)
Guest





Posted: Fri Apr 15, 2005 1:46 pm    Post subject: Re: TN3270 disconnections and 'LU in use' Reply with quote

Paul hit the nail on the head.


"Paul Tykodi" <ptykodi@yahoo.com> wrote in message
news:oj8q51p6m3dpm5nj6q2ipal4i65ebq47l5@4ax.com...
Quote:
Hi,

From your initial posting, it sounds like your network looks like
this:

Mainframe Computer --> Token Ring DLC protocol - SNA traffic --> PC
Server Running Windows 2003 and Microsoft HIS configured to offer
TN3270E LU's for clients to use --> Ethernet TCP/IP to TN3270 or
TN3270E clients.

The Microsoft knowledgebase article is mentioning one of the problems,
which can be encountered when using TN3270, TN3270E, TN5250, or
TN5250E clients, to support communication with an IBM z Series or
iSeries host as opposed to SNA communication. The problem is not
unique to Microsoft but is a function of the TN3270, TN3270E, TN5250,
TN5250E protocol implementations.

When some form of unexpected connection failure occurs between a
TCP/IP enabled TN3270E or TN5250E server and a TCP/IP enabled
TN3270(E) or TN5250(E) client, the client will generally always
realize the connection has failed and the server will quite often not
realize the connection has failed for quite a long period of time.
Until the server realizes the connection has failed, a phantom session
still running at the server will block all attempts to reconnect to
the LU serviced by the phantom session.

The Microsoft knowledgebase article describes the two documented
methods contained in one of the TN3270E RFC's to provide knowledge of
an unexpected connection failure to a server. The Microsoft article
then explains that the server based recovery capability, to determine
an unexpected communication failure has occurred, is set to a default
of 2 hours (phantom session blocking reconnection would last for 2
hours before the server would clean it up) and that the value can be
changed through editing the registry.

While changing the default recovery timeout could probably be useful
to your situation, you probably need to discover the cause of the
unexpected communication failures as well.

With the long periods of inactivity that you mentioned in your
follow-up posting, any need to traverse a firewall between the HIS
server and a TN3270(E) client will most likely result in the errors
you have trapped. The reason is that there are two TCP socket
connections, which need to be available for a successful TN3270E
server <---> TN3270(E) client communication. One socket connection is
enabled at the client and is pointed towards a fixed TCP port on the
server (if you followed Microsoft suggestion for TN3270E support,
probably TCP port 24). Once a connection is established by the client
to the server, the server opens a second TCP socket connection from
itself back to the client. The ports for this second connection are
not pre-defined. They are established at the time the session is
initially started and remain in force for the duration of the client
initiated session. Unfortunately during long periods of inactivity,
firewalls will frequently cancel both of the socket connections. This
is not really much of a problem for the client as it can successfully
re-establish a connection to the server via the firewall when it has
information to transmit. Unfortunately the server will be unable to
re-establish its session based return socket connection through the
firewall once it is cancelled and the whole session at the server must
be terminated and a new session started on the server to re-establish
a successful TCP socket connection through the firewall.

Usually firewalls have tuning parameters that can be adjusted to allow
TN3270(E) and TN5250(E) communications to remain active though this
sometimes requires enabling the keepalive packets between server and
client to keep the firewall happy.

HTH

Best Regards,

/Paul
--
Paul Tykodi
Principal Consultant
TCS - Tykodi Consulting Services LLC
E-mail: ptykodi@tykodi.com


On Tue, 12 Apr 2005 05:51:04 -0700, "NATD"
NATD@discussions.microsoft.com> wrote:

Thanks Dwayne.

That does look useful but can you tell me this (I think the wording isn't
clear).

Does setting this GENERATE a keep alive yet let tn3270 know when the
client
has died?

The settign in HIS is no use to me because we need long idle times - we
have
many customer facing terminals where a session might not get used for an
hour
or so, but if the next customer in the queue asks for something needing
that
session, it has to be ready.

Does the registry key above mean that the session stays alive if the
client
is still running, but HIS times out if a problem occurs?
Back to top
NATD
Guest





Posted: Tue Apr 19, 2005 5:50 am    Post subject: RE: TN3270 disconnections and 'LU in use' Reply with quote

Matthew,

If you haven't already, can I encourage you to open a call with MS on this
issue. If it is something in sp1 then the more they see it form various
customers, the better chance they have of identifing if it is a product bug,
as opposed to some condition causing it on the customer side. I have a call
open, and I suspect they will quickly link the fact that I have this even
cropping up regularly (I'm on 2k3 sp1) and the fact that you only started
getting them after applying sp1.

NATD.

"R. Matthew Cole" wrote:

Quote:
Have you found a resolution to this problem? We are having a similar issue.
We are using a HIS 2004 box that have the sessions set to log off and log on
every 24 hours to keep the sessions from expiring on the host. This has been
in production for some time without any issues. We only started having
problems after applying SP1 for Windows 2003 on the HIS server. Ever since
the host connection dies with the following error:

Event Type: Warning
Event Source: TN3270 Server
Event Category: None
Event ID: 902
Date: 4/12/2005
Time: 10:52:12 PM
User: N/A
Computer: PIPC3
Description:
Logic error in module CompletionRoutineRead identified by:
CompletionRoutineErrorNotZero

EXPLANATION
An unexpected logic error has occurred.

ACTION
Record message and contact technical support.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: d4 04 00 00 Ô...

We can temporarly work around the solution by rebooting the client machine
that is talking to the HIS box, or by stopping and restarting the SNA
services on the HIS box itself. Is your machine running 2003 SP1?

"NATD" wrote:

Hi,

We have recently gone into production with new equipment which uses tn3270
compared to existing use which used 'Microsoft SNA'.

We're finding 3 problems:

1) unexplained (so far) disconnections
2) Inability to reconnect afterwards ("LU in use")
3) Inability to connect even whan the LU shows as available and hasn't
actually been used since a reboot ("LU in use" message)

I've pasted some events which relate to the issue;

Most are frequent. The terminals are a variety of PCs (Running the BlueZone
client), Wyse Winterms and IBM Netvistas. All work in general and if an LU is
refusing to work, it won't work from any device (ie I can't get it from my
own PC for troubleshooting):

When the client is being told 'LU in use', the SNA Manager can show it as
available. NetView shows it as ACTIVE and if I 'inact' and 'act' it, while
the status changes in SNA Manager, it still says 'in use' from the client.

Server: Windows Server 2003 (fully patched)
HIS: 2004 with one hotfix to resolve the problem with new tn3270 after a
config change.
Connection: DLC 802.2 via Token Ring.

Surely these have to be bugs? But I see no mention of it by searching Google
or Microsoft.com for the event IDs or any of the terms.

I hope someone here recognises the symptoms and can give me a hand!

NATD.


*Event Type: Warning
*Event Source: TN3270 Server
*Event Category: None
*Event ID: 902
*Date: 9/04/2005
*Time: 9:56:57 PM
*User: N/A
*Computer: AU-BU-HIS-1
*Description:
*Logic error in module CompletionRoutineRead identified by:
CompletionRoutineErrorNotZero
*
*EXPLANATION
*An unexpected logic error has occurred.
*
*ACTION
*Record message and contact technical support.


Event Type: Warning
Event Source: TN3270 Server
Event Category: None
Event ID: 902
Date: 9/04/2005
Time: 9:56:57 PM
User: N/A
Computer: AU-BU-HIS-1
Description:
Logic error in module CompletionRoutineRead identified by:
CompletionRoutineErrorNotZero

EXPLANATION
An unexpected logic error has occurred.

ACTION
Record message and contact technical support.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: d4 04 00 00 Ô...


Event Type: Error
Event Source: SNA Manage Agent
Event Category: None
Event ID: 5167
Date: 9/04/2005
Time: 8:40:53 PM
User: N/A
Computer: AU-BU-HIS-1
Description:
An internal error has occurred in the mngsna module - Dynamic update for
3270 LU failed.

Event Type: Warning
Event Source: TN3270 Server
Event Category: None
Event ID: 603
Date: 9/04/2005
Time: 6:16:27 PM
User: N/A
Computer: AU-BU-HIS-1
Description:
TN3270(E) session with client at 172.16.101.90 (port 1039) using LU <none
terminated abnormally because:
02 Requested LU unavailable.

EXPLANATION
A TN3270(E) client session was terminated abnormally.

ACTION
No action is necessary.


Back to top
lsring@hotmail.com
Guest





Posted: Wed Apr 27, 2005 6:15 am    Post subject: RE: TN3270 disconnections and 'LU in use' Reply with quote

This looks bothersome. Is this unique to HIS 2004? We are using HIS 2000 and
are getting ready to upgrade to HIS 2004. We will have issues with this in
our environment.

"NATD" wrote:

Quote:
Hi,

We have recently gone into production with new equipment which uses tn3270
compared to existing use which used 'Microsoft SNA'.

We're finding 3 problems:

1) unexplained (so far) disconnections
2) Inability to reconnect afterwards ("LU in use")
3) Inability to connect even whan the LU shows as available and hasn't
actually been used since a reboot ("LU in use" message)

I've pasted some events which relate to the issue;

Most are frequent. The terminals are a variety of PCs (Running the BlueZone
client), Wyse Winterms and IBM Netvistas. All work in general and if an LU is
refusing to work, it won't work from any device (ie I can't get it from my
own PC for troubleshooting):

When the client is being told 'LU in use', the SNA Manager can show it as
available. NetView shows it as ACTIVE and if I 'inact' and 'act' it, while
the status changes in SNA Manager, it still says 'in use' from the client.

Server: Windows Server 2003 (fully patched)
HIS: 2004 with one hotfix to resolve the problem with new tn3270 after a
config change.
Connection: DLC 802.2 via Token Ring.

Surely these have to be bugs? But I see no mention of it by searching Google
or Microsoft.com for the event IDs or any of the terms.

I hope someone here recognises the symptoms and can give me a hand!

NATD.


*Event Type: Warning
*Event Source: TN3270 Server
*Event Category: None
*Event ID: 902
*Date: 9/04/2005
*Time: 9:56:57 PM
*User: N/A
*Computer: AU-BU-HIS-1
*Description:
*Logic error in module CompletionRoutineRead identified by:
CompletionRoutineErrorNotZero
*
*EXPLANATION
*An unexpected logic error has occurred.
*
*ACTION
*Record message and contact technical support.


Event Type: Warning
Event Source: TN3270 Server
Event Category: None
Event ID: 902
Date: 9/04/2005
Time: 9:56:57 PM
User: N/A
Computer: AU-BU-HIS-1
Description:
Logic error in module CompletionRoutineRead identified by:
CompletionRoutineErrorNotZero

EXPLANATION
An unexpected logic error has occurred.

ACTION
Record message and contact technical support.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: d4 04 00 00 Ô...


Event Type: Error
Event Source: SNA Manage Agent
Event Category: None
Event ID: 5167
Date: 9/04/2005
Time: 8:40:53 PM
User: N/A
Computer: AU-BU-HIS-1
Description:
An internal error has occurred in the mngsna module - Dynamic update for
3270 LU failed.

Event Type: Warning
Event Source: TN3270 Server
Event Category: None
Event ID: 603
Date: 9/04/2005
Time: 6:16:27 PM
User: N/A
Computer: AU-BU-HIS-1
Description:
TN3270(E) session with client at 172.16.101.90 (port 1039) using LU <none
terminated abnormally because:
02 Requested LU unavailable.

EXPLANATION
A TN3270(E) client session was terminated abnormally.

ACTION
No action is necessary.


Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> Host Integration Server All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB