cancel
Showing results for 
Search instead for 
Did you mean: 

ERROR => DlLoadLib()==DLENOACCESS - dlopen("libjvm.so") FAILED

former_member196171
Participant
0 Kudos

Hi Experts,

I have just upgraded kernel to (7.21_EXT)  with SOL MAN 7.1 now Java does not come up , getting following ewrror in dev_bootstrap

[Thr 01] Wed Dec  5 11:40:39 2012

[Thr 01] *** ERROR => DlLoadLib()==DLENOACCESS - dlopen("libjvm.so") FAILED

  "Could not load module .

System error: No such file or directory"  (errno=2,No such file or directory) [dlux_mt.c    445]

[Thr 01] *** ERROR => Can't load VM shared library (libjvm.so) (rc=-2) [jhvmxx_mt.c  1692]

[Thr 01] **********************************************************************

[Thr 01] *** ERROR => Cannot load the Java VM shared library.

[Thr 01] *** Please see SAP Note 943602 , section 'Java VM shared library issues'

[Thr 01] *** for additional information and trouble shooting.

[Thr 01] **********************************************************************

[Thr 01] *** ERROR => JLaunchUnixLoadDLL: Cannot load DLL for Java VM [jlnchxx_mt.c 1013]

[Thr 01] *** ERROR => Cannot preload DLL for Java VM [jlnchxx_mt.c 392]

thanks ,

Al Mamun

Accepted Solutions (0)

Answers (9)

Answers (9)

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello

Here is the error:

Thr 01] *** ERROR => DlLoadLib()==DLENOACCESS - dlopen("libjvm.so") FAILED

  "Could not load module .

System error: No such file or directory"  (errno=2,No such file or directory) [dlux_mt.c    445]

[Thr 01] *** ERROR => Can't load VM shared library (libjvm.so) (rc=-2) [jhvmxx_mt.c  1692]

You need to check the path for Java for the sidadm user

Also check in the config tool the value for Java Home

Regarding the password error for SAPJSF

It looks like you have an ABAP system as the UME data source

So you need to unlock the user from the ABAP side.

http://help.sap.com/saphelp_bw30b/helpdata/en/d6/225f3ce4dd3370e10000000a114084/content.htm

Cheers

RB

former_member188073
Active Participant
0 Kudos

Hi,

I agree to posts suggesting checks on user locks and passwords.

Regards

Former Member
0 Kudos

[Thr 01] Wed Dec  5 11:40:39 2012

[Thr 01] *** ERROR => DlLoadLib()==DLENOACCESS - dlopen("libjvm.so") FAILED

  "Could not load module .

System error: No such file or directory"  (errno=2,No such file or directory)

To me it looks like the kernel patching wasn't succesful. Check that the dynamic library aka DLL exists and that file permissions are correctly set.

Former Member
0 Kudos

Hi

Please post std_server0.log file

thanks

former_member185239
Active Contributor
0 Kudos

Hi Mamun,

Things to do.

1. logon to the useradmin of java http://<hostname>:<port>/useradmin

2. Look for the user SAPJSF and unlock the user.

Now in the ume page , you will find configuration tab click on it.

Over there , choose the ABAP system and performed the connection test.

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Hi,

Are you using a R/3 system as the user store? If so, pls check if the user SAPJSF is locked in the R/3 system.

former_member196171
Participant
0 Kudos

Hi Joe , 

Thanks for your reply,

I looked in to the logs again and found that dispatcher is staring only the server0 is failing with the error as below, please help

ine.core.service630.container.ServiceRunner#Plain###Service UT started. (41 ms).#
#1.5^H#BAC5F72FD404001E0000000100AA00400004D0322D68DF1B#1354813835632#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#####-0##SAPEngine_System_Thread[impl:5]_20##0#0#Info#1#com.sap.eng
ine.core.service630.container.ServiceRunner#Plain###Service tc~lm~nzdm~crrsrv started. (1512 ms).#
#1.5^H#BAC5F72FD404001F0000000C00AA00400004D0322DD9273A#1354813842990#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#####-0##SAPEngine_System_Thread[impl:5]_67##0#0#Error#1#com.sap.en
gine.core.service630.container.ServiceRunner#Plain###Service com.sap.security.core.ume.service error. Nested exception is: com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic
"Start of UME Service Failed". Technical details: Password logon no longer possible - too many failed attempts
        at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:407)
        at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
        at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
        at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
        at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
        at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83)
        at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:109)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Password logon no longer possible - too many failed attempts
        at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
        at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
        at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:447)
        at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
        at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
        at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
        at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
        at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:288)
        ... 6 more

#
#1.5^H#BAC5F72FD404001F0000000E00AA00400004D0322DD9345C#1354813842994#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#####-0##SAPEngine_System_Thread[impl:5]_67##0#0#Error#1#/System/Se
rver#Plain###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
#1.5^H#BAC5F72FD404001F0000001000AA00400004D0322DD95499#1354813843001#/System/Server/Critical##com.sap.engine.core.Framework#####-0##SAPEngine_System_Thread[impl:5]_67##0#0#Fatal#1#com.sap.engine.core.Framew
ork#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#

Asha_Pillai
Active Participant
0 Kudos

Hello,

Please delete instance.properties.vmprop from ...j2ee/cluster. They will be created again the next time you start the engine. Check which directory LD_LIBRARY_PATH is point to?

Please check the note 830578 and make sure the ennvironment vaiables are

correctly set.

Regards,

Asha

Former Member
0 Kudos

Well. let's see:

SAP wrote:

[Thr 01] *** Please see SAP Note 943602 , section 'Java VM shared library issues'

[Thr 01] *** for additional information and trouble shooting.