The information in this article applies to product: e-Work 6.x
Issue
- When installed on a server that's part of a server cluster, the Engine fails to start.
Resolution
When the Engine is installed, MSDTC (Microsoft Distributed Transaction Coordinator) is set as a local dependency for the Engine service. However, in a server cluster, MSDTC runs as part of the cluster. Thus the Engine fails to start when it is unable to find a local instance of MSDTC.
To resolve this, MSDTC needs to be removed from the list of dependencies for the Engine service. This can be done as follows:
- Go to Start --> Settings --> Control Panel --> Administrative Tools --> Services --> e-Work Engine. Right-click, select Properties --> Log On and note the user account that is being used to run the Engine service.
- Because the dependencies will be deleted when the service is uninstalled, make a note of the dependencies for the e-Work Engine service by checking the DependOnService registry value here:
HKEY\_LOCAL\_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\e-Work Engine.
RPCSS, COMSysApp, and MSDTC can be ignored.
- Stop the Engine service, if it is running.
- Run the following at the command line:
eEngine.exe /uninstall
Next, reinstall the Engine service at the command line with all of the dependencies noted in the registry, other than RPCSS, COMSysApp, and MSDTC. The first 2 are added by default and MSDTC is being removed. There may not be any dependencies that need to be added. If a dependency name contains a space, put the entire switch in double-quotes, e.g. eEngine.exe /install "/dependency:dependency name here".
Go back to Start --> Settings --> Control Panel --> Administrative Tools --> Services --> e-Work Engine. Right-click, select Properties --> Log On and verify that the account noted previously is being used. Click on the Dependencies tab and verify that Distributed Transaction Coordinator has been removed.
- Start the Engine service.
