Unable to log into solution manager portal

[former_member465457]

Hi All,

I am unable to login to solman portal.

My authentication details failed and account got locked.

I tried to enable the emergency user sap* using the config tool following the instructions in the thread

http://help.sap.com/saphelp_nw04s/helpdata/en/3a/4a0640d7b28f5ce10000000a155106/frameset.htm

Even then I am unable to login with sap* and newly configured password.

Please help me in resolving this issue.

[Former Member · Accepted solution]

Naveen,

Try doing the following

1> shutdown server0 with jcmon and deactivate sap*

2> start server0 in console mode by executing the following

goto /usr/sap/SID/dvebmgs<nr>/work look for dev_jcontrol in this file look for entries

-> arg[17] = -DSAPPROFILE=/usr/sap/PR1/SYS/profile/PR1_DVEBMGS05_TSILPRD

-> arg[18] = -DFRFC_FALLBACK=ON

-> arg[19] = -DFRFC_FALLBACK_HOST=localhost

-> lib path = LIBPATH=/usr/java14_64/jre/bin:/usr/java14_64/jre/bin/classic:/usr/sap/PR1/DVEBMGS05/exe:/usr/sap/PR1/DVEBMGS05/exe:/usr/sap/PR1/DVEBMGS05/exe:/usr/sap/PR1/SYS/exe/run:/oracle/client/10x_64/instantclient:/usr/java14_64/jre/bin/sovvm:/usr/lib:/usr/sap/PR1/DVEBMGS05/j2ee/os_libs:/usr/sap/PR1/DVEBMGS05/exe:/usr/sap/PR1/DVEBMGS05/exe:/usr/sap/PR1/DVEBMGS05/exe:/usr/lib:/lib:/usr/sap/PR1/SYS/exe/run:/oracle/client/10x_64/instantclient

-> exe path = PATH=/usr/java14_64/bin:/usr/sap/PR1/DVEBMGS05/j2ee/os_libs:/oracle/PR1/102_64/bin:/usr/java14_6/bin:/home/pr1adm:/usr/sap/PR1/SYS/exe/run:/usr/bin:/etc:/usr/sbin:/usr/ucb:/home/pr1adm/bin:/usr/bin/X11:/sbin:.

logon as sidadm and

Set the env variable PATH and LIBPATH with the values mentioned above.

>jlaunch -file=/usr/sap/PR1/DVEBMGS05/j2ee/cluster/instance.properties -nodeName=<NODEID> pf=/usr/sap/<SID>/SYS/profile/<inst_profile -traceFile=jcontrol.trc -startMode=console

Wait until the server has started. (The prompt '>' appears.)

add user

create_user emergency

password emergency <password>

group_user emergency administrators

For more information about starting console mode refer note 669848

now restart the server in normal mode try logging in with emergency user.

Regards

Anil Verma B

[former_member465457]

Hi Anil,

I was able to login to the portal.

Thanks a lot.

Anil, I was able to configure the sld.

But I was not knowing how to add a sap system s60 to the sld so that i can monitor it through solman.

Can you please guide me on this

Thanks,

Krishna.

[Former Member]

Login to your S60 system and execute RZ70 and maintain SLD Bridge data. i.e solman host name and gateway service.

logon to S60 sld using url http://<hostname>:port/sld

click on administration button and under that click on data suppliers.

Now enter the SLD url of your solution manager

eg: http://solman:50000/sld

User id should be SLDDSUSER and its password.

You can change this users password in SU01 and then maintain the same in transaction SLDAPICUST.

again the same procedure has to be repeated for solman. logon to solution manager sld and maintain the S60 url in datasuppliers.

After this goto RZ70 in S60 system and activate the setting and execute.

Login to visual Admin in S60 system goto the server node --> services --> SLD data supplier.

On the runtime tab page in HTTP settings make sure SLDDSUSER and correct password is given

There should be a icon on the top looking like a thunderbolt with a arrow mark. Clicking this should transfer SLD data to your solman.

Now both your S60 abap and java system should reflect in solution manager SLD.

Regards

Anil Verma B

[Former Member]

If you have queries apart from login problems to portal please post a new thread.

Regards

Anil Verma B

[former_member465457]

Hi Anil,

The problem is that we dont remember any username ,password.

I am not able log into client 001 also. Is there any solution to this

Thanks,

Krishna.

[Former Member]

Hi Naveen,

You can delete the sap* user from the database level and it will be created again with default password PASS.

execute the following query :

delete from USR02 where BNAME='001' and MANDT='SAP*'

