cancel
Showing results for 
Search instead for 
Did you mean: 

Error: java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Exception

0 Kudos

hi, all,

Now I'm facing a problem that the J2ee Server node could not start.

The system is a double stack on SunOS while R3 runs fine.

Looking into std_server0.out, I found the following error msg:

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

tarted.

java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Exception

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

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

at com.sap.security.core.persistence.datasource.imp.r3persistence.R3JC

oProxy.getInstance(R3JCoProxy.java:81)

at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.

doInitRfc(R3PersistenceBase.java:684)

at com.sap.security.core.persistence.datasource.imp.R3Persistence.loca

lInitialization(R3Persistence.java:277)

at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.

init(R3PersistenceBase.java:424)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstan

ce.<init>(PrincipalDatabagFactoryInstance.java:357)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newIn

stance(PrincipalDatabagFactory.java:156)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getIn

stance(PrincipalDatabagFactory.java:109)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getIn

stance(PrincipalDatabagFactory.java:56)

at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFac

tory.java:270)

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMES

erviceFrame.java:295)

at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrame

Adaptor.java:31)

at com.sap.engine.core.service630.container.ServiceRunner.startApplica

tionServiceFrame(ServiceRunner.java:214)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceR

unner.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:79)

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

:105)

Could anyone pls tell me what is going on there and how shall I get the j2ee server

run again?

Any help is highly appreciated, thanks!

best regards,

Zhichao

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Looking at the error it seems some jar file is not in place.

Either its a class path issue or one of the essential jar file is missing.

try restarting the computer to begin with.

Alternatively try placing the jar file in the respective location

Answers (3)

Answers (3)

0 Kudos

hi,

Thanks for your reply.

FYI,

The UME database adapted R3 system as the datasource.

There's no SQL or MAX DB instance installed on that server...

I'll double check the configtool r3 master connection settings.

0 Kudos

hi, thank you for your reply.

I have double checked. the R3 is working fine as well as the Oracle database.

Also, dispathcer and SMD server are both running, only server node is not able to start anymore...

Former Member
0 Kudos

Hi,

I meant your UME instance not the R/3. With your installation of NetWeaver, a database is also installed - either it uses the MS SQL Server or the Max DB database. You will need to check if this database is up and running.

I would suggest you try to check using the config tool because it logs on to the local database using the default settings. If it shows an error, you know your database (the one used by NW) is down.

Could you check that?

Bye,

Sameer

0 Kudos

Thanks, I thought it should be the problem of the sapjco.jar. So I redeploy the SAP java Connector yesterday. The error msg changed, but still not able to start the j2ee Server.

Now the error msg looks like this:

Nov 13, 2007 6:11:13 PM com.sap.security.core.persistence [SAPEngine

SystemThread[impl:5]_105] Fatal: Initialization of UME persistence adapter

"R3_DATASOURCE" failed.

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

=========

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

started.

com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundl

e='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed

.', Arguments: []--> : Can't find resource for bundle java.util.PropertyReso

urceBundle, key UME initialization failed.

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UM

EServiceFrame.java:388)

at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFra

meAdaptor.java:31)

at com.sap.engine.core.service630.container.ServiceRunner.startAppli

cationServiceFrame(ServiceRunner.java:214)

at com.sap.engine.core.service630.container.ServiceRunner.run(Servic

eRunner.java:144)

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

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThrea

d.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.ja

va:105)

Caused by: com.sap.security.core.persistence.datasource.PersistenceException

: Connect to SAP gateway failed

Connect_PM GWHOST=localhost, GWSERV=sapgw00, ASHOST=localhost, SYSNR=00

LOCATION CPIC (TCP/IP) on local host

ERROR partner not reached (host localhost, service 3300)

TIME Tue Nov 13 18:11:13 2007

RELEASE 640

COMPONENT NI (network interface)

VERSION 37

RC -10

MODULE nixxi_r_mt.cpp

LINE 8673

DETAIL NiPConnect

SYSTEM CALL connect

ERRNO 146

ERRNO TEXT Connection refused

COUNTER 1

at com.sap.security.core.persistence.datasource.imp.R3PersistenceBas

e.newPersistenceException(R3PersistenceBase.java:178)

at com.sap.security.core.persistence.datasource.imp.R3PersistenceBas

e.init(R3PersistenceBase.java:446)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInst

ance.<init>(PrincipalDatabagFactoryInstance.java:357)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.new

Instance(PrincipalDatabagFactory.java:156)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.get

Instance(PrincipalDatabagFactory.java:109)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.get

Instance(PrincipalDatabagFactory.java:56)

at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMF

actory.java:270)

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UM

EServiceFrame.java:295)

... 6 more

com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundl

e='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed

.', Arguments: []--> : Can't find resource for bundle java.util.PropertyReso

urceBundle, key UME initialization failed.

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UM

EServiceFrame.java:388)

at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFra

meAdaptor.java:31)

at com.sap.engine.core.service630.container.ServiceRunner.startAppli

cationServiceFrame(ServiceRunner.java:214)

at com.sap.engine.core.service630.container.ServiceRunner.run(Servic

eRunner.java:144)

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

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThrea

d.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.ja

va:105)

Caused by: com.sap.security.core.persistence.datasource.PersistenceException

: Connect to SAP gateway failed

Connect_PM GWHOST=localhost, GWSERV=sapgw00, ASHOST=localhost, SYSNR=00

LOCATION CPIC (TCP/IP) on local host

ERROR partner not reached (host localhost, service 3300)

TIME Tue Nov 13 18:11:13 2007

RELEASE 640

COMPONENT NI (network interface)

VERSION 37

RC -10

MODULE nixxi_r_mt.cpp

LINE 8673

DETAIL NiPConnect

SYSTEM CALL connect

ERRNO 146

ERRNO TEXT Connection refused

COUNTER 1

at com.sap.security.core.persistence.datasource.imp.R3PersistenceBas

e.newPersistenceException(R3PersistenceBase.java:178)

at com.sap.security.core.persistence.datasource.imp.R3PersistenceBas

e.init(R3PersistenceBase.java:446)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInst

ance.<init>(PrincipalDatabagFactoryInstance.java:357)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.new

Instance(PrincipalDatabagFactory.java:156)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.get

Instance(PrincipalDatabagFactory.java:109)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.get

Instance(PrincipalDatabagFactory.java:56)

at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMF

actory.java:270)

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UM

EServiceFrame.java:295)

... 6 more

[Framework -> criticalShutdown] Core service com.sap.security.core.ume.servi

ce failed. J2EE Engine cannot be started.

Nov 13, 2007 6:11:13 PM com.sap.engine.core.Framework [SAPEngine

SystemThread[impl:5]_105] Fatal: Critical shutdown was invoked. Reason is:

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

e started.

Former Member
0 Kudos

Hi,

I think your database is down. Could you check if your database is up and running? You can do this through the config tool or the MaxDB Database Manager.

Try restarting the database instance if it is indeed running and check again.

Bye,

Sameer