← Common Redwood Server ErrorsCommon SAP BAE Errors →

on-site-related topic Common SAP-Related Errors

Exception: 104: No RFC authorization for function module

Platform

This error has been reported on all SAP R/3 systems.

Specific Error Message

Caused by: com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: No RFC authorization for function module BAPI_CM_PROFILE_CREATE.\
 (Remote shortdump: RFC_NO_AUTHORITY in system [PR1|sap.example.com|43])
     at com.sap.conn.jco.rt.AbstractConnection.generateJCoException(AbstractConnection.java:616)
     at com.sap.conn.jco.rt.ClientConnection.executeInternal(ClientConnection.java:2025)
     at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:2212)
     at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:2079)
     at com.sap.conn.jco.rt.RfcDestination.execute(RfcDestination.java:2235)
     at com.sap.conn.jco.rt.RfcDestination.execute(RfcDestination.java:2199)
     at com.sap.conn.jco.rt.AbapFunction.execute(AbapFunction.java:305)
     at com.redwood.scheduler.connector.sap.rfc.jco3.connection.impl.ClientConnectionImpl.call(ClientConnectionImpl.java:399)
     ...23 more 16 more
Caused by: RfcException raised by system [PR1|sap.example.com|43]:
     message: No RFC authorization for function module BAPI_CM_PROFILE_CREATE.
     return code: RFC_SYS_EXCEPTION (3)
     error group: 104
     key: RFC_ERROR_SYSTEM_FAILURE
     message class: 00
     message type: X
     message number: 341
     message parameter 0: RFC_NO_AUTHORITY
     at com.sap.conn.rfc.engine.RfcIoOpenCntl.RfcReceive(RfcIoOpenCntl.java:2142)
     at com.sap.conn.jco.rt.ClientConnection.executeInternal(ClientConnection.java:1974)
     ... 22 more
Caused by: com.sap.conn.rfc.exceptions.RfcGetException: No RFC authorization for function module BAPI_CM_PROFILE_CREATE.
     at com.sap.conn.rfc.engine.RfcImp.ab_rfcerror(RfcImp.java:931)
     at com.sap.conn.rfc.engine.RfcGet.ab_rfcget(RfcGet.java:194)
     at com.sap.conn.rfc.engine.RfcRcv.ab_rfcreceive(RfcRcv.java:41)
     at com.sap.conn.rfc

Example error message for missing authorizations on function module BAPI_CM_PROFILE_CREATE.

Resolution

Grant the required RFC authorizations to the user. It is recommended to grant EXECUTE on the function group, you must at least grant EXECUTE on all required function modules, see SAP RFC Authorizations.

  1. In SAPGui, open transaction SE37 and fill the name into the Function Module field, choose Display.
  2. On the Attributes tab, you see which function group it belongs to and you grant EXECUTE on the function group and are done. Alternatively, grant EXECUTE on the function module, see SAP RFC Authorizations of required function modules, depending on your needs in the SAP connector.
  3. Re-run the test, repeat these steps for each function module for which you have missing authorizations.

Exception: 113: CPIC-CALL: SAP_CMACCPTP3 on convId:

Platform

This error has been reported on SAP Inbound connection to AS ABAP 7.30 application servers.

Specific Error Message

  SAP Inbound connection "XXX" stopped unexpectedly.
  Details:
  Exception: 113: CPIC-CALL: SAP_CMACCPTP3 on convId:

  LOCATION SAP-Gateway on host <hostname> / sapgw<instance ID>
  ERROR registration of tp <SAP inbound rfc destination> from host <SAP inbound host> not allowed

Resolution

In you gateway profile, you have to allow connections to the SAP system. Inspect the value of the gw/acl_mode and gw/reg_info parameters; if the former is set to 1, the latter has to point to a file which allows connections from external servers. See SAP Note 1843782 and Defining the reginfo File for more information.

note

It is not recommended to change gw/acl_mode if it is set to 1 and register the appropriate external program in gw/reg_info instead.

Example

In the following example, the gw/acl_mode is set to 1, so gw/reg_info points to a file with the contents below; in SM59 the name of your RFC connection is CPSECCMLS, 10.0.0.5 is the IP of the SAProuter client and 10.1.2.9 is the IP of the central Redwood Server.

TP=CPSECCMLS HOST=10.0.0.5,10.1.2.9

Exception: 102: SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed

Platform

Reported on systems with many connections to SAP systems.

Specific Error Message

Note that this problems affects process servers connecting to SAP systems and thus may affect processes as well. Alternate warnings are printed for at the end.

ERROR 2023-09-28 13:31:23,740 Europe/Berlin [Redwood SAPService Job Worker (RSI.T09_SAP_P20121) worker 4] com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiConnectionPool - Exception while connecting to SAP system

