How To Fix ESH_SEARCH358 - Export SWC: Object type &1 node &2 request &3 attr &4 does not exist

ESH_SEARCH358 - Overview

• Message type: E = Error

• Message class: ESH_SEARCH - ESH Search

• Message number: 358

• Message text: Export SWC: Object type &1 node &2 request &3 attr &4 does not exist

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_SEARCH358 - Export SWC: Object type &1 node &2 request &3 attr &4 does not exist ?

  The SAP error message ESH_SEARCH358 typically indicates that there is an issue with the export of a Software Component (SWC) related to the Enterprise Search (ESH) configuration. The error message specifies that an object of a certain type, node, request, and attribute does not exist in the system.
  
  Cause:
  
  Missing Object: The specified object type, node, request, or attribute may not exist in the system. This could be due to a misconfiguration or an incomplete setup.
  Incorrect Configuration: The configuration for the Enterprise Search might be incorrect, leading to references to non-existent objects.
  Transport Issues: If the system is involved in a transport process, the required objects may not have been transported correctly.
  Version Mismatch: There may be a version mismatch between the components involved, leading to references to outdated or non-existent objects.
  
  
  Solution:
  
  Check Object Existence: Verify that the object type, node, request, and attribute mentioned in the error message actually exist in the system. You