Skip to main content

What can I do if login to the web client fails?

  • Updated

Error messages when logging on to the web client can provide information about the causes. Depending on the error code and message, several solutions are possible.

 

Error Error message Solution  
No login mask No login mask is shown. The browser window remains blank. Check your internet connection. If your Internet connection is working, the web server may be down: How to resolve such outages is explained under this link for product installations running in your own infrastructure and under this link for product installations running in the BOC Cloud (SaaS).  
Wrong or missing password The user could not be logged on. An incorrect username or password was entered. You can find solutions for incorrect or missing login credentials here.  
Web Admin Toolkit (ADONIS 16, ADOIT 17 and ADOGRC 13 or higher)
Logon failed The logon attempt failed because the user is not assigned to a repository. Please contact your administrator.

Solution 1: Make sure that at least one repository is assigned to the user in the Web Administration Toolkit.

Solution 2: If you are using a "Starter" edition of a BOC product, please ensure that all current invoices related to your subscription have been paid.
Logon failed The user could not be logged on, because no scenarios are assigned to him. Make sure that at least one system role is assigned to the user in the Web Administration Toolkit.

Administration Toolkit (pre ADONIS 16, ADOIT 17 and ADOGRC 13)

Logon failed The logon attempt failed because the user is not assigned to a repository. Please contact your administrator.

Solution 1: Make sure that at least one repository is assigned to the user in the administration toolkit. You can change the lock symbol (🚫) to a green tick (✔️) by double-clicking on the repository, and thus carry out the assignment.

Solution 2: If you are using a "Starter" edition of a BOC product, please ensure that all current invoices related to your subscription have been paid.

 The screenshot shows where in the ATK the symbol must be changed.
Logon failed The user could not be logged on, because no scenarios are assigned to him. Make sure that at least one system role is assigned to the user in the Administration Toolkit. The screenshot shows where in the ATK system the roles need to be set.

For other login problems, contact BOC technical support.

Related articles