Exception: 102: SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed
Connect_PM  GWHOST=pr1.example.com, GWSERV=sapgw.example.com, SYSNR=00

LOCATION    CPIC (TCP/IP) on local host
ERROR       max no of 100 conversations exceeded
TIME        Tue Oct 30 13:31:13 201
RELEASE     640
COMPONENT   CPIC (TCP/IP)
VERSION     3
RC          466
MODULE      r3cpic.c
LINE        9706
COUNTER     275

 at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall.perform(RemoteFunctionCall.java:250)

 at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection.perform(AbstractRfcConnection.java:475)

 at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection.doConnect(AbstractRfcConnection.java:447)

 at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiConnection.connect(AbstractXmiConnection.java:64)

 at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiConnectionPool.borrowConnection(AbstractXmiConnectionPool.java:188)

 at com.redwood.scheduler.connector.sap.rfc.command.AbstractXbpCommand.doExecute(AbstractXbpCommand.java:81)

 at com.redwood.scheduler.connector.sap.rfc.command.AbstractCommand.execute(AbstractCommand.java:59)

 at com.redwood.scheduler.connector.sap.rfc.service.operation.RunJobOperation.doWork(RunJobOperation.java:103)

 at com.redwood.scheduler.connector.sap.rfc.service.SapJobWork.doWork(SapJobWork.java:38)

 at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:75)

 at java.lang.Thread.run(Unknown Source)

Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed
Connect_PM  GWHOST=pr1.example.com, GWSERV=sapgw.example.com, SYSNR=00

LOCATION    CPIC (TCP/IP) on local host
ERROR       max no of 100 conversations exceeded
TIME        Tue Oct 30 13:31:13 201
RELEASE     640
COMPONENT   CPIC (TCP/IP)
VERSION     3
RC          466
MODULE      r3cpic.c
LINE        9706
COUNTER     275

 at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeConnect(Native Method)

 at com.sap.mw.jco.rfc.MiddlewareRFC$Client.connect(MiddlewareRFC.java:1125)

 at com.sap.mw.jco.JCO$Client.connect(JCO.java:3272)

 at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnectionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:125)

 at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnectionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45)

 at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepositoryImpl.connect(RfcRepositoryImpl.java:119)

 at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection$5.doPerform(AbstractRfcConnection.java:452)

 at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall.perform(RemoteFunctionCall.java:147)

 ... 10 more

WARN  2023-09-28 13:31:23,743 Europe/Berlin [Redwood SAPService Job Worker (RSI.T09_SAP_P20121) worker 4] com.redwood.scheduler.connector.sap.rfc.command.AbstractCommand - Transient communication error while executing job 123456

Exception: 102: SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed
Connect_PM  GWHOST=pr1.example.com, GWSERV=sapgw.example.com, SYSNR=00

max no of 404 conversations exceeded

Resolution

This problem occurs when you run out of RFC connections. The RFC library in SAP NetWeaver is limited to 404 concurrent RFC connections by default, this can be changed by setting the jco.cpic_maxconv Java property, please see the SAP documentation for more information and SAP Note 2124330. On the Redwood Server side you should specify the jco.cpic_maxconv Java property with a value of 3000 as well.

Note that on Redwood Platform running on Windows as a service you must specify this property in the Java Options field on the Java tab of the Appache Tomcat Service Properties; the Apache Tomcat Service Properties can be opened by specifying <installation_directory>\j2ee\cluster\global\tomcat\bin\tomcat9w_<bits>.exe //ES/<service_name> where <bits> is the bittiness of the service, usually 64, and <service_name> is the name you chose for the service. For example: <install_directory>\j2ee\cluster\global\tomcat\bin\tomcat9w_64.exe //ES/Scheduler. Note that you can find the service name in the Properties dialog of the service in services.msc; note that the Service Name is required, not its description as displayed in services.msc.

Error: E XM 034 Internal problem

Platform

Reported with different SAP releases when scheduling an ABAP with any of the SAP_AbapRun process definition. Note that the name of the function (BAPI_XBP_JOB...) can vary.

Specific Error Messages

BAPI exception while calling BAPI_XBP_JOB_ADD_ABAP_STEP: E XM 034 Internal problem (function BAPI_XBP_JOB_ADD_ABAP_STEP) BAPI_XBP_JOB_ADD_ABAP_STEP,, ,
BAPI exception while calling BAPI_XBP_JOB_CLOSE: E XM 034 Internal problem (function BAPI_XBP_JOB_CLOSE) BAPI_XBP_JOB_CLOSE,, ,

Resolution

A parameter of the job has an illegal value. Open the system log via transaction SM21 for around the time the error occurred and locate the following (example for BAPI_XBP_JOB_ADD_ABAP_STEP)

