Do you have any question about this error?
Message type: E = Error
Message class: ESH_EX - Extraction
Message number: 025
Message text: L'indexation en temps réel a été arrêtée de manière inattendue.
This message is issued if the last-executed process for ESH real-time
indexing has terminated<(>,<)> or has been terminated<(>,<)> before the
final status update. This situation is reported if the process for the
ESH real-time indexing is not running at the point of time of the check,
but the last recorded status is still wrongly indicating the process as
'running'. The reason for the process termination can no longer be
determined by the real-time indexing engine.
Possible causes:
The real-time indexing job has been cancelled manually
Work process has been terminated in SM50
Connectors have been deleted / ESH has been reset while real-time
indexing was running
System has been shut down or restarted while the real-time indexing
process was running
Real-time indexing process has terminated without being able to update
its status, for example, due to a runtime error
The real-time indexing process will automatically restart with the next
data package that arrives for indexing. If the issue was due to a
one-time incident (e.g. system shutdown, manual job cancellation) the
status will not occur the next time, and no further actions are
required. The next process execution will automatically reprocess all
entries which could not be processed because of the preceding job
termination.
If the message reoccurs each time the real-time indexing job runs (job
never completes successfully) check for object-related issues: for
example, check job logs in SM37 or check for runtime errors in ST22.
If you do not want to wait for the next auto-restart of the real-time
indexing process you can also restart the real-time indexing manually
from the ESH Administration Cockpit:
ESH Administration Cockpit: Go to System Settings and open the Real-Time
Indexing Administration.
Start the process by choosing 'Start'.
We recommend a manual restart if a lot of data to be indexed (open
change pointers) has accumulated in the real-time indexing queues.
If you do not have any search connectors which are relevant for
real-time indexing (for example because all search connectors have been
deleted in the meantime) an auto-restart will not be triggered. Also in
this case, we recommend a manual restart of the job to update to a final
status (the job will not execute anything in this case).
For more information on the concrete reason of failure, check process
logs in the ESH Administartation Cockpit, refer to the system log
(SM21), or check for runtime errors (ST22).
Le système émet un message d'erreur et ne vous permettra pas de poursuivre cette transaction tant que l'erreur n'est pas résolue.
Extrait du message d'erreur du système SAP. Copyright SAP SE.
ESH_EX025
- L'indexation en temps réel a été arrêtée de manière inattendue. ?Get instant SAP help. Start your 7-day free trial now.
ESH_EX024
L'indexation en temps réel n'est pas exécutée.
Message auto-explicatif Étant donné que SAP estime que ce message d'erreur spécifique est 'auto-explicatif', aucune autre information n'a été fou...
ESH_EX023
Exécution de l'indexation en temps réel
Message auto-explicatif Étant donné que SAP estime que ce message d'erreur spécifique est 'auto-explicatif', aucune autre information n'a été fou...
ESH_EX026
Arrêt du processus ; mise en attente du processus après exéc. actuelle
Message auto-explicatif Étant donné que SAP estime que ce message d'erreur spécifique est 'auto-explicatif', aucune autre information n'a été fou...
ESH_EX027
L'indexation en temps a été suspendue.
Message auto-explicatif Étant donné que SAP estime que ce message d'erreur spécifique est 'auto-explicatif', aucune autre information n'a été fou...
Cliquez sur ce lien pour rechercher tous les messages SAP.