This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 70%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
We are experiencing search function issues even though the incremental search crawl had been running on Application server every 4 hours for the past 18 months. Decided to run a full search but it did not finish running so Stopped it. Even since then we have been unable to run a full or incremental crawl without errors or latency issues.
Error example "The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Caught exception when preparing generation GID[82146]: (Not enough free parts for a new generation to be prepared.); Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID =_______________________________________"
We have also discovered that an upgrade is required on the Web Front End Server and Application Server - upgraded last in 2017 when SP2016 farm was implemented.
Tried to upgrade to August 2020 Patch 16.0.5044.1001 this also failed.
We still have the search function issue and not sure where to progress from here , any ideas are welcome?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 7.000000000000001%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
Hi @Ali ,
Is there any progress on this issue? Have you solved it?
If my reply helps you, please click "Accept Answer" and upvote it.
Hi @Ali ,
Per my research, I found some similar issues here:
the-item-could-not-be-indexed-successfully-because-the-item-failed-in-the-indexing-subsystem
what-is-the-source-of-this-crawl-error-the-item-could-not-be-indexed-successful
You could try the way they provided: increased the drive space of the index, reset the index, reboot the crawl server and run a full crawl.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.