EFN|BP_JOB_EDITOR: Job <process_name> is invalid. Reason:
EFT|> Step <n> contains illegal values
EF2|BP_STEPLIST_EDITOR: Invalid step values (step <n> ) found. Reason:
EF8|> <reason>

In the above example, <Process_name> is the name of the job, <n> is the step number, <reason> should provide you with enough information to find a resolution.

If the above did not help, refer to SAP Note 1777900, an issue has been corrected that led to functions reporting "inconsistent" error messages.

Error: E XM 251 Time stamp "FROM_TIMESTAMP" is invalid

Platform

Reported with different SAP releases with XBP 3.0, when synchronizing event history criteria.

Specific Error Message

BAPI exception while calling BAPI_XBP_BTC_EVTHISTORY_GET: E XM 251 Time stamp "FROM_TIMESTAMP" is invalid [, , , ]

Resolution

Time zone information is client-dependent and has to be maintained in each client separately. The report TZCUSTIM imports time zone data into a client.

Please refer to SAP Note 198411 for more information.

Error: I:XM:233 BAPI_XBP_NEW_FUNC_CHECK

Platform

Reported when attempting to enable XBP 3.0 job interception features on a very old system that does not have XBP 3.0.

Specific Error Message

BAPI exception: RFC function module = BAPI_XBP_NEW_FUNC_CHECK, message type=E, id=XM,
number=233, text=I:XM:233 BAPI_XBP_NEW_FUNC_CHECK,
msgv1=BAPI_XBP_NEW_FUNC_CHECK, msgv2=, msgv3=, msgv4=

Resolution

Upgrade the remote SAP System to a version that supports XBP 3.0 or do not attempt to enable XBP 3.0 job interception features on that system.

Error: You have no authorization to log into interface XBP

Platform

This error can occur on any SAP Basis 3.1i or higher

Specific Error message

BAPI exception: RFC function module = BAPI_XMI_LOGON, message type=E, id=XM,
number=026, text=You have no authorization to log into interface XBP,
msgv1=XBP, msgv2=, msgv3=, msgv4=

Resolution

Check the Authorizations of the RFC user.

  • Ensure the REDWOOD role has all the required privileges.
  • Ensure the user specified has been granted the REDWOOD role.
  • Check the S_XMI_PROD Authorizations and make sure the XMI logging: company name is set to REDWOOD. This entry is case-sensitive.

Error Incomplete Layout

Platform

This error can occur on all known SAP Industry Solutions platforms, it indicates that the layout of a mass activity is not complete.

Specific Error Message

Exception while calling /REDWOOD/MA_GET_LAYOUT : 126: Incomplete Layout
definitions
    at
com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientConnectionImpl.call(ClientConnectionImpl.java:513)
    at
com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection$4.doPerform(AbstractRfcConnection.java:289)
    at
com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall.perform(RemoteFunctionCall.java:130)
    at
com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection.perform(AbstractRfcConnection.java:445)
    at
com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection.execute(AbstractRfcConnection.java:282)
    at
com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.SapFunctionModuleWrapper.execute(SapFunctionModuleWrapper.java:194)
    at
com.redwood.scheduler.connector.sap.rfc.jco.AbstractSapFunctionModule.execute(AbstractSapFunctionModule.java:107)
    at
com.redwood.scheduler.connector.sap.rfc.command.impl.MassActivityImportCommand.doExecute(MassActivityImportCommand.java:354)
    at
com.redwood.scheduler.connector.sap.rfc.command.impl.AbstractMassActivitiyCommand.execute(AbstractMassActivitiyCommand.java:56)
    at
com.redwood.scheduler.connector.sap.rfc.command.AbstractXbpCommand.doExecute(AbstractXbpCommand.java:123)
    at
com.redwood.scheduler.connector.sap.rfc.command.AbstractCommand.execute(AbstractCommand.java:56)
    at
com.redwood.scheduler.connector.sap.rfc.service.SapJobWork.doWork(SapJobWork.java:106)
    at
com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:59)
    at java.lang.Thread.run(Unknown Source)
Caused by: com.sap.mw.jco.JCO$AbapException: (126) BAD_LAYOUT: Incomplete
Layout definitions
    at com.sap.mw.jco.JCO$Function.getException(JCO.java:18207)
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:3298)
    at
com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientConnectionImpl.call(ClientConnectionImpl.java:487)
    ... 13 more

Resolution

This usually means that the mass activity in question is not usable in the SAP system, and import is not useful, if this is the case, you may ignore this error. If you receive this error for a mass activity that you want to use, please contact Redwood support services.

onsiteTopic

← Common Redwood Server ErrorsCommon SAP BAE Errors →