Do you have any question about this error?
Message type: E = Error
Message class: ESH_ADM_MSG - ESH Administration and Monitoring Tool
Message number: 321
Message text: Connector '&1' was deleted from ESH_ADM_SC_MAIN
The connection key of the connector does not exist in table
ESH_ADM_RFC_CONN.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
There are no further steps necessary.
Error message extract from SAP system. Copyright SAP SE.
ESH_ADM_MSG321
- Connector '&1' was deleted from ESH_ADM_SC_MAIN ?The SAP error message ESH_ADM_MSG321 indicates that a connector has been deleted from the ESH_ADM_SC_MAIN table in the SAP Enterprise Search (ESH) system. This message typically arises in the context of managing connectors within the ESH administration.
Cause:
The error can occur due to several reasons:
- Manual Deletion: A connector may have been manually deleted by an administrator or through a configuration change.
- System Cleanup: A system cleanup process might have removed the connector if it was deemed obsolete or not in use.
- Configuration Issues: There may be inconsistencies or misconfigurations in the ESH setup that led to the deletion of the connector.
- Transport Issues: If the connector was part of a transport request that was not properly imported, it could lead to this error.
Solution:
To resolve the issue, you can take the following steps:
Check Connector Status: Verify the status of the connector in the ESH administration interface. Ensure that it is still configured and active.
Recreate the Connector: If the connector was deleted and is required, you may need to recreate it. This can be done through the ESH administration tools:
- Go to the ESH administration transaction (usually
EshAdmin
or similar).- Navigate to the connectors section and create a new connector with the same settings as the deleted one.
Review Logs: Check the system logs for any additional error messages or warnings that might provide more context on why the connector was deleted.
Transport Management: If the issue is related to transport, ensure that all necessary transport requests have been properly imported and that there are no inconsistencies in the system landscape.
Consult Documentation: Refer to the SAP documentation for Enterprise Search for specific guidelines on managing connectors and troubleshooting related issues.
Contact SAP Support: If the issue persists and you cannot determine the cause, consider reaching out to SAP support for assistance.
Related Information:
By following these steps, you should be able to address the ESH_ADM_MSG321 error and restore the functionality of the affected connector.
Get instant SAP help. Start your 7-day free trial now.
ESH_ADM_MSG320
Connector was changed from '&1' to '&2'
What causes this issue? After a system copy or a client copy the connector was not correct adjusted.System Response The system issues an error messa...
ESH_ADM_MSG319
Select a single line
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_ADM_MSG322
Changes have been saved
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_ADM_MSG323
Error reading data
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.