cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to login in Remote Gui

Former Member
0 Kudos

Dear Team,

During update of JSPM from RemoteGui.bat.Its hang. Now I am unable to login in RemoteGui.bat.

When i am giving password.it give messege "Cannot Log in . There are already active session id 0 / An administrator logged in via Gui

If I check J2EE Process server 0 Developer Trace it give below messege.All user is not locked

Thr 5932] Thu Sep 23 17:27:14 2010

[Thr 5932] JLaunchIExitJava: exit hook is called (rc = -11113)

[Thr 5932] **********************************************************************

      • ERROR => The Java VM terminated with a non-zero exit code.

      • Please see SAP Note 943602 , section 'J2EE Engine exit codes'

      • for additional information and trouble shooting.

**********************************************************************

[Thr 5932] JLaunchCloseProgram: good bye (exitcode = -11113)

If I check log in \usr\sap\R3P\DVEBMGS00\j2ee\cluster\server0\log\system

#1.5#00016C88A23900100000000000000BF8000490EBF612422C#1285243026937#/System/Server##com.sap.engine.services.httpserver#######SAPEngine_System_Thread[impl:5]_55##0#0#Warning#1#com.sap.engine.services.httpserver#Plain###User <system thread>, IP address

The default (JDK) implementation will be used for writing compressed data in the GZIP file format!#

#1.5#00016C88A23900110000000000000BF8000490EBF61B895E#1285243027546#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_8##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service naming started. (1109 ms).#

#1.5#00016C88A23900120000000000000BF8000490EBF6250469#1285243028171#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_93##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service appclient started. (359 ms).#

#1.5#00016C88A23900130000000000000BF8000490EBF6260EB5#1285243028234#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_40##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service javamail started. (469 ms).#

#1.5#00016C88A23900140000000000000BF8000490EBF62623E0#1285243028234#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_52##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service ts started. (453 ms).#

#1.5#00016C88A23900100000000100000BF8000490EBF6270AA7#1285243028296#/System/Server##com.sap.engine.services.httpserver#######SAPEngine_System_Thread[impl:5]_55##0#0#Warning#1#com.sap.engine.services.httpserver#Plain###User <system thread>, IP address

Sub configuration with name 5339250 not found! HTTP aliases on virtual host default could not be initialized.#

#1.5#00016C88A23900150000000000000BF8000490EBF62AE0EC#1285243028546#/System/Server##com.sap.engine.services.licensing.LicensingFrame.bindToNaming(expectNamingAvailable)#######SAPEngine_System_Thread[impl:5]_29##0#0#Info#1#com.sap.engine.services.licensing.LicensingFrame#Java### successfully bound in JNDI#1#Licensing service# #1.5#00016C88A23900150000000100000BF8000490EBF62AE274#1285243028546#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_29##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service licensing started. (265 ms).# #1.5#00016C88A23900160000000000000BF8000490EBF62B3DB2#1285243028578#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_24##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service jmsconnector started. (782 ms).# #1.5#00016C88A23900100000000200000BF8000490EBF62D1C26#1285243028703#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_55##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service http started. (2219 ms).# #1.5#00016C88A23900170000000000000BF8000490EBF6300D78#1285243028890#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_42##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service failover started. (1094 ms).# #1.5#00016C88A23900020000000100000BF8000490EBF630185F#1285243028890#/System/Server##com.sap.engine.services.licensing.LicensingFrame.bindToNaming(expectNamingAvailable)#######SAPEngine_System_Thread[impl:5]_21##0#0#Info#1#com.sap.engine.services.licensing.LicensingFrame#Java### successfully bound in JNDI#1#Licensing service#

#1.5#00016C88A23900180000000000000BF8000490EBF637E77C#1285243029406#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_9##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service connector started. (1266 ms).#

#1.5#00016C88A23900190000000000000BF8000490EBF63A99F2#1285243029578#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_16##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service webservices started. (2000 ms).#

#1.5#00016C88A239001A0000000000000BF8000490EBF63AF45E#1285243029609#/System/Server##com.sap.engine.services.configuration.ConfigurationApplicationFrame.startIndependent()#######SAPEngine_System_Thread[impl:5]_87##0#0#Info#1#com.sap.engine.services.configuration.ConfigurationApplicationFrame#Java### started successfully#1#configuration-service#

#1.5#00016C88A239001A0000000100000BF8000490EBF63AF5CC#1285243029609#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_87##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service configuration started. (16 ms).#

#1.5#00016C88A239001B0000000000000BF8000490EBF63DC48E#1285243029796#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_66##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service iiop started. (1266 ms).#

#1.5#00016C88A239001C0000000200000BF8000490EBF67F8C1B#1285243034093#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl#######SAPEngine_System_Thread[impl:5]_91##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'cafruntimeconnectivity~impl Service' application started successfully.#

#1.5#00016C88A239001C0000000300000BF8000490EBF67FAB71#1285243034109#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl#######SAPEngine_System_Thread[impl:5]_91##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'monitor Service' application started successfully.#

