text: Messages 397, 398, and 399 are viewable and contain the list of documents (their metadata) 
  that are affected by this operation. In the case of message 398 (fail), the failure reason is 
  documented, as well. 
  
  Each time the FTS Server reports an error, message 439 is issued, and it contains the error 
  message that was returned by the FTS Server. In this case, the query that is entered by the 
  user contained a wrong syntax for a proximity or fuzzy search. 
  
  **15.7.2 Full Text Search Server log**
  
  You can troubleshoot the FTS Server by configuring and viewing the FTS Server logs. The 
  FTS Server generates logging information during server startup, indexing, and searching. 
  The log files contain configuration information, warnings, errors, and debugging information 
  that can be useful for monitoring the server and for troubleshooting specific issues. The 
  command-line tools also generate log files. By default, log files are stored in the FTS_Home/log 
  directory. You can run the**configTool**with the**list -logFolder**command to see your log 
  directory. 
  
  Every message in the log file has an associated level that indicates the message type. The 
  logging levels, in descending order of severity, are defined: 
  
  (cid:2) SEVERE: Errors and exceptions that occur while the server is running. Typically, SEVERE 
  messages include detailed information with the stack trace. 
  
  (cid:2) WARNING: Mild problems that might require the attention of an administrator, such as a 
  missing value for a setting with a default value, or the truncation of a document during 
  indexing. 
  
  (cid:2) INFO: Informational messages that are generated during system operation. 
  
  (cid:2) FINE: Detailed messages for debugging purposes. This level includes parsed queries. 
  
  (cid:2) FINER: More details, for example, the results of document parsing. 
  
  (cid:2) FINEST: The most detailed level. 