a pre-requisite to this is the parameter login/no_automatic_user_sapstar is set to 0

[Former Member]

Do the following:

Logon to the client to which you remember ID n password. Goto RZ10 transaction open instance profile and add the parameter

login/no_automatic_user_sapstar with value '0'

Restart the system.

goto command prompt and execute

sqlplus "/as sysdba"

and in sql execute the following

DELETE FROM SAPSR3.USR02 WHERE MANDT='001' AND BNAME='SAP*'
commit;

now you can logon to sap* with password 'pass'.

Regards

Anil Verma B

[former_member465457]

Hi Anil,

Thank you very much for the detailed information.

This time I am able to start the server in console mode successfully but I am facing the following problem while adding the emergency user.

How do i change ume/abap user management connector to write mode. Please help me.

Thank a lot,

Naveen.

>add user

>create_user emergency

unable to register new user.

Could not create user emergency: The UME/ABAP user management connector is set t

o read-only mode and therefore rejects the creation request for user EMERGENCY

[Former Member]

Logon to 001 client.

execute PFCG and open role SAP_BC_JSF_COMMUNICATION. If there is no profile generated yet generate it in PFCG.

Assign this role to user SAPJSF.

Regards

Anil Verma B

[former_member465457]

Hi Anil,

I tried what all u said, now I am able to execute the jlaunch command .

But server is not starting in console mode throwing the below exception.

Please help me from here.

Thanks,

Naveen

[Thread[Thread-1,5,main]] Fatal: Cannot attach to the Message Serv

er. Can't open port [3900] on host [vmeisolman/10.8.28.44] (Connection refused:

connect).

C:\usr\sap\SM4\DVEBMGS01\j2ee\os_libs>jlaunch -file=C:\usr\sap\SM4\DVEBMGS01\j2e

e\cluster\instance.properties -nodeName=ID14645450 pf=C:\usr\sap\SM4\SYS\profile

\SM4_DVEBMGS01_vmeisolman -traceFile=jcontrol.trc -startMode=console

Reserved 1610612736 (0x60000000) bytes before loading DLLs.

CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addI

viewResources

CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBased

SecurityConnector getApplicationDomain

CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator g

enerateStub

CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS

CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem

startServices

CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConf

igurationHandler downloadFile

CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHiera

rchicalContext lookup

SAP J2EE Engine Version 7.00 PatchLevel is starting...

Loading: LogManager ... 7813 ms.

Loading: PoolManager ... 0 ms.

Loading: ApplicationThreadManager ... 15391 ms.

Loading: ThreadManager ... 515 ms.

Loading: IpVerificationManager ... 47 ms.

Loading: ClassLoaderManager ... 15 ms.

Loading: ClusterManager ... Jul 23, 2009 3:27:45 AM ...anagerImpl.init(java.uti

l.Properties) [Thread[Thread-1,5,main]] Fatal: Cannot attach to the Message Serv

er. Can't open port [3900] on host [vmeisolman/10.8.28.44] (Connection refused:

connect).

[Former Member]

Try the following

Restart the system entire application server. This should start the all the services, if you are on windows check if everything is in green status in SAPMMC.

Now goto command prompt by executing the CMD and change to directory

<Drive>\usr\sap\SID\SYS\profile and execute

jcmon pf=SM4_DVEBMGS01_vmeisolman

The following screen should appear

============================================================
JControl Monitor Program - Main Menu
============================================================
0  : exit
------------------------------------------------------------
10 : Cluster Administration Menu
------------------------------------------------------------
20 : Local Administration Menu
------------------------------------------------------------
30 : Shared Memory Menu (Solid Rock, experimental)
------------------------------------------------------------
command =>

enter 20

|Idx|Name               |PID     |State                |Error|Restart|
|---|-------------------|--------|---------------------|-----|-------|
|  0|dispatcher         |    3036|Running              |    0|yes    |
|  1|server0            |    5012|Running              |    0|yes    |
|  2|SDM                |     424|Running              |    0|yes    |
------------------------------------------------------------


============================================================
JControl Monitor Program - Administration Menu  (Local)
Instance : JC_server1_ID1_11
============================================================
0  : exit
1  : Refresh list
2  : Shutdown instance
3  : Enable process
4  : Disable process
5  : Restart process
6  : Enable bootstrapping on restart
7  : Disable bootstrapping on restart
8  : Enable debugging
9  : Disable debugging
10 : Dump stacktrace
11 : Process list
12 : Port list
13 : Activate debug session
14 : Deactivate debug session
15 : Increment trace level
16 : Decrement trace level
17 : Enable process restart
18 : Disable process restart
19 : Restart instance
------------------------------------------------------------
40 : Enable bootstrapping for all processes with specified process type
41 : Enable bootstrapping for all processes excluding specified process type
------------------------------------------------------------
99 : Extended process list on/off
------------------------------------------------------------
command =>

