Do you have any question about this error?
Message type: E = Error
Message class: ESH_DB - ES: Dashboard
Message number: 012
Message text: Model import has not been attempted
Before search connectors can be created, the underlying model data needs
to be imported. This import has not yet run.
Enterprise Search is not set up, search is not possible.
Use task list (transaction STC01) SAP_ESH_INITIAL_SETUP_WRK_CLIENT to
trigger the import.
You can also start the ES-Cockpit (transaction ESH_COCKPIT), which will
likewise trigger the import.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
ESH_DB012
- Model import has not been attempted ?The SAP error message ESH_DB012, which states "Model import has not been attempted," typically occurs in the context of the SAP Enterprise Search (SAP ESH) framework. This error indicates that the system has not attempted to import a model, which is necessary for the search functionality to work correctly.
Causes:
- Configuration Issues: The model may not be properly configured in the system.
- Missing Dependencies: Required components or dependencies for the model may be missing or not activated.
- Authorization Issues: The user may not have the necessary authorizations to perform the model import.
- Technical Errors: There could be underlying technical issues, such as database connectivity problems or system inconsistencies.
- Model Not Activated: The model may not be activated in the system, preventing the import process from being initiated.
Solutions:
- Check Configuration: Verify that the model is correctly configured in the SAP ESH settings. Ensure that all necessary parameters are set.
- Activate the Model: If the model is not activated, activate it in the system. This can usually be done through the SAP GUI or relevant transaction codes.
- Review Authorizations: Ensure that the user attempting the import has the necessary authorizations. Check roles and permissions related to SAP ESH.
- Check Dependencies: Make sure that all required components and dependencies for the model are installed and activated.
- Review Logs: Check the system logs for any additional error messages or warnings that could provide more context about the issue.
- Re-run the Import: If the model was previously attempted but failed, try re-running the import process after addressing any identified issues.
- Consult Documentation: Refer to SAP documentation or notes related to the specific model and error message for additional troubleshooting steps.
Related Information:
If the issue persists after trying the above solutions, it may be beneficial to contact SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
ESH_DB011
No issues detected
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_DB010
Thresholds have to be in [0..1]
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_DB013
Model import has errors
What causes this issue? Before search connectors can be created, the underlying model data needs to be imported. This import has run, but ended with ...
ESH_DB014
Enterprise Search connection is not maintained
What causes this issue? The connection for Enterprise Search is not configured.System Response Searching is possible only for CDS-based connectors. ...
Click on this link to search all SAP messages.