cancel
Showing results for 
Search instead for 
Did you mean: 

LSO 200 Error: "SessionException: LoginContext is no R3logincontext"

0 Kudos

Hi,

We are delivering eLearning with EP6, R/3 4.7, and LSO 200. For users running courses, any attempt to restart an intentionally interrupted course, is met with following error in the logs and a generic message for the user - 'Contact you administrator'.

When we check the application log we get the following response:

#1.5#000BCD9BDF3400620000008700000EF4000438D5BF27A161#1188390592889#/Applications/sap_lso/application#sap.com/com.sap.hcm.ls.webapps#com.sap.hcm.ls.lms.servlets.control.Mediator#Guest#2####8aec0ba0562b11dc8cc7000bcd9bdf34#SAPEngine_Application_Thread[impl:3]_37##0#0#Warning#1#com.sap.hcm.ls.lms.servlets.control.Mediator#Java###[session id=(J2EE4916500)ID0537983650DB00842569642546704349End,locale=en] :Exception occured! #1#com.sap.hcm.ls.lms.servlets.exceptions.LoginException: Login failed!

[CAUSE: LoginContext is no R3LoginContext: null]

[CAUSE: com.sap.hcm.ls.shared.datamodel.session.SessionException: LoginContext is no R3LoginContext: null]#

#1.5#000BCD9BDF3400620000008800000EF4000438D5BF27A74E#1188390592889#/Applications/sap_lso/application#sap.com/com.sap.hcm.ls.webapps#com.sap.hcm.ls.lms.servlets.control.Mediator#Guest#2####8aec0ba0562b11dc8cc7000bcd9bdf34#SAPEngine_Application_Thread[impl:3]_37##0#0#Warning#1#com.sap.hcm.ls.lms.servlets.control.Mediator#Plain###[session id=(J2EE4916500)ID0537983650DB00842569642546704349End,locale=en] :EXCEPTION:#

#1.5#000BCD9BDF3400620000008900000EF4000438D5BF27A7CC#1188390592889#/Applications/sap_lso/application#sap.com/com.sap.hcm.ls.webapps#com.sap.hcm.ls.lms.servlets.control.Mediator#Guest#2####8aec0ba0562b11dc8cc7000bcd9bdf34#SAPEngine_Application_Thread[impl:3]_37##0#0#Warning#1#com.sap.hcm.ls.lms.servlets.control.Mediator#Plain###com.sap.hcm.ls.lms.servlets.exceptions.LoginException: Login failed!

at com.sap.hcm.ls.lms.servlets.control.SessionContextUpdater.makeSessionContext(SessionContextUpdater.java:82)

at com.sap.hcm.ls.lms.servlets.control.SessionContextUpdater.update(SessionContextUpdater.java:47)

at com.sap.hcm.ls.lms.servlets.control.EventDispatcher.updateModels(EventDispatcher.java:116)

at com.sap.hcm.ls.lms.servlets.control.RequestProcessor.doProcess(RequestProcessor.java:98)

at com.sap.hcm.ls.lms.servlets.control.RequestProcessor.process(RequestProcessor.java:81)

at com.sap.hcm.ls.lms.servlets.control.Mediator.processRequest(Mediator.java:221)

at com.sap.hcm.ls.lms.servlets.control.Mediator.doGet(Mediator.java:150)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

CAUSED BY: com.sap.hcm.ls.shared.datamodel.session.SessionException: LoginContext is no R3LoginContext: null

at com.sap.hcm.ls.shared.datamodel.session.r3.R3SessionProvider.getSessionContext(R3SessionProvider.java:49)

at com.sap.hcm.ls.lms.servlets.control.SessionContextUpdater.makeSessionContext(SessionContextUpdater.java:72)

We felt this must be related to the communication between browser and Portal and R/3. We dumped the temp. Internet files, and were then able to launch the courses, but this has not proved a consistent solution.

Can anyone assist with this message and this behaviour?

Thanks.

/regards,

Conor.

Accepted Solutions (0)

Answers (3)

Answers (3)

0 Kudos

Hi,

We have uncovered the issue that was causing this problem and its intermittent nature.

We have four servers in our solution.Two of the servers contain the application layer and are running in Active-Active mode,

while the persistance layer containing db and message server are in Active-Passive mode.

We are running multiple J2EE nodes in the application layer as:

Application Server 1:

- Instance 00: Nodes 0 and 1

Application Server 2:

- Instance 02: Nodes 0 and 1

Our problem stems from the use of the command https://<server id>:port/lms/mediator/config to update the

LMS configuration. We ran this command once for each application server, but it needs to target each node specifically:

Do this with the follwoing command:

https://<server>:port/lms/mediator/config;saplb_*=(J2EE4916500)4916551

( J2EE <instance number> 00 )<Instance Number> Node Number – starting from 50.

/regards,

Conor.

0 Kudos

Hi Waseem,

Thank you for the response. The RFC connection is fine, as we are able to play courses without error. However, if a user quits a course and minutes later attempts

to restart the course, they receive a generic message 'contact the system administrator', which translates to the above java error in the application.log.

/regards,

Conor.

former_member214498
Contributor
0 Kudos

Hi

It seems to me that the portal is not communicating properly with R/3 backend system.

go to IMG->Training and Events Management->SAP Learning Solution->Learning Portal->LMS Configuration-> Set RFC connection.

Check this one. Hopefully it will resolve the problem

Please award points if helpful.

Regards

Waseem Imran

Message was edited by:

Set RFC Connection

In this step, you set up the connection between the back-end system (that is, the one you are working in now) and the front-end SAP Web Application Server (as of Basis 6.10 ). R/3 systems can set up trust relationships with one another. If a calling R/3 System is known to the called system as a Trusted System, no password is required. The calling R/3 System must be registered as a Trusted System in the system it calls. The system called is designated the Trusting System.

Note

You can find detailed information on Trusted Systems in the SAP Library under Basis Services / Communications Interfaces (BC-SRV) -> Remote Communications (BC-SRV-RC) -> RFC Programming in ABAP -> Trusted System: Trust Relationships Between R/3.

Activities

You must set up a trust relationship between the back-end system and the front-end SAP Web Application Server (Trusted System). This is essentially one RFC connection per system.

Note

Ensure that the RFC destination in the SAP Web Application Server is assigned the name SAP_LSO_BACKEND. It is of no significance whether this is a logical destination that references an R/3 connection or an R/3 connection with this name.

Waseem Imran