Problems using Default_Cluster (AMQ4036)

[GuenterS]

Hello, I have several questions ...

I am using a evaluation copy of MQ Series 5.3 on a Win2000 PC and a Win2003 Server.

I installed both using the standard configuration.

The repository is hold on the win2000 pc, and the other pc is configured to use this.

After opening the Websphere Explorer I wanted to explore the Default_Cluster, to see the queue i Installed a few minutes before.

But I can't connect to the cluster, I got an AMQ4036 error code, what means that I've got not sufficient rights...

But both users are members of Administrating group.

What can I do, to connect to the Default_Cluster?

 

[mqonnet]

Your userid should also be in the "mqm" group.

Check in the mqerrlg's to see what userid it is complaining about. Are the queue managers defined locally. And did you use the same userid to install and connect to the default cluster.



Cheers
KK

 

[GuenterS]

It isn't possible to use the totally same user, because WebSphere MQ is installed on two different PCs.

The managers are both locally, but the repository of one is pointed to the other one. But there is the problem of connection and the rights.

I believe I've lost the logs in case of installing and uninstalling.

 

[mqonnet]

Could you explain your setup. How many qms are involved in the cluster. Where are they. I mean, are all the queue managers on the same system or different ones.

The machine/system where you are getting this authorization problem, are you able to start and use any other queue managers other than this default_cluster qm. And can you use apps to connect to this other qm. Say using amqsput/amqsbcg.

If you issue any commands or api calls that fail with authorization error, it would be logged to the mqerrorlog.



Cheers
KK

 

[GuenterS]

Yes of course.

I clicked on the installation program and followed the standard procedure by clicking next...

There is only one QM on each machine (two machines are involved). I don't use any apps, except the MQS Explorer.

What do you mean with "amqsput/amqsbcg" ?

I think I don't use any api/command calls...

 

[mqonnet]

But I can't connect to the cluster, I got an AMQ4036 error code, what means that I've got not sufficient rights... "
---This itself means you are trying to connect to a qm.
"I think I don't use any api/command calls... "
---And this is an MQ api call, mqconn. It may not be any of your apps since you say you are not running any. But it is the mqexplorer that is trying to do the connect.

"What do you mean with "amqsput/amqsbcg" ?"
---These are sample programs supplied with MQ installation. Take a look at the quick beginnings guide.

If 2 machines are installed, where are you getting the error on. Are you trying to connect to machine 2 qm from machine 1 using mq explorer or the other way round.



Cheers
KK

 

[GuenterS]

Could it be the problem that I am using an evaluation version of Websphere MQ Series?

I am ony evaluating it, so i think that this what I want to try is not forbidden, how else should I install it on two different machines?

 

[mqonnet]

There is only one QM on each machine (two machines are involved). "

"how else should I install it on two different machines"

---So doesnt this already mean that you have installed on 2 diff machines.

As far as evaluation version is concerned. I havent used it. But i dont think there should be any difference in the way it works when compared to a licensed version. So, you should rather find errors pertaining to this problem rather than thinking about the licensing. Just IMHO.

So, to understand your problem. Clearly explain the scenario in detail. How many machines. How many qms. What are their names. Their configs. Cluster definitions. The info we have exchanged is more or less the same all through with no new info propping up.



Cheers
KK

 

[GuenterS]

Ok I will try to get it clearer.

Websphere MQ Evaluation Version 5.3 is installed on two pcs. One pc run Windows2000 and the other Windows2003 server. The Windows2003 server doesn't act as a Domain Controller, its just a member Server in a different Workgroup. The pc with Windows2000 is in an Domain hosted by an NT Server (not a Win2000 Server).

The Windows2003 Server has an fixed IP Address (192.168.0.123) the other uses DHCP.

I followed the installation instructions which the Installation program of Websphere MQ provides.

First I installed Websphere MQ on the pc running Windows2003 Server. I clicked through the Installation instructions to the point I have to decide where to host the repository.
I decided that this pc should host it (was the first one and has a fixed IP address).
No error or warning occured at installation time.

