
Originally Posted by
markclemens
Hi Matteo,
When the zenon runtime is started as a service, it is also necessary for the console application to be started in the same session (session 0) within the same user context as the zenon runtime, in order to access the API. Windows, through something called session 0 isolation, prohibits applications in another (interactive) session to interact with applications or services in session 0.
Also Windows restricts inter process communication through the API not only to the same session but also to the user and the user elevation level. When you start the runtime as a regular user and a console application in the same user context but with elevation (e.g. because visual studio was started with elevation and debugging was started from studio), the interaction will fail.
Best regards,
Mark