Enter option 4

Process Index :

Enter the index no of server0 in my case its 1

Do you want to disable the process [1/server0] ? (y/n):

Enter 'Y' this should shutdown your Server0 in a couple of mins.

Now exit from JCMON and switch to directory D:\usr\sap\SM4\DVEBMGS01\j2ee\cluster\

Open the instance.properties file in notepad and look for the entry

This corresponds to the ID of server0 make a note of the following enter the same while executing jlaunch


now switch to directory C:\usr\sap\SM4\DVEBMGS01\j2ee\os_libs
and execute 

SET PATH=<values in dev_jcontrol>

SET LIBPATH=<values in dev_jcontrol

now execute

jlaunch -file=C:\usr\sap\SM4\DVEBMGS01\j2ee\cluster\instance.properties -nodeName=ID14645450 pf=C:\usr\sap\SM\SYS\profile\SM4_DVEBMGS01_vmeisolman -traceFile=jcontrol.trc -startMode=console

If the you are still getting the same message check the file dev_ms in work direcory and post the same.

Regards

Anil Verma B

[Former Member]

Previous post did not come up properly

Try the following

Restart the application server

This should start the all the services, if you are on windows check if everything is in green status in SAPMMC

Now goto command prompt by executing the CMD and change to directory \usr\sap\SID\SYS\profile and execute

jcmon pf=SM4_DVEBMGS01_vmeisolman

============================================================
JControl Monitor Program - Main Menu
============================================================
0  : exit
------------------------------------------------------------
10 : Cluster Administration Menu
------------------------------------------------------------
20 : Local Administration Menu
------------------------------------------------------------
30 : Shared Memory Menu (Solid Rock, experimental)
------------------------------------------------------------
command =>

enter 20

|Idx|Name               |PID     |State                |Error|Restart|
|---|-------------------|--------|---------------------|-----|-------|
|  0|dispatcher         |    3036|Running              |    0|yes    |
|  1|server0            |    5012|Running              |    0|yes    |
|  2|SDM                |     424|Running              |    0|yes    |
------------------------------------------------------------


============================================================
JControl Monitor Program - Administration Menu  (Local)
Instance : JC_server1_ID1_11
============================================================
0  : exit
1  : Refresh list
2  : Shutdown instance
3  : Enable process
4  : Disable process
5  : Restart process
6  : Enable bootstrapping on restart
7  : Disable bootstrapping on restart
8  : Enable debugging
9  : Disable debugging
10 : Dump stacktrace
11 : Process list
12 : Port list
13 : Activate debug session
14 : Deactivate debug session
15 : Increment trace level
16 : Decrement trace level
17 : Enable process restart
18 : Disable process restart
19 : Restart instance
------------------------------------------------------------
40 : Enable bootstrapping for all processes with specified process type
41 : Enable bootstrapping for all processes excluding specified process type
------------------------------------------------------------
99 : Extended process list on/off
------------------------------------------------------------
command =>

Enter option 4

Process Index :

Enter the index no of server0 in my case its 1

Do you want to disable the process [1/server0] ? (y/n):

Enter 'Y' this should shutdown your Server0 in a couple of mins.

Now exit from JCMON and switch to directory D:\usr\sap\SM4\DVEBMGS01\j2ee\cluster\ Open the instance.properties file in notepad and look for the entry

 

This corresponds to the ID of server0 make a note of the entry. The same should be used while executing jlaunch

switch to directory C:\usr\sap\SM4\DVEBMGS01\j2ee\os_libs and execute

SET PATH= <values in dev_jcontro>

SET LIBPATH= <values in dev_jcontro>

execute the following now

jlaunch -file=C:\usr\sap\SM4\DVEBMGS01\j2ee\cluster\instance.properties -nodeName=ID14645450 pf=C:\usr\sap\SM\SYS\profil\SM4_DVEBMGS01_vmeisolman -traceFile=jcontrol.trc -startMode=console

This should start in console mode

If you are still getting the same error check the file dev_ms in work directory and post the same.

Regards

Anil Verma B

[Former Member]

My post is not comming in the proper format. Have sent the same post to your email.

Regards

Anil Verma B

[former_member465457]

Hi All,

In reference to the above problem ,regarding the error I am facing while trying to start the solman server in console mode

