How To Fix ESH_HANA_FL_ADMIN058 - Job: No file is ready for search

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_HANA_FL_ADMIN - ESH HANA File Loader

• Message number: 058

• Message text: Job: No file is ready for search

What causes this issue?

The connector has an attribute with semantic "Content URL" but none of
the files is searchable (or no file exists).

System Response

The content of the files is currently not taken into account by search.

How to fix this error?

Go to 'File Loader Administration' -> Job Manager -> Detail.
Use the navigation link (details of the search connector -> 'General').

Procedure for System Administrators

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message ESH_HANA_FL_ADMIN058 - Job: No file is ready for search ?

  The SAP error message ESH_HANA_FL_ADMIN058 with the description "Job: No file is ready for search" typically occurs in the context of the SAP Enterprise Search (SAP ESH) when the system is unable to find any files that are ready for processing in the search job. This can happen for various reasons, and understanding the cause is essential for troubleshooting.
  Possible Causes:
  
  No Data Available: There may not be any data available in the source system that meets the criteria for indexing.
  Indexing Job Not Executed: The indexing job may not have been executed or completed successfully, leading to no files being generated for the search.
  File Generation Issues: There could be issues with the file generation process, such as errors in the extraction or transformation of data.
  Configuration Issues: Incorrect configuration settings in the search framework or the data source could prevent files from being generated.
  Job Scheduling Issues: The job responsible for generating the files may not be scheduled correctly or may have failed.
  
  Solutions:
  
  Check Data Availability: Ensure that there is data available in the source system that can be indexed. You may need to run a data extraction job to populate the necessary data.
  Run Indexing Job: Manually trigger the indexing job to see if it generates the necessary files. You can do this through the SAP GUI or the relevant transaction code (e.g., /IWFND/MAINT_SERVICE).
  Review Job Logs: Check the logs of the indexing job for any errors or warnings that might indicate why files are not being generated. This can provide insights into what went wrong.
  Verify Configuration: Review the configuration settings for the search framework and ensure that they are set up correctly. This includes checking the data source settings and the search connector configurations.
  Schedule Jobs Properly: Ensure that the jobs responsible for data extraction and indexing are scheduled correctly and are running as expected. You can use transaction codes like SM37 to monitor job statuses.
  Consult Documentation: Refer to SAP documentation or notes related to the specific version of SAP you are using for any known issues or additional troubleshooting steps.
  
  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 (transaction SLG1) for any related error messages that could provide more context about the issue.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it. If the issue persists, consider reaching out to SAP support for further assistance.