Bug #790
closedProblems
0%
Description
Hello alltogether,
after your nice app worked for me very good for years, I have now problems and I dont't know the reason. Maybe my hardware?
I see during trying to login in different sites errors like "TCToken konnte nicht empfangen werden" and "Bad request, keine Redirect-Adresse für eine Verbindung im Fehlerfall verfügbar."
I work with a Lenovo X1 ThinkPad (Win 10, 64Bit) with integrated NFC-reader, which worked fine in the past.
I enabled DEBUG mode and recognized the following exception:
org.openecard.common.ifd.scio.SCIOException: Failed to transmit control command to the terminal 'Microsoft IFD 0'.
at org.openecard.scio.PCSCCard.transmitControlCommand(PCSCCard.java:110)
at org.openecard.ifd.scio.wrapper.SingleThreadChannel.lambda$transmitControlCommand$2(SingleThreadChannel.java:288)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: javax.smartcardio.CardException: transmitControlCommand() failed
at sun.security.smartcardio.CardImpl.transmitControlCommand(Unknown Source)
at org.openecard.scio.PCSCCard.transmitControlCommand(PCSCCard.java:107)
... 5 common frames omitted
Caused by: sun.security.smartcardio.PCSCException: Unknown error 0x32
at sun.security.smartcardio.PCSC.SCardControl(Native Method)
... 7 common frames omitted
For me this looks like an access problem to the reader hardware but in the update history of my machine is no new nfc-driver install detectable.
The full log-file is attached.
Has someone an idea?
Best wishes for the new year
Jürgen
Files
| log.txt (42.3 KB) log.txt | full log file | ||
| richclient_info.log (43.7 KB) richclient_info.log | |||
| Icon.jpg (1.36 KB) Icon.jpg | |||
| Open eCard App.jpg (40.4 KB) Open eCard App.jpg | |||
| Open-eCard-App-1.4.0.exe (57.5 MB) Open-eCard-App-1.4.0.exe | build of the release candidate 5 of the coming version 1.4 | ||
| Open-eCard-Screenshot.jpg (55.9 KB) Open-eCard-Screenshot.jpg |
Updated by Tobias Assmann over 4 years ago
- File Open-eCard-App-1.4.0.exe added
Attached you can find a build of the release candidate 5 of the coming version 1.4.
Please check if the problem you encounter persits with this version and let us know.
Thank you very much.
Updated by Jürgen Womser-Schütz over 4 years ago
- File richclient_info.log richclient_info.log added
No, version 1.4 behaviour isn't better but worse :-)
The same exception and in addition the API is missing completely for me. No dialog for finishing, configuration ...
The new log-file is attached.
Updated by Jürgen Womser-Schütz over 4 years ago
Is it possible to get acess to the software repository (for reading)?
Updated by Tobias Wich over 4 years ago
The source is available here: https://github.com/ecsec/open-ecard
After checking the logs again I don't think the issue is related to the card at all. These Control command errors are normal with basic terminals. Ususally one would get an empty feature list, but some vendors are too lazy to add this capability to the hardware/firmware of the terminal.
The actual cause is that the socket is closed on the client while data is trying to be sent to the server.
Caused by: java.net.SocketException: Software caused connection abort: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
I have never seen something like this to happen, but from searching the web, it looks like this is something happening in the network. Maybe it is possible to see more details in a packet sniffer. However the actual question is why this suddenly starts to occur. From what you say, something must have changed on the system in a way that this now happens. This doesn't rule out a bug entirely, but I would first try to check if there is any firewall setting or antivirus software (notoriously known for checking network traffic) messing with the local socket.
In the log from version 1.4, I don't see that an authentication with the Deutsche Rente Server is started at all.
Updated by Jürgen Womser-Schütz over 4 years ago
The problem is solved now. Puuuh!
With your suggestion that this is a software and no hardware problem, I tried out different possibilities and found the reason. It was a small network-traffic visualisation tool "networx" that I am using for many years. Depending on an configuration switch of this tool (named "Lokalen LAN Verkehr ignorieren") open-eCard works fine or not. I switched this in the past without being aware of the consequences.
Thanks for your help, Jürgen
PS: For me your new version 1.4 has the problem of a completely missing API.
Updated by Tobias Wich over 4 years ago
Glad to hear that it works now.
PS: For me your new version 1.4 has the problem of a completely missing API.
What do you mean by "a completely missing API"?
Updated by Jürgen Womser-Schütz over 4 years ago
- File Icon.jpg Icon.jpg added
- File Open eCard App.jpg Open eCard App.jpg added
I mean: after starting the new version 1.4 and double clicking the icon (see attached file "icon.jpg") no user interface is shown (see attached file "Open eCard App.jpg").
Updated by Tobias Assmann over 4 years ago
Thanks for the attached Screenshots.
If the file 'Open eCard App.jpg' shows, what is missing after clicking the icon (no need to double click), please do the following:- delete the log file of the app (to be found in the users home directory under .openecard/logs)
- start the app, click the icon
- attach here the new log file (richclient_info.log)
Thank you.
Updated by Jürgen Womser-Schütz over 4 years ago
I did this already. See the attached log-file of post #5
Updated by Tobias Assmann over 4 years ago
Could you please tell us about your screen setup? Do you have multiple screens? Do you have any scaled screen?
Updated by Jürgen Womser-Schütz over 4 years ago
I have a Windows 10 Laptop (Lenovo X1 Carbon 5. Gen) and I use the Windows 10 feature of multiple desktop screens - nothing special.
Updated by Tobias Assmann about 4 years ago
Could you please tell us your setting regarding the scaling of the screen (i.e. 100%, 125%, 150%, ...)? Thank you.
Updated by Jürgen Womser-Schütz about 4 years ago
200%, as recommended by Windows
Updated by Jürgen Womser-Schütz about 4 years ago
... maybe this is also interesting for you: my screen has 2560x1440 pixel
Updated by Tobias Assmann about 4 years ago
- File Open-eCard-App-1.4.0.exe Open-eCard-App-1.4.0.exe added
Attached you find an update, could you please check if this solves your issue? Thank you!
Updated by Tobias Assmann about 4 years ago
- File deleted (
Open-eCard-App-1.4.0.exe)
Updated by Jürgen Womser-Schütz about 4 years ago
It works!
For me, the difference to 1.3 is, that a new reader is detected (see screen shot)
Best regards Jürgen
Updated by Tobias Assmann about 4 years ago
- Status changed from Feedback to Solved
Thank you very much for your feedback, I will mark this issue as solved now.
Please update to the final version 1.4 after it is released, which should happen quite soon.