I am pasting the trace files.

I also wanted to let you know that I am find the below erro in dev_bootstrap

JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\SM4\DVEBMGS01\exe\jvmx.jar

The error that is showing int the jcontrol.trc is

node name : ID14645450

pid : 6748

system name : SM4

system nr. : 01

started at : Mon Jul 13 02:56:19 2009

arguments :

arg[00] : jlaunch

arg[01] : pf=C:\usr\sap\SM4\SYS\profile\SM4_DVEBMGS01_vmeisolman

[Thr 7168] Mon Jul 13 02:56:19 2009

[Thr 7168] *** ERROR => Can't open property file [C:\usr\sap\SM4\VEBMGS01\j2ee\cluster\instance.properties] [jstartxx.c 725]

[Thr 7168] *** ERROR => Can't open property file [C:\usr\sap\SM4\VEBMGS01\j2ee\cluster\instance.properties] [jstartxx.c 1952]

[Thr 7168] *** ERROR => JStartupReadArgumentsEx: can't enumerate nodes [C:\usr\sap\SM4\VEBMGS01\j2ee\cluster\instance.properties] (rc = -1) [jstartxx.c 524]

[Thr 7168] JLaunchCloseProgram: good bye (exitcode = -3)

Please help me in resolving the issue.

Thanks,

Naveen

[Former Member]

Hello Naveen

Please check the following

1> Make sure you are logged into <SID>adm

2> make sure your node name corresponds to the server0. You can find the appropriate node from either the instance.properties or from configtool.

3> execute the the jlaunch command from the directory //usr/sap/SID/instance-name/j2ee/os_libs/

4> make sure only your server node is down not the dispatcher.

Try these and let me know.

Regards

Anil Verma B

[Former Member]

Also make sure the env variable LIBPATHand PATH are set using the set command, the values should be taken from dev_jcontrol trace file as given in my previous thread.

[former_member465457]

Hi Anil,

I am facing the following error when I tried to start the server in console mode,

Please let me know whats wrong with this.

Thanks,

Naveen.

jlaunch -file=C:\usr\sap\SM4\DVEBMGS01\j2ee\os_libs>jlaunch -file=C:\usr\sap\SM4\VEBMGS01\j2

\cluster\instance.properties -nodeName=ID14645450 pf=C:\usr\sap\SM4\SYS\profil

SM4_SCS00_vmeisolman -traceFile=jcontrol.trc -startMode=console

Reserved 1610612736 (0x60000000) bytes before loading DLLs.

Critical Error

Can't read program properties

-> Internal program error (rc = -1)

Usage : jlaunch [-options] <arg0> <arg1> ... <argn>

Launch the specified java program

options : [-file=<property file>] (default=jlaunch.properties)

[-nodename=<node name>] (default=jlaunch)

[-app=<application name>] Standalone application

-> <property file> = <application name>.properties

-> <SAP profile> = <application name>.pfl

[pf=<SAP profile>] (default=jlaunch.pfl)

[-parent=<pid of the parent process>] (default=0)

[-tracefile=<filename>] (default=dev_jlaunch)

[former_member465457]

b

[sunny_pahuja2]

Hi Naveen,

Could you please paste trace file from server0 logs here ?

Also, after changing sap* password from configtool have you restarted the system ?

Thanks

Sunny

[former_member465457]

Hi Sunny,

I am pasting the default trace.

Its too big so , I am just pasting the parts of it.

Thanks a lot,

Naveen.

<!LOGHEADER[START]/>

<!HELP[Manual modification of the header may cause parsing problem!]/>

<!LOGGINGVERSION[1.5.3.7185 - 630]/>

<!NAME[./log/defaultTrace.trc]/>

<!PATTERN[defaultTrace.trc]/>

<!FORMATTER[com.sap.tc.logging.ListFormatter]/>

<!ENCODING[Cp1252]/>

<!FILESET[3, 20, 10485760]/>

<!PREVIOUSFILE[defaultTrace.2.trc]/>

<!NEXTFILE[defaultTrace.4.trc]/>

<!LOGHEADER[END]/>

#1.5#005056A621260085000500A500000E38000464A4601C0FE9#1236557056656#com.sap.sql.jdbc.NativeConnectionFactory##com.sap.sql.jdbc.NativeConnectionFactory######584f1790092211dea747005056a62126#Timeout Service Internal Thread##0#0#Error#1#/System/Database/sql/jdbc#Java#com.sap.sql_0002##SQL error occurred on connection jdbc:oracle:thin:@vmeisolman:1527:SM4: code=1,034, state="72000", message="ORA-01034: ORACLE not available

