500 internal server error on sharepoint 2019

Question

These are the only uls errors that I'm seeing when I get this error

GetProperty : failed propertyName RecrawlTenantTimeInterval exception System.IO.FileNotFoundException: The system cannot find the file specified.

at Microsoft.Office.Server.Search.Administration.MSSITLB.IGatherApplication2.GetProperty(String pwszURIPropertyName)

at Microsoft.Office.Server.Search.Administration.SearchApi.<>c__DisplayClass12.<GetProperty>b__11()

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

Database with Id 53e6991a-c326-4d2c-a77c-a04b81ffd6a9 was not found in database collection. Returning null.

SharePoint booted. Process Name: [DistributedCacheService] App Pool: [N/A], Process ID: [0x3780], App Domain Name and ID [DistributedCacheService.exe],[1], Command Line ["c:\Program Files\AppFabric 1.1 for Windows Server\DistributedCacheService.exe"]

Answer 1

Hi @Tevon2.0 ，

Can you tell me what operation you were performing when you had this problem?

I looked up the information and found that your problem could be due to a problem with crawling or migration.

First, for error “object not found for (valueName = ServiceUser ProductKeyName = HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\16.0\Search)”:

Troubleshoot the issue as following:

1. Increase the time out value on the Proxy and Timeout page in search administration. Go to Central Admin > Manage service Applications-> Search Service Application->Farm Search Administration->Click on Time Out Seconds and change.
2. Internet Options > Connections > LAN settings. Uncheck ‘Automatically detect settings’. And check the crawl again.

Second, for error "Database with Id 53e6991a-c326-4d2c-a77c-a04b81ffd6a9 was not found in database collection. Returning null." This problem can occur when migrating. For example, you had created this content database on the SharePoint Server 2013 farm and moved a couple of 2013 site collections into it that you had scheduled for test upgrade to 2016. 

Therefore, I suggest you restart IIS on SharePoint Servers. Here is the article about how to restart IIS on SharePoint Servers: Restart IIS (IISRESET) on All Servers in the SharePoint Farm using PowerShell.

Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link. 

Here is the article that shows more information about this error:

Database with Id [ID] was not found in database collection. Returning null.

---

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.