Error shows "You reached maximum login sessions. Logout earlier sessions and try again". Why?

• Related Articles

• Why do I get the error "You reached maximum login sessions. Logout earlier sessions and try again"?

  At present, there is no feature to track the user sessions. Alternatively, if such errors are encountered, modify the LOGIN_COUNT field from the ADMIN_MST USER table in admin db to release the sessions. As a quick workaround, we can also increase the ...

• Error in the Log file while rendering Login Page

  We have added a column 'CHARSET_TYPE' in the table 'ADMIN_LANGUAGE' and updated the column with value 'ISO-8859-'

• After using the Save As KPI option, should I logout and login so that the saved KPI becomes visible?

  There is no need to logout and login after using the Save As KPI option. You can just navigate from one module to another module. This will refresh the KPI browser. Alternatively, you can also click on the same module to refresh the KPI browser. The ...

• Data Security page under the Privileges tab, does not load properly and shows error. Why?

  Ensure that the foreign key of the problematic hierarchy has an equivalent match with one of the level column names. The dimension in the combo-box loads according to that. This you can navigate to Administrator->Metadata Management and verify

• KPI shows error when drilled down from one level to another. Why?

  It can be due to the incorrect data type of the measures used in the KPI. This needs to be verified at the metadata management module.