SearchIndexer (24716) Windows: The version store for this instance (0) has reached its maximum size of 128Mb

Cloud_Geek_82 776 Reputation points

Hi guys,

I've been having this for about 3 months and could find any solution since then.
It happens on one of the RDS servers (Windows Server 2016) and started all of a sudden (no patches were installed before or any changes were done)
What happens:

  • Searching functionality stops working
  • In the Event Viewer there are number errors
    "SearchIndexer (24716) Windows: The version store for this instance (0) has reached its maximum size of 128Mb. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back.
    Possible long-running transaction:
    SessionId: 0x00000126AC800260
    Session-context: 0x00000000
    Session-context ThreadId: 0x000000000001104C
    Cleanup: 0
    47141@9:03:50 AM"
  • Windows Search service stops running
  • Indexing file rebuild itself from the scratch.

This what I've already tried:

  • rebuild indexing fime manually
  • add DWORD key CoreCount DWORD (1) in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search
  • add DWORD key SetupCompletedSuccessfully (0) in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search

Unfortunately nothing helped.
I've came across a couple of articles for the similar issue but on the RD Licensing server and AD domain controller suggesting to increase maximum version store size.
If someone know where to create a registry key and which key exactly please let me know.

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,321 questions
Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,147 questions
0 comments No comments
{count} votes

5 answers

Sort by: Most helpful
  1. Carl Fan 6,836 Reputation points

    You have tried to rebuild the Index. I consider that if it is related to Windows.edb.
    Try to change the index location and check if the large Windows.edb file still exists, Please perform the following steps to move the file:

    1. Enter Indexing Options into the search field on the Start Menu.
    2. Click on Indexing Options.
    3. Click on Advanced at the bottom.
    4. Click on Select New and specify a new location for your Windows.edb file.
    5. Click on OK and wait until Windows restarted the Windows.
      Do you mean you can't start Windows Search manually either?
      Open CMD window, using the commands below to check.
      DISM /online /Cleanup-Image /RestoreHealth
      sfc /scannow
      Best Regards,
    0 comments No comments

  2. Cloud_Geek_82 776 Reputation points

    Tried to point indexing file to another drive but the error is still generated.
    Not sure what has happened as none of hundreds RDS servers has the same issue.
    DISM /online /Cleanup-Image /RestoreHealth - tried and no result
    sfc /scannow - tried and no result

    0 comments No comments

  3. Cloud_Geek_82 776 Reputation points

    CORRECTON: now indexing status is complete. However, there are two questions I have.

    1. I noticed that the number of indexed items is around 650.000 whereas previously it was around 1.500.000. I think it is because now drives (where files and Outlook ost files are stored) are unchecked as indexing selected locations.



    Is it normal?

    2) Although the indexing status is now complete the error in question itself hasn't stopped to be generated. This makes me think this issue may reoccur in the future. In general, what is the root cause of it and is there a way to fix it permanently?

    0 comments No comments

  4. Cloud_Geek_82 776 Reputation points

    It still crashes unfortunately.
    Could that be an AV or Azure back on server\file level?

    0 comments No comments

  5. Cloud_Geek_82 776 Reputation points

    The issue has been resolved by itself.

    0 comments No comments