DCS 4.2.0.0 running on RL "stops" when trace window closed

[alekz]

This one is a first for me.

Running DCS 4.2.0.0 (Latest) on IDM 4.7.1 HF1 on a Windows Server 2012R2
in a Remote Loader.

I tail the tracefile using Baretail and the Remote Loader Trace window
is open. It's processing events like crazy.

As soon as I close the Driver Trace window the processing stops.
Nothing more is written to the RL trace.

On the IDM Engine side it sits and waits with this in the trace for the
last 35 minutes:
Data Collection Service Driver ST:Remote Interface Driver: Waiting for
receive...

The dirxml_remote.exe process is running, using 212MB of memory.
0% CPU utilization.

Can't stop the service, have to kill it with Task Manager.

Very odd.

Anybody seen this before?



--
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

[aburgemeister]

This sounds like things I think many of us have hit with the regular
microsoft active directory (MAD) driver when using a Remote Loader (RL).
I presume your RL is also the 4.7 SP1 version, and if so I would probably
tinker with the 'Interact with desktop' checkbox (something like that) on
the service under 'services.msc' to see if that helps. Otherwise, don't
load the trace screen.

I've see nit other ways where the service never auto-started unless
somebody logged into the physical console of the lousy system, but no of
course this is not how it should be.

Do you have the RL service set to run as a particular user, or just as SYSTEM?

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.