Forums de discussion

Liferay 6.2 Can not export the Global site - NoSuchGroupException

thumbnail
William Gosse, modifié il y a 7 années.

Liferay 6.2 Can not export the Global site - NoSuchGroupException

Liferay Master Publications: 533 Date d'inscription: 04/07/10 Publications récentes
I'm not able to export the web content from my Global site because the export page is not rendering completely.

I'm seeing the following exception being added each time I try to do an export:
15:33:49,535 ERROR [http-hal-pptla-d01/10.5.75.167:8443-4][IncludeTag:129] Current URL /group/control_panel/manage?p_p_id=86&p_p_lifecycle=0&p_p_state=pop_up&doAsGroupId=20195&refererPlid=20185&controlPanelCategory=sites&_86_struts_action=%2Fportlet_configuration%2Fexport_import&_86_redirect=%2Fgroup%2Fcontrol_panel%2Fmanage%3Fp_p_auth%3DMZWLlsvF%26p_p_id%3D15%26p_p_lifecycle%3D0%26p_p_state%3Dmaximized%26p_p_mode%3Dview%26doAsGroupId%3D20195%26refererPlid%3D20185%26controlPanelCategory%3Dsites%26_15_redirect%3D%252Fgroup%252Fcontrol_panel%253FrefererPlid%253D20185%2526p_p_id%253D134&_86_returnToFullPageURL=%2Fgroup%2Fcontrol_panel%2Fmanage%3Fp_p_auth%3DMZWLlsvF%26p_p_id%3D15%26p_p_lifecycle%3D0%26p_p_state%3Dmaximized%26p_p_mode%3Dview%26doAsGroupId%3D20195%26refererPlid%3D20185%26controlPanelCategory%3Dsites%26_15_redirect%3D%252Fgroup%252Fcontrol_panel%253FrefererPlid%253D20185%2526p_p_id%253D134&_86_portletResource=15&_86_&yui_patched_v3_11_0_1_1463412825340_1327=1463412829344 generates exception: java.lang.IllegalStateException: com.liferay.portal.NoSuchGroupException: No Group exists with the key {companyId=20155, classNameId=20191, classPK=56801}
com.liferay.portal.NoSuchGroupException: No Group exists with the key {companyId=20155, classNameId=20191, classPK=56801}
at com.liferay.portal.service.persistence.GroupPersistenceImpl.findByC_C_C(GroupPersistenceImpl.java:5227)
at com.liferay.portal.service.impl.GroupLocalService

Pièces jointes:

thumbnail
William Gosse, modifié il y a 7 années.

RE: Can not export the Global site

Liferay Master Publications: 533 Date d'inscription: 04/07/10 Publications récentes
I'm seeing the NoSuchGroupException affecting other parts of Liferay such as deleting sites and users. When I try to delete an inactive user i get and INV001 displayed in the control panel and the following in my log file:

13:46:14,879 ERROR [http-hal-pptla-d01/10.5.75.167:8443-4][render_portlet_jsp:132] null
com.liferay.portal.NoSuchGroupException: No Group exists with the key {companyId=20155, classNameId=20191, classPK=56801}
at com.liferay.portal.service.persistence.GroupPersistenceImpl.findByC_C_C(GroupPersistenceImpl.java:5227)
at com.liferay.portal.service.impl.GroupLocalServiceImpl.getUserPersonalSiteGroup(GroupLocalServiceImpl.java:1962)

Pièces jointes:

thumbnail
Jorge Díaz, modifié il y a 7 années.

RE: Liferay 6.2 Can not export the Global site - NoSuchGroupException

Liferay Master Publications: 753 Date d'inscription: 09/01/14 Publications récentes
Hi William,

Check classNameId=20191 value in classname_ database table ¿What classname is related to it?

Do you have the full stacktrace of first export error?
thumbnail
William Gosse, modifié il y a 7 années.

RE: Liferay 6.2 Can not export the Global site - NoSuchGroupException

