org.jasig.portal.PortalException

AggregatedUserLayoutStore::getAggregatedLayout(): No INIT_NODE_ID in UP_USER_LAYOUT_AGGR for 16 and LAYOUT_ID 1 at org.jasig.portal.layout.AggregatedUserLayoutStore.getAggregatedLayout (AggregatedUserLayoutStore.java:1881)

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web19

  • via Apereo Issues by David Grimwood, 1 year ago
    AggregatedUserLayoutStore::getAggregatedLayout(): No INIT_NODE_ID in UP_USER_LAYOUT_AGGR for 16 and LAYOUT_ID 1 at org.jasig.portal.layout.AggregatedUserLayoutStore.getAggregatedLayout (AggregatedUserLayoutStore.java:1881)
  • via Apereo Issues by Robin John West, 1 year ago
    null [based on exception: AggregatedUserLayoutStore::getAggregatedLayout(): No INIT_NODE_ID in UP_USER_LAYOUT_AGGR for 16 and LAYOUT_ID 1] org.jasig.portal.PortalException: AggregatedUserLayoutStore::getAggregatedLayout(): No INIT_NODE_ID in
  • via Apereo Issues by Brad Johnson, 1 year ago
    null [based on exception: AggregatedUserLayoutStore::getAggregatedLayout(): No INIT_NODE_ID in UP_USER_LAYOUT_AGGR for 17 and LAYOUT_ ID 1]
  • Stack trace

    • org.jasig.portal.PortalException: AggregatedUserLayoutStore::getAggregatedLayout(): No INIT_NODE_ID in UP_USER_LAYOUT_AGGR for 16 and LAYOUT_ID 1 at org.jasig.portal.layout.AggregatedUserLayoutStore.getAggregatedLayout (AggregatedUserLayoutStore.java:1881) at org.jasig.portal.layout.AggregatedLayoutManager.loadUserLayout(AggregatedLayoutManager.java:1081) at org.jasig.portal.layout.channels.CFragmentManager.analyzeParameters(CFragmentManager.java:242) at org.jasig.portal.layout.channels.CFragmentManager.renderXML(CFragmentManager.java:276) at org.jasig.portal.ChannelRenderer$Worker.run(ChannelRenderer.java:528) at org.jasig.portal.utils.threading.Worker.run(Worker.java:88)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.