User Interface & Server as Windows Service

[n_lev]

Hi!

I've configured my server to run WinCC OA as a service with auto start.
In the WinCC OA Server Console I have 2 User Interface managers (1 for GEDI and 1 for vision) for the purposes of development and testing (configured to start manually only). Usually (in production environment) I don't use them as I have a proper WinCC clients on other PCs. What I found is if I run my server the usual way (Start via the project administration) then I can start my UI managers when needed. BUT if i run my server as a Windows service then I can't start neither of my UI managers. If I select it and click "Manager Start" the console shows that manager changes status to "2" and pmon seem to report that it started but I can't actually see anything on the screen, it's like the UI is invisible). Is that an expected behaviour when the server runs as a service or am I doing something wrong?

[leoknipp]

Hello,

the service is used for processes which shall run in the background without any user interface.
Therefore you don't see the tasks which are started by the Pmon running as service.

You can start the user-interfaces with an own command, e.g. a desktop link:
WCCOAui -proj

If the service is started with the local system account you can activate the option "Allow service to interact with desktop". Then you would see the user interface.
It is recommended not to use the local system account because we have noticed permission problems when accessing network devices if this account is used.

Best Regards
Leopold Knipp
Senior Support Specialist