Bug 512032 - Again "aqhbci" doesn't update my account, but shows error "-109"
Summary: Again "aqhbci" doesn't update my account, but shows error "-109"
Status: RESOLVED NOT A BUG
Alias: None
Product: kmymoney
Classification: Applications
Component: onlinebanking (other bugs)
Version First Reported In: unspecified
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
: 512599 (view as bug list)
Depends on:
Blocks:
 
Reported: 2025-11-13 12:01 UTC by Stefan Hohrein
Modified: 2026-01-01 16:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Hohrein 2025-11-13 12:01:23 UTC
SUMMARY
11:49:55	AqBanking v6.7.7.0beta
11:49:55	Sende Aufträge an die Bank(en)
11:49:55	Aufträge nach Konto sortieren
11:49:55	Konten-Aufträge nach Providern sortieren
11:49:55	Aufträge an Provider verteilen
11:49:55	Aufträge an Provider "aqhbci" übergeben
11:50:55	Fehler beim Übergeben der Aufträge an Provider "aqhbci":-109
11:50:55	Vorgang abgeschlossen, Sie können das Fenster nun schließen.

kmymoney   version 5.2.70 
Windows 10 version 2009 (X86_64)

mingw64-kmymoney5-portable-5.2.1+20251111+git.9492c4db-lp156.739.1.noarch.cpio
and
mingw64-kmymoney5-portable-5.2.70+20251002+git.be166fa-lp156.731.2.noarch.rpm
are showing same behaviour


