Legacy Knowledge Base
Published Sep. 10, 2025

No portlet bag for {id=0, companyId=0, portletId=xxxxx, roles=, active=true} reported during import process

Written By

Emma Liu

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

  • When publishing from staging to live, or importing lar into a new site, the following error is reported:
11:09:48,470 ERROR [liferay/background_task-1][StagingServiceHttp:153] com.liferay.portal.kernel.exception.SystemException: java.lang.IllegalStateException: No portlet bag for {id=0, companyId=0, portlet
Id=xxxxx, roles=, active=true}
com.liferay.portal.kernel.exception.SystemException: java.lang.IllegalStateException: No portlet bag for {id=0, companyId=0, portletId=1_WAR_opensocialportlet, roles=, active=true}

Environment

  • Liferay Portal 6.2

Resolution

  • The error normally happens when the reported portlet bag is missing in memory on the target site (live site or the site that the user would like to import the lar into). For example, if the reported portlet is undeployed on the target site, the portlet bag will be removed from memory.
  • Please check if the reported portlet is undeployed on the target site.
    • If it is undeployed, please deploy it back.
    • If it is not undeployed, try redeploying it. 
Did this article resolve your issue ?

Legacy Knowledge Base