How To Fix ESH_OM_OBJ_MODEL_REP797 - Connector for model &1 of SWC &2 was created in SWC &3

ESH_OM_OBJ_MODEL_REP797 - Overview

• Message type: E = Error

• Message class: ESH_OM_OBJ_MODEL_REP - Object Model Repository

• Message number: 797

• Message text: Connector for model &1 of SWC &2 was created in SWC &3

What causes this issue?

If a software component B is included in software component A and this
usage is to be deleted, then there must be no connectors:
That have been created for object types of software component B or a
software component included in B (directly or indirectly)
In software component A or software components using A (directly or
indirectly)
In this case<(>,<)> a connector for object type &v1& of software
component &v2& has been created in software component &v3& for system
&v4&.

System Response

The usage cannot be deleted.

How to fix this error?

Delete the according connectors and then delete the usage.

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_OM_OBJ_MODEL_REP797 - Connector for model &1 of SWC &2 was created in SWC &3 ?

  The SAP error message ESH_OM_OBJ_MODEL_REP797 indicates that there is a conflict or issue related to the connector for a specific model in the SAP Enterprise Search (SAP ESH) environment. This error typically arises when there is a mismatch or inconsistency in the software component (SWC) versions or configurations.
  
  Cause:
  The error message suggests that the connector for the specified model (&1) was created in a different software component (SWC &3) than the one currently being referenced (SWC &2). This can happen due to several reasons:
  
  Version Mismatch: The model may have been updated or created in a different version of the software component.
  Transport Issues: If the model was transported from one system to another, it may not have been properly aligned with the corresponding software components.
  Configuration Errors: There may be configuration errors in the system that lead to the model being associated with the wrong software component.
  
  
  Solution:
  To resolve this error, you can take