Unsuitable DataPlugin Error With SystemLink DataFinder

Issue Details

• When indexing a file on my SystemLink DataFinder Instance, I receive an Unsuitable DataPlugin error. What causes this?
• Sometimes my DataFinder will display the error shown below. I must manually re-index files to fix it. Is there a permanent solution?

Solution

• Insufficient permissions or privileges.
• Interference from security software.
• DataFinder indexing limits.
• Invalid DataPlugin.

• Checking for insufficient permissions.
  1. On the SystemLink server, open the NI SystemLink TDM Configuration application.
  2. Select the SystemLink TDM User Account tab.
  3. Ensure that the chosen account has full administrator privileges.
  4. [OPTIONAL] If using a Windows user account, check if the Local system account results in the same error. If not, the problem is likely related to permissions with the Windows user account.
• Checking for interference from security software.
  • Some 3rd party anti-virus software can block the SystemLink server from accessing certain ports, services, or files. Uninstall any 3rd party security software and verify if the problem persists.
• Checking for DataFinder indexing limits.
  • Each DataFinder must keep up with the quantity of files being added each day. To calculate if the DataFinder is being overloaded with files:
    1. From the SystemLink Web Interface, select the Data Administration >> Data Indexing tab.
    2. Double-click the DataFinder Instance of interest.
    3. Select the Indexing Status tab.
    4. Double-click a file that has been successfully indexed.
    5. In the pop-up window, select the DataPlugins tab.
    6. Make a note of the Indexing Duration. Repeat steps 4-6 for a handful of files, so that you can calculate an average Indexing Duration.
    7. Identify how many new files are added to the DataFinder Instance per day.
       • For example: If a DataFinder Instance is only active during work hours (roughly 8 hours per day), and 1000 new files are added each hour, roughly 8000 new files are added each day. 
    8. Calculate how much time is required to index all the files.
       • For example: with an average Indexing Duration of 5000 ms (5 s), and 8000 files per day, the DataFinder Instance would need to be active for 40000 s in a day (40000 s = 666.67 minutes = 11.11 hours). Therefore, in this example, the DataFinder is not active for long enough to index all files, and a backlog of files will build up. If the backlog is large enough, the DataFinder is vulnerable to performance issues.
  • The recommended index size is 300GB - 500GB. An index size greater than 500 GB can overload the server, preventing it from successfully indexing new files. To check the index size, refer to the section titled Ensure that the DataFinder Index Size is Within Limits in Error 180: Request Timeout in SystemLink Data Navigation.
• Checking if the DataPlugin is valid.
  • On the SystemLink server, attempt to load a file into DIAdem with the problematic DataPlugin.
  • If the error occurs in DIAdem, the issue is likely related to the DataPlugin. Attempt to reinstall and re-register it, or contact the developer of the DataPlugin for further troubleshooting advice.