The information in this section concerns situations in which Search routing appears to be correctly configured, but the production site is unable to connect to the Search environment. The main symptom of this problem is that you are unable to perform a search from the production site; you may also encounter an “environment not found” error.
When attempting to diagnose a connection problem, first perform the following checks:
Check the ATG console for startup errors related to repositories or lock managers.
Verify the database host and schema that contains the shared Search repository data
If neither step makes the source of the problem clear, continue through the checks described in the sections that follow.
