How To Fix ESH_OM_OBJ_MODEL_RP2273 - Metadata provider is not available (class &1)

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_OM_OBJ_MODEL_RP2 - Object Model Repository (2)

• Message number: 273

• Message text: Metadata provider is not available (class &1)

What causes this issue?

Data provider &V1& is not available.

System Response

Node metadata cannot be modified based on the current metadata provider.

How to fix this error?

Checklist:
- Has a connectivity (back-end system) been assigned to the software
component?
- Is the connectivity up and running (connection test for RFC ABAP
connection "ES_APPL_..._EXTR" via transaction SM59).

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

If you expect the data provider to be available, create a SAP customer
ticket for the application component responsible for the data provider
(ABAP class &V1&).
The component is displayed in the details section of the package of the
ABAP class (transaction SE24).

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_RP2273 - Metadata provider is not available (class &1) ?

  The SAP error message ESH_OM_OBJ_MODEL_RP2273 indicates that a metadata provider is not available for a specific class in the Enterprise Search (ESH) environment. This error typically arises when the system is unable to find or access the required metadata provider for the object model.
  
  Cause:
  
  Missing Metadata Provider: The specified metadata provider class is not registered or does not exist in the system.
  
  Configuration Issues: There may be configuration issues in the Enterprise Search settings that prevent the metadata provider from being recognized.
  Transport Issues: If the system has recently undergone a transport, the metadata provider may not have been transported correctly.
  Authorization Issues: The user may not have the necessary authorizations to access the metadata provider.
  
  
  Solution:
  
  
  Check Metadata Provider Registration:
  
  Go to the transaction code ES_MAINTAIN or ES_ADMIN to check if the metadata provider is correctly registered.
  Ensure that the class specified in the error message is available and properly configured.
  
  
  
  Review Configuration:
  
  Check the configuration settings for the