How to Fix Event ID 9875 Source MSExchangeIS Mailbox Store Error?
You may notice an error in the Event Viewer of the Exchange Server, saying “There are not enough resources to process the document or row,” with event ID 9875. The complete error message may look like the given below:
Log Name: Application
Source: MSExchangeIS Mailbox Store
Event ID: 9875
Task Category: Content Indexing
Level: Error
Keywords: Classic
User: N/A
Description:
Unexpected error "DOC_TOO_HUGE: There are not enough resources to process the document or row" occurred while indexing document.
Mailbox Database: DB01
Folder ID: 2ec8-57936CCC
Message ID: 2ec8-20C5D9AAAA
Document ID: 1447155777
Error Code: 0x8004364a
The error message doesn’t give much information on where the problem might be but it provides a hint that the problem is associated with the content indexing of the database. It looks the issue is related to a calendar entry. For example, a recurring meeting is set by a user/s (say daily), and the meeting has no end data. Let’s see how to fix the issue.
Solutions to Resolve the Event ID 9875 Source MSExchangeIS Mailbox Store Error
As you can see, the problem resides within a particular meeting on a particular mailbox. If the issue is re-occurring and you see the error in the Event Viewer, this means that you need to repeat the process.
First, you need to download the ExFolders_SP1.zip from the Microsoft site and extract the contents in the bin folder of your Exchange Server installation folder.
Next, you need to execute the registry file - TurnOffSNVerificationForExFolders.reg and then open the ExFolders.exe to open the ExFolder tool. Then, click on File and select connect to connect to the server. Select Mailbox type, select connected by the Exchange Server database, select a Global Catalog to connect, and select the database, which is mentioned in the error message. This will establish a connection with the server’s database.
Now, in the left pane of the window, click on the top folder Mailbox. Next, click on the Tools from the menu bar, click on Export Folder Properties, and select the Selected folder and subfolders. In the Output file box, select the option where you want the results to be exported to (for example, c:\scripts\folderid.txt), only check the ptagPID: 0x67480014 property, leave the rest as default, and click OK.
Once the export is complete, open the text file and search for the folder ID, which is showing in the error message. In this case, you can search for Folder ID: 2ec8-57936CCC.
Once this is done and you found the offending mailbox related to the folder ID, open ExFolders and then open the mailbox mentioned. Select the affected folder. From the right pane, select all the contents of the folder.
Once this is done, click on Tools and click on Export Item Properties. Select the export report while making sure that you enter the ptagPID: 0x67480014 and click on Add property to the list. Click OK.
Now, from the exported file, you can search for the message ID mentioned in the error message, which in this case is Message ID: 2ec8-20C5D9AAAA. Finally, this will give you the name of the meeting which is causing this issue.
Now, all you’ve to do is to open the affected mailbox, find the event, and delete it.
To Conclude
As we have seen above, it is quite a lengthy process to find the offending message and remove it. Since we are accessing the database directly, we must ensure that nothing is modified. If something is modified, it could affect the integrity of the database. If there is an underlying issue with the database, then you need to use a professional tool to resolve the issue and recover Exchange databases with minimal impact on the business and with no data loss.