Deployment of Control-M Manage File Transfer fails with the error: Invalid key name

Knowledge Article

Article Number

000350935

Old Article Number

000169021

Article Type

Solutions to a Product Problem

Title

Deployment of Control-M Manage File Transfer fails with the error: Invalid key name

Summary

Deployment of Control-M Manage File Transfer fails with the error: Invalid key name

Product

Control-M Managed File Transfer

Component

Control-M Managed File Transfer Enterprise

Applies to

Control-M Manage File Transfer all versions

Problem

When performing Control-M Manage File Transfer deployment the deployment fails and the following messages appear in the deployment log:

19-05-10 12:20:49: "C:\Users\MYUSER~2\AppData\Local\Temp\DRAFT.9.0.00_windows_x86_64.zip_XXX\User\setup.exe" -silent silent.xml
?Fri 05/10/2019 12:20:49.34

ERROR: Invalid key name.
Type "REG QUERY /?" for usage.
The system cannot find the path specified.

Installation has failed.

Cause

1. Control-M/Agent was installed in a not conventional Default path
2. CTM-3115: MFT deployment failed on windows in case the agent was previously upgraded from version 6.4.00

Solution

Solution 1:

Convencional Path:C:\Program Files\BMC Software\CONTROL-M Agent\Default\silent.xml
Non Convencional Path: C:\Program Files\BMC Software\CONTROL-M Agent\FolderName\Default\silent.xml

To solve this issue:

1. Navigate to the Temp directory were the silent.xml is located, you can find the location on the deployment log.
For example:
agent_xml_file = C:\Program Files\BMC Software\CONTROL-M Agent\FolderName\Default\silent.xml

2. Open the silent.xml file with a text editor.
3. Navigate to the line field.Instance.Name if the value is empty, add the value "Default" save the file and retry the installation.

Solution 2:

The CTM-3115 is fixed with Control-M Server 9.0.20. If the upgrade to Control-M Server 9.0.20 is not possible at the moment, perform following steps:

1. Navigate to <CTM_Server_Home>\ctm_server\autodeploy\application_scripts\ and backup existing AutoDeploy.pl file (This is on the Control-M/Server linked to the problematic Control-M/Agent)
2. Copy attached AutoDeploy.pl (in this article) to the location above.
3. Run Control-M Manage File Transfer deployment again.

Attachment(s):

AutoDeploy.zip