Knowledge Article
Control-M/Agents are grayed out in the Agent Deployment Upgrade Activity of the Control-M Configuration Manager (CCM) and the message "No matching package" appears - INCLUDES VIDEO
Control-M Agents are grayed out and a message is displayed that says "No matching package" in the comments column even though the files are located in the AUTO_DEPLOY directory.
Control-M/Enterprise Manager
Control-M/Enterprise Manager
Control-M Enterprise Manager 9.0.00 and higher; Configuration Manager (CCM) Agent Deployment
When starting a new Upgrade Activity the Window shows Control-M Agent in the list but they are not selectable and appear to be grayed out with a message "No matching package": |
The upgrade file for the Control-M Agent must be present in the AUTO_DEPLOY folder on the Control-M Enterprise Manager Server and have the correct name.
1：Make sure the Control-M Workload Automation GUI Client is as the same level as Control-M/Enterprise Manager Server. 2：Make sure that the files for upgrading the Control-M Agents are named as follows: For UNIX/Linux Control-M Agent:
On rare occasions, the file name downloaded from EPD is missing ".tar" and looks like this: DRKAI.9.0.00_Linux-x86_64.Z If this occurs, rename the file to the proper format mentioned above. NOTE: Unix/Linux files must have the ".Z" at the end as a capital letter and cannot be lowercase ".z". As of April 2016, there are known issue with Chrome based browsers (use Firefox to avoid this issue) which result in the “.Z “ suffix of files on the BMC EPD site being converted to .z on download, rename the file to correct the above before working with the CCM Agent Deployment facility. NOTE: This scenario could also happen when a Control-M/Agent Fix Pack is downloaded and used in Agent Deployment. Please rename the ".bin" Fix Pack file to ".BIN". For example:- "PAKAI.9.0.00.300_Linux-x86_64_INSTALL.bin" to "PAKAI.9.0.00.300_Linux-x86_64_INSTALL.BIN" The following video demonstrates this solution:
|
Attachment(s):