Question
Coforge Limited
GB
Last activity: 25 Jan 2024 5:29 EST
Getting "Write Robot Manager entry failed!" when deploying assets
Hi, I am using 22.1.12 version of Pega Robot Studio. I have created a reusable automation procedure and included the same in application and trying to deploy as asset. The 4th stage in asset deployment "Write Robot Manager entry failed!" with error message "Failed to upload deployment package metadata to server. The automation package version metadata failed the validation in Robot Manager. Please refer to Robot Manager logs for more details."
However, normal project deployment works fine and able to see the versions in RM.
Could you help?
Accepted Solution
Coforge Limited
GB
@ManojanandNayagam Closing this as it got fixed as part of Pega Robotic Automation upgrade to 22.1.24. Thanks.
Pegasystems Inc.
US
@ManojanandNayagam What version of Robot Manager are you using? Assets require version 8.8.1 of Robot Manager at a minimum.
Updated: 12 Sep 2023 17:27 EDT
Coforge Limited
GB
@ThomasSasnett Yes, we use RM 8.8.1. I am able to see the asset deployed in repository but not showing in Robot Manager portal. Please see attached snapshots.
Pegasystems Inc.
US
@ManojanandNayagam This is a new one to me. I think I would have to get hands-on to see what might be happening. Are you seeing anything that might be helpful in your StudioLog? You might try enabling DEBUG level on the StudioLog and reproducing the issue to see what is being recorded.
One thing I try whenever I have a deployment issue with anything is to verify that the same version of the package (or asset in this case) has not been deployed previously. You can change the version to something that you know is unique and try to deploy again and see if that helps. If not, you might need to trace this from Pega Dev Studio. If you are uncomfortable with that, or if you'd like some hands-on assistance, I suggest opening a support request and we can assist you from there.
Updated: 13 Sep 2023 10:06 EDT
Coforge Limited
GB
@ThomasSasnett Thanks. I will submit an SR. I can see the same error message in studio log. Attached. Whenever I try to deploy, the version automatically increases. So definitely it is unique for that asset id.
Found below error in Pega log during asset deployment:
Could you let me know what this error means?
2023-09-13 13:31:40,632 [http-nio-8080-exec-8] [ STANDARD] [ ] [ CLMSRPA:01.01.01] (tomationPackage_Version.Action) ERROR ip-xxxx.eu-west-1.compute.internal|xxxx|Rest|robotics|v2|packages2fc9e51174a78dd5bfc57e8e368590b3|AS8MW5XAC54LHXDT6EA65HHWL7CYFQ1DYA AS8MW5XAC54LHXDT6EA65HHWL7CYFQ1DYA nayagm - Failed to create automation asset with error: automation asset version creation failed : Create new record failed: .pxPackageBinaryFileType: "PEGAASSET" is too long, maximum length allowed is 8. 2023-09-13 14:03:21,969 [ttp-nio-8080-exec-88] [ STANDARD] [ ] [ CLMSRPA:01.01.01] (tomationPackage_Version.Action) ERROR ip-xxxx.eu-west-1.compute.internal|xxxx|Rest|robotics|v2|packages2fc9e51174a78dd5bfc57e8e368590b3|AS8MW5XAC54LHXDT6EA65HHWL7CYFQ1DYA AS8MW5XAC54LHXDT6EA65HHWL7CYFQ1DYA nayagm - Failed to create automation asset with error: automation asset version creation failed : Create new record failed: .pxPackageBinaryFileType: "PEGAASSET" is too long, maximum length allowed is 8.
Accepted Solution
Coforge Limited
GB
@ManojanandNayagam Closing this as it got fixed as part of Pega Robotic Automation upgrade to 22.1.24. Thanks.