Installation Guide : EMSRV for Windows : Troubleshooting EMSRV as a Windows service
Troubleshooting EMSRV as a Windows service
This section describes common problems when running EMSRV as a Windows service and their solutions.
For more on the location of files in the installtion, including varoot and mgrroot, see file locations.
Normal EMSRV execution (not a service) does not start
EMSRV must be run from the directory of the executable. If it is run from any other directory, it will pause for about 30 seconds and then exit. You can check for this condition by looking in the Event Log for EMSRV error records with a RC of 1063.
The error message An internal Windows NT error has occurred appears at startup
Open the Services control panel. Verify that the startup parameters are entered correctly and the user name is a valid user on the server. The -u option is always needed to start the server.
The error message The specific service is disabled and cannot be started appears at startup
From the Control Panel, select Services and then the HW Profiles button. Select the Original Configuration. If its status is disabled, enable it by selecting the Enable button.
The start button is disabled
The service could already be running on the local machine. Otherwise the service could be disabled. Select EMSRV Service in the Services control panel. Select Startup to open the Service window. Select Automatic or Manual for Startup Type.
The error message The service did not start due to a logon failure appears at startup
An invalid password was entered in the Service window of the Services control panel, which you access by selecting Startup. Open the Service window and change the password or log on as the System Account.
The error message The process terminated unexpectedly appears at startup
EMSRV could already be running in normal mode (that is, not as a service) on the local machine. This instance must be stopped for EMSRV to run as a service.
The error message Access Denied appears when installing the service.
The user must have write access to the \Windows\system32 directory so that the message file can be copied from <varoot>\bin to the \Windows\system32 directory.
Last modified date: 06/09/2021