STEPS TO REPRODUCE
1.  Trial to update account takes some minutes till aqhbci-SW seems to be installed (this is new since last aqhbci update end of September 2025)
2.  

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Same as previous bug 509313 which was fixed
Comment 1 Ralf Habacker 2025-11-13 21:40:47 UTC
(In reply to Stefan Hohrein from comment #0)
> 1.  Trial to update account takes some minutes till aqhbci-SW seems to be installed
Error -109 and the long timeout may indicate a lock problem with the requested aqbanking user. 

It may help to search for .lck files under %APPDATA%\aqbanking\ (usually C:\Users\<user>\AppData\Roaming\aqbanking\ without special settings) and delete them.
Comment 2 Jack 2025-11-27 23:05:33 UTC
*** Bug 512599 has been marked as a duplicate of this bug. ***
Comment 3 Jack 2025-11-27 23:08:43 UTC
from other bug, still present with 
Windows: 10 Pro 22H2
AqBanking v6.7.7.0beta
KMyMoney 5.2.70+20251115+git.ea8854c
Comment 4 Ralf Habacker 2025-11-28 07:48:52 UTC
In the source gwenhywfar  https://github.com/aqbanking/gwenhywfar/blob/1c6987d9445c0ce5623831f5dce50f1921a96339/src/base/error. h#L131, there is an identical error code named GWEN_ERROR_LOCK.
Comment 5 Ralf Habacker 2025-11-28 08:39:48 UTC
(In reply to Ralf Habacker from comment #1)
 
> It may help to search for .lck files under %APPDATA%\aqbanking\ (usually
> C:\Users\<user>\AppData\Roaming\aqbanking\ without special settings) and
> delete them.

To obtain the exact directory, a function in aqbanking-cli would be helpful, for which a patch has been submitted with this ticket: https://www.aquamaniac.de/rdm/issues/323
Comment 6 Stefan Hohrein 2025-12-01 18:12:09 UTC
To delete one ".lck"-file I found, helped to overcome error -109 and the full communication worked as expected (see below). ==>  Thanks!
Unfortunately the only report which was performed was the update of the final account status of today (= Online Balance). All other bank account activities in between where skipped. The single line of today with "Online Balance" is highlighted in pink and can't be removed to try older versions of KmyMoney without the *.lck-file. This means the total history between last update (30.09.25) and today is not processed at all.

18:31:37	AqBanking v6.7.7.0beta
18:31:37	Sende Aufträge an die Bank(en)
18:31:37	Aufträge nach Konto sortieren
18:31:37	Konten-Aufträge nach Providern sortieren
18:31:38	Aufträge an Provider verteilen
18:31:38	Aufträge an Provider "aqhbci" übergeben
18:31:38	Zugriff auf Benutzer "1"
18:31:38	AqHBCI gestartet
18:31:38	Wähle iTAN Modus "Smart-TAN plus manuell" (962, Version 6, Prozess 2)
18:31:57	Verwende GnuTLS Default Ciphers.
18:31:57	TLS: SSL-Ciphers ausgehandelt: TLS1.3:ECDHE-RSA-CHACHA20-POLY1305:AEAD
18:32:05	Nachricht gesendet
18:32:05	Antwort erhalten
18:32:05	HBCI: 3060 - Bitte beachten Sie die enthaltenen Warnungen/Hinweise. (M)
18:32:05	HBCI: 3050 - UPD nicht mehr aktuell, aktuelle Version enthalten. (S)
18:32:05	HBCI: 3050 - BPD nicht mehr aktuell, aktuelle Version enthalten. (S)
18:32:05	HBCI: 3920 - Zugelassene TAN-Verfahren für den Benutzer (S)
18:32:05	HBCI: 0901 - *PIN gültig. (S)
18:32:05	HBCI: 0020 - *Dialoginitialisierung erfolgreich (S)
18:32:05	HBCI: 3076 - Starke Kundenauthentifizierung nicht notwendig. (S)
18:32:05	Gefundene Serveradresse: SSL: https://fints2.atruvia.de/cgi-bin/hbciservlet, none
18:32:05	Gefundene Serveradresse: TCP: fints2.atruvia.de, none
18:32:06	New bank info confirms current server address (fints2.atruvia.de/cgi-bin/hbciservlet)
18:32:06	Dialog wurde nicht abgebrochen, PIN scheint gültig zu sein
18:32:06	Verwende GnuTLS Default Ciphers.
18:32:06	TLS: SSL-Ciphers ausgehandelt: TLS1.3:ECDHE-RSA-CHACHA20-POLY1305:AEAD
18:32:06	Nachricht gesendet
18:32:06	Antwort erhalten
18:32:06	HBCI: 9050 - Die Nachricht enthält Fehler. (M)
18:32:06	HBCI: 9260 - Eine Challenge-Anfrage wurde abgebrochen, der Auftrag wird nicht ausgeführt. (S)
18:32:06	HBCI: 3070 - Ungültige Challenge-Anforderung. (S)
18:32:06	HBCI: 3999 - Berechtigung für diesen Geschäftsvorfall nicht ausreichend. (S)
18:32:06	Dialog wurde nicht abgebrochen, PIN scheint gültig zu sein
18:32:06	AqHBCI abgeschlossen.
18:32:06	Freigeben von Benutzer "1"
18:32:06	Vorgang abgeschlossen, Sie können das Fenster nun schließen.
Comment 7 Thomas Baumgart 2025-12-02 07:03:14 UTC
Due to recent changes at several (German) banks, the package needs at least AqBanking v6.7.12.0beta to get this working. Watch out for updates.
Comment 8 Ralf Habacker 2025-12-02 15:12:26 UTC
(In reply to Thomas Baumgart from comment #7)
> Due to recent changes at several (German) banks, the package needs at least
> AqBanking v6.7.12.0beta to get this working. Watch out for updates.

The corresponding aqbanking package was updated to version 4.7.14beta today and should be included in the portable package tomorrow.
Comment 9 Ralf Habacker 2025-12-02 15:13:59 UTC
(In reply to Ralf Habacker from comment #8)
> The corresponding aqbanking package was updated to version 4.7.14beta today
> and should be included in the portable package tomorrow.

6.7.14beta
Comment 10 Bug Janitor Service 2025-12-17 03:46:14 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 11 Stefan Hohrein 2025-12-20 08:05:30 UTC
KMyMoney	Stable snapshot	5.2.1+20251219+git.d900ee0d	64 bit	portable package [1]	KMyMoney Version 5.2.1
Aqbanking Version unknown (build against 6.8.2)

==> "There is no online account assigned to this user account"
There is no assignment between online account and user account possible because nothing offered under "assign account"
==> no update of account possible

_________________


KMyMoney	Unstable snapshot	5.2.70+20251115+git.ea8854cc	64 bit	portable package [1]
Aqbanking Version unknown (build against 6.8.2)

1509 times: "Dangerous link path was ignored : kmymoney5-mingw64-5.2.70+20251115+git.ea8854cc\share\icons\oxygen\base\22x22\emblems\emblem-added.png : ..\actions\list-add.png"

==> same behaviour like above
Comment 12 Stefan Hohrein 2025-12-20 08:12:31 UTC
KMyMoney	Stable snapshot	5.2.1+20251219+git.d900ee0d	64 bit	portable package [1]	KMyMoney Version 5.2.1
Aqbanking Version unknown (build against 6.8.2)

==> "There is no online account assigned to this user account"
There is no assignment between online account and user account possible because nothing offered under "assign account"
==> no update of account possible

_________________


KMyMoney	Unstable snapshot	5.2.70+20251115+git.ea8854cc	64 bit	portable package [1]
Aqbanking Version unknown (build against 6.8.2)

1509 times: "Dangerous link path was ignored : kmymoney5-mingw64-5.2.70+20251115+git.ea8854cc\share\icons\oxygen\base\22x22\emblems\emblem-added.png : ..\actions\list-add.png"

==> same behaviour like above
Comment 13 Stefan Hohrein 2025-12-20 08:14:09 UTC
Additional information due to update to WIN11:

Edition	Windows 11 Pro
Version	23H2
Installiert am	‎11.‎03.‎2024
Betriebssystembuild	22631.6199
Leistung	Windows Feature Experience Pack 1000.22700.1108.0

Gerätename	Stefans-Laptop
Prozessor	Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz   2.59 GHz
Installierter RAM	64,0 GB (63,8 GB verwendbar)
Geräte-ID	02817D2D-EB17-4854-B0F9-FCD5ED12B87D
Produkt-ID	00330-53662-36317-AAOEM
Systemtyp	64-Bit-Betriebssystem, x64-basierter Prozessor
Stift- und Toucheingabe	Für diese Anzeige ist keine Stift- oder Toucheingabe verfügbar.
Comment 14 Ralf Habacker 2025-12-22 09:16:39 UTC
(In reply to Stefan Hohrein from comment #12)
> There is no assignment between online account and user account possible
> because nothing offered under "assign account"

Have you added an online account with aqbanking and assigned it to the corresponding kmymoney account? – You can find out how to do this in the kmymoney manual, for example at https://docs.kde.org/trunk5/en/kmymoney/kmymoney/reference.html#reference.menus.settings.help.
> 
> 
> KMyMoney	Unstable snapshot	5.2.70+20251115+git.ea8854cc	64 bit	portable
> package [1]
> Aqbanking Version unknown (build against 6.8.2)
> 
> 1509 times: "Dangerous link path was ignored :
> kmymoney5-mingw64-5.2.70+20251115+git.
> ea8854cc\share\icons\oxygen\base\22x22\emblems\emblem-added.png :
> ..\actions\list-add.png"
This is a minor issue with the package and can be ignored for now

> 
> ==> same behaviour like above

See hints above.
Comment 15 Ralf Habacker 2025-12-23 13:48:05 UTC
(In reply to Stefan Hohrein from comment #12)
> KMyMoney	Unstable snapshot	5.2.70+20251115+git.ea8854cc	64 bit	portable
> package [1]
> Aqbanking Version unknown (build against 6.8.2)
> 
> 1509 times: "Dangerous link path was ignored :
> kmymoney5-mingw64-5.2.70+20251115+git.
> ea8854cc\share\icons\oxygen\base\22x22\emblems\emblem-added.png :
> ..\actions\list-add.png"

During which process and in which application did this message occur?
Comment 16 Stefan Hohrein 2025-12-28 12:08:22 UTC
Installation of:
KMyMoney	Stable snapshot	5.2.1+20251219+git.d900ee0d	64 bit	portable package [1]	KMyMoney Version 5.2.1
Aqbanking Version unknown (build against 6.8.2)

Trial to update account led to:
==> "There is no online account assigned to this user account"

Trial to assign account leads to
==> no update of account possible

==================================================
Installation of:
KMyMoney	Unstable snapshot	5.2.70+20251115+git.ea8854cc	64 bit	portable package [1]
Aqbanking Version unknown (build against 6.8.2)

led to 1509 times: "Dangerous link path was ignored : kmymoney5-mingw64-5.2.70+20251115+git.ea8854cc\share\icons\oxygen\base\22x22\emblems\emblem-added.png : ..\actions\list-add.png"

afterwards
==> same behaviour like previous installation attempt

=============================================

Trial to initialize AqBanking led to:

12:31:58 Server-Zertifikat abrufen
12:31:58 Verbindung vorbereiten
12:31:58 Fehler beim Vorbereiten der Verbindung
12:31:58 Konnte keine Verbindung zum Server herstellen
12:31:58 Aborted by user.
12:31:58 Vorgang abgeschlossen, Sie können das Fenster nun schließen.

Server data from your table "BBBank	660 908 00	hbci://hbci01.fiducia.de:3000/"

After several trials of "BENUTZERKENNUNG" = "Benutzername" or
                                    "BENUTZERKENNUNG" = "VR-NetKey"
I came to the conclusion, that already the link to the the server "hbci://hbci01.fiducia.de:3000/" seems to be wrong. 

I searched in Internet and found:
Wie lautet die URL zur Nutzung von HBCI?
https://fints2.atruvia.de/cgi-bin/hbciservlet (HBCI PIN/TAN)

With this URL I got the following result:
12:55:56	Server-Zertifikat abrufen
12:55:56	Verbindung vorbereiten
12:55:56	Mit Server verbinden...
12:55:56	Verwende GnuTLS Default Ciphers.
12:55:56	TLS: SSL-Ciphers ausgehandelt: TLS1.3:ECDHE-RSA-CHACHA20-POLY1305:AEAD
12:55:56	Verbunden.
12:55:57	Verbindung beendet.
12:55:57	Zertifikat erhalten
12:55:57	
12:55:57	Allgemeine Bankinfos abrufen (SCA)
12:55:57	AqHBCI gestartet
12:55:57	Öffne Dialog mit dem Server
12:55:57	Verwende GnuTLS Default Ciphers.
12:55:57	TLS: SSL-Ciphers ausgehandelt: TLS1.3:ECDHE-RSA-CHACHA20-POLY1305:AEAD
12:55:57	Nachricht gesendet
12:55:57	Antwort erhalten
12:55:57	HBCI: 3060 - Bitte beachten Sie die enthaltenen Warnungen/Hinweise. (M)
12:55:57	HBCI: 0100 - Dialog beendet. (M)
12:55:57	HBCI: 3050 - BPD nicht mehr aktuell, aktuelle Version enthalten. (S)
12:55:57	HBCI: 0020 - Informationen fehlerfrei entgegengenommen. (S)
12:55:57	Gefundene Serveradresse: SSL: https://fints2.atruvia.de/cgi-bin/hbciservlet, none
12:55:57	Gefundene Serveradresse: TCP: fints2.atruvia.de, none
12:55:57	New bank info confirms current server address (fints2.atruvia.de/cgi-bin/hbciservlet)
12:55:57	Beende Dialog mit dem Server
12:55:57	Verwende GnuTLS Default Ciphers.
12:55:57	TLS: SSL-Ciphers ausgehandelt: TLS1.3:ECDHE-RSA-CHACHA20-POLY1305:AEAD
12:55:57	Nachricht gesendet
12:55:57	Antwort erhalten
12:55:57	HBCI: 0010 - Nachricht entgegengenommen. (M)
12:55:57	HBCI: 0100 - Dialog beendet. (M)
12:55:57	AqHBCI abgeschlossen.
12:55:57	
12:55:57	Systemkennung abrufen
12:55:57	AqHBCI gestartet
12:56:14	Verwende GnuTLS Default Ciphers.
12:56:14	TLS: SSL-Ciphers ausgehandelt: TLS1.3:ECDHE-RSA-CHACHA20-POLY1305:AEAD
12:56:14	Nachricht gesendet
12:56:14	Antwort erhalten
12:56:14	HBCI: 9050 - Die Nachricht enthält Fehler. (M)
12:56:14	HBCI: 9800 - Dialog abgebrochen (M)
12:56:14	HBCI: 9942 - *Anmeldedaten sind ungültig. (M)
12:56:14	PIN ungültig laut Antwort des Servers
12:56:14	HBCI: 9340 - Auftrag abgelehnt. (M)
12:56:14	PIN ungültig laut Antwort des Servers
12:56:14	Dialog-Abbruch durch den Server.
12:56:14	AqHBCI abgeschlossen.
12:56:14	Aborted by user.
12:56:15	Vorgang abgeschlossen, Sie können das Fenster nun schließen.

==> no further idea :-(

Regards Stefan
Comment 17 Stefan Hohrein 2025-12-28 13:07:30 UTC
Latest result:
After additional trials with the Server URL "https://fints2.atruvia.de/cgi-bin/hbciservlet" and "Benutzerkennung = my VR-NetKey" I was able to finalize the AqBanking- installation.
Finally I got the following message during updating my account which seemsvery plausible:

13:44:01	AqBanking v6.8.2.0stable
13:44:01	Sende Aufträge an die Bank(en)
13:44:01	Aufträge nach Konto sortieren
13:44:01	Konten-Aufträge nach Providern sortieren
13:44:01	Aufträge an Provider verteilen
13:44:01	Aufträge an Provider "aqhbci" übergeben
13:44:01	Zugriff auf Benutzer "14"
13:44:01	AqHBCI gestartet
13:44:01	Wähle iTAN Modus "SecureGo plus (Direktfreigabe)" (946, Version 7, Prozess 2)
13:44:01	Verwende GnuTLS Default Ciphers.
13:44:01	TLS: SSL-Ciphers ausgehandelt: TLS1.3:ECDHE-RSA-CHACHA20-POLY1305:AEAD
13:44:01	Nachricht gesendet
13:44:02	Antwort erhalten
13:44:02	HBCI: 3060 - Bitte beachten Sie die enthaltenen Warnungen/Hinweise. (M)
13:44:02	HBCI: 3920 - Zugelassene TAN-Verfahren für den Benutzer (S)
13:44:02	HBCI: 0901 - *PIN gültig. (S)
13:44:02	HBCI: 0020 - *Dialoginitialisierung erfolgreich (S)
13:44:02	HBCI: 3076 - Starke Kundenauthentifizierung nicht notwendig. (S)
13:44:02	Dialog wurde nicht abgebrochen, PIN scheint gültig zu sein
13:44:02	Verwende GnuTLS Default Ciphers.
13:44:02	TLS: SSL-Ciphers ausgehandelt: TLS1.3:ECDHE-RSA-CHACHA20-POLY1305:AEAD
13:44:02	Nachricht gesendet
13:44:02	Antwort erhalten
13:44:02	HBCI: 3060 - Bitte beachten Sie die enthaltenen Warnungen/Hinweise. (M)
13:44:02	HBCI: 0020 - *Abfrage der Kontosalden erfolgreich. (S)
13:44:02	HBCI: 0901 - *PIN gültig. (S)
13:44:02	HBCI: 3920 - Zugelassene TAN-Verfahren für den Benutzer (S)
13:44:02	Dialog wurde nicht abgebrochen, PIN scheint gültig zu sein
13:44:02	Beende Dialog mit dem Server
13:44:02	Verwende GnuTLS Default Ciphers.
13:44:02	TLS: SSL-Ciphers ausgehandelt: TLS1.3:ECDHE-RSA-CHACHA20-POLY1305:AEAD
13:44:02	Nachricht gesendet
13:44:02	Antwort erhalten
13:44:02	HBCI: 0010 - Nachricht entgegengenommen. (M)
13:44:02	HBCI: 0100 - Dialog beendet. (M)
13:44:02	Dialog wurde nicht abgebrochen, PIN scheint gültig zu sein
13:44:02	AqHBCI abgeschlossen.
13:44:02	Freigeben von Benutzer "14"
13:44:02	Vorgang abgeschlossen, Sie können das Fenster nun schließen.

The Online Balance was showing the correct number (success !!!), but the latest activities where not shown or updated :-(.

Possibly the date of last update was wrong, but the tool didn't even ask me for that date as it does in former times.

Further attempts to transfer some money back and forth always showed the correct final "Online Balance" but didn't show any activities in between.

For me the AqBanking module itself or its connection to KmMoney doesn't work correctly.
Comment 18 Thomas Baumgart 2025-12-28 14:41:51 UTC
1) Is the "Prefer Statement Download as CAMT" in the AqBanking configuration of the account turned on? If not, turn it on.
2) Open the AqBanking configuration for the user of the institution and press the "Get Bank Info, "Get System ID", "Get iTAN modes" and "Get Accounts" buttons in that order.
3) Open the KMyMoney account editor for the account
4) Open the "Online settings" tab
5) Select the "Download" tab
6) To control the date for the first transaction to download, select "Ask user". (Once all is working you can switch to "Last download")
7) Start the download of transactions
8) When asked for a date, select the one of the last downloaded transaction. 

Note: you might get duplicates due to the switch to CAMT download format. If this is the case, you need to fix those manually by deleting one of them (I suggest the older one to avoid additional duplicates).
Comment 19 Stefan Hohrein 2026-01-01 15:40:20 UTC
KmyMoney is working again without any restrictions :-) Thanks a lot and have a happy new year.
Stefan Hohrein