[gnucash-de] [Aqbanking-user] Neue Betas: AqBanking 5.99.27 und Gwenhywfar 4.99.14

Do Sep 26 16:13:42 EDT 2019

Moin allerseits,

On 9/13/19 6:30 PM, Heiko Rosemann wrote:
> On 9/12/19 2:36 AM, Martin Preuss wrote:
>> Bin schon gespannt auf Rueckmeldungen...
> 
> Zwar keine Rückmeldung zur Postbank, aber zu den oben genannten
> Beta-Versionen, zusammen mit GnuCash 3.7 und der Triodos Bank (fiducia):
> 
> Kurzfassung: Umsätze und Kontostände abrufen funktioniert. Ein "leerer"
> Umsatzabruf bringt in gnucash eine Fehlermeldung. SEPA-Überweisungen
> funktionieren mit aqbanking-cli, aber nicht mit gnucash.
> [...]
> Probleme habe ich zwei, bei denen ich mich über Tipps zum weiteren
> Debugging freue:
> 
> 1) Wenn ich auf "Online Actions" -> "Issue SEPA transaction..."  klicke,
> kommt zwar das Fenster, in dem ich Überweisungsdaten eingeben kann, dann
> auch das Fenster, in dem ich einen Gegen-Account auswählen kann, und es
> wird auch in gnucash eine Buchung angelegt, aber aqbanking wird nie
> aufgerufen.

Mit inzwischen gwenhywfar-4.99.18rc2 und aqbanking-5.99.35beta sowie dem
Patch aus https://bugs.gnucash.org/show_bug.cgi?id=797430 bin ich einen
Schritt weiter: Jetzt ruft gnucash aqbanking auf, die Überweisung
schlägt aber mit folgendem Log fehl (Pin ist in gnucash gespeichert):

==========================================================================
AqBanking v5.99.35.0beta
Sending jobs to the bank(s)
Sorting commands by account
Sorting commands by account
Sorting commands by provider
Send commands to providers
Send commands to provider "AQHBCI"
Locking users
Locking customer "4474"
Executing HBCI jobs
AqHBCI started
Selecting iTAN mode "mobile TAN" (942, version 6, process 2)
Encoding queue
Sending message
Connecting to server...
Resolving hostname "hbci11.fiducia.de" ...
IP address is "195.200.35.18"
Connecting to "hbci11.fiducia.de"
Connected to "hbci11.fiducia.de"
Using GnuTLS default ciphers.
TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
Connected.
Sending message...
Message sent.
Message sent
Queue sent
Waiting for response
Receiving response...
HTTP-Status: 200 (200)
Response received.
Disconnecting from server...
Disconnected.
Response received
HBCI: 3060 - Bitte beachten Sie die enthaltenen Warnungen/Hinweise. (M)
HBCI: 3920 - Zugelassene TAN-Verfahren für den Benutzer (S)
HBCI: 0901 - *PIN gültig. (S)
HBCI: 0020 - *Dialoginitialisierung erfolgreich (S)
HBCI: 3076 - Starke Kundenauthentifizierung nicht notwendig. (S)
Dialog not aborted, assuming PIN is ok
Encoding queue
Sending message
Connecting to server...
Resolving hostname "hbci11.fiducia.de" ...
IP address is "195.200.35.18"
Connecting to "hbci11.fiducia.de"
Connected to "hbci11.fiducia.de"
Using GnuTLS default ciphers.
TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
Connected.
Sending message...
Message sent.
Message sent
Queue sent
Waiting for response
Receiving response...
HTTP-Status: 200 (200)
Response received.
Disconnecting from server...
Disconnected.
Response received
HBCI: 9050 - Die Nachricht enthält Fehler. (M)
HBCI: 9260 - Eine Challenge-Anfrage wurde abgebrochen, der Auftrag wird
nicht ausgeführt. (S)
HBCI: 3070 - Ungültige Challenge-Anforderung. (S)
HBCI: 3999 - Der SEPA-Auftrag enthält syntaktische Fehler. (S)
Dialog not aborted, assuming PIN is ok
AqHBCI finished.
Unlocking customer "4474"
==========================================================================

