Author: Marita Gonsalves <marita_gonsalves AT CARYACADEMY.PVT.K12.NC DOT US>
Date: Mon, 3 Nov 1997 10:25:04 -0500
ANR9999D tcpcomm.c(373): No buffer space is available. The socket cannot be connected. Has anyone seen this message before? All the nodes in the backup schedule did not get backed up - they have a st
Author: Doug Thorneycroft <dthorneycroft AT LACSD DOT ORG>
Date: Mon, 3 Nov 1997 08:39:12 -0800
Im not an expert in communications, but It looks like you need to increase your TCPIP buffers, I think this is done to the TCPWindowsize in the Server Options. Also, do you have plenty of memory on t
Author: "Robinson, Cris" <Cris.Robinson AT LIBERTYMUTUAL DOT COM>
Date: Mon, 3 Nov 1997 13:44:47 -0500
I also get this message. I noticed it happening about the time we updated the server with ptf 3 on our NT server. I have 300MB of memory on my server with about 400 clients. The only way I can find t
We also have seen this problem. Have you reported this to IBM? We have an open problem with IBM, but they have not found the problem yet. IBM has asked us to run a server trace with systime and tcp e
Author: Doug Thorneycroft <dthorneycroft AT LACSD DOT ORG>
Date: Wed, 5 Nov 1997 14:01:06 -0800
May not be related to your problem, but thought I'd mention our experiance. We have two NT servers running MS SQL, that exibited simular symptoms to what you have been describing. Both these servers