We don’t use marketing cookies. Functional cookies ensure a smooth performance of our website. If you continue to use our services, you agree to the use of cookies. Data protection at JAM OK

Knowledge Base

Welcome to our Knowledge Base. Search or browse through the topics below to find answers to your questions.

Is the system service "SpaceObServer Service" started?
The "SpaceObServer Service" processes all scans of directories. If this service is stopped or paused, no scan can be processed.
Are there any other scans in progress?
SpaceObServer does not run concurrent scans (See: "Why can't I run multiple scans in parallel with SpaceObServer?"). If there is another scan running, your scan will be properly started after the current scan is done.
Is the selected directory on a network drive?
You can customize the login of "SpaceObServer Service" within the installation of SpaceObServer (username, domain and password). If you do not enter a valid user account the login is set to the local system account. This may cause problems while scanning network drives. To fix this problem please switch the service log on to a user account with sufficient access rights (See: "How can I switch the login...").
Do you use "Windows Authentication" for the database login?
If you use this option ("Tools > Options > System > Database > Login info") and you switched the login of the system service "SpaceObServer Service" to a specified user account, this user must have read and write access on the selected database.
If it is not possible to give the user access rights to this database, please do not use the Windows Authentication for the database access. Use a valid database user account instead.
Does the "Observing Server" exists and is a SpaceObServer Service running on this machine?
If the "Observing Server" is set (not blank) for a root directory, only this server will execute scans for this directory, no matter from which client the scan was triggered or scheduled. If for any reason (e.g. a rename of the server) this machine is not found or no SpaceObServer Service is running on this machine, the scan will not be executed. You can configure the Observing Server from within the context menu of the Configure Scans dialog (sub menu “Expert Settings”).
If none of the above applies, please check the column "Last Error" in the "Configure Scans" dialog and the Windows Event Log for further information and error messages. Please include this information if you contact us, together with the type and version of database software you are using.

After the installation of SpaceObServer a database connection to the supplied SpaceObServer-Embedded database (FDB file) "SpaceObServer.fdb" is established. Under "Tools > Options > Database" you can change the database used.
If you want to use a SQL Server database to back up the data, your computer must be connected to a server on which a MS SQL Server is installed. A second possibility is that you have installed a MS SQL Server locally on your computer. In addition, you need a valid user account (user name and password) for database access.

A free version of the MS SQL Server is available from Microsoft as SQL Server Express. You can download this version free of charge from the Internet or use the MS SQL Installer in SpaceObServer under "Options > Database".

The space used by the database depends on the number of files, the number of folders and the change rate of your files. Generally the database needs approx. 35 MB per 100.000 files. This is just a rule of thumb and is only valid if the database has been compressed recently. When you enable the 'MD5 checksums' for your scans, the database size will increase about 1.5 MB per 100,000 files.

TreeSize Professional scans file system structures as needed and holds a snapshot of the scan in your system memory.
SpaceObServer archives all needed file system information in a backend database. This is needed to calculate size development information for the scanned directories and enables you to filter the file system tree without the need of a rescan.
Building up the SQL database is quite costly. This is why the initial scan of SpaceObServer runs very slow compared to the scans of TreeSize Professional.
Note: The update scans of SpaceObServer do only need to update the changes on your file system in the database. So generally the update scans run faster than the initial scans.

A migration of the SpaceObServer scans is described in the Database Migration chapter.

Current category: SpaceObServer