Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Admin is unable to Impersonate User with NoSuchGroupException

Written By

Aaron Wang

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How to articles!

While we make every effort to ensure this Knowledge Base is accurate,it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • The Admin is unable to impersonate certain user with the following error:
NoSuchGroupException: No Group exists with the key {companyId=20155, classNameId=20005, classPK=20555}

Environment

  • Liferay Portal 6.2

Resolution

One possible reason for this error is because the user's group record is missing in thegroup_ table in the database (data corruption). For the root cause of the data corruption issue, you may need to further check the database log to see when and why the record was missing.

Besides that, the missing record could be added back by verifying users. Refer to the following steps:

  1. Add the above properties into portal-ext.properties and restart the server. 
verify.processes=com.liferay.portal.verify.VerifyUser
verify.frequency=-1 

     2. The following INFO will be printed in the log:

06:56:07,164 INFO [localhost-startStop-1][VerifyProcess:65] Verifying com.liferay.portal.verify.VerifyUser

     3. Then Admin user should be able to impersonate this user.

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?