| Author |
Message
|
| Symonides |
 Posted: Wed Sep 01, 2010 9:06 am Post subject: .NET WebForms Client |
 |
|
Newbie
Joined: 01 Sep 2010
Posts: 7
|
Hi all,
I developing a webforms app.
I'm trying to connect to a remote queue manager but get a MQRC_Q_MGR_NAME_ERROR
I set all the enviroment setting neede for the connection.
Though with the same setting i can easily connect with Websphere MQ explorer.
Tried to test it with amqscnxc, but i get a 2035 authorinzation error since it's running on 'guest' from command line.
Any suggestions? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Sep 01, 2010 9:09 am Post subject: Re: .NET WebForms Client |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Symonides wrote: |
| Any suggestions? |
Look up the causes of MQRC_Q_MGR_NAME_ERROR (which is not the same as a 2035).
Ponder the differrence between how your app runs (and more specifically where it runs) and how MQ Explorer runs.
Then ponder how your app identifies the queue manager it connects to, and how this might differ from how MQ Explorer does it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Symonides |
| Posted: Wed Sep 01, 2010 1:11 pm Post subject: |
|
|
Newbie
Joined: 01 Sep 2010
Posts: 7
|
Hi!
| Quote: |
| Look up the causes of MQRC_Q_MGR_NAME_ERROR (which is not the same as a 2035). |
I'm aware of that.
Funny thing, now when I test the remote queue manager, I still get to authorization error. But now in the event log, i find that in the error message says smth like " could not authorize for user 'abcdefg'" but actualy my user name is 'abcdefgh'! There's a character missing in the error message.
| Quote: |
| Ponder the differrence between how your app runs (and more specifically where it runs) and how MQ Explorer runs. |
Well, i can't seem to find any.
The hostname, port, channel name, queue manager name, are all the same. Both app and MQ Explorer run on the client machine.
| Quote: |
| Then ponder how your app identifies the queue manager it connects to, and how this might differ from how MQ Explorer does it. |
Not really sure what you mean by that.
In my app, I set the MQEnviroment.Hostname/Port/Channel and try to create an instance of MQQueueManager
MQQueueManager qMgr = new MQQueueManager(qManagerName);
which throws the 2058 Error (MQRC_Q_MGR_NAME_ERROR) |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Sep 01, 2010 6:27 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
There's nothing wrong with the error message, so why does the name differ?
Why would the connection MQ Explorer be able to resolve the name, but your app not? Or put another way, why does your app try to resolve the name?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Symonides |
| Posted: Thu Sep 02, 2010 2:10 am Post subject: |
|
|
Newbie
Joined: 01 Sep 2010
Posts: 7
|
| Sorry, if it wasn't clear. The user name differs when using amqscnxc |
|
| Back to top |
|
|
| Symonides |
| Posted: Thu Sep 02, 2010 3:06 am Post subject: |
|
|
Newbie
Joined: 01 Sep 2010
Posts: 7
|
Futher tests.
I ran my app from a machine that hasn't got any websphere mq components installed on it. Now I receive two errors.
If I enter a correct port, I get a 2058 MQRC_Q_MGR_NAME_ERROR error
The event log tells me:
Error on receive from host XXX (111.111.111.111)
An error occured receiving data from XXX (111.111.111.111) over TCP/IP. This may be due to a communication failure.
The return code from the TCP/IP (recv) call was 10054 (X'2746'). Record these values and tell the system administrator.
If I enter a wrong port number, I get a 2038 MQRC_NOT_OPEN_FOR_INQUIRE error. Which seems correct.
Futher more.
Running my app on the server machine works just fine. (Connect, sending, receiving, all works, without any errors)
Last edited by Symonides on Thu Sep 02, 2010 5:08 am; edited 1 time in total |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 02, 2010 4:09 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Symonides wrote: |
| Running my app on the server machine works just fine. (Connect, sending, receiving, all works, without any errors) |
Well that's the final proof isn't? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Symonides |
| Posted: Thu Sep 02, 2010 5:12 am Post subject: |
|
|
Newbie
Joined: 01 Sep 2010
Posts: 7
|
uhhm. You mean the app trying to resolve the username? 
Hm, well I set the MQEnvironment.User and Password. But I get the errors mentioned earlier.
Telneting to the ip and port works. So it's not the firewall, if any one asked 
Last edited by Symonides on Thu Sep 02, 2010 5:21 am; edited 1 time in total |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 02, 2010 5:17 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Symonides wrote: |
| uhhm. You mean the app trying to resolve the username? |
No, I mean the configuration of the 2 machines, and the runtime environment on the client.
| Symonides wrote: |
| Hm, well I set the MQEnvironment.User and Password. But I get the errors mentioned earlier. |
As I think we've established earlier this might be connected to the 2035 but not the 2058.
WMQ also is not usually interested in passwords.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Sep 02, 2010 5:23 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| Symonides |
| Posted: Thu Sep 02, 2010 5:30 am Post subject: |
|
|
Newbie
Joined: 01 Sep 2010
Posts: 7
|
| Quote: |
| As I think we've established earlier this might be connected to the 2035 but not the 2058. |
I'm really sure about that any more. Atleast if we're talking about the username lenght. I think that, in the error message, MQ trims the username to 12 characters in lenght.
??? What about it?
| Quote: |
| WMQ also is not usually interested in passwords. |
Ok, good to know. Thanks.[/code] |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Sep 02, 2010 7:49 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Use a username with length <= 12. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Symonides |
| Posted: Thu Sep 02, 2010 11:07 am Post subject: |
|
|
Newbie
Joined: 01 Sep 2010
Posts: 7
|
| Quote: |
| Use a username with length <= 12. |
Are you serious? I hope the username is trimmed only when displaying it in the message.
This is strange. Now I get this error. After restarting both machines.
AMQ8073 Authorization failed because SID: ((none)) could not be resolved.
Explanation: The Object Authority Manager was unable to resolve the specified SID into entity and domain information.
User Response: Ensure that the application provides a SID that is recognized on this system, that all necessary domain controllers are available, and that the security policy is set as you required. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 02, 2010 11:11 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Symonides wrote: |
| This is strange. Now I get this error. After restarting both machines. |
Welcome to Windoze. Enjoy your stay. 
Follow the advice in the error message & speak to the domain admin.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sun.arun |
| Posted: Sun Sep 26, 2010 10:20 am Post subject: same error |
|
|
Newbie
Joined: 15 Jan 2010
Posts: 2
|
| We are facing same issue. We have MQ V7 client running on some domain on windows server. Our server is MQ V6 on windows in another domain. We have got same ID created on both domain. There is no relationship among these two domains. Id has got rights to connect to queue manager and get put on queues. Also same id is configured as MCA User ID on svrconn channel. |
|
| Back to top |
|
|
|
|
