on 12-08-2014 11:01 AM
Hello,
we use a Java Backend Connection to a SAP Backend with the Agentry Clients (Agentry_6.1.4.179_ClientWin32, Agentry_6.1.4.54024_ClientWinCE) and the TestEnviroment (Agentry_6.1.4.179_Test_Environment) withe the Agnetry Server 6.1.4.
In all Client if we enter a wrong Password to connect to the backend we get the backend error (wrong password) popped up on the Client as message box and after this the Client crashs.
The Agentry Server throw this exception "new LoginBlockedException(_loginErrorMessage);". If we catch the exception from the login method the client got only a Java RFC Error (no more the Message that the reason was a wrong password) but the clients do not crash.
Here a some screenshots:
What can we do? We wan't miss the error text on the client but the crash is also unacceptable for our clients.
Thanks,
André
The Solution is to catch the LoginBlockedException and throw instead a PasswordInvalidException.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Start the server with administrative privileges, and try to connect. Agentry Client based on the version may crash if we try to connect with wrong password multiple times.If the issues still exists as suggested raise an oss ticket.
Thanks & Regards,
Sravanthi Polu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello André,
well I would recommend to open an OSS ticket on this component: MOB-SYC-SAP. A few things are implemented in the client "player" application itself, which is a "closed environment" / blackbox. Only the product dev have access to the codeing of the client apps and the tools to debug them.
Frankly here we do not have chances to intervene.
Kind regards,
Mike
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.