Processing and processing agent

The following FAQs address questions about file processing and the processing agent.

Some tasks require multiple processes, or steps, to complete and the task requested is in between steps and waiting to be picked up for the next step. For example, you want to send the items in a workbook to a target. For the items in this workbook, only the metadata was indexed and the source repository and destination are managed by different agent clusters. In this scenario, the items must be collected before they can be sent to the defined target. This task may show a "waiting" task status after the items are collected as the task waits to be picked up to send the items to the target.

The assigned agent may not be reachable. If the task status remains "waiting", ensure that the agents in the agent cluster assigned to the task are running and accessible. Specifically, verify that the agentAPI service is running on the agent host assigned to perform the task.

If you are located in a region that typically uses a character set other than Latin, your SQL Server installation most likely defaults to a collation other than what is supported by the processing agent.

When installing SQL Server, you must set the server collation to SQL_Latin1_General_CP1_CI_AS.

Re-install SQL Server with the supported collation defined. Proper collation must be set during installation because it cannot be changed after SQL Server is installed.

File Analysis Suite tracks file deletions when a processing job runs against a File Analysis Suite repository. A job run occurs when a repository is updated, either run on a schedule or manually updated from the Manage Repositories page in Connect (click the inline update icon for the repository or the Update button in the repository detail panel).

File systems

File Analysis Suite tracks file deletions by directly comparing with the original file system location identified by the repository path. Items are removed from the File Analysis Suite index seven days after the deletion is detected. If an item within a container file (such as ZIP) is deleted in the original file system location, the item is removed from the index as part of updating the container file when the File Analysis Suite job run occurs. In this case, the item may be removed from File Analysis Suite sooner than seven days after deletion is detected.

Exchange

No deletion detection from Exchange. File Analysis Suite retains items it has already processed until a delete action is initiated from File Analysis Suite.

SharePoint

File Analysis Suite tracks the deletion of managed SharePoint items using the SharePoint change logs. Each time processing is run on a repository—on a schedule, or on demand—File Analysis Suite checks the SharePoint logs for deleted items. For each managed item that is deleted in SharePoint, File Analysis Suite deletes that item from the File Analysis Suite index. If an item within a container file (such as ZIP) is deleted in SharePoint, the item is removed from the index as part of updating the container file when the File Analysis Suite job run occurs.

To ensure accurate tracking of items deleted from SharePoint, ensure that the SharePoint repositories in File Analysis Suite are updated more often than the maximum number of days SharePoint logs are kept. For example, if your SharePoint logs are configured to be stored for 60 days, verify that your SharePoint repositories are updated at least every 59 days.

Content Manager

File Analysis Suite tracks the deletion of managed Content Manager items using the Content Manager delete events. Each time processing is run on a repository—on a schedule, or on demand—File Analysis Suite checks the delete events. For each managed item that is deleted in Content Manager, File Analysis Suite deletes that item from the File Analysis Suite index. If an item within a container file (such as ZIP) is deleted from Content Manager, the item is removed from the index as part of updating the container file when the File Analysis Suite job run occurs.

To ensure accurate tracking of items deleted from Content Manager, ensure that the Content manager repositories in File Analysis Suite are updated more often than Content Manager administrator purges delete events. For example, if your Content Manager administrator purges delete events every 60 days, verify that your Content Manager repositories are updated at least every 59 days.

Google Drive

File Analysis Suite tracks the deletion of managed Google Drive items using the change log for the Google drive defined by the File Analysis Suite repository. Each time processing is run on a repository—on a schedule, or on demand—File Analysis Suite checks the change logs for deleted items. For each managed item that is deleted in Google Drive, File Analysis Suite deletes that item from the File Analysis Suite index. If an item within a container file (such as ZIP) is deleted in Google Drive, the item is removed from the index as part of updating the container file when the File Analysis Suite job run occurs.

To ensure accurate tracking of items deleted from Google Drive, ensure that the Google Drive repositories in File Analysis Suite are updated more often than the maximum number of days Google Drive change logs are kept. For example, the default retention for change logs is 30 days. Verify that your Google Drive repositories are updated at least every 29 days.