An Unexpected Error Has Occurred in SystemLink TDMServer or DataFinder

Updated Nov 1, 2023

Reported In

Software

  • SystemLink
  • SystemLink TDM DataFinder Module

Issue Details

I have SystemLink installed on my PC/laptop and when I navigate to Data Administration>>Data Indexing I immediately receive this error:

An unexpected error has occurred. cannot GET https://serverurl/TDMServer_dfse/datafinders?expand=asam%3Bconfigpath%Bcouldnotstartmessage%3Bdbtype%3E (500)

vertical sl error.png

Solution

This error can occur when your SystemLink server does not have enough memory or if there are problems with its services.

Follow the recommendation mentioned in Sizing a SystemLink Server, to make sure the server has the sufficient amount of resources available for a correct operation. If the memory assigned to the server is enough, you can also check the following:
 
  • Make sure the SystemLink TDM User Account, in the NI SystemLink TDM Configuration application, has a proper user and password configured with proper permissions to access remote files.
  • Verify the TDMS services reported in the NI SystemLink Server Configuration application are live and running. If there services with errors consider checking the Skyline and TDM logs for additional information on the errors.
  • Open the Windows Services and verify the following services are running:
    • NI SystemLink TDM Account Service
    • NI SystemLink TDM Database Service
    • NI CORBA Naming Service
    • NI PSP Service Locator
      • If one of them is not running, you can try to manually start them by right-clicking them and selecting Start, if there's an error starting the service, there might be an issue with the user permissions, you can also check the Windows Event Logs for more information if one of those services is failing to start.
  • Verify there are enough TDM module licenses available for the SystemLink Server.

Additional Information

To open the Windows Event Logs, you can search for the Event Viewer application in the Windows search bar, and expanding the Windows Logs section.