There is a known issue when stopping the FAST ESP services via control panel.
When the FAST ESP services are started, some configuration files are loaded into memory.
When the FAST ESP service shuts down, those configuration files are written back in the disk.
However, if ESP is forced to shut during the process of the configuration files being written to disk, we have seen files, such as the NodeState.xml become corrupted.
This will result in an error when trying to start the services via Control Panel:
"Could not start the FAST ESP Service on local computer". The service did not return an error. This could be an internal Windows error or an internal service error. If the problem persists please contact your System Administrator.
Windows Event Logs will show: "The description for Event ID (3) in Source (FASTESPService) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: File "win32serviceutil.pyo", line 785, in SvcRun File "FASTESP.pyo", line 162, in SvcDoRun; exceptions.SystemExit; StateParseError: Line 1, Column 0, Error: not well-formed (invalid token).
To resolve, please replace $FASTSEARCH\etc\NodeState.xml with the attached NodeState.xml file on your local installation. The best way to avoid this type of corruption for future is to perform a start or a stop of FAST services using the following process:
- Stop FAST ESP: From the command line run the following command: %FASTSEARCH/bin/nctrl stop.
- Open the task manager and make sure that all FAST processes are stopped, which are any processes being run by the 'SDKTFast' user.
- Start FAST ESP: net start FASTESPService.