| Author |
Message
|
| drodrick |
 Posted: Wed Dec 26, 2012 7:19 am Post subject: AMQ4059 issue on Windows 7, 64 bits |
 |
|
Novice
Joined: 26 Dec 2012
Posts: 17
|
Hi All,
I am trying to connect an MQ V7 queue manager installed on my Windows 7, 64 bit laptop, thru client connection using MQ Explorer. I need it to test compatibility of MQ V7 to our some of the applications, before we get our Linux servers built after couple of months.
I have installed MQ V7 ver 7.0.0.0 Server on my laptop.
Whenever I try to connect it thru MQ Explorer in a client connection by specifying my computer name port no and SVRCONN channel, it gives me error AMQ4059. I tried/checked following things. Local connection (in bind mode) to the queue manager is working perfectly fine.
Created the queue manager by MQ Explorer, running it as Administrator.
Created SYSTEM.ADMIN.SVRCONN channel.
My userid ‘testid’ is part of ‘mqm’ group. I also tried it by placing ‘mqm’ in MCA UserId on the SVRCONN channel.
Norton Security’s Firewall rule is set up to allow my laptop to connect as client connection by all computers on all ports.
Any other idea ?
Thanks.
Roderick |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Dec 26, 2012 7:21 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Do you have a listener running? And if yes on which port? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| drodrick |
| Posted: Wed Dec 26, 2012 7:37 am Post subject: |
|
|
Novice
Joined: 26 Dec 2012
Posts: 17
|
Yes, it is. It is defined and running on the default 1414 port and the same is mentioned in client connection.
Thanks. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Dec 26, 2012 1:34 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
What do you find in the error logs on both qmgr and client?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Dec 26, 2012 2:17 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| drodrick wrote: |
Yes, it is. It is defined and running on the default 1414 port and the same is mentioned in client connection.
Thanks. |
Mentioned in the client connection? Exactly how?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| drodrick |
| Posted: Wed Dec 26, 2012 7:28 pm Post subject: |
|
|
Novice
Joined: 26 Dec 2012
Posts: 17
|
No error recorded in error logs.
Ok, I did not clarify it clear. The server and client both are on the same machine, my laptop.
Client connection means, creating a queue manager connection entry in 'Show/Hide Queue Managers' option in MQ Exporer, and providing host name, port no and svrconn channel therein. I entered my laptop's computer name and port no as 1414.
Thanks. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Dec 26, 2012 9:31 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| drodrick wrote: |
No error recorded in error logs.
Ok, I did not clarify it clear. The server and client both are on the same machine, my laptop.
Client connection means, creating a queue manager connection entry in 'Show/Hide Queue Managers' option in MQ Exporer, and providing host name, port no and svrconn channel therein. I entered my laptop's computer name and port no as 1414.
Thanks. |
And by computer name, you mean hostname?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Dec 27, 2012 2:07 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
start the qmgr in interactive mode?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Dec 27, 2012 6:08 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Can you run any of the supplied WMQ client-bindings utilities successfully? amqsputc? amqsbcgc?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| drodrick |
| Posted: Thu Dec 27, 2012 7:03 am Post subject: |
|
|
Novice
Joined: 26 Dec 2012
Posts: 17
|
| Quote: |
| Can you run any of the supplied WMQ client-bindings utilities successfully? amqsputc? amqsbcgc? |
It gives following unsuccessful message.
C:\Windows\System32>SET MQSERVER=SYSTEM.ADMIN.SVRCONN/TCP/MyComputer(1414)
C:\Windows\System32>amqsputc QL1 QM1
Sample AMQSPUT0 start
MQCONN ended with reason code 2538
| Quote: |
| start the qmgr in interactive mode? |
I ran the queue manager in Interactive mode, but no change. Got the same error AMQ4059.
Thanks. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Dec 27, 2012 7:15 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| drodrick wrote: |
| Quote: |
| Can you run any of the supplied WMQ client-bindings utilities successfully? amqsputc? amqsbcgc? |
It gives following unsuccessful message.
C:\Windows\System32>SET MQSERVER=SYSTEM.ADMIN.SVRCONN/TCP/MyComputer(1414)
C:\Windows\System32>amqsputc QL1 QM1
Sample AMQSPUT0 start
MQCONN ended with reason code 2538
| Quote: |
| start the qmgr in interactive mode? |
I ran the queue manager in Interactive mode, but no change. Got the same error AMQ4059.
Thanks. |
At a c: prompt type the hostname command. Does the response say 'MyComputer'? Or something else? The last parameter in the MQSERVER needs to be something discoverable, like hostname or ipaddress or dnsname.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| drodrick |
| Posted: Thu Dec 27, 2012 7:36 am Post subject: |
|
|
Novice
Joined: 26 Dec 2012
Posts: 17
|
It exactly shows as 'MyComputer', because I have set it as my computer name.
C:\Windows\system32>hostname
MyComputer
Thanks. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Dec 27, 2012 7:42 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Try 'localhost(1414)'.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Dec 27, 2012 7:52 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Process of elimination time. Things to try, post results here:
1) turn off Norton, and try again
2) use netstat command to ensure that your listener is running, and try again
3) use loopback tcpip address in MQSERVER environment variable, and try again
4) run the tcp ping command 'ping MyComputer'
5) run the dspmq command
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| drodrick |
| Posted: Thu Dec 27, 2012 5:26 pm Post subject: |
|
|
Novice
Joined: 26 Dec 2012
Posts: 17
|
| Quote: |
| 1) turn off Norton, and try again |
Tried, but got the same result.
| Quote: |
| 2) use netstat command to ensure that your listener is running, and try again |
Received following, but not sure, if anything is wrong. Any comment ?
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:135 MyComputer:0 LISTENING
TCP 0.0.0.0:445 MyComputer:0 LISTENING
TCP 0.0.0.0:554 MyComputer:0 LISTENING
TCP 0.0.0.0:1414 MyComputer:0 LISTENING
TCP 0.0.0.0:1415 MyComputer:0 LISTENING
TCP 0.0.0.0:2869 MyComputer:0 LISTENING
TCP 0.0.0.0:5357 MyComputer:0 LISTENING
TCP 0.0.0.0:9000 MyComputer:0 LISTENING
TCP 0.0.0.0:10095 MyComputer:0 LISTENING
TCP 0.0.0.0:10243 MyComputer:0 LISTENING
TCP 0.0.0.0:49152 MyComputer:0 LISTENING
TCP 0.0.0.0:49153 MyComputer:0 LISTENING
TCP 0.0.0.0:49154 MyComputer:0 LISTENING
TCP 0.0.0.0:49155 MyComputer:0 LISTENING
TCP 0.0.0.0:49156 MyComputer:0 LISTENING
TCP 127.0.0.1:5354 MyComputer:0 LISTENING
TCP 127.0.0.1:49158 MyComputer:0 LISTENING
TCP [::]:135 MyComputer:0 LISTENING
TCP [::]:445 MyComputer:0 LISTENING
TCP [::]:554 MyComputer:0 LISTENING
TCP [::]:1414 MyComputer:0 LISTENING
TCP [::]:1415 MyComputer:0 LISTENING
TCP [::]:2869 MyComputer:0 LISTENING
TCP [::]:5357 MyComputer:0 LISTENING
TCP [::]:9000 MyComputer:0 LISTENING
TCP [::]:10243 MyComputer:0 LISTENING
TCP [::]:49152 MyComputer:0 LISTENING
TCP [::]:49153 MyComputer:0 LISTENING
TCP [::]:49154 MyComputer:0 LISTENING
TCP [::]:49155 MyComputer:0 LISTENING
TCP [::]:49156 MyComputer:0 LISTENING
TCP [::1]:49159 MyComputer:0 LISTENING
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5004 *:*
UDP 0.0.0.0:5005 *:*
UDP 0.0.0.0:54337 *:*
UDP 0.0.0.0:62237 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:5353 *:*
UDP 127.0.0.1:58512 *:*
UDP 127.0.0.1:61864 *:*
UDP 127.0.0.1:62239 *:*
UDP [::]:500 *:*
UDP [::]:3702 *:*
UDP [::]:3702 *:*
UDP [::]:4500 *:*
UDP [::]:5004 *:*
UDP [::]:5005 *:*
UDP [::]:54338 *:*
UDP [::]:62238 *:*
UDP [::1]:1900 *:*
UDP [::1]:61863 *:*
| Quote: |
| 3) use loopback tcpip address in MQSERVER environment variable, and try again |
Tried with 127.0.0.1, but no change. I even tryied with 'localhost', but got same result.
| Quote: |
| 4) run the tcp ping command 'ping MyComputer' |
C:\Windows\system32>ping mycomputer
Pinging MyComputer [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Ping statistics for ::1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
| Quote: |
| 5) run the dspmq command |
C:\Windows\system32>dspmq
QMNAME(QM1) STATUS(Running)
QMNAME(QM2) STATUS(Running) |
|
| Back to top |
|
|
|
|
