Receiving a "Last index failed" message or the Index History has many successive failures when attempting to index a collection
Symptom
- The Index Status in CONTENTdm Administration shows "Last index failed" and clicking View log shows "collection files are busy" statements
- The index log shows multiple ongoing failing index attempts
Applies to
- CONTENTdm Administration
Resolution
Please contact OCLC Support with the following details to have your collection unlocked:
- Server ID
- Collection alias
The collection will have to complete the current indexing process before it can be unlocked. Successive indexing failures are typically caused by an interruption to the current job by new requests.