Author Topic: Batch trigger EA Client  (Read 1736 times)

Lalabox

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Batch trigger EA Client
« on: June 01, 2022, 08:22:50 pm »
Hi @All
I know there are Issues running the EA Client "headless", but maybe someone knows a way around:

What I succeeded in:
- Create Task in Windows Task Planner with "Auto-User" context
- to trigger a batch script that will call
- a parametrised xy.exe that will
- call the ea.exe to perform spectial automated operations on some repository.
--> Task --> Batch --> xy.exe --> ea.exe --> Happyness!

This works perfectly, but ONLY when the Auto-User is (remotely) logged in.

What my problem is:
- When NOONE is logged in at the server, the task fails: the ea.exe won't run (Error 800401a).
- When ONE OTHER user (e.g. Admin-User) is logged in at the server, the task runs perfectly, but ea.exe does not run in the context of "Auto-User", but is owned by the currently logged in "Admin-User". Although, it was initially triggered by the Task-Planner from a task configured to run in the context of the "Auto-User"...

So:
- How can this even be happening?!?
- What can be done to get the ea.exe to a) run and b)in the context of the configured "Auto-User" when c) NOONE is logged in at all?

Hint: Someone told me this has to do with Windows "Services" triggering "Desktop", whatever thsi means, but I have not further details.

Ideas?

Regards
Christian

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +396/-301
  • I'm no guru at all
    • View Profile
Re: Batch trigger EA Client
« Reply #1 on: June 02, 2022, 03:51:43 am »
I guess he Sparxians would suggest thei web stuff.

For me I once just set up a WS somewhere in an office to serve as "EA server" with a label "Do not turn off!". Worked but is definitely nothing for a large company.

q.