Knowledge Base


Question / Problem

SpaceObServer doesn't start to scan a specified directory. What's the problem?

Answer / Solution

There could be reasons for this issue:

1. Is the system service "SpaceObServer Agent" started? The "SpaceObServer Agent" processes all scans of directories. If thisservice is stopped or paused, no scan can be processed.

2. Is theselected directory on a network drive? You cancustomize the login of SpaceObServer Agent within the installation ofSpaceObServer (username, domain and password). If you do not enter a valid useraccount the login is set to the local system account. That may cause problemswhile scanning network drives. To fix this problem please switch the servicelog on to a user account with sufficient access rights (See: "How can Iswitch the login...").

3. Do you use"Windows Authentication" for the database login? If you usethis option ("Tools > Options > Database > Login info") andyou switched the login of the system service SpaceObServer Agent to a specifieduser account, this user must have read and write access on the selecteddatabase.If it isnot possible to give the user access rights to this database, please do not usethe Windows Authentication for the database access. Use a valid database useraccount instead.

4. Does the"Observing Server" exists and is an SpaceObServer Agent running onthis machine? If the"Observing Server" is set (not blank) for a root directory, only thisserver will execute scans for this directory, no matter from which client thescan was triggered or scheduled. If for any reason (e.g. a rename of theserver) this machine is not found or no SpaceObServer Agent is running on thismachine, the scan will not be executed. You can configure the Observing Serverform within the context menu of the Configure Scans dialog (sub menu "ExpertSettings"). If none ofthe above applies, please check the column "Last Error" in the"Configure Scans" dialog and the Windows Event Log for furtherinformation and error messages. Please include this information if you contactus, together with the type and version of database software you are using.