SAP ME Loginmodule

[Former Member]

Hi

We have these errors in trace aprox every 30 mins. Any ideas why?

I cant believe that login module is missing since SAP ME would not work at all if it would.

#2.0 #2011 02 11 11:27:49:446#+0200#Error#com.sap.me.trace#

##sap.com/me_{ear#0025B3E1D6F40EB70000000000002B54#8615050000000004#sap.com/me}ear#com.sap.me.trace#Guest#0##195B365535C111E0A57500000083748A#195b365535c111e0a57500000083748a#195b365535c111e0a57500000083748a#0#Thread[HTTP Worker [@1156993647],5,Dedicated_Application_Thread]#Plain##

The Login ID is missing.#

#2.0 #2011 02 11 11:27:49:446#+0200#Error#com.sap.me.trace#

##sap.com/me_{ear#0025B3E1D6F40EB70000000100002B54#8615050000000004#sap.com/me}ear#com.sap.me.trace#Guest#0##195B365535C111E0A57500000083748A#195b365535c111e0a57500000083748a#195b365535c111e0a57500000083748a#0#Thread[HTTP Worker [@1156993647],5,Dedicated_Application_Thread]#Plain##

Login module exception. com.sap.me.frame.security.loginmodules.common.MfgLoginException: null#

Br,

Jennsen

[Former Member · Accepted solution]

Here is what happens: on opening ME, request is sent to Logon Screen (ME logon screen). At this point Login Module stack associated with application is invoked. Because this request does not contain any user information, login module fails.

After user submits credentials, login module can obtain required information and authenticate user.

In other words this error can be ignored. It appears only on Netweaver and occurs because of using our own login screen. As it was mentioned the whole login model is changed on 6.0.

[Former Member · Accepted solution]

Hi

Thanks for the clarifications. i will continue ignoring the error.

Br,

Jennsen

[sergiy_katerinich]

Jennsen,

We have been observing such kind of error message for a while but it is not about missing the login module. In fact, this "issue" does not seem harmful - at least no actual problem against ME functionality has been reported yet which could have been related to this message.

And this is not an issue replicable locally on demand.

Regards,

Sergiy

[Former Member]

Hi Sergiy,

The log message is easy to replicate. This happens every time I'm logging in to ME, before I logged in. Looks like during the first request the login module is checking for user name and cannot find it, because obviously it doesn't exist in the new session.

ME version is 5.2.4.7 and the login module configured as described in the installation guide.

Thanks

Ivan

[Former Member]

Hello,

This error message will disappear on SAP ME 6.0 as user authentication is handle on a different way.It shouldn't be of concern as Sergiy mentions it is not harmful.Regarding its cause,probably related to the new session as Ivan mentions,30 minutes is usually the default time out for sessions so it could be related as well.

Thanks,

German

Edited by: German Ramirez on Feb 11, 2011 4:30 PM