| Author |
Message
|
| rk1891 |
 Posted: Thu Jun 14, 2012 6:34 am Post subject: Not able to access remote Q manager with rfhutilc |
 |
|
Apprentice
Joined: 12 Oct 2011
Posts: 42
|
Hi,
We've a queue manager(V7) on linux server that we are trying to connect from our local machines using rfhutilc ver#7.0.2.
One of us is able to connect by defining
MQSERVER=CHANNEL1/TCP/IP(1414) and launching the rfhutilc in a batch file.
The other user is not able to connect with the this error -
Queue manager not available (Connect) - may not be started
I don't think there are any access related issues since I'm able to connect and I insured that we both have identical group assgingments and stuff.
I did even took the trace files by setting -
SET RFHUTIL_VERBOSE_TRACE=1
SET RFHUTIL_TRACE_FILE=C:\RFHUtilTrace_local.txt
The trace file also did not provide much information except these lines -
| Quote: |
12-06-13:10.31.41 Entering DataArea::setErrorMsg() cc=2, rc=2059, operation=Connect
12-06-13:10.31.41 2059 Queue manager not available (Connect) - may not be started
12-06-13:10.31.41 General::UpdatePageData() pDoc->browseActive=0 pDoc->propertiesSupported=0
12-06-13:10.31.41 2059 Queue manager not available (Connect) - may not be started |
Are there any other obvious reasons that I'm missing here.
Thanks .. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Jun 14, 2012 6:54 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
A 2059 is the most common & the most insidious WMQ error.
Check that the failing user can connect using a command line application like amqsgetc from his machine & the problem is not that his location on the network can't access the queue manager and/or there's a firewall on his machine.
Then follow the diagnostic steps discussed in the huge number of posts in here on 2059 errors.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Jun 14, 2012 7:26 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
MQSERVER is a fairly crude way of going about matters.
Much better to use a CCDT.
No need for clumsy batch scripts then, rfhutilc will even show the list of queue managers (from the CCDT) in a pull down list. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 14, 2012 7:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zpat wrote: |
| Much better to use a CCDT. |
But even a CCDT doesn't fix connectivity problems.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| rk1891 |
| Posted: Thu Jun 14, 2012 7:50 am Post subject: |
|
|
Apprentice
Joined: 12 Oct 2011
Posts: 42
|
@vitor
when we issue
amqsgetc QName QMgr
it's failing with same 2059 error..
We could able to telnet to that IP and port. Not sure that other diagnostic tests to run..
@zpat
We don't have many qmgrs(in fact we've just one) that we access remotely..that is the reason why we did not go for CCDT. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 14, 2012 7:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rk1891 wrote: |
@vitor
when we issue
amqsgetc QName QMgr
it's failing with same 2059 error..
We could able to telnet to that IP and port. Not sure that other diagnostic tests to run.. |
Ok, so now you're in trouble..... 
Be sure that the MQSERVER variable is in the shell being used (I don't see how you could fail to do that but ....)
Check that when you telnet to that IP and port 1414 you see a) a blank screen because something's picked up the phone & b) an error in the log because the channel MCA was expecting a sender MCA and doesn't speak telnet.
If you don't get those, beat your network people until they confess.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| rk1891 |
| Posted: Thu Jun 14, 2012 9:52 am Post subject: |
|
|
Apprentice
Joined: 12 Oct 2011
Posts: 42
|
Vitor,
We did these two in the same command window. So I would think we are setting the MQSERVER correctly.
SET MQSERVER=CHANNEL1/TCP/IPAddress(1414)
amqsgetc TEST.RES.OUT WMB
Coming to the 'telnet IP portno' -
a)Blank screen and was timed out after some time
b)We see the below errors -
| Quote: |
----- amqrmrsa.c : 524 --------------------------------------------------------
06/14/2012 01:26:30 PM - Process(5480.315) User(mqm) Program(amqrmppa)
Host(hostname)
AMQ9259: Connection timed out from host 'IPAddress'.
EXPLANATION:
A connection from host 'IPAddress' over TCP/IP timed out.
ACTION:
The select() [TIMEOUT] 360 seconds call timed out. Check to see why data was
not received in the expected time. Correct the problem. Reconnect the channel,
or wait for a retrying channel to reconnect itself.
----- amqccita.c : 3788 -------------------------------------------------------
06/14/2012 01:26:30 PM - Process(5480.315) User(mqm) Program(amqrmppa)
Host(hostname)
AMQ9492: The TCP/IP responder program encountered an error.
EXPLANATION:
The responder program was started but detected an error.
ACTION:
Look at previous error messages in the error files to determine the error
encountered by the responder program.
----- amqrmrsa.c : 524 -------------------------------------------------------- |
I think that is what you are expecting to see..
On another note - From that Pc we could not access QMgr that is on my system also let alone linux server.
Definitely something got to do with that system only but what is it  |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 14, 2012 10:05 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rk1891 wrote: |
| I think that is what you are expecting to see.. |
I think you're right.
| rk1891 wrote: |
On another note - From that Pc we could not access QMgr that is on my system also let alone linux server.
Definitely something got to do with that system only but what is it |
I'd uninstall & reinstall the WMQ client.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jun 14, 2012 7:45 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
what do you see when you run dspmqver on the pc that does not work? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rk1891 |
| Posted: Fri Jun 15, 2012 5:59 am Post subject: |
|
|
Apprentice
Joined: 12 Oct 2011
Posts: 42
|
We've originally MQ6 server on that machine,later MQ7 client with explorer is installed.
Even at that time rfhutilc worked. Suddenly stopped working.
Thought that some problem with MQ7 client so uninstalled it, so now we've MQ6 server (along with 6 client,explorer.. based on reg entries below) on that machine.
Here are the results -
For dspmqver -
| Quote: |
Name: WebSphere MQ
Version: 6.0.0.0
CMVC level: p000-L050519
BuildType: IKAP - (Production) |
We went in reg entries to check other details,here is what we got-
| Quote: |
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\Components
Local Clients\Windows NT Client REG_SZ Installed
FTA_Client REG_SZ Installed
FTA_Server REG_SZ Installed
JavaMsg REG_SZ Installed
Server REG_SZ Installed
Development Toolkit REG_SZ Installed
XA_Client REG_SZ Installed
XA_Java REG_SZ Installed
Explorer REG_SZ Installed |
| Quote: |
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\Components
FilePath REG_SZ C:\IBM\MQ
ProductType REG_SZ Server
....and some other stuff |
Am I still missing something here..  |
|
| Back to top |
|
|
| rk1891 |
| Posted: Fri Jun 15, 2012 8:17 am Post subject: |
|
|
Apprentice
Joined: 12 Oct 2011
Posts: 42
|
No other ideas???  |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jun 15, 2012 8:47 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
This is almost a  version.
Upgrade to the latest fixpack or move up 1 or 2 versions...
You realize that you will be out of support by end of September?
Could be a myriad of things that were fixed in later fixpacks...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rk1891 |
| Posted: Fri Jun 15, 2012 9:10 am Post subject: |
|
|
Apprentice
Joined: 12 Oct 2011
Posts: 42
|
fjb-saper,
We do know that it is out-dated. We are on 7 everywhere except on our workstations..We are in process of upgrading our systems also.
My problem here is that it used to work on that machine and suddenly stopped working.
In fact,I also have 6.0 only on my machine and it is working fine.
We can do Upgrade/Uninstall and Reinstall..but I'm trying to know the problem here before I take those desperate steps. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jun 15, 2012 9:15 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rk1891 wrote: |
| We can do Upgrade/Uninstall and Reinstall..but I'm trying to know the problem here before I take those desperate steps. |
On Windows that's not desperate. That's the 2nd thing after switching it off & switching it on again. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jun 15, 2012 9:29 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| rk1891 wrote: |
My problem here is that it used to work on that machine and suddenly stopped working.
|
So what did you do in between. May be apply a windows update?
You cannot stay on an antiquated version of MQ and expect it to work fine while you are applying OS patches... Over time comes a moment where it will no longer work...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
