Overview
The following behavior may be seen most often in a vault that uses a network location as a secondary data location. It can apply to any other folder used where there are special access permissions set that do not allow the M-Files processes to access it (read more at the end of the article).
dtSearch
Using dtSearch, the following error will appear regularly in the Windows Event Viewer of the M-Files application server. In addition, searches will not return results or incorrect results. New files will not be indexed or searchable via file content.
Be aware that the "Index name" and the vault GUID will be different, but the error message should be similar.
M-Files Online
Vault ID: {ABC123D-E456-4379-B02E-92C8ADF6F641}
Index name: File
Partition:
The M-Files indexer failed to index the vault: " ABC123D-E456-4379-B02E-92C8ADF6F641".
Index name: "File". Indexing request type: "DestructionsOnly".
Access is denied.
Indexer.cpp, 1285, The M-Files indexer failed to index the vault: " ABC123D-E456-4379-B02E-92C8ADF6F641". (0x80040885)
Indexer.cpp, 1282, Index name: "File". Indexing request type: "DestructionsOnly". (0x80040120)
Indexer.cpp, 1193, Access is denied. (0x80070005)
Indexer.cpp, 743, Access is denied. (0x80070005)
Indexer.cpp, 2644, Access is denied. (0x80070005)
IndexingHelper2.cpp, 93, Access is denied. (0x80070005)
ConcurrentFileOps.cpp, 43, Access is denied. (0x80070005)
FileHelper.cpp, 562, Access is denied. (0x80070005)
FileHelper.cpp, 562, Access is denied. (0x80070005)
(M-Files <version> <timestamp>)
Smart Search
When using Smart Search as the search indexer, this can present in the M-Files Client as an error like the following:
It can also be present in the M-Files Admin for new setups as the following where the Indexing Status section is just blank and does not fill out.
If this is a network error as defined above and in the dtSearch section, it will also always be accompanied by this or very similar error in the Windows Event Viewer on the M-Files application server:
M-Files Online
Vault ID: {ABC123D-E456-4379-B02E-92C8ADF6F641}
Index name: Smart Search
Partition:
The M-Files indexer failed to index the vault: " ABC123D-E456-4379-B02E-92C8ADF6F641".
Index name: "Smart Search". Indexing request type: "DestructionsOnly".
Access is denied.
Indexer.cpp, 1285, The M-Files indexer failed to index the vault: " ABC123D-E456-4379-B02E-92C8ADF6F641". (0x80040885)
Indexer.cpp, 1282, Index name: "Smart Search". Indexing request type: "DestructionsOnly". (0x80040120)
Indexer.cpp, 1193, Access is denied. (0x80070005)
Indexer.cpp, 743, Access is denied. (0x80070005)
Indexer.cpp, 2644, Access is denied. (0x80070005)
IndexingHelper2.cpp, 93, Access is denied. (0x80070005)
ConcurrentFileOps.cpp, 43, Access is denied. (0x80070005)
FileHelper.cpp, 562, Access is denied. (0x80070005)
FileHelper.cpp, 562, Access is denied. (0x80070005)
(M-Files <version> <timestamp>)
Be aware that the "Index name" and vault GUID could differ for every installation.
Solution
It is generally suggested to use a location directly on the M-Files app server itself to store secondary data as it can be quite time-intensive to debug and resolve network permissions and network-related issues such as this.
If it's a requirement that the secondary data location is on a network location (or another special folder), it should be checked that the M-Files application server has:
- Access to the share/network location (Advanced Sharing à Permissions)
- Read, write, and delete permissions to the share/network location:
In both instances, it needs to be made sure that the account that is being used to run the M-Files Server and M-Files Indexing Service services has access. In normal setups, when looking at the M-Files application server, this is just Local System.
This means that the Computer object needs to be selected when adding new permissions to the share or permissions tab. The account once added will end up looking like this:
MFilesAppServerName$
or similar.
If a service account is being used to run the M-Files Server and M-Files Indexing Service services, then that specific service account needs to be the one added to that share/permissions.
In the case of Smart Search specifically, it's first suggested to double-check the vault GUID and Smart Search API provided during the initial configuration of Smart Search to make sure they have been entered correctly.
Other Causes
If the associated error is NOT seen in the Windows Event Viewer, but users are still seeing the 403 Forbidden errors or are having issues with Smart Search specifically, please contact support at https://support.m-files.com/supportportal/ directly and include the following:
- License serial number.
- Vault GUID where Smart Search is being enabled/should be enabled.
- Location where the M-Files app server is located such as United States, EU, etc.
More detailed information about the above can be found here
https://userguide.m-files.com/user-guide/latest/eng/creating_search_index.html
