JCO_ERROR_RESOURCE: Destination UMEBackendConnection does not exist

[Former Member]

Dear all,

i patched our SAP PI 7.11 SP05 with the newest SERVER Core hotfix 28.

now i got an error when jspm doing the automatic restart of the java engine :

JCO_ERROR_RESOURCE: Destination UMEBackendConnection does not exist

the server show status STOPPED.

When i activate the SAP* inside java and restart JAVA Server i can log on

with the NWA. I checked the jco connection UMEBackendConnection and try

a ping --> everything works. I can see logins in the abap of SAPJSF too in transaction AL08.

please, have you any ideas ?

greetings

oliver

Edited by: A. ATOS Origin on Sep 30, 2011 1:03 PM

[Former Member]

Hi,

Even after deploying the below still gettting the same error...

ENGINEAPI 7.30 - ENGINEAPI04P_7-10007921.SCA

J2EE ENGINE SERVERCORE 7.30 - SERVERCORE02P_17-10007988.SCA

2EE ENGINE CORE TOOLS 7.30 - CORETOOLS05P_2-10007976.SCA still

#2.0 #2012 01 31 08:04:56:740#+00#Fatal#com.sap.engine.core.Framework#

com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000C0A80341000D000000060000084C#8080650000000830##com.sap.engine.core.Framework#####3ef28b2c4be211e18fba005056b00010##0#Service Runner [tc_lmnzdm~crrsrv]#Plain##

Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [tc_lmnzdm~crrsrv] failed to start]#

I'm on Netweaver 7.3 PI (dualstack) - the disp+work is yellow.

disp+work comes up as;

disp+work=>sapparam<1c>: No Profile used.

disp+work=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

r3trans -d comes up as:

C:\>r3trans -d

This is r3trans version 6.22 (release 720 - 18.11.11 - 11:29:00).

unicode enabled version

R3trans=>sapparam(1c): No Profile used.

R3trans=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

r3trans finished (0000).

any help on this, appreciated.

[Former Member]

hy Ramesh,

did you solve the error meanwhile?

we are facing a similar Problem

kind regards

Tom

[gopi_sagi]

I have same issue after upgrading NW CE720 SP4 Server Core to patch 38. After upgrade ENGINEAPI to latest patch the issue resolved.

Gopi

[Former Member]

Hi Oliver,

Not sure if you are still having this issue, but you should be able to resolve it by applying the latest

patch to the engineapi component. From release 7.10 the following SCAs provide the core functionality of

the engine, and always must be in synch, because they have interdependencies:

BASETABLES.SCA, SERVERCORE.SCA, J2EEFRMW.SCA and ENGINEAPI.SCA

Deploying the latest patch to the ENGINEAPI.SCA should resolve the issue for you.

As the engine cannot be started you should use the batchdeployer tool to

install the patch:

/usr/sap/<SID>/<INSTANCE_ID>/j2ee/cluster/bootstrap/scripts/batchdeploye

r.csh -sdu <hotfix file location>

Kind regards,

Shimon Zafrir

SAP AGS

[Former Member]

Hi,

i already checked the SDN entry listed above and that is a thread that isnt solved i think.

I deployed server core again ( already the latest version ), but the problem still exists and and

1) "com.security.ume.service" if this backend connection exists

2) Go to configtool offline editor and in "Destinations" check if this connection exists.

i checked 3 times --> destination is there and test is successful ( i alredy checked that see above )

any other ideas.

greetings

oliver

Edited by: A. ATOS Origin on Oct 4, 2011 10:15 AM

[Former Member]

LOG OUTPUT :

#

#2.0 #2011 09 30

08:38:17:270#+0200#Fatal#com.sap.security.core.server.ume.service.UMEServiceFrame#

Start of UME service failed. Check help topic "Start of UME Service

Failed". Technical details: com.sap.conn.jco.JCoException: (106)

JCO_ERROR_RESOURCE: Destination UMEBackendConnection does not

exist#BC-JAS-SEC-UME#com.sap.security.core.ume.service#005056845C2F00030000000A00001930#5690550000000063##com.sap.security.core.server.ume.service.UMEServiceFrame#####c308d604eb2e11e08834005056845c2f##0#Service

Runner [com.sap.security.core.ume.service]#Plain##

Start of UME service failed. Check help topic "Start of UME Service

Failed". Technical details: com.sap.conn.jco.JCoException: (106)

JCO_ERROR_RESOURCE: Destination UMEBackendConnection does not exist#

#2.0 #2011 09 30 08:38:17:270#+0200#Fatal#com.sap.engine.core.Framework#com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#005056845C2F00030000000F00001930#5690550000000063##com.sap.engine.core.Framework#####c308d604eb2e11e08834005056845c2f##0#Service

Runner [com.sap.security.core.ume.service]#Plain##

Critical shutdown with exit code [2150] was requested due to [AS Java

cannot be started; core service [com.sap.security.core.ume.service]

failed to start]#

[Former Member]

Hi,

Same problem as your:

Try to recreate this JCo and restart java instance.

Or try to install latest SP - "SP08 for J2EE ENGINE SERVERCORE 7.11", if it's possible.

Best Regards,

Aleh

[Former Member]

Hello,

Can you go to Configtool and check what is the datasource?

Also check,

1) "com.security.ume.service" if this backend connection exists

2) Go to configtool offline editor and in "Destinations" check if this connection exists.

Many Thanks.

Ravindra