Knowledgebase

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.

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.

Since SEPA-Transfer is a 32bit application, there are sometimes issues with connecting databases to SEPA-Transfer.

Since most windows versions only have the 64bit driver installed, the connection has to be set up manually.

In Windows 10 and 11, there is a program called "OCDB Data Sources (32bit)" which 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.

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.

Yes, this option is available in the Enterprise Edition of SEPA Transfer.

Unfortunately, the Small Business Edition does not offer this function.

When sending bookings to the bank, there is a checkbox in the SEPA Transfer dialog "List bookings on the account statement individually". If this is selected, an indicator called "Batch booking" is written to the SEPA file, which instructs the bank to show all of the collector's bookings individually on the account statement.

However, some banks ignore this flag. The only workaround is to send all bookings individually. Please note that this may incur higher booking costs than for a collector and that you will need a TAN for each booking.

SEPA-Trafser supports you in this if you set the option "Maximum number of postings for SEPA export" at the bottom of the "Advanced" page of the settings dialog to "1". This option is also only available in the Enterprise Edition.

Owners of the Small Business Edition can purchase an upgrade to the Enterprise Edition at a reduced price in our customer area.

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.

According to the SEPA standard, the execution date 01.01.1999 for credit transfers means "earliest possible date" (formally "non-terminated credit transfer") and is always used by SEPA-Transfer if the execution date is the respective today's date.

If you specify a future date, SEPA-Transfer exports a "scheduled transfer". This contains the date as specified.

Some banks and other programmes do not accept that standard. In that case you would please have to switch to the Enterprise Edition:

In the Enterprise Edition of SEPA-Transfer, there is an option to influence this behavior in the settings under "Advanced". In the "Bank specific settings" section, check the "Execution date of non-terminated SEPA transfers is the current day instead of 01.01.1999" to always use the date you set in SEPA transfers.