SAP Knowledge Base Article - Preview

2563299 - Error SUM Execution phase Deploy DB Content

Symptom

During a Java stack Upgrade, a deployment error happens in phase Deploy DB Content, similar to:

Deployment of queue Queue_2017.11.13 at 15:16:33 completed with error Deployment error. See log ../SUM/sdt/log/SUM/deploy_api.0.log for details.
java.lang.RuntimeException: com.sap.engine.services.dc.api.deploy.EngineTimeoutException: [ERROR CODE DPL.DCAPI.1041] Deploy API could not retrieve the Result after 7200000 ms.
Possible reasons:
        1.J2EE Engine cannot start.
                Please check in Sap MMC or jcmon the engine status.
                        -If the server is stopped please check the server log files why the engine cannot start.
        2.Engine is up and running but deploy controller could not be looked up due to some Runtime exception.
                Please start telnet session to the SAP Application Server , check if the tc~bl~deploy_controller service is started.
com.sap.engine.services.dc.api.deploy.EngineTimeoutException: [ERROR CODE DPL.DCAPI.1041] Deploy API could not retrieve the Result after 7200000 ms.
Possible reasons:
        1.J2EE Engine cannot start.
                Please check in Sap MMC or jcmon the engine status.
                        -If the server is stopped please check the server log files why the engine cannot start.
        2.Engine is up and running but deploy controller could not be looked up due to some Runtime exception.
                Please start telnet session to the SAP Application Server , check if the tc~bl~deploy_controller service is started.

On the defaulttrace file, a lock user error is reported:

#2.#2017 11 14 13:21:42:854#+0530#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000071#BC-JAS-SEC-UME#sap.com/com.sap.security.core.ume.service#C0000A010371000D0000000D000041FF#1203650000003206##com.sap.engine.core.service630.container.ServiceRunner#####a474173ac91011e7acb15cf3fc7812bc##0#
Service Runner[com.sap.security.core.ume.service]#Plain##

Service [com.sap.security.core.ume.service] failed to start; Reason: [Error in execution of service's start method]; nested exception is:
[EXCEPTION]
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Initialization of destination UMEBackendConnection failed: Password logon no longer possible - too many failed attempts on <server> sysnr 00
        at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:463)
        at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
        at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
        at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
        at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
        at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
        at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
        at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Initialization of destination UMEBackendConnection failed: Password logon no longer possible - too many failed attempts on <server> sysnr 00
        at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:699)
        at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getNewInstance(PrincipalDatabagFactory.java:203)
        at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:153)
        at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:215)
        at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:139)
        at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:94)
        at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:211)
        at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:289)
        ... 7 more

Upgrade is stopped due to that.


Read more...

Environment

  • SAP Netweaver Java release independent
  • SUM (Software Update Manager) release independent

Product

SAP ERP 6.0

Keywords

KBA , BC-UPG-TLS-TLJ , Upgrade tools for Java , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.