Pinned topic Agent failure:File not transferring
When I am trying to transfer a file from one agent to another agent in a single system i am getting the following issue.
BFGCL0003E: A messaging problem prevented the command from completing successfully, for queue SYSTEM.FTE.COMMAND.AGENT1 on queue manager QM_A. The WebSphere MQ completion code was 2, and the reason code was 2087.
Even when I am trying to stop the agent also I am getting the same message...
Could any one suggest the above issue ASAP.
Re: Agent failure:File not transferring2012-03-06T15:42:03ZThis is the accepted answer. This is the accepted answer.You need to resolve your mq error "2087"
Can't provide any more than that with out see the transfer command submitted. Also check all of your properties files to ensure each is configured correctly for the environment you have set up.
agent.properties for sending agent
agent properties for receiving agent
ShivaPrasadChelluru_Miracle 2700052D2H2 Posts
Re: Agent failure:File not transferring2012-03-06T16:40:44ZThis is the accepted answer. This is the accepted answer.
- R_Simons 27000167KS
command i am submitting is ftpCreateTransfer -sa AGENT -sm FTE_QM -da AGENT1 -dm QM_A -df /root/Desktop /root/smaple.txt
Am I going any thing wrong....?
Re: Agent failure:File not transferring2012-03-06T18:41:07ZThis is the accepted answer. This is the accepted answer.
- ShivaPrasadChelluru_Miracle 2700052D2H
SystemAdmin 110000D4XK64 Posts
Re: Agent failure:Remote agent does not start2012-07-23T12:53:09ZThis is the accepted answer. This is the accepted answer.Hi, I am trying to connect to a remote coordination queue manager with an agent and constantly getting 2087
When trying to connect as mq client from the same queue manager it works without a problem
What can be wrong?
We have installed a coordination and command QueueManager on one computer and the agent on the remote computer
Both machine are windows based on the same network.
Both have local QueueManager installed , both FTE are 7041 and under WMQ 7016
How can I check manually the connection made by the FTE agent ? Something like amqsputc in WMQ ?
Re: Agent failure:Remote agent does not start2012-07-23T14:58:20ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
The agent "connects" to the agent QM named in its agent.properties file. What QM is the Agent being hosted on. The 2087 is a unknown remote QM. If this message is received on a fteStartAgent then it is most likely about the agent not being able to connect to it hosting QM, not the coordination QM. Can you post the contents of the agents output0.log file so I can see exactly what the 2087 error is for? also post the contents of the agent.properties file.
XanderD 50UA57PGQ01 Post
Re: Agent failure:File not transferring2017-10-23T05:48:53ZThis is the accepted answer. This is the accepted answer.
I am getting the same reason code 2085 when I tried to start agent on MQ v9.Please find the log info
[23/10/2017 10:48:12:310 IST] 00000013 AgentRecovery E BFGAG0039E: The agent received MQI reason code 2085 when opening queue 'SYSTEM.FTE.COMMAND.QM1AGT1' on the remote queue manager 'QM1' with connection name '127.0.0.1(4411)' and channel 'MFT.SVRCONN'. The agent cannot continue and will end.
[23/10/2017 10:48:12:313 IST] 00000001 AgentRuntime E BFGAG0171E: The agent has ended abnormally with return code 70.
I hope this is helpful to resolve the problem.