!--a11y-->
Error Handling During Searches 
In Customizing for the search engine service, check whether the service is correctly configured. Choose SAP NetWeaver ® SAP Web Application Server ® System Administration ® Search Engine Service ® System Settings.
Check whether the TREX system is accessible. Perform the following availability test:
...
1. Start transaction SES_ADMIN.
2. Choose TREX Admin ® RFC Administration ® Connection Test.
If the system displays the error message No RFC connection when you perform the test, this means that the TREX system is not accessible. In this case, check whether the RFC destination data is correct (transaction SM59). For more information about setting up an RFC connection, see the SAP NetWeaver 2004s Search and Classification (TREX) installation guide.
You cannot find newly created or changed objects immediately because the TREX system does not perform a “live” search. You can only find these objects once the next delta indexing has taken place.
Check whether delta indexing has run successfully after the object was created or changed. Delta indexing is scheduled as a periodic job. In addition, you can trigger delta indexing directly by entering the transaction SES_ADMIN, and choosing the pushbutton Index Immediately ® Delta.
See the previous section.
You can only find attributes that already existed for the objects, but that were not previously added to the TREX index, after the next time the TREX system performs a complete indexing.
You must perform a complete indexing (not delta indexing) because this is not a change to the objects concerned and therefore no change pointer is written to the change pointer table. This means that this change cannot be added during delta indexing. Therefore, you must perform a complete indexing.
To perform a complete indexing, start transaction SES_ADMIN.