IndexerGetStatus Status Codes

NOTE:

Codes in bold are status messages. All other codes indicate there is a problem with the indexing process.

Code Message Explanation
-1 Finished

The indexing process is complete.

By default, the action reports a job as finished only when all the child servers report the job as finished. This behavior can result in large queue sizes. To mark each job as finished when one child server completes it, set the Polling parameter in the [Server] section of the DIH configuration file to False.

-2 Out of disk space IDOL Server ran out of disk space before the indexing process was completed.
-3 File not found The index file was not found.
-4 Database not found The database that you tried to index into was not found.
-5 Bad parameter The indexing action syntax is incorrect.
-6 Database exists The database that you tried to create already exists.
-7 Queued DIH queues the indexing action and runs it when all preceding indexing actions are complete.
-8 Unavailable IDOL Server is about to shut down or indexing is paused.
-9 Out of Memory IDOL Server ran out of memory before the indexing process was completed.
-10 Interrupted The indexing action was interrupted.
-11 XML is not well formed Indexing failed because the XML is not well formed.
-12 Retrying interrupted command IDOL Server is running an indexing action that was previously interrupted.
-13 Backup in progress IDOL Server is performing a backup.
-14 Max index size reached The indexing job exceeds the maximum indexing size (your license determines the maximum indexing size).
-15 Max number of sections reached The indexing job exceeds the maximum number of sections that you can index (your license determines the number of sections you can index).
-16 Indexing Paused The indexing process was paused.
-17 Indexing Resumed The indexing process was restarted.
-18 Indexing Cancelled The indexing process was cancelled.
-19 Out of file descriptors IDOL Server ran out of file descriptors.
-20 LanguageType not found The language type of the index data was not found.
-21 SecurityType not found The security type of the index data was not found.
-22 Child engines returned differing messages The child servers returned different messages to the DIH. This code is reported only by DIH.
-23 Badly formatted index command The indexing action was rejected by a child server because the syntax is not valid.
-25 To be sent to DRE DIH queues the index action to send to the IDOL Server. This code is reported only by DIH.
-26 DREADDDATA: Data received did not include #DREENDDATA The data in the DREADDDATA action did not contain a #DREEDNDDATA statement to indicate the end of the data.
-27

Command failed more times than the configured retry limit

The indexing action exceeded the maximum number of retries specified by the MaximumRetries parameter in the DIH configuration. This code is reported only by DIH.
-28 The index ID specified is invalid The index ID returned by the child server is not valid. This code is reported only by DIH.
-29 Command was redistributed to sibling engines as this engine was either unavailable or not accepting index jobs The indexing action was sent to sibling servers because the child server was either unavailable or not accepting indexing jobs. This code is reported only by DIH.
-30 Database name too long The name of the database that you are indexing documents into is too long. The maximum length is 63 characters.
-31 Command ignored due to id match The DREINITIAL action was not processed because it did not match the ID specified in the InitialID parameter.
-33

 

IDOL Server cannot create the database because it has reached the maximum number of databases. The maximum is 32,767.
-34 Pending commit The indexing job is complete and the documents are available for searching after the next delayed synchronization cycle, which you specify in the DelayedSync parameter.
-35 Initializing DIH is starting the indexing job. This code is reported only by DIH.
-36 Reading IDX DIH is reading the IDX file from disk, prior to sending it to IDOL Server. This code is reported only by DIH.
NOTE:

If the IndexerGetStatus action returns a positive number, this number indicates the percentage of the indexing queue that is complete.


_HP_HTML5_bannerTitle.htm