Error 180: Request Timeout in SystemLink Data Navigation

Issue Details

• When I try to apply a search criteria to a DataFinder Instance, I receive error 180 and a timeout. What causes this?
• I want to apply an Advanced Search in the SystemLink Data Navigation tab, but the web interface displays "Could not execute the search".
• After applying a search criteria to a DataFinder Instance from the Data Navigation page, the below error appears:

Could not execute the search.

Getaway Time-out: EXCEPTION: AoException:
AO_QUERY_TIMEOUT_EXCEEDED(57): RequestorBase(378):
ERROR(180): DFCP: Request timeout. No response.

Solution

This error can occur if the SystemLink Server is being used beyond it's capability, or if the DataFinder timeout value is insufficient.
Refer to the sections below to troubleshoot this issue.
 

Increase the DataFinder Timeout

Each DataFinder Instance configures a timeout value to process each file. If a file takes longer to process than the specified timeout, this will impact the search results in the Data Navigator. To modify the timeout value:

1. Access the SystemLink web interface.
2. Select the Data Indexing menu.
3. Double-click the DataFinder Instance of interest.
4. Navigate to the Index tab.
5. Select the Timeout per File setting and increase it's value.
   • It may be necessary to perform incremental tests to ensure that a balanced timeout value is chosen. A timeout value too high can cause search requests to take undesirably long.

Ensure that the DataFinder Index Size is Within Limits

Each DataFinder Instance should have an Index Size less than approximately 500GB. This is not a hard limit, but should be used as a guideline.

There is no hard limit to the Index Size because the performance of the DataFinder Instance is dependent on the server's specifications. However, DataFinder Instances with an Index Size greater than 500GB can be susceptible to timeouts.

To check the Index Size:

1. Access the SystemLink web interface.
2. Select the Data Indexing menu.
3. Double-click the DataFinder Instance of interest.
4. From the top right-hand corner, click the Pie Chart symbol and select Advanced Statistics.
5. In the pop-up window, check the Index Size from the General tab.

If the Index Size significantly exceeds 500GB, the following considerations should be made:

• Split the DataFinder Instances in to smaller DataFinder Instances.
  • If a DataFinder Instance uses multiple Search Areas, consider splitting the Search Areas between multiple DataFinder Instances.
    • For example, if 1 DataFinder Instance with an Index Size of 600GB has 2 Search Areas, replace the Instance with 2 new DataFinder Instances (1 for each Search Area).
  • Note: a maximum of 16 DataFinder Instances can be configured on a SystemLink Server.
• More SystemLink servers may be required if 16 DataFinder Instances are still exceeding the recommended Index Size.