Automic Workload Automation

 View Only

 "Error during XRequest com.uc4.communication.requests.SaveObject" on saving calender events!

Daniel Babace's profile image
Daniel Babace posted Feb 18, 2024 04:16 AM

Hello togehter,
on 17 February 2024 we updatest our Automic Engine System and AWI to 21.0.9.HF1.
On the AE server we stopped the services, renamed c:\automic to c:\automic_old and installed the new AE like in
https://docs.automic.com/documentation/WEBHELP/English/all/components/DOCU/21.0.9/Automic%20Automation%20Guides/Content/Installation_Upgrade/install_upgrade_v123.htm
We got a few problems with an calender event in Client 0 in UC_HOLIDAY.D because the event EASTER could not be saved. This ist ok now but we cant save events in our calenders in Client1!
If we want to safe we get the error: "Error during XRequest com.uc4.communication.requests.SaveObject" and we cant save it.
The logs shows nothing interessting...
Please help.

Nico Mager's profile image
Nico Mager

Hi Daniel,

we had an issue very similar to yours and got the same error message. However our message was triggered by a formatting issue of the Documentation. The formatting is most likely introduced by Version 21.0.9HF1 as since this Version we are encountering it too. 

So the issue lies within how the object is stored. You can see it by exporting the object via the Context menu and checking out the .xml file it generated. Our issue was within the <DOCU_Docu> tag. While not being fully relevant to your issue, I will explain a bit further. Maybe it helps you to find out the issue in your .xml defintion. 

We had a job that had a Documentation Content node. Since this version, some tags seem to be written differently. Here you can see that <Content> is getting written into one line. However a javascript of the AWI does not like that and does not even trigger a request to the AE. Hence why there is zero logs.

If you go to the .xml and edit it like this and re-import it, the object can be saved again:

I tried to manipulate the specific Calender you mentioned on our Dev system but I could not find any constellation that triggers that error for our side as well. But maybe you can find anomalies in the .xml Export.

Maybe as a reference you can revert your Calendar to the initial version, export it and compare both .xml files. 

Good look to anyone fighting this issue.
Cheers, Nico