cancel
Showing results for 
Search instead for 
Did you mean: 

Agentry: client crash after login with wrong Password

Former Member
0 Kudos

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é

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

The Solution is to catch the LoginBlockedException and throw instead a PasswordInvalidException.

Answers (2)

Answers (2)

sravanthi_polu
Contributor
0 Kudos

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

Former Member
0 Kudos

The Server Starts every time with admin privileges. And the client crashs at the first time when the user will connect with wrong password.

We raise an oss ticket now and posed the answer here if we get one.

Andre

Former Member
0 Kudos

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