Automic Workload Automation

 View Only
  • 1.  Executing CallAPI - Access Denied

    Posted Dec 13, 2019 01:55 PM
    I setup the CallAPI for Windows and Java in v12.3 on my AE engine server.  I am trying to test the Windows version.  I am an admin with all the authorizations and privileges set.

    I created a script that contains:  :SET &ACTJOB# = ACTIVATE_UC_OBJECT(JOBS.WIN.TEST.CALLAPI)
    I did the hardcoding of the user in ucxbxxxc.ini
    [GLOBAL]
    system=AUTOMICD
    language=(E,D)
    helplib=.\uc.msl
    queue=
    timeout=60

    [TRACE]
    file=..\temp\ucxbxxxc_trace_##.txt
    trccount=10

    [USER]
    client=1111
    user=tosgood
    dept=XXX
    pass=­­XXXXXXX

    [CP_LIST]
    2217=OITAEAPT01
    2218=OITAEAPT01

    I executed this command:  C:\Automic\CallAPI\windows\x64>UCXBXXXC SCRIPT=C:\Automic\Scripts\run_jobs_win_test_callapi.txt

    I get this result:
    20191213/111115.419 - U03000000 Program 'UC4 Call Interface', version '12.3.0+build.1560514133449', change list '1560505849' started.
    20191213/111115.419 - U03000017 Build Date: '2019-06-14', '14:20:22'
    20191213/111123.687 - U00003210 Logon error: Access denied
    20191213/111123.687 - U03000002 Program 'UC4 Call Interface' version '12.3.0+build.1560514133449' ended abnormally.

    Any suggestions on how to troubleshoot this?

    Thanks

    ------------------------------
    Developer
    State of Colorado
    ------------------------------


  • 2.  RE: Executing CallAPI - Access Denied

    Posted Dec 16, 2019 04:59 AM
    Hi

    user tosgood neets the privileague Logon via call api (set in user object)

    cheers, Wolfgang

    ------------------------------
    Support Info:
    if you are using one of the latest version of UC4 / AWA / One Automation please get in contact with Support to open a ticket.
    Otherwise update/upgrade your system and check if the problem still exists.
    ------------------------------



  • 3.  RE: Executing CallAPI - Access Denied

    Posted Dec 16, 2019 10:30 AM
    Hi Wolfgang,

    I am an admin and I have full authorizations and all privileges are set, including Logon via call api.

    Looking through the documentation, I found "Use the key RESERVED_API_USERS in the UC4 Variable UC_SYSTEMS_SETTINGS (available in system client 0000) to reserve a number of Dialog licenses for CallAPI logins. This way, CallAPI and manual user logins do not block each other."  However, it does not say what the setting should be.  Looking further in documentation, the UC_SYSTEMS_SETTINGS does not show RESERVED_API_USERS in the list of parameters.  Searching for RESERVED_API_USERS returns 0 results.

    So I changed the RESERVED_API_USERS from 0 to 1, all the way to 5, and still get access denied.

    I've searched the CP/WP logs and the Windows agent logs but find no entries related to the attempted login using callapi.

    At this point, I'm at a loss on how to find why access is denied.

    Tim


    ------------------------------
    Developer
    State of Colorado
    ------------------------------



  • 4.  RE: Executing CallAPI - Access Denied

    Posted Dec 16, 2019 11:57 AM
    It must have been something in my user object.  I created a new user and used those credentials, it worked.  So I renamed myself and created a new user account for myself and it is working.

    ------------------------------
    Developer
    State of Colorado
    ------------------------------



  • 5.  RE: Executing CallAPI - Access Denied

    Posted Dec 16, 2019 12:03 PM
    great that it works now!

    the cause would have been interesting but I am afraid we will never know :-(
    cheers, Wolfgang

    ------------------------------
    Support Info:
    if you are using one of the latest version of UC4 / AWA / One Automation please get in contact with Support to open a ticket.
    Otherwise update/upgrade your system and check if the problem still exists.
    ------------------------------



  • 6.  RE: Executing CallAPI - Access Denied

    Posted Dec 01, 2020 11:38 AM
    Hello Expert, 

    We are also getting same error.  "Logon error: Access denied "

    We are executing below command 
    D:\install\AE V12.3\API\CallAPI\windows\x64>ucxbxxxc.exe SCRIPT=D:\install\AE V12.3\API\CallAPI\windows\x64\test_1.txt LOGON=100, test_user, department, password INI=D:\install\AE V12.3\API\CallAPI\window

    Output :

    20201201/165911.292 - U03000000 Program 'UC4 Call Interface', version '12.3.0+build.1560514133449', change list '1560505849' started.
    20201201/165911.292 - U03000017 Build Date: '2019-06-14', '14:20:22'
    20201201/165911.354 - U00003210 Logon error: Access denied
    20201201/165911.354 - U03000002 Program 'UC4 Call Interface' version '12.3.0+build.1560514133449' ended abnormally. ​

    From CP log I can see below error 

    20201201/165911.292 - U00003406 Client connection '23(11)' from 'xx.xx.xx.xx:12121' has logged on to the Server.
    20201201/165911.308 - Dialog '1,' logged on (Client connection='23').
    20201201/165911.354 - U00003413 Socket call 'recv(23)' returned error code '10054'.
    20201201/165911.354 - An existing connection was forcibly closed by the remote host.
    20201201/165911.354 - U00003407 Client connection '23(10)' from 'xx.xx.xx.xxx:12121' has logged off from the Server.

    I manually trigger the job, user has enough permission to execute the job.

    Appreciate , if any suggestion/guidance on this.  

    Regards,
    Viral ​


  • 7.  RE: Executing CallAPI - Access Denied

    Posted Dec 01, 2020 07:48 PM
    @viral pabari  

    Check the grants for the user within UC4.  Under privileges/AccessControl there is a setting called "Logon via CallAPI".  This has to be turned on.

    ------------------------------
    Pete Wirfs
    SAIF Corporation
    Salem Oregon USA
    ------------------------------



  • 8.  RE: Executing CallAPI - Access Denied

    Posted Dec 02, 2020 02:54 AM
    Hello @Pete Wirfs ,

    User has full access including ​ "Logon via CallAPI". 

    Regards,
    Viral 



  • 9.  RE: Executing CallAPI - Access Denied

    Posted Dec 16, 2019 12:01 PM
    Hi Tim,

    RESERVED_API_USERS is only valid/important if you are limited on User dialog licenses fot the case that all licesnces are taken from users that are logged on - this setting reserves xxx dialog client licenses for call API connections.

    If you user has this privileague i would guess its a typo in user/dep password string in ini file...

    In PWP log and CP log ther must be an logon attempt from APi and this user.

    cheers, Wolfgang


    ------------------------------
    Support Info:
    if you are using one of the latest version of UC4 / AWA / One Automation please get in contact with Support to open a ticket.
    Otherwise update/upgrade your system and check if the problem still exists.
    ------------------------------



  • 10.  RE: Executing CallAPI - Access Denied
    Best Answer

    Broadcom Employee
    Posted Dec 16, 2019 12:01 PM
    @Tim Osgood
    the parameter still exists in v12.3 but the item has been removed from the doc​. I will need to check if we removed to for a reason.
    In the meantime, the details still exist in earlier doc versions RESERVED_API_USERS

    Hope that helps

    David


    ------------------------------
    Senior Product Line Manager - Automation
    CA Technologies, A Broadcom Company
    ------------------------------