Knowledgebase

Answer / Solution

Please open UltraSearch, navigate to the DataCentral connection configuration settings and press the button "Test connection". If the connection check fails, please continue with these options:

1. Verify service availability and network connectivity
   Make sure the "SpaceObServer DataCentral" service is running on the SpaceObServer host system.
   Open https://hostname:port/healthz or http://hostname:port/healthz. The endpoint must return "Healthy".
   Make sure the DataCentral connection is not blocked by a firewall. The default port is 5149.
   In SpaceObServer, open Options > Index Service and verify that the DataCentral server is enabled and uses the same port that is configured in UltraSearch.

2. Verify the certificate used by DataCentral
   In SpaceObServer, under Options > Index Service, check which certificate is currently configured for the DataCentral service.
   Compare the certificate thumbprint shown there with the certificate or fingerprint configured in UltraSearch.
   In UltraSearch, certificate settings can only be changed in administration mode.
   If UltraSearch was installed without explicit certificate parameters, it validates the DataCentral certificate by fingerprint by default and stores the fingerprint from the first connection for later communication.

3. Verify authentication and SPN configuration
   Try out connection to the IP adress of the SpaceObServer DataCentral host in UltraSearch. If the connection works with the IP address but not with the server name, the problem is typically related to Kerberos/SPNs. UltraSearch uses NTLM when connecting by IP address and Kerberos when connecting by host name.
   If the connection check with the hostname returns something like "the user is not authenticated" / "cannot access the resource", you can
   1) use NTLM (use the IP address) as authentication method (not recommended because of security reasons)
   2) making Kerberos work by adding the required SPNs to the user account running the DataCentral service (via your ActiveDirectory).
   If DataCentral runs under a dedicated domain account, register the HTTP SPNs on that service account (not on the computer account).
   Use setspn -L <account> to review the current SPNs. Typical examples are HTTP/servername and HTTP/servername.domain.tld.
   Modifying SPNs requires the appropriate permissions on the account object.
   Use setspn -S <SPN> <account> to add a missing SPN.
   
   

If the connection check works, please follow these steps:

1. Scan/Index existence
   If the search returns no results, verify that the folder you are searching in has already been scanned and indexed by SpaceObServer/DataCentral.
   For content searches, verify that the full text index is enabled for the scan.
   Check whether an UltraSearch exclude filter is active.

2. Check the logs on the DataCentral server
   Check the Windows Event Log for errors from SpaceObServer Agent and SpaceObServer DataCentral.
   If a file should be searchable but is not, the file might not have been indexed because of an indexing problem shown in the Event Log.