Knowledgebase

This error code indicates that the root certificate is not trusted on the system. We just recently updated the certificate we used to sign our applications, so it still seems to be the case that this root certificate is not yet up to date.

These certificates are usually being updated and installed online and/or along with Windows updates. These updates might be disabled manually though.

Please check for pending or available Windows updates first.

If this doesn't work, please try to download and install the updated certificates manually. They are issued from GlobalSign and should therefore be considered safe:

Root certificate https://secure.globalsign.com/cacert/codesigningrootr45.crt

Intermediate certificate https://secure.globalsign.com/cacert/gsgccr45evcodesignca2020.crt

Please ensure to install the root certificate to the correct store (root certificates). Having Windows select the store automatically, it might select the wrong store for this certificate.

To install the root certificate, proceed as follows:

1. Download the certificate. If the browser reports that the file could damage the system, confirm this message with "Keep".
   As the certificate comes from a trusted source (GlobalSign), this warning is not relevant in this case.
2. Right-click on file and select "Install certificate" in the context menu.
3. A Windows dialog opens. First select the storage location "Local computer" and "Next".
4. On the following page, select "Save all certificates in the following location" -> Browse -> "Trusted root certification authorities" for this certificate.
5. Click on continue/next until the import process is complete.

Proceed in the same way to install the intermediate certificate, but select the "Intermediate certification authorities" folder in step 4.

To grant permissions on the respective site collections to be scanned via TreeSize/SpaceObServer, the PowerShell cmdlet Grant-PnPAzureADAppSitePermission can be used.

1.  Import-Module PnP.Powershell
2. Connect-PnPOnline -Url <SharePointSIteURL> -Interactive
3. Grant-PnPAzureADAppSitePermission -AppId <AzureAppID> -DisplayName <AzureAppName>  -Site < SharePointSiteURL> -Permissions write

The user that is used for granting the permission must be a site collection admin of the respective site collection. The role 'Owner' is not sufficient.

For more information about the used cmdlets please see: https://pnp.github.io/powershell/cmdlets/

Some database providers may not be installed on a device.

Please visit the following Microsoft page to download the SQL Server Native Client: Download Microsoft® SQL Server® 2012 Native Client - Latest Servicing Release from Official Microsoft Download Center

Please run the downloaded installer and try to connect to the database again.

When you are using the option "Use MAPI client" in the settings under "Export > Email", you need to make sure that an email program like i.e. Outlook is installed and operational.

During your maintenance period, they are located at Downloads -> Older versions in the customer area, if you are logged in to your customer account.

You should be able to find the installation files and keys of the two last major versions there.

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.

The reason why PDF files cannot be opened is because Adobe Acrobate Reader is preventing to open files from an application with administrator rights via its Protected Mode. To solve this issue disable protected mode by doing the following:

1. Open Adobe Reader.
2. Choose Edit > Preferences...
3. In the Categories list on the left, select Security (Enhanced).
4. In the Sandbox Protections section, deselect Enable Protected Mode at startup.
5. Click OK to save the changes.
6. Close Adobe Reader.

For more information about Protected Mode (and possible vulnerabilities) refer to the Adobe website.

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.

Yes, a dark mode is available in the latest version of the software. You can activate the dark mode in the options at "View > Display". Please note that this feature requires Windows 10 build 1809 or later.

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.