#1.5#00016C88A239001C0000000400000BF8000490EBF67FC675#1285243034109#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl#######SAPEngine_System_Thread[impl:5]_91##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'MigrationService Service' application started successfully.#

#1.5#00016C88A239001C0000000500000BF8000490EBF67FE119#1285243034125#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl#######SAPEngine_System_Thread[impl:5]_91##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'failover Service' application started successfully.#

#1.5#00016C88A239001C0000000600000BF8000490EBF682F504#1285243034328#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl#######SAPEngine_System_Thread[impl:5]_91##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sl.ut.infoprovider Library' application started successfully.#

#1.5#00016C88A239001C0000000700000BF8000490EBF6830F83#1285243034328#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl#######SAPEngine_System_Thread[impl:5]_91##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'bimmrdb Library' application started successfully.#

#1.5#00016C88A239001C0000000800000BF8000490EBF68325F4#1285243034328#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl#######SAPEngine_System_Thread[impl:5]_91##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'tcTechSrvXML_DAS_Connector Library' application started successfully.#

#1.5#00016C88A239001C0000000900000BF8000490EBF68329D2#1285243034343#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_91##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service dbpool started. (4734 ms).#

#1.5#00016C88A239001D0000000000000BF8000490EBF6834E50#1285243034343#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_56##0#0#Error#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service com.sap.security.core.ume.service error. Nested exception is: java.lang.NoClassDefFoundError: com/sap/security/core/util/config/IUMConfiguration

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Class.java:219)

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

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#00016C88A239001D0000000200000BF8000490EBF6835363#1285243034343#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_56##0#0#Error#1#/System/Server#Plain###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#

#1.5#00016C88A239001D0000000400000BF8000490EBF6835543#1285243034343#/System/Server##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_56##0#0#Fatal#1#com.sap.engine.core.Framework#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

error shows Service com.sap.security.core.ume.service. Check your UME configration. is your server configured for external UME or local?

Former Member
0 Kudos

Dear

I have checked in Global Server Configuration in Services in com.sap.security.core.ume.service ,All is by Default that come with installation. I have not changed any thing.

Then Witch parameter should I check in com.sap.security.core.ume.service .

Regards

Former Member
0 Kudos

Dear

I have check the log of Std_Server0.out.

service com.sap.security.core.ume.service ================= ERROR =================

Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

java.lang.NoClassDefFoundError: com/sap/security/core/util/config/IUMConfiguration

#at java.lang.Class.forName0(Native Method)

#at java.lang.Class.forName(Class.java:219)

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

#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)

java.lang.NoClassDefFoundError: com/sap/security/core/util/config/IUMConfiguration

#at java.lang.Class.forName0(Native Method)

#at java.lang.Class.forName(Class.java:219)

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

#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)

[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Sep 28, 2010 12:06:07... com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_47] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.secur

Where to search error log . What should be problem,?

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

JLaunchIExitJava: exit hook is called (rc = -11113)

If u have searched with the above term in SDN, u could have come across lots of threads with the status "answered".

Check whether ur UME database is up and running.

Make sure that the users JAVA_ADMIN, SAPJSF, JAVA_GUEST or not locked

Ensure that u have maintained correct password for the administrator in secstore in configtoo. If u have changed the password of the J2EE_ADMIN user in UME database u need to maintain the same in secstore in the configtool as per the link provided by Eric.

Hope this fixes ur issue.

Regards,

Varadharajan M

Former Member
0 Kudos

Dear

After restart I can login in RemoteGui .I have udated JSPM .But J2EE Process is not able to start. Its show Exitcode -11113

I have to check the log

\usr\sap\R3P\DVEBMGS00\j2ee\cluster\server0\log\system\server.0.log

#1.5#00016C88A239001E0000000000000D2C000490FD4D1F177F#1285317501859#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_55##0#0#Error#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service com.sap.security.core.ume.service error. Nested exception is: java.lang.NoClassDefFoundError: com/sap/security/core/util/config/IUMConfiguration

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Class.java:219)

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

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#00016C88A239001E0000000200000D2C000490FD4D1F1E36#1285317501859#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_55##0#0#Error#1#/System/Server#Plain###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#

#1.5#00016C88A239001E0000000400000D2C000490FD4D1F205C#1285317501859#/System/Server##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_55##0#0#Fatal#1#com.sap.engine.core.Framework#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#

former_member204746
Active Contributor
0 Kudos

Read your errors:

The Java VM terminated with a non-zero exit code. *** Please see SAP Note 943602 , section 'J2EE Engine exit codes'

Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

From these info, it looks like your UME is stored in an ABAP system. So, make sure that ABAP system is up and running.

Also, read http://wiki.sdn.sap.com/wiki/display/EP/ResetlockedSDM+Password to make sure that every was setup properly. Pay special attention to the last section "Post processing (for Unix or Windows):".