Knowledgebase
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:
-
Verify service availability and network connectivity
Make sure the "SpaceObServer DataCentral" service is running on the SpaceObServer host system and the REST interface is activated in SpaceObServer.
Open https://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 Start > Options > Index Service and verify that the DataCentral server is enabled and uses the same port that is configured in UltraSearch. -
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. -
Verify authentication and SPN configuration
Try out the connection to the IP address 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. Connections by IP address usually use NTLM, connections by host name prefer Kerberos.
If the connection check with the host name returns "Cannot establish the connection", you can
1) use NTLM (use the IP address) as authentication method (not recommended because of security reasons; does not work if NTLM is disabled by group policy)
2) Reset password of the service account to ensure an AES Key
3) make Kerberos work by correcting the SPN configuration in your Active Directory (see below).
Which account runs the DataCentral service?
- Local System / Network Service: usually no SPN configuration is required, the existing HOST/ SPNs of the computer account also cover HTTP/. Do not register HTTP/ SPNs for the server name on any other account, this causes exactly this error.
- Dedicated domain account: register the HTTP SPNs on that service account (not on the computer account). Note the following warning.
Important: an explicit HTTP/ SPN for the server name affects the whole host.
As long as no explicit HTTP/ SPN exists, Active Directory resolvesHTTP/servernamethrough the HOST/ SPN of the computer account. OnceHTTP/servernameis registered on the DataCentral service account, clients receive a Kerberos ticket for the DataCentral service account for every HTTP or HTTPS service on this host. Other HTTP-based services that run under the computer account can then no longer authenticate with Kerberos, e.g. Windows Remote Management (WinRM/PowerShell Remoting), IIS websites or WSUS.setspn -Sandsetspn -Xdon't warn about this, because no duplicate SPN is created. Services with a different service class, e.g. file shares (CIFS/) or Remote Desktop (TERMSRV/), are not affected.
If other HTTP-based services run on the host, use a dedicated DNS name for DataCentral instead (see below).
Check and correct SPNs
Modifying SPNs requires write permissions on the account servicePrincipalName (e.g. Domain Admin or delegated).
1) Usesetspn -L <service account>to review the current SPNs. You need an SPN for every name UltraSearch uses to reach the server, e.g.HTTP/servernameandHTTP/servername.domain.tld, plus any DNS aliases. The port (e.g. 5149) is not part of the SPN.
2) Usesetspn -Q HTTP/servernameandsetspn -Q HTTP/servername.domain.tldto check whether these SPNs are already assigned to another account.setspn -Xlists duplicate SPNs in the domain.
3) If an SPN is assigned to the wrong account, remove it there withsetspn -D <SPN> <wrong account>.
4) Usesetspn -S <SPN> <service account>to add a missing SPN. Ifsetspn -Sreports a duplicate SPN, it is already assigned to another account (see 2 and 3).
5) On the UltraSearch client, clear the cached Kerberos tickets withklist purge(or sign out and back in), then repeat the connection check.
Kerberos also requires the client to be a member of the domain (or a trusted domain) and the clocks of client and server to differ by no more than 5 minutes.
Use a dedicated DNS name for DataCentral (recommended with a domain account)
With a dedicated DNS name, e.g.sosdatacentral.domain.tld, DataCentral gets its own HTTP/ SPN. The HTTP/ SPN of the server name stays with the computer account, so the other HTTP-based services of the host keep working with Kerberos. In return, the new name must be included in the DataCentral certificate, and UltraSearch must connect to DataCentral using this name.
1) In DNS, create an A record (not a CNAME) that points to the IP address of the DataCentral server, e.g. with PowerShell on the DNS server:Add-DnsServerResourceRecordA -ZoneName domain.tld -Name sosdatacentral -IPv4Address <IP address>. With a CNAME, the client builds the SPN from the target name, i.e. from the server name again. Check the name resolution on the client withResolve-DnsName sosdatacentral.domain.tld.
2) If HTTP/ SPNs for the server name were previously registered on the service account, remove them withsetspn -D HTTP/servername <service account>andsetspn -D HTTP/servername.domain.tld <service account>.
3) Register the SPNs for the new name on the service account withsetspn -S HTTP/sosdatacentral <service account>andsetspn -S HTTP/sosdatacentral.domain.tld <service account>.
4) Issue a certificate for the new name, e.g. from your enterprise CA. The certificate created by the SpaceObServer installer doesn't contain the new name. The certificate must contain the new name as a Subject Alternative Name (SAN) (sosdatacentral.domain.tld, andsosdatacentralif needed), be valid for server authentication and have a private key. Import it into the certificate store Local Computer > Personal and give the service account read access to the private key.
5) In SpaceObServer, select the new certificate under Options > Index Service and restart the DataCentral service.
6) In UltraSearch (administration mode), entersosdatacentral.domain.tldas the DataCentral server and update the certificate fingerprint.
7) On the client, clear the Kerberos tickets withklist purgeand check the connection.klistshould then show a ticket forHTTP/sosdatacentral.domain.tld.
8) Optional: check that remote management of the host works with Kerberos again withTest-WSMan -ComputerName servername.domain.tld -Authentication Kerberos. Without-Authentication,Test-WSMansends an anonymous request and says nothing about Kerberos.
Afterwards, UltraSearch can reach DataCentral with Kerberos only through the new name. Through the server name, the client receives a ticket for the computer account, which DataCentral can't accept while running under the domain account.
If the connection check works, please follow these steps:
-
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. -
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.
The speed of DataCentral depends on many factors.
The speed of the indexing of documents depends on:
- the number of actually indexable files (xlsx and txt are indexable, but exe not)
- the size of the files
- the type of the files (txt files are usually faster than xlsx/pdf)
- the hardware (RAM and CPU, incl. the number of cores)
- the index location (avoid HDD drives or network storage, prefer an attached SSD drive... in our experiments, SSD was usually 1.5x - twice as fast as HDD when creating a fulltext index)
For a small drive, DataCentral can be done within minutes, for larger ones, it can take hours and for very large drives with multiple TB of indexable files (exe files, images, ... don't count), it can even take days. Smaller scans lead to smaller indexes, which can usually be searched through faster. The initial creation of the index takes the longest. The repetitive updating of the index should be far faster, becaues only changes on the file system need to be applied on the index then.
SpaceObServer shows a progress and an estimation for the remaining time of the indexing in the "Configure scans" window in the "State" column of the scan.
The performance of a search is usually faster than without DataCentral and depends on:
- the number of the files found by the search
- the search term and its frequency in the index
- the network between the UltraSearch client and the DataCentral server
We aim to execute most of the searches within a few seconds.
A first step is looking in the EventLog under "Windows protocols" / "application" for warnings, but especially errors regarding SpaceObServer and DataCentral (on the machine that is running DataCentral).
If a file cannot be indexed or searched, it could make sense to share this file with us via email to spaceobserver@jam-software.com.
If there is another problem, please contact our support.
We might ask you to provide us log file of DataCentral, which are located at C:\ProgramData\JAM Software\SpaceObServer\logs
A detailed explanation of the hardware requirements can be found here: https://manuals.jam-software.de/spaceobserver/EN/DataCentral/2-system-requirements-datacentral.html
If the search results are coming from DataCentral, UltraSearch shows the words "via DataCentral" at the bottom left.
If something does not work and search results cannot be loaded via DataCentral, UltraSearch attempts a "fallback" search, which searches the target folder manually.
DataCentral supports a variety of document types that can be indexed and searched. The following file extensions are supported at the moment:
Textual: DOC, DOT, DOCX, DOCM, DOTX, DOTM, TXT, ODT, OTT, RTF
PDF: PDF
Markup: HTML, XHTML, MHTML, MD, XML
Ebooks: CHM, EPUB, FB
Spreadsheet: XLS, XLT, XLSX, XLSM, XLSB, XLTX, XLTM, XLA, XLAM, ODS, OTS, CSV, TSV, XML
Presentations: PPT, PPS, POT, PPTX, PPTM, POTX, POTM, PPSX, PPSM, ODP
Emails: OST, EML, EMLX, MSG
Notes: ONE, ONENOTE
MISC: ADOC, BAT, BIB, CMD, CONF, CPP, CS, CSPROJ, CSS, DOCKERFILE, DOCKERIGNORE, ENV, ENV.LOCAL, ENV.PRODUCTION, FB2, GITIGNORE, GITATTRIBUTES, GO, GRADLE, GROOVY, H, HTACCESS, HTM, INI, IPYNB, JAVA, JS, JSON, KTS, LOG, MHT, PAS, PHP, POM, PROPERTIES, PS1, PY, R, RB, RE, RST, RS, SH, SHTML, SLN, SQL, SWIFT, TEX, TOML, TS, TSX, VCXPROJ, YAML, YARN.LOCK, YML
For all we know so far, this issue seems to be caused by defects in the system itself. It might affect other applications as well.
To fix it, you might try to (please check the installation after each step):
- Restart the system.
- Check for pending/available Windows updates
- Download and run the Microsoft .NET Framework Repair Tool
- Download and reinstall .NET Framework 4.8
- Open a command line prompt (Win+R -> CMD -> Ok) and run
DISM.exe /Online /Cleanup-Image /RestoreHealth - Open a command line prompt (or use the same as before) and run
sfc /Scannow - Uninstall KB5011048 from the system (how to)
- Check for updates again or install KB5011048 manually again
Please find more information on DISM and SFC here.
Yes, Azure Files Shares can be accessed through a UNC-path. The UNC path format is \\<storageAccountName>.file.core.windows.net\<fileShareName>. Please find more information here.
The SpaceObServer Client Access connects to the SpaceObServer database. For the right-click Explorer context menu to work, it requires a direct connection to the file server, but this is optional. Also, for displaying a few MS Office specific metadata fields (Author, Last Saved By, Last Save Date, Keywords, ) it requires access to the files as these metadata is currently not part of the SpaceObServer database.
The SpaceObServer Web Access connects to the database only.
SpaceObServer runs fully on prem, but it can scan cloud storage, e.g. SharePoint Online, S3, Azure Blob. So, no agents on the scanned system are required.
The chart on our website "How SpaceObServer works" should demonstrate this:
https://www.jam-software.com/spaceobserver/how-spaceobserver-works.shtml
Need further help getting started?
You did not find what you were looking for? Please contact us so we can provide an answer to your question.
Contact Form