How To Fix ESH_SEARCH359 - Export SWC: Obj.type &1 node &2 req. &3 attr group &4 does not exist

ESH_SEARCH359 - Overview

• Message type: E = Error

• Message class: ESH_SEARCH - ESH Search

• Message number: 359

• Message text: Export SWC: Obj.type &1 node &2 req. &3 attr group &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_SEARCH359 - Export SWC: Obj.type &1 node &2 req. &3 attr group &4 does not exist ?

  The SAP error message ESH_SEARCH359 typically occurs in the context of the SAP Enterprise Search (SAP ESH) when there is an issue related to the export of a Software Component (SWC) or when the system is unable to find a specific object type, node, or attribute group that is expected during the export process.
  
  Cause:
  The error message indicates that the system is trying to export a specific object type (denoted by &1), node (&2), and attribute group (&4), but it cannot find the required object or attribute group in the system. This can happen due to several reasons:
  
  Missing Configuration: The specified object type or attribute group may not be configured correctly in the system.
  Data Inconsistency: There may be inconsistencies in the data or configuration that prevent the system from locating the required elements.
  Transport Issues: If the SWC is being transported from one system to another, there may be issues with the