search cancel

Documentation Change for CallAPI for Windows due to Invalid parameter in example


Article ID: 87402


Updated On:


CA Automic Workload Automation - Automation Engine


Error Message :
U03000010 Could not open script file 'AE', error code '2' 

The description in the chapter Application Integration Guide > CallApi > Using the CallApi mentions an invalid start parameter for the ini file in the example for the Windows CallAPI: 

Old Documentation:
Example of calling the CallAPI in Windows: 
Which results in: 
C:\uc4112\CallAPI\Windows_x64>ucxbxxxc script=script.txt, AE INI=ucxbxxxc.ini 
20161013/105120.087 - U03000000 Program 'UC4 Call Interface', version '11.2.0+build.2347', change list '6995609' started. 
20161013/105120.087 - U03000017 Build Date: '2015-10-21', '14:44:44' 
20161013/105123.134 - U03000010 Could not open script file 'AE', error code '2' 
20161013/105123.134 - U03000002 Program 'UC4 Call Interface' version '11.2.0+build.2347' ended abnormally. 

New Documentation:
A correct example would be:


Cause type:
Root Cause: The example in the documentation is syntactically corrrect, but the spaces after the commas are wrong for the LOGON= parameter.


OS Version: N/A


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


Automation Engine 12.0 Online Documentation:
Installation Guide > CallApi > Using the CallApi

Fix Status: Released

Fix Version(s):
Component(s): Documentation Guide

Automation Engine 12.0.1 - Available

Additional Information

Workaround :
Remove the blanks between the parameters or remove the department from the Logon parameter if it is not necessary.