The reason is the installation on a file system, on which locks cannot be generated. This could be a USB stick on MacOS or a network drive (all platforms).
Remedy is found by deactivating the locking via the BL Banking.ini file. Here the line -Dosgi.locking=none must be added.
To find the file BL Banking.ini under Mac OS, see FAQ 19.
During operation, a window appears with the message: "An internal error occurred ..."
If you click the Details button, you also see: Java heap space
You should then give BL Banking more memory by adding the following line in the configuration file BL Banking.ini at the end below -vmargs.
-Xmx512m
About the configuration file BL Banking.ini see FAQ 154.
For Mac OS, see also FAQ 19.
For the operation of BL Banking an Internet connection is required. The error message UnknownHostException means that an Internet connection could not be established. First you could enter an URL in the browser to check if there is a general connection problem, which also occurs independent from the BL Banking client. Often a disruption of the Internet connection persists only short-time and disappears by itself.
See also chapter General - System requirements - Internet connection.
Furthermore you can enter the URL of the banking server in the browser to check if the server of the bank can be reached. You can look-up this URL in the bank properties by double-clicking the bank in the Jobs perspective. For most banking servers a description of the manufacturer is displayed in the browser.
See also chapter Jobs - Bank properties.
If this check was successful, but the connection still does not work in BL Banking, you should check if a proxy server is entered in the settings of the browser. If this is the case, you should also enter it in BL Banking. Additionally you can also check, if the proxy in the browser is configured via a so-called PAC file.
See also chapter General - Preferences - General information.
Check the Host-ID. In most cases this is not correct.
If the URL would be wrong, you would rather receive a java.net.UnknownHostException.
Check the URL: Was is entered correctly?
Enter the URL in a web browser: Can you connect then? Can you connect to the Internet at all?
See also FAQ 20.
This error message may occur with various requests to the server of the bank, e. g. while retrieving account statements. It means that the server does not respond within a given time.
You can check whether the server of your bank can be reached by typing its address in your web browser. The address you can find under Jobs - Bank properties.
This means that the bank server does not respond within the given time interval.
The timeout for Connect und Read is set to two minutes by default, but can be configured in the BL Banking.ini file by adding the following lines.
Connect-timeout: -Dde.businesslogics.banking.timeout=<time in milliseconds>
Read-timeout: -Dde.businesslogics.banking.readTimeout=<time in milliseconds>
It should not be necessary to change the Connect-timeout, but for the Read-timeout it could be required to be able to retrieve very large files from the server. Sometimes the server needs more than two minutes to deliver a file.
See also FAQ 20 and about the configuration file BL Banking.ini FAQs 154 and 19.
When entering the license number during the initialization the error message java.net.ConnectException: Connection refused: connect appears.
This means that the connection to the Internet doesn't work.
In this case one should proceed as in case of an UnknownHostException. See FAQ 20.
If BL Banking does not start, the log file can help to analyse the error.
The log file is named .log and is located in the directory workspace\.metadata below the program folder.
To make the file visible under Windows, please click Organize in the file manager (Windows Explorer) and there choose Folder and search options. In the window that opens thereupon select the View tab. There unselect the checkbox Hide extensions for known file types and under Hidden files and folders choose the option Show hidden files, folders, and drives.
This error message means that a tag without content is used in the SEPA file. This is not allowed. If there is no content, then the tag should not appear at all, e.g. for the unstructured remittance information, a tag of the kind
<Ustrd> < /Ustrd>
or
<Ustrd/>
is not allowed.