After the installation of Websphere MQ on the pc with Windows2003 server I started the installation of Websphere MQ on the pc with Windows2000.

I installed it the same way as the other except that I decided to use the repository on the windows2003 server. At installation time no problem reaching the repository occurs.

After installed I started the WebSphere MQ Explorer.

When I tried to connect with the default cluster (from pc with Windows2000) an authorization error occured (AMQ4036).

I used on both machines to install and run a user with administrating rights. Second it was on each machine the same user for installing and running Websphere MQ.

I hope my English was not too bad and it got clearer what I've done.

best regards
Guenter

 

[mqonnet]

No, your english is fine.

Now, what i dont understand is what do you mean by "When I tried to connect with the default cluster ".

Did you use an application to connect to a cluster. Becauser the above line does not have any significance other than an app being used.

Also on windows2000 you should have some errors/FDs in your default mq install path\errors directory. If there are post them here. Or post the respective error message from mqerror logs in qmgrs\<your qm name>\errors directory.

What i can see going on is, if your win2k system is within a different domain and the other system in another domain, then the userids could have a domain name prefix. Like, Fred@host.com. If thats the case, then you have to deal with authorizations differently.



Cheers
KK

 

[GuenterS]

Thank you

With default cluster I mean the cluster which is installed by the setup.

With application I mean the Websphere MQ Explorer.

I will look for the logfile at monday.

best regards
Guenter

 

[GuenterS]

I checked the logfiles of both pcs, but I didn't see an useful hint in it. I post the two files maybe you see more as I have seen.

LogFile of windows2000 pc:
12.05.2004 15:58:04
AMQ7199: Die erworbene Prozessorkapazität wurde auf 1 gesetzt.

ERKLÄRUNG:
Die erstandene Prozessorkapazität für diese Installation wurde mit dem
MQ-Befehl 'setmqcap' auf 1 gesetzt.
AKTION:
Keine.
-------------------------------------------------------------------------------
12.05.2004 16:00:36
AMQ7125: Der Testzeitraum für dieses Exemplar von WebSphere MQ läuft in 90
Tag(en) ab.

ERKLÄRUNG:
Dieses Exemplar von WebSphere MQ wurde nur für einen begrenzten Zeitraum
lizenziert.
AKTION:
Keine.
-------------------------------------------------------------------------------
12.05.2004 16:00:45
AMQ7125: Der Testzeitraum für dieses Exemplar von WebSphere MQ läuft in 90
Tag(en) ab.

ERKLÄRUNG:
Dieses Exemplar von WebSphere MQ wurde nur für einen begrenzten Zeitraum
lizenziert.
AKTION:
Keine.
-------------------------------------------------------------------------------
13.05.2004 09:51:24
AMQ7125: Der Testzeitraum für dieses Exemplar von WebSphere MQ läuft in 89
Tag(en) ab.

ERKLÄRUNG:
Dieses Exemplar von WebSphere MQ wurde nur für einen begrenzten Zeitraum
lizenziert.
AKTION:
Keine.
-------------------------------------------------------------------------------
14.05.2004 09:33:10
AMQ7125: Der Testzeitraum für dieses Exemplar von WebSphere MQ läuft in 88
Tag(en) ab.

ERKLÄRUNG:
Dieses Exemplar von WebSphere MQ wurde nur für einen begrenzten Zeitraum
lizenziert.
AKTION:
Keine.
-------------------------------------------------------------------------------
17.05.2004 07:44:53
AMQ7125: Der Testzeitraum für dieses Exemplar von WebSphere MQ läuft in 85
Tag(en) ab.

ERKLÄRUNG:
Dieses Exemplar von WebSphere MQ wurde nur für einen begrenzten Zeitraum
lizenziert.
AKTION:
Keine.
-------------------------------------------------------------------------------


Logfile of windows2003 Server pc:
06.05.2004 14:45:14
AMQ7199: Die erworbene Prozessorkapazität wurde auf 1 gesetzt.

