How To Fix ESH_ADM_MSG152 - System was copied -> execute program ESH_ADM_INDEX_ALL_SC (see long text)

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_ADM_MSG - ESH Administration and Monitoring Tool

• Message number: 152

• Message text: System was copied -> execute program ESH_ADM_INDEX_ALL_SC (see long text)

What causes this issue?

The system was just copied from another system or another client of the
same system.

System Response

The current system cannot be connected to an Enterprise Search hub.

How to fix this error?

Execute report ESH_ADM_INDEX_ALL_SC. This report deletes all copied
search connectors as well as the copied connections. The system will be
prepared so that you can create search connectors.
If the current system was copied from another system, you must also run
the <ZK>TrexRfcConnection.py</> script to establish the connection
between TREX and the new ABAP server.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ESH_ADM_MSG152 - System was copied -> execute program ESH_ADM_INDEX_ALL_SC (see long text) ?

  The SAP error message ESH_ADM_MSG152 indicates that the system was copied, and as a result, you need to execute the program ESH_ADM_INDEX_ALL_SC. This message is typically related to the SAP Enterprise Search (SAP ESH) functionality, which requires certain indexing processes to be executed after a system copy to ensure that the search functionality works correctly.
  Cause:
  When a system is copied (for example, from a production environment to a development or testing environment), the data and configurations are duplicated. However, the search indices that are used by SAP ESH may not be valid or may not exist in the new environment. This can lead to issues with search functionality, as the system needs to rebuild or refresh the indices to reflect the current state of the data.
  Solution:
  To resolve this error, you need to execute the program ESH_ADM_INDEX_ALL_SC. This program is responsible for re-indexing the search data in the SAP ESH environment. Here are the steps to do this:
  
  
  Access Transaction SE38 or SA38: Go to the SAP GUI and enter transaction code SE38 or SA38 to access the program execution screen.
  
  
  Enter the Program Name: In the program name field, enter ESH_ADM_INDEX_ALL_SC.
  
  
  Execute the Program: Click on the execute button (F8) to run the program. This will initiate the indexing process.
  
  
  Monitor the Process: Depending on the amount of data and the complexity of the indices, this process may take some time. You can monitor the progress in the job overview or check the logs for any errors.
  
  
  Check for Errors: After the program has completed, check for any error messages or warnings that may indicate issues during the indexing process.
  
  
  Related Information:
  
  Documentation: Refer to the SAP Help Portal or the specific documentation for SAP ESH for more details on indexing and search configuration.
  System Administration: Ensure that you have the necessary authorizations to execute the indexing program and that you are aware of the impact on system performance during the indexing process.
  Post-Execution Checks: After executing the program, perform tests to ensure that the search functionality is working as expected.
  
  By following these steps, you should be able to resolve the ESH_ADM_MSG152 error and restore the search functionality in your SAP system after a copy.