Changing the Uproc type from FTP_PUT to CL_EXT introduces an internal corruption


Article ID: 87514


Updated On:


CA Automic Dollar Universe


Error Message :
|2017-02-14 10:59:55,540|ERROR||BackgroundWorker-5|com.orsyp.kmeleon.universe.UniverseBusiness|Problem during deployment of object [UPROC_NAME][000] on [COMPANY/NODE/X]
|2017-02-14 10:59:55,540|ERROR||BackgroundWorker-5|com.orsyp.kmeleon.universe.deployment.UnifiedDeploymentBusiness$DeploymentAction|Problem occured during deployment of UPROC [UPROC_NAME][000] on Node_Name/X/Management_Unit
com.orsyp.UniverseException: Deployment error
at com.orsyp.kmeleon.universe.UniverseBusiness.deploy(

Changing the Uproc type from FTP_PUT to CL_EXT or trying to export/import it to/from a package returns an error similar to the one above in the UVC log file.

The error appears when the Uproc type is modified after the configuration of the Uproc.  For example, when an FTP_PUT Uproc, which has been configured and saved is then updated and changed to a CL_EXT Uproc type.

Uprocs which have been modified in this manner can no longer be saved nor deployed on another system.  However, they can be exported into packages.



Cause type:
Root Cause: The specific Data Class of the Uproc is not correctly updated when the Uproc type is changed once the Uproc has been created.


OS: All
OS Version: N/A


Update to a fix version listed below or a newer version if available.​

Fix Status: Released

Fix Version(s):
Dollar Universe 6.8.21 - Available

Additional Information

Workaround :
The Uproc can be repaired using the Upgrade toolkit command set.  If the Uproc was an FTP_PUT uproc before changing the type.
  1. Export the Urpoc with 'uniexp' in xml format.
  2. Remove <ftpPut>....</ftpPut> container from the extract and change the specific Data Class from
<specificData class="com.orsyp.api.uproc.ftp.FtpPut" reference="22"/> to <specificData class="" reference="21"/>
  1. Re-import the uproc with uniimp
  2. Now the uproc can be handled as expected.