Knowledgebase

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 through a UNC-path. The UNC path format is \\<storageAccountName>.file.core.windows.net\<fileShareName>. Please find more information here.

The newest version of the MySQL ODBC driver is not supported with SpaceObServer. Please download and install the version 8.3 or lower from the oracle website after deinstalling the current version: MySQL :: Download MySQL Connector/ODBC (Archived Versions)

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

We recommend Microsoft SQL Server 2025 Enterprise with at least 32GB of free memory (RAM) and a CPU with 4-8 cores.

Please find the supported SQL server versions here. We also documented which database size you can expect, if there are any size limits for the database size.

You can find the Offline Installer in our customer area.

To download it, please log in with your user details and navigate to "Downloads".  During maintenance, you will find the current version there as an offline installer to download.