IBM Support

Unable to Initialize Framework Errors when using the Sametime System Console

Technote (troubleshooting)


When accessing the Sametime System Console, you see exceptions related to "unable to initialize framework." None of the portlets are accessible. When reviewing the Deployment Manager logs, you find that there are "ClassCastExceptions" that look similar to the following:

[4/11/12 14:42:43:285 EDT] 00000062 lifecycle E JSF1054: (Phase ID: RENDER_RESPONSE 6, View ID: /existingPlans.jsp) Exception thrown during phase execution: javax.faces.event.PhaseEvent[source=com.sun.faces.lifecycle.LifecycleImpl@79987998]
[4/11/12 14:42:43:285 EDT] 00000062 servlet E service SRVE0068E: Uncaught exception created in one of the service methods of the servlet STServerGA in application isclite. Exception created : javax.servlet.ServletException: javax.portlet.PortletException: /existingPlans.jsp(44,8) '#{empty deployment.planList}' java.lang.ClassCastException: incompatible with


This error is caused by the SSCConnector application being incorrectly mapped to the wrong application server. In the case pictured below, it is incorrectly mapped to the Deployment Manager (dmgr).

It is also possible that the "admin_host" virtual host has incorrect ports added to it when this module gets incorrectly mapped., The admin_host virtual host should only contain the deployment managers "wc_adminhost" and "wc_adminhostsecure" values (8700 and 8701 for an SSC deployment). Remove all other port mappings to prevent a potential routing conflict.

Resolving the problem

To diagnose and correct the problem, perform the following steps:

  1. Launch the console (ISC). In the navigator, select Applications -> Application Types -> WebSphere Enterprise Applications.
  2. Click the link for the SSCConnector.ear, and then click "Manage Modules."
  3. If the application is mapped to the dmgr (as shown above), place a check in the "Select" box and re-map it to the appropriate server or cluster by selecting that server or cluster from the "Clusters and servers" box above the table.
  4. Click "Apply,"then click "OK."
  5. Save/synchronize the changes.
  6. Restart the deployment manager to finalize the change.

After these steps, the System Console applications will be available

To validate the Virtual Host settings -

  1. Launch the console (ISC). In the navigator, select Environment -> Virtual Hosts
  2. Click the link for the "admin_host" and then click "Host Aliases"
  3. If there are ports in addition to the default 8700 and 8701, place a check in the box to the left of them and click the "Delete" button
  4. Save/synchronize the changes
  5. Restart all of the servers in the environment at the next opportunity for the change to take affect.


Document information

More support for: Lotus End of Support Products
IBM Sametime

Software version: 8.5.1,, 8.5.2,

Operating system(s): AIX, Linux, Solaris, Windows

Reference #: 1591426

Modified date: 16 April 2014

Translate this page: