Knowledgebase

No. On October 21, 2026, the PHP project disclosed two critical security vulnerabilities (CVE-2026-109618 and CVE-2026-109619, also known as "PHP2Shell") that could potentially allow attackers to execute malicious code on web servers.

We updated all affected systems immediately after the security updates were released. In addition, we conducted a targeted review of our systems for possible signs of attack. This review found no indication of unauthorized access or compromise.

Independently of this incident, we always keep our systems up to date and review them regularly so that we can respond quickly to new threats.

Our products, such as TreeSize, SpaceObServer (Web Access), UltraSearch, ShellBrowser and SEPA-Transfer, are not affected.

Yes, SEPA-Transfer does support the lastest SEPA-Verison. If you navigate to the configuration menu, you'll find the option to change to version 3.7 in "Account" -> "Advanced" -> "SEPA-Version".

The software must be activated for each user and each device on which it is used. This usually happens automatically in the background by connecting to our activation server at https://api.jam-software.de.
Please check the following:
    - Does your system lack Internet access?
    - Is a firewall, proxy, or similar blocking access to our activation server?
    - Is the address not on the whitelist of a firewall, proxy, or similar?

In these cases, activation can be performed manually.
You can find detailed instructions here: https://customers.jam-software.de/manualActivation.php?language=EN .

Customers with 25 or more licenses can reuse their activation response on multiple systems so they don't have to perform all the activation steps on each individual system.

For all we know so far, this issue seems to be caused by defects in the system itself. It might affect other applications as well.

To fix it, you might try to (please check the installation after each step):

1. Restart the system.
2. Check for pending/available Windows updates
3. Download and run the Microsoft .NET Framework Repair Tool
4. Download and reinstall .NET Framework 4.8
5. Open a command line prompt (Win+R -> CMD -> Ok) and run
   DISM.exe /Online /Cleanup-Image /RestoreHealth
6. Open a command line prompt (or use the same as before) and run
   sfc /Scannow
7. Uninstall KB5011048 from the system (how to)
8. Check for updates again or install KB5011048 manually again

Please find more information on DISM and SFC here.

The error "The database engine could not lock table ..." indicates that the database of SEPA-Transfer is in use by a different application (e.g. by a different SEPA-Transfer instance or by MsAccess).

In this case, please close all other SEPA-Transfer instances and other applications that could lock the SEPA-Transfer database.

If this does not solve the problem, please restart the PC and start SEPA-Transfer afterwards.

SEPA-Transfer is a tool for creating and managing SEPA credit transfers and direct debits. It supports online banking via HBCI/FinTS, generation of SEPA XML files, and batch processing through command-line automation.

Key capabilities include:

• SEPA standard 3.7 support (used by default for newly added accounts since V11.8); the SEPA version can be changed under "Start > Settings > Advanced > SEPA version".
• Recipient name verification for German online banking (since V11.6).
• 64-bit application since V11.7.
• Import from Excel, CSV, Access, DTA, SEPA XML and ISO-20022 files, and export to Excel or SEPA XML files.
• Command-line automation for scripted processing.

For details, see the manual at https://manuals.jam-software.com/sepa-transfer/EN/ and the changelog at https://www.jam-software.com/sepa-transfer/changes.shtml.

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.

SEPA-Transfer is a 64-bit application since version 11.7. Since version 11.8.2, SEPA-Transfer checks at every program start whether the required database driver is available and automatically ensures that it is installed.

If a connection still cannot be established, set it up manually via the ODBC Data Sources dialog that matches the application architecture (64-bit).

On Windows 10 and 11, the corresponding program is called "ODBC Data Sources (64bit)" and can be used for setting up the connection.

Aktuell können in SEPA-Transfer keine Intervalle hinterlegt werden, in denen Lastschriften ausgeführt werden. Jede (Sammel-)Lastschrift benötigt eine Verifizierung durch eine TAN, weswegen sich in SEPA-Transfer leider keine vollständige Automatisierung vornehmen lässt.

Die Vorgehensweise ist vielmehr so gedacht, dass Sie immer dann, wenn Lastschriften anstehen, in die Mandatsverwaltung von SEPA-Transfer gehen (Extras > Mandate) und dort aus den Mandaten Lastschriften erzeugen, indem Sie z.B. alle Mandate markieren und dann unten auf die Schaltfläche „Neue Buchungen erstellen" klicken.

First ensure that you have the installer for the full version and your license key. Both are available within your maintenance period in our customer area.

You can now uninstall our software on your old computer and install it on your new computer. An explicit license deactivation is not necessary.