Troubleshooting File Connector Issues

Access denied when crawling through a Distributed File System (DFS)

Possible cause

When the File connector performs a Rebuild or a Refresh operation through a DFS, depending on the number of threads used and the overall crawling speed, several connections can be opened simultaneously to the targeted server. In some instances where the number of connections grows to a large number, Microsoft Windows can see this as a Denial-of-Service attack on the server and start refusing to create new connections to that server. When this situation arises, the File connector logs will display Access Denied Errors for any items located on that server. You can confirm this situation by monitoring Windows Event Viewer logs for Event ID 2027.

Possible solution

If you encounter this problem, you can change your source starting address so it targets one of the DFS active referral links instead of going through the DFS itself. This could help resolve the problem if the server experiencing the connection problem is the DFS server and not the file share server where the resource being crawled is located.

Example: Replace the DFS starting address \\DFSName\Rootname\Ressource by \\ServerName\RessourceFileShare.

The File connector also has the ability to automatically attempt to detect and crawl a DFS active referral link instead of going through the DFS. You can add the EnableCrawlDFSReferralLink hidden File connector source parameter and set it to True to enable this feature which is disabled by default (see Modifying Hidden File Connector Source Parameters).

Some items are not added to the retry queue when they failed to be indexed

Possible cause

The File connector automatically retries to index any item that failed to be indexed because it was opened by another application during the initial crawling (sharing violation). To keep the retry queue to a reasonable size, the default maximum number of items in the queue is set to 100. When the connector encounters frequent sharing violations, the limit may be exceeded.

Possible solution

If you experience frequent sharing violations when crawling, you can increase the default value of the RetryQueueMaxSize hidden File connector source parameter (see Modifying Hidden File Connector Source Parameters).

When crawling a Network Share, the "CGLSecurity::SecurityInvalidUserOrGroup: No mapping between account names and security IDs was done" error is displayed for every file

Possible cause

Even though the starting address provided is valid, an error occurred when attempting to resolve the permissions on files from that address. This problem can occur with some network configurations where CES can’t properly interpret the host from the supplied starting address.

Possible solution

If you are using the network share fully qualified name, try to use its shortened version.

Example: Use file://fileshare/root/ instead of file://fileshare.domain.com/root/ and vice versa.

When crawling a mail archive with the Expand Mail Archives source option enabled, the "Failed to open mail archive, it is in use and cannot be accessed. Make sure it is not still opened in Outlook." error message is returned

Possible cause

The File connector cannot index the content of a mail archive that is currently opened in Microsoft Outlook.

Possible solution

Close the Archive in Microsoft Outlook and retry. When you encounter this error even after closing the archive in Microsoft Outlook, restart Microsoft Outlook to ensure it releases all handles on the archive.

When crawling a mail archive with the Expand Mail Archives source option enabled, the "Failed to open mail archive, it is password protected. The password specified in the Mail Archives Mapping File for this archive is incorrect." error message is returned

Possible cause

This message indicates that a password for the archive was found in the mail archive mapping file but the password is incorrect. Passwords are case sensitive.

Possible solution

Ensure that you specify the passwords in the File connector mapping file with the same casing as when you open the archives in Microsoft Outlook (see Creating a Mail Archive Mapping File).

When crawling a mail archive with the Expand Mail Archives source option enabled the "Failed to open mail archive, it is password protected. You need to add this archive password to the Mail Archives Mapping File, please refer to the Connector documentation for further details." error message is returned

Possible cause

This means that there is no password specified for the protected archive in the mail archive mapping file

Possible solution

Ensure that you specify a password for each protected archive file in the mail archive mapping file (see Creating a Mail Archive Mapping File). If you did specify a password for the archive, ensure the mapping type for the archive was properly entered and that it contains the full path to the archive.

Example: <Mapping type="\\svr-archives\mail\employees\jdow.pst">