Not again, yet another Cookie banner!
We know, we know. It annoys us, too. So let’s do it quickly:

We use only a few cookies to ensure the functioning of our website. Besides that, we need a few cookies for our search engine ads.

We don't have any other cookies, we don't collect personalized data. Instead, we operate anonymized website tracking with Matomo, entirely without cookies, and thus deliberately avoid Google Analytics.
cookiesSelect Cookies manually
By clicking on "Select All", you help us improving both our products and our website. You can adjust your selection at any time in our privacy policy.
✓ Select All Save Selection
Learn more about our cookie usage Privacy | Imprint

FAQs & Knowledge Base

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

Categories: ServerSentinel | Show all categories

status_loader

During your maintenance period, you will find them at Downloads/Updates -> Older versions in your customer account. There are the installation files and keys of the two last major versions.

None of our applications depend on Java Spring or any other Java library and are thus not affected by this vulnerability.

All of our products are being developed in Delphi or C#. Although we use Spring4D(elphi) with some of the components, they are safe to use, because the reported vulnerability applies to Java Spring framework only.

This applies to all versions and editions of our applications (TreeSize, SpaceObServer, SpaceObServer WebAccess, HeavyLoad, SmartPOP2Exchange, Exchange Server Toolbox, SpamAssassin in a Box, SpamAssassin for Windows, SmartCallMonitor, SEPA-Transfer, ServerSentinel, and ShellBrowser). It is recommended to always use the latest available versions though to benefit from the latest patches, improvements, and features.

All of our products are being developed in Delphi or C#. Although we use Log4Net with some of the components, they are safe to use, because the reported vulnerability applies to Log4J only.

None of our applications depend on Log4J or any other Java library and are thus not affected by this vulnerability.

This applies to all versions and editions of our applications (TreeSize, SpaceObServer, SpaceObServer WebAccess, HeavyLoad, SmartPOP2Exchange, Exchange Server Toolbox, SpamAssassin in a Box, SpamAssassin for Windows, SmartCallMonitor, SEPA-Transfer, ServerSentinel, and ShellBrowser). It is recommended to always use the latest available versions though to benefit from the latest patches, improvements, and features.

The space used by the database depends on the number of sensors, their types and how often they are executed. Generally the database needs approx. 60 MB per 100,000 sensor checks. This is just a rule of thumb and may vary depending on the used database and its recovery settings.

The unit for the temperature is selected according to the regional settings of the current user. If the measurement system is set to "Metric", Celsius will be used. If the measurement system is set to "U.S.", Fahrenheit will be used. This also applies to the service. If notifications from the service use the wrong unit, the measurement system must be changed for the corresponding user. For system accounts, the regional settings can be used to transfer the settings of the current user to all system accounts.

You will have to download the full version of the software from our customer's area. The login data may be found in the e-mail or in the printed license which you have received after the purchase. In case you do not have your login data anymore, you may request them to be sent to the e-mail address you already used when purchasing the software.

The evaluation copy allows you to test the software before you buy it. The evaluation time is limited to 30 days. Further usage of the software after this period is not permitted and violates the law. In order to allow our customers to fully test our software products, our evaluation versions usually do not contain significant limitations. But the software may remind you from time to time to purchase it after you are finished testing it.

In the case that VDS is not supported check the manufacturer-specific management software if SNMP is supported and use the SNMP Request Sensor to query the specific OIDs.

To reinstall the service there are two options:

  1. Re-install ServerSentinel. During the installation, you should be asked to choose a user for the service. If this page does not occur, the service is damaged and must be uninstalled first. Follow the instruction from 2. to do this.
  2. You can install the service manually by executing “ServerSentinel.Service.exe /install” on the command line. The file is located in the installation directory in the sub-directory "bin”. A dialog should open, where you can choose the user for the service. If the dialog does not open, the service is damaged and must be uninstalled first. In this case execute first “ServerSentinel.Service.exe /uninstall” and then install it again.

This is a bug in the provider. To avoid it, you have several options:

  1. Go in the dialog to the 'All' tab and set the option 'Persist Security Info' to true. Afterwards the password should be saved.
  2. Extend the connection string manually with the parameter 'Password=********;'.
  3. Use instead of user name/password the integrated Windows security.
  4. Use the 'Microsoft OLE DB Provider for SQL Server instead which does not have this problem.

All entries (Page 1 / 2)