Message Number list used by SAP ABAP Class CL_ESH_TO_CHECK_CONSISTENCY (Check Connector Consistency)
SAP ABAP Class CL_ESH_TO_CHECK_CONSISTENCY (Check Connector Consistency) is using
# Object Type Object Name Object Description Note
     
1 Message Number  ESH_BOS_INDEX_CTRL - 056 Error while composing the index name for object type &1, node &2, type &3
2 Message Number  ESH_BOS_INDEX_CTRL - 117 Error while checking the request attributes of object &1 node &2 req. &3
3 Message Number  ESH_BOS_INDEX_CTRL - 056 Error while composing the index name for object type &1, node &2, type &3
4 Message Number  ESH_CHECK_CONN - 039 Inconsistency for logsys &1; delete all conn. for &1, create them again
5 Message Number  ESH_CHECK_CONN - 026 Error by creation of subconnector_ID based on object_type &1 and node &2
6 Message Number  ESH_CHECK_CONN - 038 The ODP connector &1 is consistent
7 Message Number  ESH_CHECK_CONN - 037 The default request of connector &1 is inactive
8 Message Number  ESH_CHECK_CONN - 036 No appropriate extraction implementation exists for object type &1
9 Message Number  ESH_CHECK_CONN - 035 ICM comm. failure while accessing TREX with &1 from app. server &2
10 Message Number  ESH_CHECK_CONN - 034 ICM communication failure while accessing TREX with RFC desination &1
11 Message Number  ESH_CHECK_CONN - 033 Communication failure while accessing TREX with RFC destination &1
12 Message Number  ESH_CHECK_CONN - 032 Connector &1 has no requests. No more checks are possible
13 Message Number  ESH_CHECK_CONN - 031 Connector &1 has no nodes. No more checks are possible
14 Message Number  ESH_CHECK_CONN - 030 Why are the following requests inactive?
15 Message Number  ESH_CHECK_CONN - 029 No sizing information possible because TREX server is not available
16 Message Number  ESH_CHECK_CONN - 028 Runtime buffer is consistent with reg. to request attr. of connector &1
17 Message Number  ESH_CHECK_CONN - 027 Subconnector &1 has no requests
18 Message Number  ESH_CHECK_CONN - 052 Database trigger activation for authorization check &1 was unsuccessful
19 Message Number  ESH_CHECK_CONN - 040 Connector &1 has no response fields. Search cannot return any results.
20 Message Number  ESH_CHECK_CONN - 041 No crawler(s) available for connector &1
21 Message Number  ESH_CHECK_CONN - 042 Crawler &1 of the connector &2 has status '&3'
22 Message Number  ESH_CHECK_CONN - 043 Index &1 of connector &2 is corrupt on Trex &3.
23 Message Number  ESH_CHECK_CONN - 043 Index &1 of connector &2 is corrupt on Trex &3.
24 Message Number  ESH_CHECK_CONN - 044 Corrupted index &1 for connector &2 was corrected on Trex &3.
25 Message Number  ESH_CHECK_CONN - 044 Corrupted index &1 for connector &2 was corrected on Trex &3.
26 Message Number  ESH_CHECK_CONN - 045 Corrupted index &1 couldn't be repaired. Delete and Recreate conn &2
27 Message Number  ESH_CHECK_CONN - 045 Corrupted index &1 couldn't be repaired. Delete and Recreate conn &2
28 Message Number  ESH_CHECK_CONN - 046 The authorization index &1 is empty. Do indexing of authorization data
29 Message Number  ESH_CHECK_CONN - 047 &1 of model &2 is inactive during a switch off of a field or node.
30 Message Number  ESH_CHECK_CONN - 048 For &1 the following authorization update tasks have failed on &2:
31 Message Number  ESH_CHECK_CONN - 049 Update of authorization index &1 has terminated unsuccessfully
32 Message Number  ESH_CHECK_CONN - 050 Update of normalized authorization index &1 has terminated unsuccessfully
33 Message Number  ESH_CHECK_CONN - 051 Object USER_AUTHORITY did not get updated for authorization object &1
34 Message Number  ESH_CHECK_CONN - 011 Connector &1 is not prepared (no nodes/no requests)
35 Message Number  ESH_CHECK_CONN - 001 Conversion error by checking the existence of physical indexes on TREX &1
36 Message Number  ESH_CHECK_CONN - 002 Request &1 of connector &2 is inactive. It is not searchable
37 Message Number  ESH_CHECK_CONN - 003 Error while searching for request &1 in connector &2
38 Message Number  ESH_CHECK_CONN - 003 Error while searching for request &1 in connector &2
39 Message Number  ESH_CHECK_CONN - 004 No search results for &1 request &2; check authoriz./indexing in back end
40 Message Number  ESH_CHECK_CONN - 004 No search results for &1 request &2; check authoriz./indexing in back end
41 Message Number  ESH_CHECK_CONN - 005 Faulty physical index &1 on TREX &2:
42 Message Number  ESH_CHECK_CONN - 006 Connector &1 invalid in buffer (does not exist/no requests/no nodes)
43 Message Number  ESH_CHECK_CONN - 006 Connector &1 invalid in buffer (does not exist/no requests/no nodes)
44 Message Number  ESH_CHECK_CONN - 006 Connector &1 invalid in buffer (does not exist/no requests/no nodes)
45 Message Number  ESH_CHECK_CONN - 006 Connector &1 invalid in buffer (does not exist/no requests/no nodes)
46 Message Number  ESH_CHECK_CONN - 006 Connector &1 invalid in buffer (does not exist/no requests/no nodes)
47 Message Number  ESH_CHECK_CONN - 006 Connector &1 invalid in buffer (does not exist/no requests/no nodes)
48 Message Number  ESH_CHECK_CONN - 007 Conversion error by checking the existence of join indexes on TREX &1
49 Message Number  ESH_CHECK_CONN - 008 Faulty join index &1 on TREX &2:
50 Message Number  ESH_CHECK_CONN - 025 Connector &1 is searchable
51 Message Number  ESH_CHECK_CONN - 012 Request &1 of connector &2 not in buffer; update buffer
52 Message Number  ESH_CHECK_CONN - 013 Runtime buffer is consistent concerning requests for connector &1
53 Message Number  ESH_CHECK_CONN - 014 No active requests available for connector &1
54 Message Number  ESH_CHECK_CONN - 014 No active requests available for connector &1
55 Message Number  ESH_CHECK_CONN - 015 No requests attributes available for connector &1
56 Message Number  ESH_CHECK_CONN - 016 Attr. of request &1, connector &2 do not match buffer attributes
57 Message Number  ESH_CHECK_CONN - 017 Runtime buffer is consistent concerning status for connector &1
58 Message Number  ESH_CHECK_CONN - 018 Status of connector &1 does not match buffer status; update buffer
59 Message Number  ESH_CHECK_CONN - 019 System &1 is a back end. Check possible only on hub or for embedded sys.
60 Message Number  ESH_CHECK_CONN - 020 Error while getting categories from the runtime buffer
61 Message Number  ESH_CHECK_CONN - 021 Runtime buffer is consistent concerning the category of connector &1
62 Message Number  ESH_CHECK_CONN - 022 Category &1 not available in the buffer; update buffer
63 Message Number  ESH_CHECK_CONN - 023 Response attr. of connector &1 do not match response attr. in buffer
64 Message Number  ESH_CHECK_CONN - 024 Runtime buffer is consistent with reg. to response attr. of connector &1