Author |
Message
|
AlainB |
Posted: Fri Jan 23, 2004 6:01 am Post subject: TCP problems ? |
|
|
 Voyager
Joined: 31 Oct 2002 Posts: 79 Location: Belgium
|
Hi all,
On an NT box, I'm having problems with channels. Since a few days, it's impossible to start a channel. The content of the error file is right below ... in french
Quote: |
-------------------------------------------------------------------------------
23/01/2004 14:40:50
AMQ9002: Canal lancé.
EXPLICATION :
Le canal 'BBWDEV89.BBDAKAR.RR' est lancé.
ACTION :
Aucune.
-------------------------------------------------------------------------------
23/01/2004 14:40:50
AMQ9212: Un socket TCP/IP n'a pas pu être alloué.
EXPLICATION :
Un socket TCP/IP n'a pas été créé, probablement suite à des incidents liés à la
mémoire.
ACTION :
Le code retour de l'appel TCP/IP (socket) était 10106 (X0). Relancez le
programme. Si l'incident persiste, notez les valeurs correspondantes et
communiquez-les à l'administrateur système.
-------------------------------------------------------------------------------
23/01/2004 14:40:50
AMQ9999: Arrêt anormal du canal.
EXPLICATION :
Le canal 'BBWDEV89.BBDAKAR.RR' s'est arrêté de manière anormale.
ACTION :
Lisez les précédents messages d'erreur relatifs au canal 'BBWDEV89.BBDAKAR.RR'
dans les journaux d'erreur, afin de déterminer la cause de l'incident.
-------------------------------------------------------------------------------
|
It's easy to understand : TCP-IP cannot alocate a socket, and error is 10106. Well, what's the problem, and how to solve this ? The network guys say everythings' OK with the network, the NT guys say the machine is running fine (well, as an NT can run) and my MQ users are saying it's not working. _________________ Alain Buret
Visit http://www.fosdem.org |
|
Back to top |
|
 |
Michael Dag |
Posted: Fri Jan 23, 2004 2:18 pm Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
Sure looks funny in french
What does the LOG say on the other end?
Can you telnet to the machine on the port that is listening?
(if all is well you should get a blank screen)
Michael |
|
Back to top |
|
 |
AlainB |
Posted: Sun Jan 25, 2004 2:35 am Post subject: |
|
|
 Voyager
Joined: 31 Oct 2002 Posts: 79 Location: Belgium
|
The LOG doesn't say anything on the other side ... and I can successfully telnet the port 1414 on the target host. IMO, I think it's a problem at OS level, but the NT guys are telling me that everything's fine ... _________________ Alain Buret
Visit http://www.fosdem.org |
|
Back to top |
|
 |
JasonE |
Posted: Sun Jan 25, 2004 12:47 pm Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
If it realy is 10106, and if it comes from the winsock api layer, this seems to me a more basic o/s issue too - Do a google search on '10106 winsock' - it shows it as WSAEPROVIDERFAILEDINIT
or from a command line:
C:\Documents and Settings\Administrator>net helpmsg 10106
The requested service provider could not be loaded or initialized. |
|
Back to top |
|
 |
AlainB |
Posted: Sun Jan 25, 2004 1:00 pm Post subject: |
|
|
 Voyager
Joined: 31 Oct 2002 Posts: 79 Location: Belgium
|
Thanks for info JasonE ... but if so, what's the solution if any to that problem ? _________________ Alain Buret
Visit http://www.fosdem.org |
|
Back to top |
|
 |
JasonE |
Posted: Sun Jan 25, 2004 3:21 pm Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
Never seen or heard of it myself. I read some hits on google about reloading the tcpip component giving mixed success, but aside from that I really dont have much of an idea. Have you tried a reboot (server side)?
You said it started a few days ago - was anything done to the machine? (Security patches, new service packs, virus, unexpected machine restart, new VPN software, etc)
If I was looking into this, I'd go for a trace to find out where the error comes from, but probably end up pointing you at Microsoft if it really is that return code from the place I expect it.
Is the server Windows 5.3? If so you could try disabling the thread pooling (MQNOREMPOOL=1 set in the SYSTEM environment variables) and see if it helps, but remove the env var if it makes no difference. |
|
Back to top |
|
 |
