How To Fix ESH_TEST_FUNC060 - Could not create an application log for object &1 and subobject &2

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_TEST_FUNC - Test Functions of ESH

• Message number: 060

• Message text: Could not create an application log for object &1 and subobject &2

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 ESH_TEST_FUNC060 - Could not create an application log for object &1 and subobject &2 ?

  The SAP error message ESH_TEST_FUNC060 indicates that the system was unable to create an application log for a specified object and subobject. This error typically arises in the context of the SAP Enterprise Search (ESH) or related functionalities where logging is essential for tracking processes and errors.
  Causes:
  
  Authorization Issues: The user may not have the necessary authorizations to create logs for the specified object and subobject.
  Configuration Issues: The application log configuration might not be set up correctly for the specified object and subobject.
  Database Issues: There could be issues with the database where the logs are supposed to be stored, such as connectivity problems or database table issues.
  System Errors: There may be underlying system errors or inconsistencies that prevent the log from being created.
  Missing Log Object: The log object or subobject may not be defined in the system.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to create application logs. This can be done by reviewing the user's roles and authorizations in transaction SU53 or SUIM.
  Review Configuration: Check the configuration for the application log in transaction SLG0. Ensure that the log object and subobject are correctly defined and active.
  Database Check: Verify the database connection and check for any issues with the database tables related to application logging. You can use transaction SE11 to check the relevant tables.
  System Logs: Review the system logs (transaction SM21) for any related errors that might provide more context on why the log creation failed.
  Debugging: If the issue persists, consider debugging the relevant function module or program to identify where the failure occurs.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide patches or updates.
  
  Related Information:
  
  
  Transaction Codes:
  
  SLG1: To view application logs.
  SLG0: To maintain application log objects.
  SE11: To check database tables.
  SU53: To analyze authorization issues.
  SM21: To view system logs.
  
  
  
  Documentation: Refer to SAP Help documentation for more details on application logging and troubleshooting.
  
  
  If the problem persists after trying the above solutions, it may be beneficial to contact SAP support for further assistance.