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

SAP Error Message - Details

• 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 transport itself, leading to missing objects.
  Version Mismatch: The version of the software component may not match the expected version, leading to missing attributes or nodes.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Configuration:
  
  Verify that the object type and attribute group mentioned in the error message are correctly configured in the system.
  Use transaction codes like SE11 (Data Dictionary) or SE80 (Object Navigator) to check the existence of the object type and attribute group.
  
  
  
  Review Transport Requests:
  
  If the error occurred during a transport, check the transport request for any missing objects or components.
  Ensure that all necessary objects are included in the transport request.
  
  
  
  Consistency Check:
  
  Perform a consistency check on the relevant components to identify any discrepancies.
  Use transaction SLG1 to check for logs related to the error and gather more information.
  
  
  
  Recreate Missing Objects:
  
  If the object type or attribute group is indeed missing, you may need to recreate it or restore it from a backup.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific version of SAP ESH you are using for any known issues or additional troubleshooting steps.
  
  
  
  Contact SAP Support:
  
  If the issue persists after trying the above steps, consider reaching out to SAP Support for further assistance. Provide them with the error message details and any relevant logs.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  System Logs: Review system logs for any additional error messages or warnings that may provide context for the issue.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.