AlainB |
Posted: Sun Jan 25, 2004 11:34 pm Post subject: |
|
|
 Voyager
Joined: 31 Oct 2002 Posts: 79 Location: Belgium
|
Hi all,
First of all : it's an MQ 5.2 server (I know, it's no more supported, but here they don't care).
Second point : the "net helpmsg 10106" doesn't work, as it says :
Quote: |
Microsoft(R) Windows NT(TM)
(C) Copyright 1985-1996 Microsoft Corp.
V:\>net helpmsg 10106
10106 is not a valid Windows NT network message number.
More help is available by typing NET HELPMSG 3871.
V:\> |
The host where the problem occurs is a (stupid) windows NT 4 server. Ping, telnet, ... are working fine ... except MQ channels. I've also seen that the channel listener doesn't start automatically as a service, but start in foreground mode (in a console-dosbox). The only errors available in the NT eventlog are the following ones :
For the channel problem
Quote: |
A TCP/IP socket could not be allocated.
A TCP/IP socket could not be created, possibly because of a storage problem.
The return code from the TCP/IP (socket) call was 10106 (X'0'). Try the program again. If the failure persists, record the error values and tell the systems administrator. |
For the runmqlsr
Quote: |
A communications error for TCP/IP occurred.
An unexpected error occurred in communications.
The return code from the TCP/IP (socket) call was 0 (X'0'). Record these values and tell the systems administrator.
Unexpected return code, '20', from command 'RUNMQLSR -mBBWDEV89 -t"TCP" -p 1414 '.
An unexpected return code, '20', was returned by command 'RUNMQLSR -mBBWDEV89 -t"TCP" -p 1414 '. This command was issued by the MQSeries service for queue manager 'BBWDEV89'.
Verify that the command and parameters are correct.
Error code 0 starting BBWDEV89/Listener MQSeries service.
The MQSeries service was unable to start BBWDEV89/Listener. The error message reported was as follows:
The process has terminated with return code 20.
Use MQSeries Services to investigate why the service could not begin. If recovery for this service is active, MQSeries will attempt to recover. |
_________________ Alain Buret
Visit http://www.fosdem.org |
|
Back to top |
|
 |
JasonE |
Posted: Mon Jan 26, 2004 2:50 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
FYI net helpmsg is being improved on release to release of Windows - I ran it on XP, so thats probably why it didnt work. You can do net helpmsg for most Windows return codes nowdays.
It worries me that both the service and command line listeners are having problems!
I dont recognize the r/c 0 from the socket call in the listeners case though, but I still maintain the 10106 is pretty conclusive.
Did anything change on the machine when this problem started? eg. New security patch, change to machine settings etc.
You could try regmon and filemon (from www.sysinternals.com) covering the period of the failure and look for access denied type errors, in case it is security related.
5.2 eh? Not my prob anymore Unfortunately I dont think 5.3 would make any difference in this case as I still dont think its MQ related. |
|
Back to top |
|
 |
AlainB |
Posted: Mon Jan 26, 2004 4:24 am Post subject: |
|
|
 Voyager
Joined: 31 Oct 2002 Posts: 79 Location: Belgium
|
I know this was a strange problem : someone removed the freshly installed "Tivoli Monitoring" application, and after that no more problem !
Thanks to all for help. _________________ Alain Buret
Visit http://www.fosdem.org |
|
Back to top |
|
 |
JasonE |
Posted: Mon Jan 26, 2004 6:11 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
Thanks for that info - I've noted that into an internal database, so if anyone ever asks about that return code, we can look for that product |
|
Back to top |
|
 |
Francis |
Posted: Wed Oct 20, 2004 6:44 pm Post subject: |
|
|
Novice
Joined: 20 Oct 2004 Posts: 10
|
i met the same problem, but i don't know solve it?
does everybody solve this problem? |
|
Back to top |
|
 |
|