How To Fix CB01004 - Problems calling the system to read the application log using RFC

SAP Error Message - Details

• Message type: E = Error

• Message class: CB01 - Messages for Interface Objects

• Message number: 004

• Message text: Problems calling the system to read the application log using RFC

What causes this issue?

You attempted to call the application log in the system from a logistics
system using a Remote Function Call (RFC) connection. This attempt
failed.

System Response

The application log is not displayed.

How to fix this error?

Check whether the RFC connection to the system is working.
Check in the logistics system whether the name of the RFC destination is
specified in Customizing for <ZK>Product Safety</> in the IMG activity
<LS>Specify Environment Parameters</> under the environment parameter
DEST_SRE_DS.

Procedure for System Administrators

You can set up RFC destinations in Customizing or in a productive
system. To do this, you either edit the activity
<DS:SIMG.SIMG_BCSNC_SM59>Define RFC destination</> in Customizing for
Basis or you choose <LS>Tools -> Administration -> Administration ->
Network -> RFC Destinations</> on the <LS>SAP Easy Access</> screen.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CB01004 - Problems calling the system to read the application log using RFC ?

  The SAP error message CB01004 indicates that there is a problem when the system attempts to read the application log using Remote Function Call (RFC). This error can occur due to various reasons, and understanding the cause is essential for troubleshooting and resolving the issue.
  Possible Causes:
  
  RFC Connection Issues: The RFC connection to the target system may not be configured correctly or may be down.
  Authorization Problems: The user executing the RFC call may not have the necessary authorizations to read the application log.
  Network Issues: There may be network connectivity problems between the systems involved in the RFC call.
  System Configuration: The target system may not be properly configured to handle the application log requests.
  Application Log Not Found: The specific application log being requested may not exist or may have been deleted.
  
  Solutions:
  
  
  Check RFC Connection:
  
  Verify the RFC destination in transaction SM59. Ensure that the connection is correctly configured and test the connection to see if it is working.
  
  
  
  Review Authorizations:
  
  Check the user authorizations in the target system. Ensure that the user has the necessary permissions to access the application log. You can use transaction SU53 to analyze authorization issues.
  
  
  
  Network Troubleshooting:
  
  Ensure that there are no network issues preventing communication between the systems. You can use tools like ping or traceroute to check connectivity.
  
  
  
  System Configuration:
  
  Review the configuration settings in the target system to ensure that it is set up to handle application log requests. Check for any relevant settings in transaction SICF or SMICM.
  
  
  
  Check Application Log:
  
  Verify if the application log you are trying to access exists. You can check this in transaction SLG1 by entering the relevant object and sub-object.
  
  
  
  Review System Logs:
  
  Check the system logs (transaction SM21) for any additional error messages or warnings that might provide more context about the issue.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM59: RFC Destinations
  SU53: Authorization Check
  SLG1: Application Log Display
  SM21: System Log
  SICF: HTTP Service Hierarchy
  
  
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  
  
  Documentation: Review the official SAP documentation for more details on application logs and RFC communication.
  
  
  By following these steps, you should be able to identify the root cause of the CB01004 error and implement the appropriate solution. If the issue persists, consider reaching out to SAP support for further assistance.