SNA server 4.0 problem

[tamibp]

We are working with SNA server and every 2 days we get the following message:

Connection to client 10.8.8.109:1096 has been aborted due to too many (100) pending writes.

EXPLANATION
SNA Server has aborted a TCP/IP connection because asynchronous writes queued on the connection have not completed.

ACTION
Provide network support personnel with the event log file(s) related to SNA, and SNA internal trace file(s). For information about SNA log and trace files, see the "Microsoft SNA Server Administration Guide."

Do you know what does it mean?

 

[Concepts2000]

You don't say if the target IP address runs the 3270 client, the 5250 client, an APPC app, or an LUA connection. This makes a difference. Also, I see from the IP address that you seem to be on a private IP network of some kind. Uhh - may I recommend that you NEVER EVER put an IP address in a public forum - even if the addres is private and firewalled.

 

[lring]

We are getting this same message as well as SNA Message Routing Error messages. I am working with Microsoft in resolving some of these issues now. I know we have some programmers that have written some "Screen Scraping" programs using Attachmate EXTRA! client. It appears that this is happening on the SNA Servers that run on Windows 2000 but not on our NT 4.0 boxes. Will keep you posted on our findings if you'd like.

 

[DaDukeOfEarl]

Tamibp, if you have and more info on your SNA problem:

Host Integration Server 2000 has aborted a TCP/IP connection because asynchronous writes queued on the connection have not completed.

Please let me know I seem to have this same problem.
I hope also to have Microsoft Support look at it but you know how that goes.

 

[Concepts2000]

Hi all:

(1) is the client connecting to HIS via sponsor connection or via TN3270??

(2) is the client connecting to the HIS server as a 5250? 3270? or as an LUA or LU 6.2 application of some flavor?

(3)what's your link service (SDLC, 802.2....)

(4) Yes, it makes a difference

(5) If it were me, and I was under the gun, and didn't want to research several potentially academic questions, I'd slap on HIS 2000 SP2 on the client and the server and see if the problem goes away. Yep. SP2 is out (March 2005 , I think) and we have it on one of our test servers - looks OK so far.

 

[DaDukeOfEarl]

I'm using a LU 6.2 application 802.2 and already have SP2 installed. also dual NICS are disabled. I think we are about ready to move to an IBM solution. this dropping our connection crap has got to go.