Updating JSCH causes Unexpected Error in AWI after upgrade

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation

Issue/Introduction

After upgrading to a 24.4 service pack, when attempting to edit a schedule (JSCH) object, a popup comes up that says "An unexpected error occurred. Further details in the log files."

The AWI log shows:

2026-01-13 20:54:09,226 pool-2-thread-5        [ERROR] [AUTOMIC_SYSTEM]:[CLIENT_NUMBER]/USERNAME/DEPT node0jbmbyfs4lasih7g0hh221ow49-0 0000000006701167  [com.uc4.ecc.framework.commons.controls.messageprovider.MessageProvider] - An unexpected error occurred. Further details are available in the logfiles.
com.uc4.ecc.backends.exceptions.AutomationEngineAPIException: [HTTP 500] (45110) An Automation Engine internal error occurred.: No detail information available.
...
 Suppressed: java.lang.Throwable: null

At the same time, a forced trace is created for the REST API which shows:

20260113/205409.207 - 766              com.automic.search.api.IndexException: Indexing exception [com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException]: Unrecognized field "data" (class com.automic.search.api.IndexExceptionInfo), not marked as ignorable (one known property: "mls"])
20260113/205409.207 - 766               at [Source: (StringReader); line: 1, column: 34] (through reference chain: com.automic.search.api.IndexExceptionInfo["data"]) 

Environment

AE/AWI: 24.4

Cause

This error is caused by a character that cannot be read with a UTF-8 interface.

Resolution

Troubleshooting steps:

Turn on tcp/ip=2, database=4 and rest=5 trace on the REST API.  Then check for a line that has the hex for a "hidden" UTF8 character.  For example, the following might show up:

0037F710  6179206F 66206120 6D6F6E74 68200B74  >ay of a month .t<

In this case the character that looks like a period (.) has a hex code of 0B.  This is a Vertical Tab character and cannot be read by UTF-8 interfaces.  Once this is identified, look for the xml element directly above that that has <id> and </id> and <name> and </name>:

20260203/233729.995 - 81               0037FC60  6174613E 3C6E616D 653E4144 56323130  >ata><name>OBJECT<
20260203/233729.995 - 81               0037FC70  304D5F4A 502E5453 543C2F6E 616D653E  >NAMENAME</name><
20260203/233729.995 - 81               0037FC80  3C747970 653E4A4F 42503C2F 74797065  ><type>JOBP</type<
20260203/233729.995 - 81               0037FC90  3E3C7375 62547970 652F3E3C 706C6174  >><subType/><plat<
20260203/233729.995 - 81               0037FCA0  666F726D 2F3E3C69 643E3130 31363333  >form/><id>101633<
20260203/233729.995 - 81               0037FCB0  333C2F69 643E3C74 69746C65 3E746F20  >3</id><title>to <
20260203/233729.995 - 81               0037FCC0  62652065 78656375 74656420 77697468  >be executed with<
20260203/233729.995 - 81               0037FCD0  2061206C 6F676963 616C2064 61746520  > a logical date <
20260203/233729.995 - 81               0037FCE0  65717561 6C20746F 206C6173 7420776F  >equal to last wo<
20260203/233729.995 - 81               0037FCF0  726B696E 67206461 79206F66 2061206D  >rking day of a m<
20260203/233729.995 - 81               0037FD00  6F6E7468 200B746F 2070726F 64756365  >onth .to produce<

This may take an external tool to find as well as a good eye for xml.  For example in a tool like RSView, you would look for the following with wildcards:

*      ////////  * 0b////// *
*      ////////  * //0b//// *
*      ////////  * ////0b// *
*      ////////  * //////0b *

In the example above, the oh_idnr for the object is 1016333 (shown in two lines between the element tags <id> and </id>) and the name is OBJECTNAMENAME (shown in two lines here between <name> and </name>).  This object is the one causing the problem and will need to have the part updated that's throwing the problem or you can replace the entire object with a blank object by doing one of the following:

In a different Automic client, create a blank object, like workflow, with the same name as the problem object
Add the blank object to a transport case
Unload the transport case
Load the transport case into the client where the problem object is and overwrite the object

OR

In a different Automic client, create a blank object, like workflow, with the same name as the problem object
Export the blank object in an .xml export
Import that object into the client where the problem object is, overwriting existing objects