How To Fix /ACCGO/IC_MSG035 - Job log is empty

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/IC_MSG -

• Message number: 035

• Message text: Job log is empty

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /ACCGO/IC_MSG035 - Job log is empty ?

  The SAP error message /ACCGO/IC_MSG035 Job log is empty typically indicates that a job related to the SAP application has been executed, but there is no log information available for that job. This can happen for various reasons, and understanding the cause is essential for troubleshooting.
  Possible Causes:
  
  Job Not Executed Properly: The job may not have run to completion due to an error or interruption.
  Job Log Deletion: The job log might have been deleted or not saved due to system settings or manual intervention.
  Authorization Issues: The user executing the job may not have the necessary authorizations to view the job log.
  System Configuration: There may be configuration issues in the job scheduling or logging settings in the SAP system.
  Technical Issues: There could be underlying technical issues with the SAP system or database that prevent the job log from being created or displayed.
  
  Solutions:
  
  Check Job Status: Go to transaction SM37 to check the status of the job. Look for any error messages or indications that the job did not complete successfully.
  Review Job Details: If the job is still in the system, review its details to see if there are any indications of what went wrong.
  Check Authorizations: Ensure that the user has the necessary authorizations to view job logs. This can be checked in transaction SU53 or by consulting with your security team.
  System Logs: Check the system logs (transaction SM21) for any related errors or warnings that might provide more context about the issue.
  Job Configuration: Review the job configuration settings to ensure that logging is enabled and properly configured.
  Re-run the Job: If possible, try to re-run the job to see if it generates a log this time. Make sure to monitor it closely.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM37 (Job Monitoring), SM21 (System Log), and SU53 (Authorization Check).
  SAP Documentation: Refer to SAP Help documentation for more details on job scheduling and logging.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.