ESH_CHECK_CONN - Check connector consistency
The following messages are stored in message class ESH_CHECK_CONN: Check connector consistency.
It is part of development package S_ESH_ENG_TOOLS in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "Tools for BOS".
It is part of development package S_ESH_ENG_TOOLS in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "Tools for BOS".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Error checking availability of physical indexes. Destination used: &1 |
| 002 | Request &1 of connector &2 is inactive. It is not searchable |
| 003 | Error while searching for request &1 in connector &2 |
| 004 | No search results for &1 request &2; check authoriz./indexing in back end |
| 005 | Faulty physical index &1 on TREX &2: |
| 006 | Connector &1 invalid in data base (does not exist/no requests/no nodes) |
| 007 | Error checking availability of join indexes. Destination used: &1 |
| 008 | Faulty join index &1&2 on TREX '&3' |
| 009 | Error by get connectivity for the connector &1 |
| 010 | TREX version is too old |
| 011 | Conn. &1 not searchable(no nodes/no requests/update buffer in processing) |
| 012 | Request &1 of connector &2 not in buffer; update buffer |
| 013 | Runtime buffer is consistent concerning requests for connector &1 |
| 014 | No active requests available for connector &1 |
| 015 | No requests attributes available for connector &1 |
| 016 | Attr. of request &1, connector &2 do not match buffer attributes |
| 017 | Runtime buffer is consistent concerning status for connector &1 |
| 018 | Status of connector &1 does not match buffer status; update buffer |
| 019 | System &1 is a back end. Check possible only on hub or for embedded sys. |
| 020 | Error while getting categories from the runtime buffer |
| 021 | Runtime buffer is consistent concerning the category of connector &1 |
| 022 | Category &1 not available in the buffer; update buffer |
| 023 | Response attr. of connector &1 do not match response attr. in buffer |
| 024 | Runtime buffer is consistent with reg. to response attr. of connector &1 |
| 025 | Connector &1 is searchable |
| 026 | Error by creation of subconnector_ID based on object_type &1 and node &2 |
| 027 | Subconnector &1 has no requests |
| 028 | Runtime buffer is consistent with reg. to request attr. of connector &1 |
| 029 | No sizing information possible because TREX server is not available |
| 030 | Why are the following requests inactive? |
| 031 | Connector &1 has no nodes. No more checks are possible |
| 032 | Connector &1 has no requests. No more checks are possible |
| 033 | Communication failure while accessing TREX with RFC destination &1 |
| 034 | ICM communication failure while accessing TREX with RFC desination &1 |
| 035 | ICM comm. failure while accessing TREX with &1 from app. server &2 |
| 036 | No appropriate extraction implementation exists for object type &1 |
| 037 | The default request of connector &1 is inactive |
| 038 | The ODP connector &1 is consistent |
| 039 | Inconsistency for logsys &1; delete all conn. for &1, create them again |
| 040 | Connector &1 has no response fields. Search cannot return any results. |
| 041 | No crawler(s) available for connector &1 |
| 042 | Crawler &1 of the connector &2 has status '&3' |
| 043 | Index &1 of connector &2 is corrupt on Trex &3. |
| 044 | Corrupted index &1 for connector &2 was corrected on Trex &3. |
| 045 | Corrupted index &1 couldn't be repaired. Delete and Recreate conn &2 |
| 046 | The authorization index &1 is empty. Do indexing of authorization data |
| 047 | &1 of model &2 is inactive during a switch off of a field or node |
| 048 | For &1 the following authorization update tasks have failed on &2: |
| 049 | Update of authorization index &1 has terminated unsuccessfully |
| 050 | Update of normalized authorization index &1 has terminated unsuccessfully |
| 051 | Object USER_AUTHORITY did not get updated for authorization object &1 |
| 052 | Database trigger activation for authorization check &1 was unsuccessful |
| 053 | Connector &1 has no data or connector &1 is not indexed |
| 054 | No user authorizations for conn. &1 or user authorization are not indexed |
| 055 | Connector &1 is consistent. |
| 056 | Connector &1 (CDS) has no data |
| 059 | Connector &1 with request &2 is searchable |
| 060 | for physical index : &1 |
| 061 | with Trex destination :&1 |
| 062 | for logical index : &1 |
| 063 | Runtime buffer ist consistent for connector &1 |
| 064 | Subconnector &1 with request &2 is searchable |
| 065 | &1&2&3&4 |
| 066 | Join index &1&2 is missing on Trex Destination '&3' |
| 067 | Join index &1&2 is missing on SAP HANA Connection '&3' |
| 068 | Destination/connectivity for the search connector could not be determined |
| 069 | Connection GUID not specified |
| 070 | Check connectivities in tables ESH_ADM_RFC_CONN / ESH_ADM_GEN_CONN |
| 071 | Last activation job has failed - check the connector preparation logs |
| 072 | Connector &1 has been deactivated |
| 073 | Connector &1 is in process of being updated |
| 074 | Check for running jobs and refresh display after job completion |
| 075 | Connector &1 is prepared, but not yet active |
| 076 | Schedule indexing for all objects used by the connector |
| 077 | Authorization update for connector &1 has failed |
| 078 | Model &1 has changes("Modified" indicator is set), update connector &2 |
| 079 | Connector &1 is not searchable |
| 080 | Connector &1 is currently not available |
| 081 | Model &2 has model &1 as successor. It could be replaced in the Fiori UI |
| 082 | Test search not executed for connector &1 due to system failure: &2 |
| 083 | Test search not executed for connector &1 due to communication failure:&2 |
| 084 | Test search not executed for connector &1 due to resource failure: &2 |
| 085 | Test search not executed for connector &1 due to unknown failure: &2 |
| 086 | Test search not executed for connector &1 due to deserialization failure |
| 087 | Test search not executed for connector &1 due to serialization failure |
| 088 | The active default request of the connector &1 is an internal request |
| 089 | Current system is a copy of another system. No check for connector &1 |
| 090 | There are duplicate local connections. No check for connector &1 |
| 091 | &1: For connector &2 no cardinality issue has been detected |
| 092 | Connector &1 was created in the software component &2 |
| 093 | The current session does not contain the current cache |
| 094 | Upgrade is running. Conn. consistency check is not possible. Try later. |
| 095 | Another CDS-activation is running. No Consist.Check possible. Try later. |
| 096 | Connector &1 was not checked |
| 097 | To repeat the check restart the current applic. (e.g. Cockpit/Tasklist) |
| 098 | Consist.Check is supported only for local connectors. No check was done. |