Configuring Enterprise Server to not run as a service
By default, Meridian Enterprise Server runs as a service. Among other things, this means that it:
- Does not require a user to log on
- It can start automatically when Windows starts
- Performance, reliability, security, and administration are simplified
This also means that Enterprise Server cannot interact with the Windows desktop or a specific user. In most cases, this is not a problem. However, some rendering applications do not support running as a service for all output types. In those scenarios, Enterprise Server must be configured to run under a logged on user account for rendering to succeed.
Note This requirement is noted in the "Configuring the ... rendering module options" chapter of the rendering modules that are known to require configuration as described in this topic.
To configure Enterprise Server to run as a logged on user:
- In Meridian Enterprise Server Administration Console, create and configure the rendering profiles and schedule the publishing jobs normally as described elsewhere in this guide.
- On any Meridian Enterprise Server node, log on as the Windows user that is configured for the Meridian Enterprise Server service as described in Creating the configuration database.
- If the computer has an application installed for rendering that does not support being run as a service, modify the scheduled tasks that perform rendering with that application and enable the Run only when user is logged on option.
- In the Services applet in Control Panel, stop and disable the Meridian Enterprise Server service.
-
Start the Meridian Enterprise Server service manually from a command line in console mode:
BlueCieloECM.EnterpriseService.exe /c
- Leave the service account logged on. It will need to be re-logged on after server restarts before scheduled jobs will run.
- Repeat steps 2 to 6 on all remaining nodes (primary and cluster nodes) that will perform rendering with the affected rendering applications to the affected rendition formats.