Do you use Servoy’s authorisation methods or your own?
As in that method there must be that message, so one could look at the if()-code that causes it.
Sometimes, clearing the user’s java cache also works wonders when a single user has problems and other users not.
You also could ask the user to start his pc new, so that he has a clean starting environment.
We are using the Servoy Framework and ist authorisation methods.
After all, the user could login a while later without any Problems (and doing anything). So it seems to be a temporary problem. I just wondered, what the cause could be (as we allways have to explain it to our customers… )