Ideen? Eher bei gnucash oder bei aqbanking suchen? aqbanking-cli
sepatransfer funktioniert weiterhin, gibt es in gnucash Einstellungen,
wie aqbanking aufgerufen wird, die hier etwas ändern könnten?

aqbanking-cli sepatransfer sagt folgendes (Pins, Kontonummern etc. ausgeXt)
==========================================================================
AqBanking v5.99.35.0beta
Sending jobs to the bank(s)
Sorting commands by account
Sorting commands by account
Sorting commands by provider
Send commands to providers
Send commands to provider "AQHBCI"
3:2019/09/26 22-03-09:aqbanking-cli(7587):provider_sendcmd.c:  115:
Handling user "xxxxxxxxxx"
Locking users
Locking customer "4474"
Executing HBCI jobs
AqHBCI started
Selecting iTAN mode "mobile TAN" (942, version 6, process 2)
Encoding queue
===== Enter PIN =====
Please enter the PIN for
user xxxxxxxxxx at Triodos Bank Deutschland

Input:
Sending message
Connecting to server...
Resolving hostname "hbci11.fiducia.de" ...
IP address is "195.200.35.18"
Connecting to "hbci11.fiducia.de"
Connected to "hbci11.fiducia.de"
Using GnuTLS default ciphers.
TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
5:2019/09/26 22-04-44:aqbanking(7587):siotlsext.c:  157: Found matching
certificate "6F:29:06:28:FB:6F:B1:7F:05:62:BC:AE:76:49:49:D3" with same
status
5:2019/09/26 22-04-44:aqbanking(7587):siotlsext.c:  163: Automatically
accepting certificate [6F:29:06:28:FB:6F:B1:7F:05:62:BC:AE:76:49:49:D3]
Connected.
Sending message...
Message sent.
Message sent
Queue sent
Waiting for response
Receiving response...
HTTP-Status: 200 (200)
Response received.
Disconnecting from server...
Disconnected.
Response received
HBCI: 3060 - Bitte beachten Sie die enthaltenen Warnungen/Hinweise. (M)
HBCI: 3050 - UPD nicht mehr aktuell, aktuelle Version enthalten. (S)
HBCI: 3920 - Zugelassene TAN-Verfahren für den Benutzer (S)
HBCI: 0901 - *PIN gültig. (S)
HBCI: 0020 - *Dialoginitialisierung erfolgreich (S)
HBCI: 3076 - Starke Kundenauthentifizierung nicht notwendig. (S)
Dialog not aborted, assuming PIN is ok
5:2019/09/26 22-04-45:aqbanking(7587):provider_accspec.c:   54: Writing
account spec for account 4475
5:2019/09/26 22-04-45:aqbanking(7587):provider_accspec.c:   54: Writing
account spec for account 4476
5:2019/09/26 22-04-45:aqbanking(7587):provider_accspec.c:   54: Writing
account spec for account 4477
3:2019/09/26 22-04-45:aqhbci(7587):job_commit_account.c:  358: Account
is new, adding
5:2019/09/26 22-04-45:aqbanking(7587):provider_accspec.c:   54: Writing
account spec for account 7874
5:2019/09/26 22-04-45:aqbanking(7587):provider_accspec.c:   54: Writing
account spec for account 7874
3:2019/09/26 22-04-45:aqhbci(7587):job_commit_account.c:  358: Account
is new, adding
5:2019/09/26 22-04-45:aqbanking(7587):provider_accspec.c:   54: Writing
account spec for account 7875
5:2019/09/26 22-04-45:aqbanking(7587):provider_accspec.c:   54: Writing
account spec for account 7875
3:2019/09/26 22-04-45:aqhbci(7587):job_commit_account.c:  358: Account
is new, adding
5:2019/09/26 22-04-45:aqbanking(7587):provider_accspec.c:   54: Writing
account spec for account 7876
5:2019/09/26 22-04-45:aqbanking(7587):provider_accspec.c:   54: Writing
account spec for account 7876
3:2019/09/26 22-04-45:aqhbci(7587):job_commit_account.c:  358: Account
is new, adding
5:2019/09/26 22-04-45:aqbanking(7587):provider_accspec.c:   54: Writing
account spec for account 7877
5:2019/09/26 22-04-45:aqbanking(7587):provider_accspec.c:   54: Writing
account spec for account 7877
Encoding queue
Sending message
Connecting to server...
Resolving hostname "hbci11.fiducia.de" ...
IP address is "195.200.35.18"
Connecting to "hbci11.fiducia.de"
Connected to "hbci11.fiducia.de"
Using GnuTLS default ciphers.
TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
5:2019/09/26 22-04-45:aqbanking(7587):siotlsext.c:  157: Found matching
certificate "6F:29:06:28:FB:6F:B1:7F:05:62:BC:AE:76:49:49:D3" with same
status
5:2019/09/26 22-04-45:aqbanking(7587):siotlsext.c:  163: Automatically
accepting certificate [6F:29:06:28:FB:6F:B1:7F:05:62:BC:AE:76:49:49:D3]
Connected.
Sending message...
Message sent.
Message sent
Queue sent
Waiting for response
Receiving response...
HTTP-Status: 200 (200)
Response received.
Disconnecting from server...
Disconnected.
Response received
HBCI: 0010 - Nachricht entgegengenommen. (M)
HBCI: 0030 - Auftrag empfangen - Sicherheitsfreigabe erforderlich (S)
Dialog not aborted, assuming PIN is ok
3:2019/09/26 22-04-45:aqhbci(7587):provider_tan.c:  171: Challenge
contains no optical data
3:2019/09/26 22-04-45:aqhbci(7587):tanmechanism.c:  206: Using TAN
mechanism "text"
===== TAN Entry =====
Please enter the TAN for user xxxxxxxxxxx at Triodos Bank Deutschland.
The server provided the following challenge:
SMS wurde an Handy um 22:04:45 versandt. Bitte geben Sie diese TAN ein.
Input:
Encoding queue
Sending message
Connecting to server...
Resolving hostname "hbci11.fiducia.de" ...
IP address is "195.200.35.18"
Connecting to "hbci11.fiducia.de"
Connected to "hbci11.fiducia.de"
Using GnuTLS default ciphers.
TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
5:2019/09/26 22-06-43:aqbanking(7587):siotlsext.c:  157: Found matching
certificate "6F:29:06:28:FB:6F:B1:7F:05:62:BC:AE:76:49:49:D3" with same
status
5:2019/09/26 22-06-43:aqbanking(7587):siotlsext.c:  163: Automatically
accepting certificate [6F:29:06:28:FB:6F:B1:7F:05:62:BC:AE:76:49:49:D3]
Connected.
Sending message...
Message sent.
Message sent
Waiting for response
Receiving response...
HTTP-Status: 200 (200)
Response received.
Disconnecting from server...
Disconnected.
Response received
HBCI: 0010 - Nachricht entgegengenommen. (M)
HBCI: 0020 - *SEPA-Sammelüberweisung erfolgreich (S)
HBCI: 0900 - *TAN entwertet. (S)
TAN "xxxxxx" has been used, please strike it out.
Dialog not aborted, assuming PIN is ok
Closing dialog
Encoding queue
Sending message
Connecting to server...
Resolving hostname "hbci11.fiducia.de" ...
IP address is "195.200.35.18"
Connecting to "hbci11.fiducia.de"
Connected to "hbci11.fiducia.de"
Using GnuTLS default ciphers.
TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
5:2019/09/26 22-06-45:aqbanking(7587):siotlsext.c:  157: Found matching
certificate "6F:29:06:28:FB:6F:B1:7F:05:62:BC:AE:76:49:49:D3" with same
status
5:2019/09/26 22-06-45:aqbanking(7587):siotlsext.c:  163: Automatically
accepting certificate [6F:29:06:28:FB:6F:B1:7F:05:62:BC:AE:76:49:49:D3]
Connected.
Sending message...
Message sent.
Message sent
Queue sent
Waiting for response
Receiving response...
HTTP-Status: 200 (200)
Response received.
Disconnecting from server...
Disconnected.
Response received
HBCI: 0010 - Nachricht entgegengenommen. (M)
HBCI: 0100 - Dialog beendet. (M)
Dialog not aborted, assuming PIN is ok
AqHBCI finished.
Unlocking customer "4474"
==========================================================================

