Knowledgebase

Usually, you need 1 license to run SpaceObServer and DataCentral on a server + n licenses of UltraSearch Professional for n people that can search the DataCentral indexes.

The amount of data in the indexes and the number of searches is unlimited.

The size of the index varies and depends on many factors:

• the number of actually indeable files (xlsx and txt are indexable, exe is not)
• the size of the files

For an average drive, the required space ranges between less than 0.01% of the target to 1%.

For a very high ratio of textual content, up to 30% of the target size might be necessary, but this is quite rare.

When the connection test in UltraSerach (button "Test connection" in the DataCentral connection configuration settings) does not work, please make sure, that...

• the "SpaceObServer DataCentral" service is running
• the connection between UltraSearch and DataCentral is not blocked by a Firewall / ports are opened. The default port of DataCentral is 5149.

When the connection test in UltraSerach (button "Test connection" in the DataCentral connection configuration settings) works, but the search doesn't, there could be the following reasons:

• The folder you search for has not been scanned and/or index yet by SpaceObServer/DataCentral.
• The authentication fails. A connection between UltraSearch and DataCentral is authenticated to make sure that only documents that can actually be accessed by the user can be found. Some of our customers had success by switching between host name and IP address when connecting UltraSearch to DataCentral.

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)

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 searches through faster.

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 serach 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):

1. Restart the system.
2. Check for pending/available Windows updates
3. Download and run the Microsoft .NET Framework Repair Tool
4. Download and reinstall .NET Framework 4.8
5. Open a command line prompt (Win+R -> CMD -> Ok) and run
   DISM.exe /Online /Cleanup-Image /RestoreHealth
6. Open a command line prompt (or use the same as before) and run
   sfc /Scannow
7. Uninstall KB5011048 from the system (how to)
8. 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 thorugh an UNC-path.e. The UNC path format is \\<storageAccountName>.file.core.windows.net\<fileShareName>. Please find m ore information here.