Headless: Failed to open EA, error 800706BE

[koenemann]

In our Jenkins build, we managed to access the COM object and call Repository.open: http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1393239529

We carefully followed this guide (each step was necessary): http://www.catchlimited.com/enterprisetester/Configuring%20EA%20for%20use%20with%20ET.pdf

The EA does in fact start (it is shown in the task manager) but it does not respond, I waited up date 30min. After killing the EA instance, i get this error:

Der Remoteprozeduraufruf ist fehlgeschlagen. (Ausnahme von HRESULT: 0x800706BE)    bei EA.IDualRepository.OpenFile(String FilePath)

The English translation would something like:

The remote procedure call failed. (Exception of HRESULT: 0x800706BE)    at EA.IDualRepository.OpenFile(String FilePath)

The fact that worries me most is that the EA is stuck in memory until it is terminated manually.
First I thought that the license is missing, but I can start EA from the 'jenkins' user.

Any idea why the EA does not start properly?

[qwerty]

Google leads me to this Mickeysoft page (it's already in German): http://support.microsoft.com/kb/896989/de

q.

[koenemann]

Google leads me to this Mickeysoft page (it's already in German): http://support.microsoft.com/kb/896989/de

q.

Thanks for the reply. Unfortunately, this is unrelated to our problem. We do not use the Microsoft Operations Manager at all.

[chris pearce]

I also have encountered this problem when trying to run a c# automation .exe to export the database to HTML.  I find that I only get the exception when the system is running as a scheduled task, I even wrote a service to wrap up the export in, however the same issue occurs.

EA starts in task manager opens then get lost in it own little world never to return @ 0% CPU load.   When the task is terminated control returns and the exception is thrown although I expect the exception has more to do with the ungraceful exit of the thread that anything else.

HOWEVER if I run the exe as a USER from the desktop this problem does not occur.  I have tried all possible combinations of run-as-user x etc as well as a scheduled task or a service.  It doesn't seem to want to work unless manually executed?

How  :-? can we progress this thawny issue ?  

[qwerty]

Just as a side note: it has been discussed here that EA can not be run as a service. It must be run from a user or any dialog box will run into the void and never complete. This will cause the hang you see.

q.

[chris pearce]

Ah hmmm, thats odd because im getting the same problem when i run the    standalone non service version if i run it as a scheduled task.  I cannot access the server and have to invoke everything via remote desktop, this automatically logs off after 24hrs of inactivity so i need to run the automation SOMEHOW on the server.... unattended.

Do you understand what the actual problem is qwerty? or if there's a work around? or a "normal" way of doing this ?

[qwerty]

Actually when I ran into this I simply used an old workstation sitting somewhere in a corner where I logged in and started EA. IIRC there is no real solution for the "run as service" issue. I might be wrong though as I was happy with my work around. You can try to search the forum (use the button top left, extend the time frame to all posts). Or maybe someone else has a clue.

q.

[Geert Bellekens]

Actually when I ran into this I simply used an old workstation sitting somewhere in a corner where I logged in and started EA. IIRC there is no real solution for the "run as service" issue. I might be wrong though as I was happy with my work around. You can try to search the forum (use the button top left, extend the time frame to all posts). Or maybe someone else has a clue.

q.

I think the guys from LieberLieber managed to get EA running as a service.
Check out EA as an unattended Windows Service on Windows Server 2008R2 and higher

Geert

[chris pearce]

Yes Geert i asked sparx directly and they also pointed me to that whitepaper, although i haven't yet had time to try it properly.  The problem stems from the licence activation with EA being tied to the id of the thing that starts it, when system starts it it has no Key info registered and hangs on the keystore window interaction.  You need to create a service which starts EA in the system context once setup the keystore licence stuff for SYSTEM, then it should work.  Thats my reading of the method anyway....