When logging out, the error message "Failed to start the access agent." is displayed.

[MARUBUN SUPPORT]

Hi Team,

 

The following symptoms are occurring in our customer's environment:

 

In our customer's environment, when logging in with PAM Client and logging out within about a minute,  an error message dialog appears saying "Failed to start the access agent."

If our customers take the time to log out, this error dialog will not appear.

Additionally, if the customer logs in with the PAM client after receiving the error message, the PAM client will work.

 

We searched for a KB with the same error message and found the following KB. .

 

https://knowledge.broadcom.com/external/article?articleNumber=95080

 

The cause of this KB is that the JAVA applet was not loaded because there was an error in the custom signing certificate.

 

Did the problem occur for the same reason when our customer logged in and then immediately logged out?

Or did it appear because our customer logged out while the PAM Client was loading, which interrupted the JAVA applet loading?

 

 

Please let us know the cause of this error message and how to resolve it.

Thanks,

[Ralf Prigl]

Based on your observations, the answer to the question has to be "Yes". I have not observed it myself. But for multi-threaded applications it's not surprising that one task reports an error when getting interrupted during initialization. I wouldn't be concerned about any message I see when I exit a process before I let it complete initialization.

[Ralf Prigl]

"If our customers take the time to log out, this error dialog will not appear." answers the questions.

[MARUBUN SUPPORT]

Is it possible that this is because they logged out while the JAVA applet was loading and the loading was forcibly terminated?

This error message was displayed because it was not provided.