Skip to Content
0
Aug 20, 2011 at 03:24 AM

SAP NW PI 7.11 JAVA STACK IS NOT COMING UP AFTER SERVERCORE 6.19 UPGRADE

131 Views

Dear Team,

After deploying SERVERCORE Patch from 6.0-->6.19 in PI7.11 ,servernode failing due to UME errors.

default trace log:-

#2.0^H#2011 08 19 21:10:52:546#+0300#Error#com.sap.security.core.persistence.datasource.imp.R3Persistence#

An exception was thrown in the UME/ABAP user management connector that was caused by unavailability of the RFC communication with the backend system: "". #BC-JAS-SEC#com.sap.security.core.sda#00199997A94400030000000400007FDC#227010850000000057##com.sap.security.core.persistence.datasource.imp.R3Persistence#####8fdd1566ca8e11e098b400199997a944##0#Service Runner [com.sap.security.core.ume.service]#Plain## An exception was thrown in the UME/ABAP user management connector that was caused by unavailability of the RFC communication with the backend system: "com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination UMEBackendConnection does not exist". # #2.0^H#2011 08 19 21:10:52:553#+0300#Fatal#com.sap.security.core.persistence.datasource.imp.R3Persistence# Initialization of ABAP data source () failed: "". This message is critical if it appears during the startup of the AS Java.#BC-JAS-SEC#com.sap.security.core.sda#00199997A94400030000000600007FDC#227010850000000057##com.sap.security.core.persistence.datasource.imp.R3Persistence#####8fdd1566ca8e11e098b400199997a944##0#Service Runner [com.sap.security.core.ume.service]#Plain## Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination UMEBackendConnection does not exist". This message is critical if it appears during the startup of the AS Java.# #2.0^H#2011 08 19 21:10:52:554#+0300#Error#com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance# #BC-JAS-SEC#com.sap.security.core.sda#00199997A94400030000000700007FDC#227010850000000057##com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.[cf=com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance][md=<init>][cl=133163]#####8fdd1566ca8e11e098b400199997a944##0#Service Runner [com.sap.security.core.ume.service]#Plain## Initialization of UME persistence adapter "PRIVATE_DATASOURCE" failed. [EXCEPTION] com.sap.security.core.persistence.datasource.PersistenceException: com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination UMEBackendConnection does not exist Security log:- #2.0^H#2011 08 20 01:28:12:517#+0300#Fatal#/System/Security/Usermanagement# Initialization of ABAP data source () failed: "". This message is critical if it appears during the startup of the AS Java.#BC-JAS-SEC#com.sap.security.core.sda#00199997A944000300000005000031BA#227010850000000056##com.sap.security.core.persistence.datasource.imp.R3Persistence#####80725891cab211e0b47400199997a944##0#Service Runner [com.sap.security.core.ume.service]#Plain##

Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination UMEBackendConnection does not exist". This message is critical if it appears during the startup of the AS Java.#

#2.0^H#2011 08 20 01:28:12:520#+0300#Fatal#/System/Security/Usermanagement#

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#00199997A944000300000009000031BA#227010850000000056##com.sap.security.core.server.ume.service.UMEServiceFrame#####80725891cab211e0b47400199997a944##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#

*std_server0.out:-*

Caused by: com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination UMEBackendConnection does not exist

at com.sap.conn.jco.rt.DefaultDestinationManager.update(DefaultDestinationManager.java:198)

at com.sap.conn.jco.rt.DefaultDestinationManager.searchDestination(DefaultDestinationManager.java:349)

at com.sap.conn.jco.rt.DefaultDestinationManager.getDestinationInstance(DefaultDestinationManager.java:99)

at com.sap.conn.jco.JCoDestinationManager.getDestination(JCoDestinationManager.java:61)

at com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo700Proxy.<init>(R3JCo700Proxy.java:75)

... 19 more

Caused by: java.lang.NoSuchMethodError: com.sap.security.core.server.destinations.lib.RFCDestinationCore.setLoginTicket(Ljava/lang/String;)V

at com.sap.security.core.server.destinations.provider.DestinationsProviderFrame.getDestinationProperties(DestinationsProviderFrame.java:164)

at com.sap.conn.jco.rt.DefaultDestinationManager.getProperties(DefaultDestinationManager.java:298)

at com.sap.conn.jco.rt.DefaultDestinationManager.update(DefaultDestinationManager.java:169)

... 23 more

FATAL: 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]

I can see some latest configuration update in Configurations -> cluster_config -> system -> custom_global -> cfg-->services

Is there anything I need to change manually after this patch deployment?

Regards,

Mahesh Phegade