No way to use the utility binaries in a scheduled way

[marc broussard]

Hello

our version :
AWA 12.2

We have some difficulties tu use "utility".
For instance about the forecast.
We have 2 jobs:
the first generates the XML file. This XML contains the name of the application, the date, the time ... (the result is : forecast_XXXX.xml ), we want to forecast.
It works fine.

The second does not work in an one automation job but works by executing it in a command line on the server:
D:\Automic\Utility\bin\UCYBDBRT.exe -X D:\Automic\Utility\bin\Queries\forecast_XXXX.xml

If we create a powershell script, it is fine bye executing it in a powsershell windows ...
But not in the Task Scheduler of windows, and neither in One automation.

It seems that the binaries in utility can not be excecuted in a scheduled way (windows task scheduler, neither one automation).

We have another kind of utility's binary with the same problem.

No error (the job does nothing that is all), but we have  a return code :
     -1073741819

the account is administrator

thanks a lot

------------------------------
Marc Broussard
ENGIE FRANCE
------------------------------

[Pete Wirfs]

In my opinion, you are missing some UCYBDBRT parameters.  I always use three parameters at minimum; -X, -O and -T.   I also find it useful to :REGISTER the output file.

https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/12.3/Automic%20Automation%20Guides/help.htm#Utilities/admin_AEDBReportingTool_About.htm


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

[Krum Ganev]

Hey there,

I may sound a little bit like the support but we need that info.

What is your exact version of the AE?

Which is the other utility binary that fails when executed via automic?

Is the job started with a specific account or as NT Authority System? Is ot local or AD?

Was this working before? Did it occur after an upgrade?

Are there any logfiles produced? Can you enable the traces and start again?

Can you try to start with all paremeters as per the official documentation. In you command there is a blank space between X and D, did you try without?

Is there any error in the Windows Event Viewer?

What type of job you are using(BAT or EXTCOMPROC)? 

[Bernhard Flegel]

Hello Marc,

you wrote your command line:
D:\Automic\Utility\bin\UCYBDBRT.exe -X D:\Automic\Utility\bin\Queries\forecast_XXXX.xml

Is it possible that you simply inserted a space between the parameter -X and the path? According to the documentation, the path has to be added directly to -X (-XD:\Automic\....)

In my own experience, there are problems when this space is inserted.

Greetings
Bernhard

------------------------------
Landeshauptstadt München
------------------------------

[marc broussard]

hello
our version  :
OA 12.2.3
windows: 

Windows Server 2016 Standard

we have the problem since an minor OS upgrade.

It is not the space which is the raison of the error:

on the server if with we put the command in a script (powershell) ...
    => it works (with the space and without the space)
the same script does nothing in a JWIN
it looks like the utility of AWI does only want to work , if we start it from the console.

otherwise: No log (finish OK but just  does nothing)

actually we do have the same problem with the report utility binaries.

we manage to do same reports only when we are connected on the server with a windows session.

[Pete Wirfs]

I would make sure the service account that runs your windows tasks still has all of the required elevated rights under "Local Security Settings".

Those rights include;
   Act as part of the operating system
   Adjust memory quotas for a process
   Allow log on locally
   Back up files and directories
   Logon as batch job
   Logon as service
   Replace a process level token
   Restore files and directories


https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/12.3/Automic%20Automation%20Guides/help.htm#Installation_Manual/InstallAgents/InstallAgentWindows.htm

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

[marc broussard]

Thanks
It was a good idea:
1/ our account service belongs to the group "administrators"
2/ the groupe administrators had not all the rights you said
    => also I added the group administrators where it was missing

but not enough 
it does not work

thanks for any another idea

Marc Broussard

[Michael Dolinek]

Hi @marc broussard

I would try to run a shell (Command Prompt) with your technical user that is used to execute the JOBS in the Automation Engine​.

1) Login to your server using RDP
2) Open a Command Prompt
3) Start a new shell with the technical user by typing e.g. runas /user:TechnicalUser cmd.exe
4) Execute the desired commands (step-by-step) in the new Command Prompt and observer the output; Check if you can access all the required files/directories/network resources....

Error -1.073.741.819 converted to Hex is FFFF FFFF C000 0005. Searching this in the internet points to "access violation".....

------------------------------
Engineering Program Manager
Broadcom
------------------------------

[marc broussard]

thanks

Our command is in a powershell script  (script_rapport.ps1),
so what we did is:
1/  connexion by RDP with the account service used by automic
2/ in a cmd window, I execute:
      D:\>runas /user:domain/account_service    "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe D:\Automic\Utility\bin\script\script_rapport.ps1"

and it works fine!
the rapports are generated!
il the script  we have such commands like:
         D:\Automic\Utility\bin\ucybdbrt.exe -C 1111 -X D:\Automic\Utility\bin\Queries\rapport.applicationX.xml

with 1111  the OA client


IN OA, we tried again:
nothing


in the  D:\Automic\Utility\Logs we find:

      20200818/153349.418 - U00003545 UCUDB: Opening database ...
     20200818/153349.418 - U00029112 UCUDB - Length of the DB-History area: 100

thanks for help

[marc broussard]

one more thing: 
in the windows logs we found those errors (numerous) :

Faulting application name: ucybdbrt.exe, version: 12.2.3.0, time stamp: 0x5cdf165d
Faulting module name: ntdll.dll, version: 10.0.14393.3630, time stamp: 0x5e8d4386
Exception code: 0xc0000005
Fault offset: 0x000000000003fa0c
Faulting process id: 0x22b7c
Faulting application start time: 0x01d675645aefcee4
Faulting application path: D:\Automic\Utility\bin\ucybdbrt.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 9d5ba420-a144-45a8-9af2-ab1f0a26f725
Faulting package full name:
Faulting package-relative application ID:

[Dejan Hrubenja]

We use a Windows service account too and it is/was member of group "Administrators"
Batch jobs didn't run here too.
Then we assigned these rights to the service account directly (no idea where this information originated from) and it worked.