How To Fix ESH_ENG_CDS_ABAP059 - Upgrade running; connector test skipped

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_ENG_CDS_ABAP - ES-CDS/ABAP

• Message number: 059

• Message text: Upgrade running; connector test skipped

What causes this issue?

The activation of the CDS-search view as an Enterprise Search connector
happened during system upgrade. In this situation, any error will make
the upgrade halt. Errors detected during test searches are not grave
enough to justify this behavior.

System Response

In this phase, no test searches are carried out. Because the system will
be restarted after upgrade, it does also not make sense to build the
runtime load.
After the system has been restarted, it will trigger the Enterprise
Search runtime load to be built. In the course of this process, the test
searches on the resulting connectors will be carried out. As usually,
connectors failing in the test searches will go to status "error while
preparing"; only, that this error will not reflect in the job log.

How to fix this error?

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

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ESH_ENG_CDS_ABAP059 - Upgrade running; connector test skipped ?

  The SAP error message ESH_ENG_CDS_ABAP059 indicates that the upgrade process for the SAP Enterprise Search (ESH) connector is currently running, and as a result, the connector test has been skipped. This message typically arises during the configuration or testing of the ESH connector in an SAP system.
  Cause:
  
  Ongoing Upgrade Process: The primary cause of this error is that an upgrade or a similar process is currently in progress for the ESH connector. During this time, certain operations, including tests, cannot be executed to avoid conflicts or inconsistencies.
  Locking Mechanism: SAP systems often implement locking mechanisms to prevent changes while an upgrade is in progress. This ensures data integrity and consistency.
  
  Solution:
  
  Wait for the Upgrade to Complete: The most straightforward solution is to wait until the ongoing upgrade process is finished. Once the upgrade is complete, you should be able to run the connector test without encountering this error.
  Check Upgrade Status: You can monitor the status of the upgrade process through transaction codes like SM37 (for job monitoring) or SICF (for service monitoring) to see if the upgrade is still running.
  Review Logs: If the upgrade seems to be taking an unusually long time, check the upgrade logs for any issues or errors that might be causing delays. This can be done through transaction SLG1 (Application Log).
  Restart the Test: After confirming that the upgrade has completed, you can attempt to rerun the connector test to ensure everything is functioning correctly.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might provide additional context or solutions related to this error message. You can search for notes in the SAP Support Portal.
  Documentation: Review the official SAP documentation for Enterprise Search and the specific connector you are working with to ensure that all prerequisites and configurations are correctly set up.
  System Performance: If you frequently encounter this issue, consider reviewing your system's performance and upgrade scheduling to minimize conflicts during critical operations.
  
  If the problem persists even after the upgrade is complete, it may be necessary to consult with SAP support or your system administrator for further investigation.