Issue with DM Add Deployment Target to Component action

Document ID : KB000112174
Last Modified Date : 25/01/2019
Show Technical Document Details
Issue:
Our customer got the following error while using the action assign component to target, 
 
DMTool: PARAM: url = http://araserver.com 
DMTool: PARAM: component = SBI_NODE01 
DMTool: PARAM: delete = 
DMTool: PARAM: applicationName = SBI 
Internal Error 
java.lang.IllegalArgumentException: The deployment target MMPCCBH7_SBI_PRD_LV00393_APP wasn't assigned to environment 854657 
at com.uc4.ara.feature.rm.ChangeDeploymentProfileTarget.run(ChangeDeploymentProfileTarget.java:165) ~[dm-tool.jar:?] 
at com.uc4.ara.feature.AraFileCmd.main(AraFileCmd.java:126) [dm-tool.jar:?] 
DMTool: ================================================= 
DMTool: Executing rm ChangeDeploymentProfileTarget finished 
DMTool: Ended at 2018-07-31 21:42:18 
DMTool: Elapsed Time: 0 min, 22 sec 
DMTool: Return Code: 999


even that target and profile are in same envrioment PRD (854657), and we can assign it manually 
Environment:
Package.DM 1.2.6
Cause:
Action Add Deployment Target to Component fails in case environment contains more than 100 deployment targets
Resolution:
The issue was found and fixed with Package.DM 1.2.7 in PCK.AUTOMIC_DM. The Package is available for download at the Automic-Support-Zone (https://support.automic.com).
Hotfix-Description: Action Add Deployment Target to Component fails in case environment contains more than 100 deployment targets
Cannot add deployment target to component in case environment contains more than 100 deployment targets