Jump to content

One customer getting error message when trying to access Employee portal


Adrian Simpkins

Recommended Posts

Hi All

I have one basic user who is having some issues logging into the portal. When she uses the link to logon no identity provider box, or SSO box appears - she just gets the below error message appear. 

We have cleared her cookies / cached data etc and restarted the whole desktop but still getting this error for her. Her account looks fine in Hornbill admin and was last accessed by her in February of this year. The computer is on the network with no obvious issues, and has connectivity to the internet, and we are able to remote to her desktop (I initially thought it may be some kind of network issue on the desktop).

Any ideas on anything else I should check here? I have asked her to try logging onto another desktop to see if the same issue occurs, and I am waiting on an update from this action.

Many thanks 

image.png.a13515455bc998b86cb4ad592b972d46.png

Link to comment
Share on other sites

Once you have confirmed if they are able to login on a different computer, you may want to also look at which browser they are using and that it is on the latest version.  Also have a look at what browser extensions they are running and maybe turn these off. Are you able to login to that user's computer and login to Hornbill as yourself?

If they are not able to login using a different computer, and other users have successfully logged in using that same computer, then we can look at their account in Hornbill to see if anything jumps out.  

  • Like 1
Link to comment
Share on other sites

Hi James, she was able to logon to Hornbill on another PC with no issues - when we remoted into her PC we were not able to logon either as no logon screen offered, just moved straight to the error.

I will ask our 2nd line team to check the PC and ensure all up to date, and no issues on browser. If we still see the issue after this check, I will raise a support ticket to get someone to check the system, however, I suspect it is a software build issue specific to that desktop

Many thanks as always

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...