How should I go about resolving these 2 errors?

Tevon2.0 1,096 Reputation points
2023-07-18T13:39:13.62+00:00

Event ID - bgt2c

Category - Config Cache

Message - SPPersistedObjectCollectionCache.RefreshDirtyCollections(): detected intervening update to collection cache file, dirtying all in-memory collection caches.

Event ID - barqy

Category - Search Platform Services

Message - GetValue : object not found for (valueName = ServiceUser ProductKeyName = HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\16.0\Search)

SharePoint Server
SharePoint Server
A family of Microsoft on-premises document management and storage systems.
2,145 questions
SharePoint Development
SharePoint Development
SharePoint: A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.Development: The process of researching, productizing, and refining new or existing technologies.
2,545 questions
SharePoint Server Development
SharePoint Server Development
SharePoint Server: A family of Microsoft on-premises document management and storage systems.Development: The process of researching, productizing, and refining new or existing technologies.
1,557 questions
SharePoint Server Management
SharePoint Server Management
SharePoint Server: A family of Microsoft on-premises document management and storage systems.Management: The act or process of organizing, handling, directing or controlling something.
2,759 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Yanli Jiang - MSFT 19,671 Reputation points Microsoft Vendor
    2023-07-19T07:08:21.08+00:00

    Hi Tevon ,

    For the first error message, it indicates that there is an intervening update to the collection cache file, which has caused all in-memory collection caches to be dirtied. This error can occur if the configuration cache is corrupted or if there is an issue with the SharePoint timer service. You can try restarting the SharePoint timer service and clearing the configuration cache to see if that resolves the issue.

    Follow these steps:

    1. Open the Services on the SharePoint server.
    2. Locate the SharePoint Timer Service and stop it.
    3. Navigate to the following directory: C:\ProgramData\Microsoft\SharePoint\Config\GUID.
    4. Delete all the XML files in this directory.
    5. Restart the SharePoint Timer Service.

    For the second error message, it indicates that an object was not found for the specified value name and product key. This error can occur if there is an issue with the search service application or if the search service account does not have the necessary permissions. You can try restarting the search service application and ensuring that the search service account has the necessary permissions to access the registry key specified in the error message.

    Follow these steps:

    1. Open the Services on the SharePoint server.
    2. Locate the SharePoint Search Host Controller service and stop it.
    3. Navigate to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\16.0\Search.
    4. Check if the ServiceUser value exists. If it does not exist, create it as a REG_SZ value and set it to the account that is running the SharePoint Search Host Controller service.
    • Press the Windows key + R to open the Run dialog box.
    • Type "regedit" and press Enter to open the Registry Editor.
    • Navigate to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15.0\Search\Setup\ContentIndexCommon
    • Look for the ServiceUser value. If it exists, you can edit its value data to set it to the account that is running the SharePoint Search Host Controller service.
    • If the ServiceUser value does not exist, you can create it as a REG_SZ value by right-clicking on the ContentIndexCommon key, selecting New > String Value, and naming it "ServiceUser". Then, double-click on the ServiceUser value and set its value data to the account that is running the SharePoint Search Host Controller service.

    Note: Be careful when editing the Windows Registry, as making incorrect changes can cause serious problems with your system. It's always a good idea to back up your registry before making any changes.

    1. Restart the SharePoint Search Host Controller service.

    After completing these steps, monitor the SharePoint logs and event viewer for any further errors. If the errors persist, you may need to review the logs and event viewer in more detail to determine the root cause of the issue.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    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.