Microsoft FAST service cannot start on the server where FAST is installed. A message in the Windows Event Log and messages in the node controller log indicate that the Microsoft file, nodestate.xml, is corrupt. The file must be replaced.
When the $FASTSEARCH/etc/nodestate.xml file is corrupt, the following error message is written to the Windows Event Viewer;
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).
Additionally, according to Microsoft, the following messages are written to the node controller log:
[2010-09-24 12:29:24.136] VERBOSE systemmsg Starting ESP Service (PID: 740)
[2010-09-24 12:29:24.136] CRITICAL systemmsg Failed to start ESP Service
(Node Controller): StateParseError: Line 1, Column 0, Error: not well-formed
Nodestate.xml is a configuration file. Its contents are unique to your system, and depend on the features installed and how they are configured. CA Technologies is not able to supply you with a replacement file; the file must be obtained from Microsoft Support.