ERKLÄRUNG:
Die erstandene Prozessorkapazität für diese Installation wurde mit dem
MQ-Befehl 'setmqcap' auf 1 gesetzt.
AKTION:
Keine.
-------------------------------------------------------------------------------
06.05.2004 14:46:14
AMQ7125: Der Testzeitraum für dieses Exemplar von WebSphere MQ läuft in 90
Tag(en) ab.

ERKLÄRUNG:
Dieses Exemplar von WebSphere MQ wurde nur für einen begrenzten Zeitraum
lizenziert.
AKTION:
Keine.
-------------------------------------------------------------------------------
06.05.2004 14:46:21
AMQ7125: Der Testzeitraum für dieses Exemplar von WebSphere MQ läuft in 90
Tag(en) ab.

ERKLÄRUNG:
Dieses Exemplar von WebSphere MQ wurde nur für einen begrenzten Zeitraum
lizenziert.
AKTION:
Keine.
-------------------------------------------------------------------------------

I tried to use my domain extensions, but I didn't find out where to fill this information in.

 

[mqonnet]

Are you using MQEXPLORER to just connect to the remote system. Thats it. If so, how is clustering invovled. If you just click on show queue manager and add a remote qm, you should be able to see it. I am still unclear as to where this clustering coming into picture.

Also it looks like you posted the errors from one system. What about the other one.



Cheers
KK

 

[GuenterS]

The posted errors are not from the same system. In cause that the pcs are both in same house, they are both native language (german in my case).

I wanted to use MQSeries in a program to send messages from one pc to another. But I think if it is not possible through the MQEXPLORER I don't need to program it.

After reading some documentation stuff, I got the idea that a Message Queue which belongs to a cluster can be used to send the message to the other pc or if there are more pcs with WebSphere MQ to them too.

But the main problem is, why I can't connect to the default cluster from my windows2000pc.
The error which occurs tells me that I've got not sufficient rights to do that, but what must I do to get the right?

 

[GuenterS]

Now I tried to add the WS manager of the windows2003 pc in MQEXPLORER, but I've got there errors too.

The program (MQExplorer) tells me the same error, which occurs if I want connect to the default_cluster.

 

[GuenterS]

In your first answer of this thread you posted that both users must be in the mqm group but this is not possible in my case I think.

I just try to explain you my network structure.

I take letters to name pcs.

A ... domain controller, running NT4;
B ... windows2000 pc running WebSphere MQ;
C ... Windows2003 pc running WebSphere MQ


B is in the domain of A, but C is in its own Workgroup.

The installation program added a group "mqm", but only on the pc C, not on B or A.

Do you think it could help if I create the group manually on A and add my user (B)?

 

[mqonnet]

I wanted to use MQSeries in a program to send messages from one pc to another. But I think if it is not possible through the MQEXPLORER I don't need to program it.
"
---As far as i know you cannot send messages and just browse if there are any, on your queues.

"After reading some documentation stuff, I got the idea that a Message Queue which belongs to a cluster can be used to send the message to the other pc or if there are more pcs with WebSphere MQ to them too.
"
---What i dont understand is, what are you trying to do here. If your sole purpose is to test if a message put on the local qm on B reaches system C, then just define a remote queue, xmitq and sdr channel on System B. On System C define a local queue, receiver channel. Start the sender channel on System B. Run amqsput sample supplied with MQ to put a message onto the remote queue on system B. Message would land up on System C. No clustering involved anywhere.

"Do you think it could help if I create the group manually on A and add my user (B)?
"
---From the diagram you showed, A is not in the scope of MQ at all. So, creating userids on that system wont help. What you need to try and do is run a sample amqsputc client app on one of the systems, B or C. Look at the clients manual for how to configure it using MQSERVER environment variable.



Cheers
KK

 

[GuenterS]

Hello,

I just tried out to define a remote queue and send successfully messages to this queue.

The task I should realize is done with that, but the problem why I can't connect to the default_cluster is still not solved.

But I am happy that Websphere MQ now work correctly in the case I needed it.

Thank you, for your patience and help

 

[mqonnet]

Well, glad that you are satisfied, at last.

But as for the cluster problem, i would say that there may be something with the domain that you are using. Just a thought.

Good luck!!!



Cheers
KK