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.
Related
I've just installed the demo version of this but fail to connect to the default queue manager. The error in the logs shows me that configuration is not correct for the mq dlls
2022/09/29 17:12:49 MQCmdServer: isCmdServerRunning: Error: MQJE001: Completion Code '2', Reason '2495'.
2022/09/29 17:12:49 MQCmdServer: isCmdServerRunning: getCause()=com.ibm.mq.jmqi.JmqiException: CC=2;RC=2495;AMQ8568: The native JNI library 'mqjbnd64' was not found. For a client installation this is expected. [3=mqjbnd64]
I've tried everything I can to set the path and java.library.path correctly but it all fails. They appear in the visual edit logs as being set but it makes no difference to the outcome.
Visual edit log also tells me that it should have the mq jars in its install directory:
C:\Capitalware\MQVE3\com.ibm.mq.commonservices.jar;
but these are not there and are nowhere to be seen. So, I'm mystified as to what version of the client it's using and therefore what help I can give it. I'm wondering if it's using a different version of the client from the one I have installed and so the dll and mq java lib have a mismatch? Or, if it's using the client I have installed then how is it finding it - because it's not in the paths that I've got in the visual edit logs !
Any thoughts anyone? What can I do to investigate further?
thank you !
Background: There are 2 ways an MQ client application can connect to a queue manager:
(1) Bindings mode means that the MQ client application is connecting to a local (i.e. on the same server) queue manager
(2) Client mode means that the MQ client application will connect to a remote queue manager by specifying the hostname/IP address, port # and channel name
CC=2;RC=2495;AMQ8568: The native JNI library 'mqjbnd64' was not found. For a client installation this is expected. [3=mqjbnd64]
This error mean that you are trying to connect to a local queue manager (in bindings mode) but there is no local queue manager. MQ client library uses the 'mqjbnd64' DLL to handle the connection to the local queue manager. But clearly, the queue manager is remote to where MQ Visual Edit is running.
Go back to the Queue Manager Access Profile, click on the Remote icon, then fill in the channel name, hostname/IP address and port # of the remote queue manager, save the information then you should be able to the remote queue manager.
I am setting up my corporate laptop to install IBM MQ 7.5 and create a Queue Manager and create some queues inside it.
The installation of IBM MQ 7.5 got success. My user id (Ex.malai) is linked to 'mqm' user group.
Creation of Queue Manager
C:\Program Files\IBM\IIB\10.0.0.3>crtmqm A24QM
WebSphere MQ queue manager created.
Directory 'C:\Program Files (x86)\IBM\WebSphere MQ\qmgrs\A24QM' created.
The queue manager is associated with installation 'Installation1'.
Creating or replacing default objects for queue manager 'A24QM'.
Default objects statistics : 77 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
Starting the Queue Manager
C:\Program Files\IBM\IIB\10.0.0.3>strmqm A24QM
WebSphere MQ queue manager 'A24QM' starting.
The queue manager is associated with installation 'Installation1'.
5 log records accessed on queue manager 'A24QM' during the log replay phase.
Log replay for queue manager 'A24QM' complete.
Transaction manager state recovered for queue manager 'A24QM'.
WebSphere MQ queue manager 'A24QM' started using V7.5.0.0.
The above command looks ok. I launch the IBM MQ with my user id 'malai' and I see as below
The Queue Manager is Disconnected. I do not see the tree icon to expand the Queue Manager to create the Queues.
When I try creating the Queue Manger from GUI it is giving the below output
****************************************
* Command: "C:\Program Files (x86)\IBM\WebSphere MQ\bin\runmqsc" TESTQM
* Input: DEFINE LISTENER('LISTENER.TCP') TRPTYPE(TCP) PORT(1414) CONTROL(QMGR)
****************************************
5724-H72 (C) Copyright IBM Corp. 1994, 2011. ALL RIGHTS RESERVED.
Starting MQSC for queue manager TESTQM.
AMQ8135: Not authorized.
No MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.
exitvalue = 20
And also, even though I see the manager is in running state, once in 4/5 seconds the up green arrow goes to down red arrow and comes back.
I dont see any error in AMQERR01
I understand it is something to do with user group, rights and permission. Since this is a corporate laptop, I do not have admin rights to my computer (i can get temporarily). It is a dev setup and I would like to know what configuration do I need to do in order for MQ 7.5 to run in my machine.
Update:
When I try execute runmqsc it throws the below error
C:\Program Files\IBM\IIB\10.0.0.3>runmqsc A24QM
5724-H72 (C) Copyright IBM Corp. 1994, 2011. ALL RIGHTS RESERVED.
Starting MQSC for queue manager A24QM.
AMQ8135: Not authorized.
No MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.
Output of amqsput
C:\Program Files\IBM\IIB\10.0.0.3>amqsput A24QM
Sample AMQSPUT0 start
MQCONN ended with reason code 2059
I got a network admin and tried running the MQ Explorer and the cmd with 'Administrator' privileges. Login the PC with my id 'malai' and right click the MQ and select 'Run as Administrator' and login with admin id.
By doing that both runmqsc and MQ explorer works great. Does that giving any clue.
Add your UserId (malai) to the mqm group:
Open a Command Prompt and issue the following command:
net localgroup mqm malai /add
Then reboot Windows. Yes, reboot, its Windows. Then everything will work correctly with your UserId.
Also, why in the world are you installing MQ v7.5? Support for MQ v7.5 ended in April 2018!! Why didn't you install MQ v8.0 or v9.0 or v9.1??
So this is with some of my Windows Remote Desktop License Servers, which I am using with Microsoft Azure Cloud Subscription.
The issue I am facing is related to the license expiry. A fully functional and activated 2012 Remote Desktop Session Host server displayed the following message:
"THE REMOTE SESSION WAS DISCONNECTED BECAUSE THERE ARE NO REMOTE DESKTOP LICENSE SERVERS AVAILABLE TO PROVIDE A LICENSE.PLEASE CONTACT THE WINDOWS ADMINISTRATOR"
This was a simple setup on one server with the: connection broker, Session Host and Licensing server with 2012 CAL’s installed. And though the licensing seems to be configured correctly, in server manager.
But with the CAL(client access license), every user logging on to Server, gets the error message mentioned before. For every user, I need to update the CAL license again and again, and this issue occurs every 30 or 60 days. Kindly suggest something, and feel free to ask more details on this, if needed.
Step 1: The solution is delete the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing
Step 2: Try connecting in again.If it doesn’t work and you get the following error message: “The remote computer disconnected the session because of an error in the licensing protocol“then all you need to do is Right-Click on the Remote Desktop Connection icon and select “Run as Administrator“.
What's the difference of amqsvc and strmqsvc?
I have installed IBM MQ and configured for multi instance. It uses amqsvc.exe to start the service as installed, the service is logon from a domain account, and the account is a member of group mqm.
It was working fine but yesterday for some unknown reason the service is not starting properly, here is what happened:
when amqsvc is run on automatic or manual, amqzxma0 runs on full cpu usage until timeout and windows prompted the service not starting with error 1053, but the MQ service is started, then I tried to start the queue manager but fail to start, however it can be started on interactive.
However I can start the service fine with strmqsvc and can start the queue manager normally. So what's the difference between these two and what is the problem behind it?
amqsvc is the actual windows service.
strmqsvc is the command used to start the above service.
The IBM v7.5 Knowledge Center documents the error 1053 as:
Windows: amqmsrvn.exe process removed
The amqmsrvn.exe DCOM process was replaced by a Windows service,
amqsvc.exe, in Version 7.1. This change is unlikely to cause any
problems. However, you might have to make some changes. You might have
configured the user that runs the IBM® WebSphere® MQ Windows service
MQSeriesServices without the user right to Log on as a service.
Alternatively, the user might not have List Folder privilege on all the subdirectories from the root of the drive to the location of the
service amqsvc.exe.
If you omitted the Log on as a service user privilege, or one of
the subdirectories under which IBM WebSphere MQ is installed does not
grant the List Folder privilege to the user, the MQ_InstallationName
IBM WebSphere MQ Windows services in Version 7.5 fails to start.
...
If you did not give the user the List Folder privilege, the Windows Service Control Manager adds an event: 7009: Timed out waiting for the
service to connect. The strmqsvc command reports error 1053.
Ensure that you have provided List Folder privilege on all the subdirectories from the root of the drive to the location of the service amqsvc.exe. This should resolve the issue.
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.