ORA-27101: shared memory realm does not exist

".

[EXCEPTION]

#6#1034#72000#ORA-01034: ORACLE not available

ORA-27101: shared memory realm does not exist

#jdbc:oracle:thin:@vmeisolman:1527:SM4#<null>#java.sql.SQLException: ORA-01034: ORACLE not available

ORA-27101: shared memory realm does not exist

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:283)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:278)

at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOsesskey(T4CTTIoauthenticate.java:293)

at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:357)

at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:420)

at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)

at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)

at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)

at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)

at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)

at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:302)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.getConnectionInternal(DBConnectionPool.java:193)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.getConnection(DBConnectionPool.java:135)

at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:100)

at com.sap.engine.core.configuration.impl.cache.CachedConfiguration.<init>(CachedConfiguration.java:62)

at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:848)

at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:882)

at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:748)

at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:694)

at com.sap.sldserv.DataCollector.getLastCollectTimeIntervalDatabase(DataCollector.java:761)

at com.sap.sldserv.DataCollector.checkTimeBasedRunDatabase(DataCollector.java:745)

at com.sap.sldserv.DataCollector.checkTimeBasedRun(DataCollector.java:736)

at com.sap.sldserv.DataCollector.check(DataCollector.java:364)

at com.sap.engine.services.timeout.TimeoutNode.check(TimeoutNode.java:97)

at com.sap.engine.services.timeout.TimeoutManagerImpl.multiThreadRun(TimeoutManagerImpl.java:489)

at com.sap.engine.services.timeout.TimeoutManagerRunner.run(TimeoutManagerRunner.java:20)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

#1.5#005056A62126004A000000000000114800046E4077F43983#1247123076265#com.sap.engine.services.iiop.server##com.sap.engine.services.iiop.server.PICurrentImpl#######SAPEngine_System_Thread[impl:5]_86##0#0#Error##Plain###

java.lang.NullPointerException

at com.sap.engine.services.iiop.internal.interceptors.PICurrentImpl.getThreadSlotTable(PICurrentImpl.java:85)

at com.sap.engine.services.iiop.internal.giop.ClientRequest.<init>(ClientRequest.java:66)

at com.sap.engine.services.iiop.server.portable.Delegate_1_2$ClientRequest_1_2.<init>(Delegate_1_2.java:41)

at com.sap.engine.services.iiop.server.portable.Delegate_1_2.createRequestLocal(Delegate_1_2.java:32)

at com.sap.engine.services.iiop.server.portable.Delegate.createRequest(Delegate.java:370)

at com.sap.engine.services.iiop.server.portable.Delegate.request(Delegate.java:170)

at org.omg.CORBA.portable.ObjectImpl._request(ObjectImpl.java:431)

at com.adobe.service._FontManagerStub.getAdobeServerFontDirectory(_FontManagerStub.java:18)

at com.adobe.document.XMLFormService.getFontDirectories(Unknown Source)

at com.adobe.document.XMLFormService.onStartService(Unknown Source)

at com.adobe.service.Service.start(Service.java:387)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)

#

#1.5#005056A62126007000000004000012D400046E55731AE932#1247213189218#com.sap.security.core.sapmimp#sap.com/com.sap.security.core.admin#com.sap.security.core.sapmimp.[cf=com.sap.security.core.sapmimp.logon.SAPMLogonLogic][md=doLogon][cl=10120]#J2EE_GUEST#2####9287b4206d2811dec2c2005056a62126#SAPEngine_Application_Thread[impl:3]_15##0#0#Error##Java###doLogon failed

[EXCEPTION]

#1#com.sap.security.core.logon.imp.UMELoginException: USER_AUTH_FAILED

at com.sap.security.core.logon.imp.SAPJ2EEAuthenticator.logon(SAPJ2EEAuthenticator.java:924)

at com.sap.security.core.logonadmin.ServletAccessToLogic.logon(ServletAccessToLogic.java:206)

at com.sap.security.core.sapmimp.logon.SAPMLogonLogic.doLogon(SAPMLogonLogic.java:974)

at com.sap.security.core.sapmimp.logon.SAPMLogonLogic.uidPasswordLogon(SAPMLogonLogic.java:630)

at com.sap.security.core.sapmimp.logon.SAPMLogonLogic.executeRequest(SAPMLogonLogic.java:156)

at com.sap.security.core.sapmimp.logon.SAPMLogonServlet.doPost(SAPMLogonServlet.java:59)

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

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

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

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

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

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

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

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

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

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

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)