New Agent Install error

Tools and several solutions to manage Control-M products
Post Reply
User avatar
Venkateshwarulu
Nouveau
Nouveau
Posts: 77
Joined: 24 Jun 2009 12:00
Location: London

New Agent Install error

Post by Venkateshwarulu » 09 Jun 2010 6:18

Hello,

Greetings...I have installed brand new agent on brand new server and I can able to install the agent 6.4.01 sucessfully. But when I am trying to connect it from the server it is gving the following error.

"Failed to send the agent it's connection configuration"


I changed the communication parameters as per the Agent requirement.

FYI....
Parameters for Communicating with Specific Agent Platform (PRODGRT)


1) Communication Timeout: 120
2) Maximum Retries: 12
3) Retry Interval (Unavailable): 90
4) Server-to-Agent Port Number: 10006
5) Communication Protocol Version: 07
6) Check Interval (Available): 7200
7) Unavailability Shout Urgency: R
8) Persistent Connection: N
9) Allow Agent Disconnection: Y
10) Session Idle Timeout: 900
11) Maximum Disconnect Time: 300

a) Modify all of the above
s) Save agent configuration
q) Quit

(All time parameters expressed in seconds)

Enter option or item number you wish to change: [q]:s
Enter option or item number you wish to change: [q]:s
Trying to send the agent it's current connection configuration

This may take a while...

Failed to send the agent it's connection configuration


Press Enter to continue



AM I missing something here? Any suggestions/help greately appreciated?

Thanks
Venkat

User avatar
Walty
Nouveau
Nouveau
Posts: 473
Joined: 20 Jan 2006 12:00

Post by Walty » 09 Jun 2010 7:22

Hi,

For agent 6.4.01 the protocol version is 08
Best regards
Walty

User avatar
Venkateshwarulu
Nouveau
Nouveau
Posts: 77
Joined: 24 Jun 2009 12:00
Location: London

Post by Venkateshwarulu » 09 Jun 2010 8:02

Thanks Walty for quick reply.

I tried changing that, but it is giving the below error.

Enter option or item number you wish to change: [5]:5
Communication Protocol Version [07]:08
*** Invalid Communication Protocol Version. Valid values are 01 through 07.
Communication Protocol Version [07]:Enter option or item number you wish to change: [5]:5


Just FYI...I am using the Control-M server 6.3.01 on Solaris.

Thanks
Venkat

User avatar
Walty
Nouveau
Nouveau
Posts: 473
Joined: 20 Jan 2006 12:00

Post by Walty » 09 Jun 2010 8:26

Hi,
I'm not sure if the agent 6.4 is compatible with Controlm-Server 6.3
Check availibilty on documentation
Best regards
Walty

User avatar
Walty
Nouveau
Nouveau
Posts: 473
Joined: 20 Jan 2006 12:00

Post by Walty » 09 Jun 2010 10:48

Hi,

I find this:

The following combinations are supported by BMC Software:
CONTROL-M/Server v6.3.01.xxx with CONTROL-M/Agent v6.4.01.xxx --> PROTOCOL_VERSION on CONTROL-M/Agent should be changed to 07 (from 08)

For versions where the Agent is higher for configuration to work you must configure the 'PROTOCOL_VERSION' parameter on CONTROL-M/Agent to match the CONTROL-M/Server that it will communicate with for versions where the Agent is higher than Server.

- Stop CONTROL-M/Agent
- Navigate to the directory $CONTROLM/data
- Backup the file CONFIG.dat
- Edit the file CONFIG.dat and update the value of PROTOCOL_VERSION to the appropriate value
- Save an Exit the file
- Start CONTROL-M/Agent
Last edited by Walty on 09 Jun 2010 10:52, edited 1 time in total.
Best regards
Walty

User avatar
Venkateshwarulu
Nouveau
Nouveau
Posts: 77
Joined: 24 Jun 2009 12:00
Location: London

Post by Venkateshwarulu » 09 Jun 2010 10:51

Thanks Walty!!!

My issue has been resolved. I have changed some permissions on UNIX box to fix this issue.

Just FYI...Control-M/agent 6.4 is compatible with Controlm-Server 6.3 and jobs are running fine in our shop with out any issues.

Thanks again for all your reply...

Regards
Venkat

Post Reply