Hi
We are having an issue with the filewatcher exe. we only have one control M agent installed on the windows server and if the agent name is not passed as the parameter to the filewatcher it returns with an error saying that the agent name is mandatory...I read if the agent is set as default its not required to pass so....so can someone help me understand if we have only one agent installed would that not be default automatically ?
secondly if not how do i check if my agent is set to default or not....
any help will be greatly appreciated...
Filewatcher Agent Name Mandatory
- CTMUSERIND
- Nouveau
- Posts: 5
- Joined: 12 Feb 2013 12:00
Re: Filewatcher Agent Name Mandatory
Hi
Please confirm whether your Control-M server and agent are in one machine or are in different machine.
If you are using one remote Agent then you have to mention the Agent name(If you are saying it was installed as defult then you have to mention the logical agent name in the job)
Thanks.
Please confirm whether your Control-M server and agent are in one machine or are in different machine.
If you are using one remote Agent then you have to mention the Agent name(If you are saying it was installed as defult then you have to mention the logical agent name in the job)
Thanks.
- ank_cm_info
- Nouveau
- Posts: 3
- Joined: 11 Apr 2013 12:00
The Agent and server on on different machines. I only have agent installed on my windows server.
so does that mean the Agent name has to be passed ? i tried passing the logical agent name and it does not work...so which means it was not installed as default ?
do we have a command to check if my agent is installed as default ?
thanks for the help
so does that mean the Agent name has to be passed ? i tried passing the logical agent name and it does not work...so which means it was not installed as default ?
do we have a command to check if my agent is installed as default ?
thanks for the help
- CTMUSERIND
- Nouveau
- Posts: 5
- Joined: 12 Feb 2013 12:00
Hi,
Goto the Agent machine and open your command prompt.
Run the ctmagcfg utility it will show the agent name you want to modify.(But just refer the instance name don't modify any properties).
If you find the Agent name as 'Default' then while job configuration in the Node ID field mention the host name where you have installed the Control-M Agent.
This will solve your issue.
Thanks
Goto the Agent machine and open your command prompt.
Run the ctmagcfg utility it will show the agent name you want to modify.(But just refer the instance name don't modify any properties).
If you find the Agent name as 'Default' then while job configuration in the Node ID field mention the host name where you have installed the Control-M Agent.
This will solve your issue.
Thanks
- ank_cm_info
- Nouveau
- Posts: 3
- Joined: 11 Apr 2013 12:00
- CTMUSERIND
- Nouveau
- Posts: 5
- Joined: 12 Feb 2013 12:00
Hi,
Does this agent comes in CCM ?
Try to ping the agent from Control-M Server, if it success then mention the agent name in the Node Id field, else in the host file do an entry with the agent name and the agent IP and try to ping.
After successful communication with Server and agent your issue will be resolved.
Thanks
Does this agent comes in CCM ?
Try to ping the agent from Control-M Server, if it success then mention the agent name in the Node Id field, else in the host file do an entry with the agent name and the agent IP and try to ping.
After successful communication with Server and agent your issue will be resolved.
Thanks