Und der folgende Fehler besteht auch weiterhin:

> 2) Wenn eine Umsatzauskunft leer ist, wirft gnucash die Fehlermeldung
> "Error on executing job. Status: rejected (5)" bei folgendem aqbanking log:
> ========================================================================
> AqBanking v5.99.27.0beta
> Sending jobs to the bank(s)
> Sorting commands by account
> Sorting commands by provider
> Send commands to providers
> Send commands to provider "AQHBCI"
> Locking users
> Locking customer "xxxx"
> Executing HBCI jobs
> AqHBCI started
> Selecting iTAN mode "mobile TAN" (942)
> Encoding queue
> Sending message
> Connecting to server...
> Resolving hostname "hbci11.fiducia.de" ...
> IP address is "195.200.35.18"
> Connecting to "hbci11.fiducia.de"
> Connected to "hbci11.fiducia.de"
> Using GnuTLS default ciphers.
> TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
> Connected.
> Sending message...
> Message sent.
> Message sent
> Queue sent
> Waiting for response
> Receiving response...
> HTTP-Status: 200 (200)
> Response received.
> Disconnecting from server...
> Disconnected.
> Response received
> HBCI: 3060 - Bitte beachten Sie die enthaltenen Warnungen/Hinweise. (M)
> HBCI: 3920 - Zugelassene TAN-Verfahren für den Benutzer (S)
> HBCI: 0901 - *PIN gültig. (S)
> HBCI: 0020 - *Dialoginitialisierung erfolgreich (S)
> HBCI: 3076 - Starke Kundenauthentifizierung nicht notwendig. (S)
> Dialog not aborted, assuming PIN is ok
> Encoding queue
> Sending message
> Connecting to server...
> Resolving hostname "hbci11.fiducia.de" ...
> IP address is "195.200.35.18"
> Connecting to "hbci11.fiducia.de"
> Connected to "hbci11.fiducia.de"
> Using GnuTLS default ciphers.
> TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
> Connected.
> Sending message...
> Message sent.
> Message sent
> Queue sent
> Waiting for response
> Receiving response...
> HTTP-Status: 200 (200)
> Response received.
> Disconnecting from server...
> Disconnected.
> Response received
> HBCI: 3060 - Bitte beachten Sie die enthaltenen Warnungen/Hinweise. (M)
> HBCI: 3010 - *Es liegen keine Umsätze im abgefragten Zeitraum vor (S)
> HBCI: 0901 - *PIN gültig. (S)
> HBCI: 3920 - Zugelassene TAN-Verfahren für den Benutzer (S)
> HBCI: 3076 - Starke Kundenauthentifizierung nicht notwendig. (S)
> Dialog not aborted, assuming PIN is ok
> Closing dialog
> Encoding queue
> Sending message
> Connecting to server...
> Resolving hostname "hbci11.fiducia.de" ...
> IP address is "195.200.35.18"
> Connecting to "hbci11.fiducia.de"
> Connected to "hbci11.fiducia.de"
> Using GnuTLS default ciphers.
> TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
> Connected.
> Sending message...
> Message sent.
> Message sent
> Queue sent
> Waiting for response
> Receiving response...
> HTTP-Status: 200 (200)
> Response received.
> Disconnecting from server...
> Disconnected.
> Response received
> HBCI: 0010 - Nachricht entgegengenommen. (M)
> HBCI: 0100 - Dialog beendet. (M)
> Dialog not aborted, assuming PIN is ok
> Reading file...
> Reading SWIFT document 1
> Parsing SWIFT data
> Importing SWIFT data
> Swift document successfully imported
> Reading SWIFT document 2
> Parsing SWIFT data
> Data imported, transforming to transactions
> AqHBCI finished.
> Unlocking customer "xxxx"
> ========================================================================

Vielen Dank und viele Grüße,
Heiko

-- 
eMails verschlüsseln mit PGP - privacy is your right!
Mein PGP-Key zur Verifizierung: http://pgp.mit.edu

-------------- nächster Teil --------------
Ein Dateianhang mit Binärdaten wurde abgetrennt...
Dateiname   : signature.asc
Dateityp    : application/pgp-signature
Dateigröße  : 163 bytes
Beschreibung: OpenPGP digital signature
URL         : <http://lists.gnucash.org/pipermail/gnucash-de/attachments/20190926/4c830fb9/attachment-0001.sig>