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

FAQs & Knowledge Base

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

Categories: SpaceObServer | Show all categories

The last access date of a file is maintained by Windows. Since Windows Vista/Server 2008, Microsoft disabled the automatic update for the "Last access" date by default to improve system performance on NTFS formatteddrives. Because of this, the date won't be updated anymore if a file content is changed for example. That is also the reason why the last access date isn't a good indicator anymore for recent usage of a file.

For more information, see the MSDN homepage.

The installation (upgrade) to the new version is straight forward and does not require an reboot of the server/machine you install the update on.

For security reasons, the Windows Api used only allows a user to log on from a trusted domain (Trust). Otherwise the login attempt fails. Please make sure that the domain of the user you want to use to perform the scan belongs to a trusted domain.

You can use the OLE automation interface of the SpaceObServer Enterprise Version for this purpose. A sample script that exports the "History" graph and sends it via email can be found in the "Demos" subfolder of the SpaceObServer installation directory ("SendHistoryDemo.vbs"). >For further information please refer to the SpaceObServer help.

Please check the following settings of your MS SQL Server to ensure that remote connections are allowed:

1. Open the "SQL Server Configuration Manager" ("Programs > Microsoft SQL Server > Configuration Tools"), select "SQL Server Network Configuration" and ensure that the protocol "TCP/IP" is activated.
2. Check your Windows Firewall to ensure that the port used by the SQL Server for TCP/IP is not blocked.
3. Open the "SQL Server Configuration Manager", select "SQL Server Services" and ensure that the "SQL Server Browser" is started and the "start mode" is set to "Automatic".
4. Open the "SQL Server Management Studio" ("Programs > Microsoft SQL Server"), connect to your SQL Server, select "Properties" in the context menu of your SQL Server instance, select the page "Connections" and ensure on that the option "Allow remote connections to this server" is activated.
5. Restart your SQL Server in case you had to change any of its configurations (Step 1. or 4.).