# Troubleshoot the Connector

This section describes how to troubleshoot common problems that might occur when you set up the File System Connector.

Files are not retrieved

If the File System Connector does not retrieve the files that you expect, check whether the files are excluded by the configuration parameters that you have set, particularly those that accept regular expressions.

If you encounter problems with permissions, ensure you run the connector as a user who has the necessary permissions for the files that you want to retrieve. For more information about permissions, see Permissions.

NSF or PST files are not retrieved

The File System Connector can retrieve files that are read-only. However, due to limitations with the MAPI and Notes APIs, KeyView cannot process read-only `.nsf` and `.pst` files.

To resolve this issue, you can:

- remove the read-only attribute from these files (the files will appear to be modified but the data, such as e-mail messages, are not changed).
- configure CFS to copy the files to a temporary directory (the temporary copies are not read-only). To do this, set the `WorkingDirectory` parameter in the CFS configuration file.

Files are ingested repeatedly

When performing extraction from `.nsf` and `.pst` files, KeyView can change the last modified date of a file. This causes the connector to re-ingest the document on the next `synchronize` action. You can prevent this happening by setting the `EnableExtractionCopy` parameter to `true`. When this parameter is `true`, the connector makes a copy of the original document and KeyView performs extraction on the copy.

The connector does not retrieve all items from a Netware ACL

If the connector does not retrieve all of the security information from ACLs in a Netware file system, make sure that the connector's Windows service is run by a user who has administrative permissions on the connector machine.

_FT_HTML5_bannerTitle.htm