Symptom
- After a restart of a Process Orchestration (PO) or Process Integration (PI) system, the inboundRA service used for IDoc_AAE adapter integrations does not start up
- You may have a landscape set up with several Instances with multiple Java Server Nodes on each
- This can happen especially after a rolling restart i.e. restarting individual Java Server Nodes separately
- Checking the defaultTraces, you can find an error such as:
Error#com.sap.mw.jco.jra#
#BC-MID-CON-JCO#sap.com/tc~sapjra~temp#C0000A3072330039000000010018E8DF#105889150000006397#sap.com/com.sap.aii.adapter.idoc.sapjra.inboundRA#com.sap.mw.jco.jra#deploy_service#0##0A2024A9789RT3KDK938PIS0A307234#082be8537e2e11edca0e15987fbd7e##0#ResourceAdapter Starter#Plain##
[JRA] Creation of ManagedConnectionFactory default repository failed#Error#com.sap.mw.jco.jra#
#BC-MID-CON-JCO#sap.com/tc~sapjra~temp#C0000B65464987000000020018E8DF#105889151549862657#sap.com/com.sap.aii.adapter.idoc.sapjra.inboundRA#com.sap.mw.jco.jra#deploy_service#0##0A2024A9789RTLKASJFI92S0A307234#082be8537KLASDUI33dca0e154984fbd7e##0#ResourceAdapter Starter#Plain##
com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Initialization of repository destination XI_IDOC_DEFAULT_DESTINATION failed: User is locked; notify the person responsible#Error#com.sap.mw.jco.jra#
#BC-MID-CON-JCO#sap.com/tc~sapjra~temp#C0000B65464987000000020018E8DF#105889151549862657#sap.com/com.sap.aii.adapter.idoc.sapjra.inboundRA#com.sap.mw.jco.jra#deploy_service#0##0A2024A9789RTLKASJFI92S0A307234#082be8537KLASDUI33dca0e154984fbd7e##0#ResourceAdapter Starter#Plain##
com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Initialization of repository destination XI_IDOC_DEFAULT_DESTINATION failed: User is locked; notify the person responsible
at com.sap.conn.jco.rt.RfcDestination.getSystemID(RfcDestination.java:1077)
at com.sap.conn.jco.rt.RepositoryManager.getRepository(RepositoryManager.java:29)
at com.sap.conn.jco.rt.RfcDestination.initRepository(RfcDestination.java:1025)
at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:1167)
at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:33)
at com.sap.mw.jco.jra.JRA$ManagedConnectionFactoryImpl.getRepository(JRA.java:1897)
at com.sap.mw.jco.jra.JRA$ResourceAdapterImpl.start(JRA.java:9716)
at com.sap.mw.jco.jra.JRA$ResourceAdapterImpl.start(JRA.java:935)
at com.sap.engine.services.connector.deploy.util.ApplicationContextRunner.run(ApplicationContextRunner.java:638)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:1385)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: User is locked; notify the person responsible (remote system is [<SID|<host>|<inst_nr>])
at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:581)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.connect(MiddlewareJavaRfc.java:1347)
at com.sap.conn.jco.rt.ClientConnection.connect(ClientConnection.java:747)
at com.sap.conn.jco.rt.RepositoryConnection.connect(RepositoryConnection.java:72)
at com.sap.conn.jco.rt.PoolingFactory.init(PoolingFactory.java:107)
at com.sap.conn.jco.rt.ConnectionManager.createFactory(ConnectionManager.java:425)
at com.sap.conn.jco.rt.DefaultConnectionManager.createFactory(DefaultConnectionManager.java:46)
at com.sap.conn.jco.rt.ConnectionManager.getFactory(ConnectionManager.java:373)
at com.sap.conn.jco.rt.RfcDestination.getSystemID(RfcDestination.java:1069)
... 12 more
Caused by: RfcException raised by system [<SID|<host>|<inst_nr>] for user [<user_name>]:
message: User is locked; notify the person responsible
return code: RFC_SYS_EXCEPTION (3)
error group: 103
key: RFC_ERROR_LOGON_FAILURE
at com.sap.conn.rfc.api.RfcApi.RfcOpen(RfcApi.java:186)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.connect(MiddlewareJavaRfc.java:1311)
... 19 more
Caused by: RfcException raised by system [<SID|<host>|<inst_nr>]:
message: User is locked; notify the person responsible
return code: RFC_SYS_EXCEPTION (3)
error group: 104
key: RFC_ERROR_SYSTEM_FAILURE
at com.sap.conn.rfc.engine.RfcIoOpenCntl.RfcReceive(RfcIoOpenCntl.java:1995)
at com.sap.conn.rfc.api.RfcApi.RfcOpen(RfcApi.java:165)
... 20 more
Caused by: com.sap.conn.rfc.exceptions.RfcGetException: User is locked; notify the person responsible
at com.sap.conn.rfc.engine.RfcImp.ab_rfcerror(RfcImp.java:1101)
at com.sap.conn.rfc.engine.RfcGet.ab_rfcget(RfcGet.java:155)
at com.sap.conn.rfc.engine.RfcRcv.ab_rfcreceive(RfcRcv.java:35)
at com.sap.conn.rfc.engine.RfcIoOpenCntl.RfcReceive(RfcIoOpenCntl.java:1937)
... 21 more
#
Read more...
Environment
- SAP NetWeaver 7.5
Product
Keywords
Resource Adapter, startup, failure, error, automatic , KBA , BC-XI-CON-IDO , Idoc Adapter J2EE , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview