I encountered a really wired problem. I have successfully install Websphere MQ on my windows machine and want to create QManager and Queue to connect to a remote Qmanager server. I have already created a QManager as you can see in the picture below. However, when I tried to create a queue for this QManager, I could not find any expand button as the IBM tutorial mentioned.
I have already tried to create a queue with MQSC but when I run runmqsc in the command prompt with administrator user, it shows AMQ8135: Not Authorized error!
Check your error logs (AMQERR01.LOG) for an explanation of why AMQ8135 was returned to the client - for security reasons clients aren't given more information and so you have to go to the logs to get the detail.
I suspect the user you're running MQ Explorer and runmqsc as isn't in the 'mqm' group, or is otherwise not authorised to connect to the queue manager.
Run your IBM MQ Explorer as administrator and it will solve most of the issues.
Related
This question was already answered by joshmc but I'm not understanding the answer after a lot of digging. And don't have enough points to post a comment, sorry.
C# MQ Connect get Error 2035 but Java MQ Connect works well
I only have access to the client and can't change the server, which belongs to a third-party. They require we post messages to their IBM MQ server over the internet for XML integration. We have some simple Java code working fine but can't get the same thing running in .NET because of the 2035 issue. We have a username and password. Trying to do both from the same Windows 10 desktop. Using the version 8 client libraries in both Java and .NET.
The answer Josh discussed was to run
ALTER CHL(ServerChannel) CHLTYPE(SVRCONN) MCAUSER('mq').
This looks like a server-side command or how do we run this on the client, ideally in C#?
The given command is an example of an MQSC command.
To invoke this from your client machine will only be possible if you have been given permissions to make administrative changes on the server from your client.
To try, set up an environment variable to indicate where the server is and what channel name to use:
set MQSERVER=CHANNEL-NAME/TCP/hostname(port)
Then use the runmqsc command as follows:-
runmqsc -c -u yourUserId
The runmqsc tool will prompt you for a password and then try to connect. If it is successful you can then type in the MQSC command. If the MQSC command fails you will have to get the owner of the queue manager to make the change for you.
I was trying to configure my WMQ.
queue manager was running until i changed the password of my musr_mqadmin account.
Now it the local queue manager that i created cannot be start any more
The pop up says "The MQ service for installation "installation1" must be running"
While i tried to reset the musr_mqadmin account, it says "mq configuration an error while validating the security credentials "
I am really stuck and helpless. Please kindly advise.
MQ Service runs under MUSR_MQADMIN account. You will need to provide the same password for MQ Service also. Go to Administrative Tools/Services console. Select IBM WebSphere MQ service and open the properties by double clicking on the service. On the Log On tab provide the new password and OK to close the dialog and start the service.
HTH/Shashi
I have some stopped QMGRs. When I try to start them or delete them from MQ Explorer, I encounter this error:
AMQ7077: You are not authorized to perform the requested operation.
exitvalue=119
How can I change or remove the restrictions on this object?
You can start or delete a queue manager via the MQ Explorer too, so long as the queue manager and MQ Explorer are running on the same machine/installation. You must ensure that the MQ Explorer is running under an mqm user ID, just as you needed to do run the strmqm or dltmqm commands.
I figured it out that I can do this by command STRMQM 'qmName' or DLTMQM 'qmName' as an alternative to using MQ Explorer.
I’m new to MQ. I have successfully installed WebSphere MQ, setup the queue managers, queues and channels between the queue managers. I have set up agents and I can start, stop and successfully ping the agents but the agents are not listed as shown on the attached screen shot. I have been trying to make the agents work so that I can test file transfer and set it up in our environment.
I even tried to create new coordination and command queue managers and no luck. I even tried the fteListAgents -p (coordination queue manager) and -v
I will really appreciate all the help I can get.
What is the user id you are logged into machine as? Is it Administrator (on Windows)? If so you may be hitting the 12 character user id issue. Administrator is 13 character long and the 'r' at the end may be getting chopped off. I recommend you to look at this troubleshooting link.
If your windows user id is longer than 12 character, check this out:
1) Agents are started, but MQ Explorer agent list is empty?
2) Check under Queuemanager->YOURQM->Subscriptions -> User. Do you see your windows user name truncated to 12 characters?
3) Create a new windows user, with the user name as the 12 characters trancated user.
4) Add this 12 characters username to the Admin group.
MQ FTE used the queued PubSub mechanism. Usually this problem happens because the ID being used doesn't have access to publish. The procedure to diagnose this is as follows:
Download the MS0P SupportPac and install it into WMQ Explorer.
Enable authorization events on the Coordination Qmgr.
Stop and restart an agent or two.
Open MQ Explorer to the queues panel and find the SYSTEM.ADMIN.QMGR.EVENT queue.
Right click on the queue and select "Format Event Messages."
You should find some auths errors.
If the problem is authorization failures MS0P will tell you exactly which ID MQ thinks was used, the API call that failed and the object it failed on.
I am trying file transfer between two windows servers connected over network in the same domain. I have successfully connected with remote agent through Explorer but when try to browse the destination directory in remote system I find it is not enabled. I do not see any specific error in agent logs.
I do not see any specific error in MQ or Agent logs as I am actually not able to do anything.
Is this because the user I use does not have write access in the remote server. If that is the case How can I make sure the user has write access in the remote server?. The user I use has write access on remote server on direct login. Please find attached screenshot.
When I run in command mode I get 2087 reason code
C:\>fteCreateTransfer -sa AGENT1 -sm hubQM -da AGENT3 -dm hubQ
M -w -dd "D:\MQFTE\Destination" "D:\MQFTE\Source\sample.txt"
5724-H72 Copyright IBM Corp. 2008, 2012. ALL RIGHTS RESERVED
BFGCL0003E: A messaging problem prevented the command from completing successful
ly, for queue SYSTEM.FTE.COMMAND.AGENT1 on queue manager hubQM. The WebSphere MQ
completion code was 2, and the reason code was 2087.
The 2087 means MQRC_UNKNOWN_REMOTE_Q_MGR. This indicates that the QMgr that your WMQ Explorer is connected to cannot resolve the QMgr where the remote agent is connected. You'll need to look at your FTE Command QMgr to make sure it has a path to the QMgr where the remote agent lives.