# IndexerGetStatus Status Codes

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

Code | Message | Explanation
--- | --- | ---
–1 | Finished | The indexing process is complete.
–2 | Out of disk space | Content ran out of disk space before it completed the indexing process.
–3 | File not found | The index file could not be found.
–4 | Database not found | The database into which you are trying to index could not be found.
–5 | Bad parameter | The indexing action syntax is incorrect.
–6 | Database exists | The database that you are trying to create already exists.
–7 | Queued | The indexing action is queued and it is run when all preceding indexing actions are complete.
–8 | Unavailable | Content is about to shut down or indexing is paused.
–9 | Out of Memory | Content ran out of memory before the indexing process could be 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 | Content is processing an index action that was previously interrupted.
–13 | Backup in progress | Content 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 that 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 | Content ran out of file descriptors.
–20 | LanguageType not found | The language type of the index data could not be found.
–21 | SecurityType not found | The security type of the index data could not be found.
–22 | Child engines returned differing messages | The child servers returned different messages to the DIH. This code is reported by DIH only.
–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 | The index action is queued to be sent to the IDOL Content component. This code is reported by DIH only.
–26 | `DREADDDATA`: Data received did not include `#DREENDDATA` | The data in the `DREADDDATA` action did not contain a `#DREEDNDDATA` statement indicating 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 by DIH only.
–28 | The index ID specified is invalid | The index ID returned by the child server is not valid. This code is reported by DIH only.
–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 by DIH only.
–30 | Database name too long | The name of the database in which you are indexing documents is too long. The length is defined internally as 63 characters.
–31 | Command ignored due to id match | The `DREINITIAL` action was ignored because it did not match the ID specified in the `InitialID` parameter.
–33 |  | The database cannot be created because the maximum number of databases was exceeded. The maximum is defined internally as 32,767.
–34 | Pending commit | The indexing job is complete and the documents become available for searching after the next delayed sync cycle, which is specified in the `DelayedSync` parameter.
–35 | Initializing | The indexing job is being started. This code is reported by DIH only.
–36 | Reading IDX | The IDX file is being read from disk, prior to being sent to the DRE. This code is reported by DIH only.
–38 | Processing in remote engine | The target engine of a `DREEXPORTREMOTE` operation is processing the exported documents.

NOTE: If the `IndexerGetStatus` action returns a positive number, this number indicates the percentage of the indexing queue that has been completed.

© Copyright 2020 Micro Focus or one of its affiliates | Send documentation feedback Close Send documentation feedback To open the configured email client on this computer, open an email window. Otherwise, copy the information below to a mail client, and then send this email to swpdl.idoldocsfeedback@microfocus.com. We appreciate your feedback! Product: Topic Title: Help Topic: Feedback:

_FT_HTML5_bannerTitle.htm