Resolution:
Description:
==========

This error occurs when the EMS server is started as a Windows Service and the secondary configuration files location in the main configuration file of the EMS server is pointing to a shared network drive (i.e. \\share-name\path\queues.conf) or a mapped drive on the local machine that maps to a shared network drive (i.e. Z:\path\queues.conf).


Environment:
=========

Microsoft  Windows
TIBCO Enterprise Message Service (All versions)

Symptoms:
========

When started as a Windows Service, the EMS Service fails to start with a “service specific Error”. The EMS server will start with the same configuration files when started from the command line.

Cause:
=====

When started from the command line, the EMS server is started with the privileges of the user logged on to the Windows machine. If the user has read/write/execute permission on the shared drive, the EMS server will start. However, when started as a Windows Service and the EMS server is started as the local SYSTEM user who does not have permission on the shared drive, the service will fail to start.

Resolution:
=========

On Windows 2000/2003/2008, a Windows Service can be configured to start up using a non-SYSTEM user. The EMS service needs to be configured to start up using a normal user who has access to the shared drive, not the default SYSTEM user. When the machine reboots, the user will need to login to the machine and start the Service as the Service cannot be started automatically as it does for a SYSTEM user.

This feature is not available on Windows XP. There is no other way to start the EMS Service on Windows XP while the secondary configuration files are located on a shared drive. The only option is to start the EMS server from the command line or to put the secondary configuration files on the local machine.