Liferay Master Publications: 533 Date d'inscription: 04/07/10 Publications récentes
Thanks for your response.

There's one entry for 20191 in the classname_ table with a value: com.liferay.portal.model.UserPersonalSite

Here's the stack trace:
16:52:48,289 ERROR [http-hal-pptla-d01/10.5.75.167:8443-5][IncludeTag:129] Current URL /group/control_panel/manage?p_p_id=86&p_p_lifecycle=0&p_p_state=pop_up&doAsGroupId=20195&refererPlid=20185&controlPanelCategory=sites&_86_struts_action=%2Fportlet_configuration%2Fexport_import&_86_redirect=%2Fgroup%2Fcontrol_panel%2Fmanage%3Fp_p_auth%3Dqg2vT2iy%26p_p_id%3D15%26p_p_lifecycle%3D0%26p_p_state%3Dmaximized%26p_p_mode%3Dview%26doAsGroupId%3D20195%26refererPlid%3D20185%26controlPanelCategory%3Dsites%26_15_redirect%3D%252Fgroup%252Fcontrol_panel%253FrefererPlid%253D20185%2526p_p_id%253D134&_86_returnToFullPageURL=%2Fgroup%2Fcontrol_panel%2Fmanage%3Fp_p_auth%3Dqg2vT2iy%26p_p_id%3D15%26p_p_lifecycle%3D0%26p_p_state%3Dmaximized%26p_p_mode%3Dview%26doAsGroupId%3D20195%26refererPlid%3D20185%26controlPanelCategory%3Dsites%26_15_redirect%3D%252Fgroup%252Fcontrol_panel%253FrefererPlid%253D20185%2526p_p_id%253D134&_86_portletResource=15&_86_&yui_patched_v3_11_0_1_1463417563641_1329=1463417567894 generates exception: java.lang.IllegalStateException: com.liferay.portal.NoSuchGroupException: No Group exists with the key {companyId=20155, classNameId=20191, classPK=56801}
com.liferay.portal.NoSuchGroupException: No Group exists with the key {companyId=20155, classNameId=20191, classPK=56801}
at com.liferay.portal.service.persistence.GroupPersistenceImpl.findByC_C_C(GroupPersistenceImpl.java:5227)
at com.liferay.portal.service.impl.GroupLocalServiceImpl.getUserPersonalSiteGroup(GroupLocalServiceImpl.java:1962)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:115)
at com.liferay.portal.spring.transaction.DefaultTransactionExecutor.execute(DefaultTransactionExecutor.java:62)
at com.liferay.portal.spring.transaction.TransactionInterceptor.invoke(TransactionInterceptor.java:51)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:56)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:56)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:56)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:56)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:56)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:56)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:56)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)

Just some additional observations:
1. I’m assuming, based on the exception, that Liferay is looking for an entry in the group_ with the values companyId=20155, classNameId=20191, classPK=56801. No such entry exists.
2. The only entry in the group_ table that close to this is companyId=20155, classNameId=20191, classPK=20159.
3. classPK=56801 matches the default user’s id in the user_ in the user table and classPK=20159 has no match in the user_.
4. classNameId=20191 does have a match in the classname_ table with the value com.liferay.portal.model.UserPersonalSite.

We could try changing the record in the group_ table to have the companyId=20155, classNameId=20191, classPK=56801 key that Liferay’s looking for. I really hat messing with Liferay’s data base this way.
thumbnail
William Gosse, modifié il y a 7 années.

RE: Liferay 6.2 Can not export the Global site - NoSuchGroupException (Réponse)

Liferay Master Publications: 533 Date d'inscription: 04/07/10 Publications récentes
Yahoo! Ok I tried my idea about changing the record in the group_ table to have the companyId=20155, classNameId=20191, classPK=56801 key that Liferay’s looking for and now everything seems to be working, exporting, deleting…

Again I really hate messing with Liferay’s data base this way but if it saves us from having to reinstall so be it.