Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

SI_LASTLOGONTIME does not exist in the object

We are encountering the above error in CMC when selecting sessions. We did not have this problem before. Once we corrected a SSO problem with SAP EP Integration, we got the above error whenever we want to look at the active sessions.

Does anyone have any ideas?

Thanks,

Garry

Here is the detailed information:

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

org.apache.jasper.JasperException: The property with ID SI_LASTLOGONTIME does not exist in the object

org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:512)

org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:395)

org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)

org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)

javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:346)

com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:152)

com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:107)

com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:245)

com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:137)

javax.faces.webapp.FacesServlet.service(FacesServlet.java:214)

root cause

com.crystaldecisions.sdk.exception.SDKRuntimeException$PropertyNotFound: The property with ID SI_LASTLOGONTIME does not exist in the object

com.crystaldecisions.sdk.plugin.desktop.connection.internal.Connection.getLastLogon(Connection.java:168)

com.businessobjects.cmc.app.sessions.ClusterSessionsBean.initConnectionCollection(ClusterSessionsBean.java:268)

com.businessobjects.cmc.app.sessions.ClusterSessionsBean.init(ClusterSessionsBean.java:132)

org.apache.jsp.App.Sessions.sessions_jsp._jspService(sessions_jsp.java:119)

org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)

javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)

org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)

org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)

javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:346)

com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:152)

com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:107)

com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:245)

com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:137)

javax.faces.webapp.FacesServlet.service(FacesServlet.java:214)

note The full stack trace of the root cause is available in the Apache Tomcat/5.5.20 logs.

Not what you were looking for? View more on this topic or Ask a question