RA Solution Load Fails with Return Code 1 and Error 38999
Article ID: 442061
Updated On:
Products
Issue/Introduction
When attempting to load a Rapid Automation (RA) solution package (e.g., RA FTP) into the Automic Automation Engine database using the DB Load utility, the process fails.
The following symptoms are observed in the logs:
- The utility identifies itself as
DLL 'ucybdbld'with a version string (e.g.,24.4.4+build...). - The log terminates abruptly with Error code = 38999.
- The job ends with Application return code = 1.
The command used to run the db load looks something like
llowing command structure:
⚠️ IMPORTANT: Always test command updates first in a non-production environment.
Environment
OS: UNIX/Windows
Version: Any (e.g., 21.0.15, 24.4.4, 26.0.0)
Component: DB Load loading RA solution (e.g., RA.FTP, RA.Informatica, etc...)
Cause
This failure occurs when the native binary executable of the DB Load utility (ucybdbld) is used to attempt to load a .jar RA solution file.
By design, Rapid Automation (RA) solution packages cannot be processed by the standard C++ batch loader. The native utility will skip the loading process and exit with a return code of 1 when a .jar file is passed via the -X parameter.
Resolution
To successfully load an RA solution into the database, the Java version of the DB Load utility (ucybdbld.jar) must be used instead of the native binary.
Update the script or job definition to execute the load via Java using the following command structure. Note that if the solution is successfully loaded, the new RA object types should be visible in the Automic Web Interface (AWI) after a fresh login:
⚠️ IMPORTANT: Always test command updates first in a non-production environment.
Additional Information
- For RA.FTP users: Note that RA.FTP is past End of Support. It is recommended to migrate to the Integration.FTP Agent, which does not require a database load.
- Consult the to verify Java and Engine version requirements.
Feedback
