SAP ABAP Message Class ESH_CHECK_CONN (Check connector consistency)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-EIM-ESH (Application Component) NetWeaver Enterprise Search
⤷ S_ESH_ENG_TOOLS (Package) Tools for BOS
⤷ BC-EIM-ESH (Application Component) NetWeaver Enterprise Search
⤷ S_ESH_ENG_TOOLS (Package) Tools for BOS
Attributes
Message class | ESH_CHECK_CONN | |
Short Description | Check connector consistency | |
Changed On | 20140121 | |
Last Changed At | 103716 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | Conversion error by checking the existence of physical indexes on TREX &1 | The short text describes the object sufficiently | |
2 | 002 | Request &1 of connector &2 is inactive. It is not searchable | The short text describes the object sufficiently | |
3 | 003 | Error while searching for request &1 in connector &2 | The short text describes the object sufficiently | |
4 | 004 | No search results for &1 request &2; check authoriz./indexing in back end | The short text describes the object sufficiently | |
5 | 005 | Faulty physical index &1 on TREX &2: | The short text describes the object sufficiently | |
6 | 006 | Connector &1 invalid in buffer (does not exist/no requests/no nodes) | The short text describes the object sufficiently | |
7 | 007 | Conversion error by checking the existence of join indexes on TREX &1 | The short text describes the object sufficiently | |
8 | 008 | Faulty join index &1 on TREX &2: | The short text describes the object sufficiently | |
9 | 009 | Error by get connectivity for the connector &1 | The short text describes the object sufficiently | |
10 | 010 | TREX version is too old | The short text describes the object sufficiently | |
11 | 011 | Connector &1 is not prepared (no nodes/no requests) | The short text describes the object sufficiently | |
12 | 012 | Request &1 of connector &2 not in buffer; update buffer | The short text describes the object sufficiently | |
13 | 013 | Runtime buffer is consistent concerning requests for connector &1 | The short text describes the object sufficiently | |
14 | 014 | No active requests available for connector &1 | The short text describes the object sufficiently | |
15 | 015 | No requests attributes available for connector &1 | The short text describes the object sufficiently | |
16 | 016 | Attr. of request &1, connector &2 do not match buffer attributes | The short text describes the object sufficiently | |
17 | 017 | Runtime buffer is consistent concerning status for connector &1 | The short text describes the object sufficiently | |
18 | 018 | Status of connector &1 does not match buffer status; update buffer | The short text describes the object sufficiently | |
19 | 019 | System &1 is a back end. Check possible only on hub or for embedded sys. | The short text describes the object sufficiently | |
20 | 020 | Error while getting categories from the runtime buffer | The short text describes the object sufficiently | |
21 | 021 | Runtime buffer is consistent concerning the category of connector &1 | The short text describes the object sufficiently | |
22 | 022 | Category &1 not available in the buffer; update buffer | The short text describes the object sufficiently | |
23 | 023 | Response attr. of connector &1 do not match response attr. in buffer | The short text describes the object sufficiently | |
24 | 024 | Runtime buffer is consistent with reg. to response attr. of connector &1 | The short text describes the object sufficiently | |
25 | 025 | Connector &1 is searchable | The short text describes the object sufficiently | |
26 | 026 | Error by creation of subconnector_ID based on object_type &1 and node &2 | The short text describes the object sufficiently | |
27 | 027 | Subconnector &1 has no requests | The short text describes the object sufficiently | |
28 | 028 | Runtime buffer is consistent with reg. to request attr. of connector &1 | The short text describes the object sufficiently | |
29 | 029 | No sizing information possible because TREX server is not available | The short text describes the object sufficiently | |
30 | 030 | Why are the following requests inactive? | The short text describes the object sufficiently | |
31 | 031 | Connector &1 has no nodes. No more checks are possible | The short text describes the object sufficiently | |
32 | 032 | Connector &1 has no requests. No more checks are possible | The short text describes the object sufficiently | |
33 | 033 | Communication failure while accessing TREX with RFC destination &1 | The short text describes the object sufficiently | |
34 | 034 | ICM communication failure while accessing TREX with RFC desination &1 | The short text describes the object sufficiently | |
35 | 035 | ICM comm. failure while accessing TREX with &1 from app. server &2 | The short text describes the object sufficiently | |
36 | 036 | No appropriate extraction implementation exists for object type &1 | The short text describes the object sufficiently | |
37 | 037 | The default request of connector &1 is inactive | The short text describes the object sufficiently | |
38 | 038 | The ODP connector &1 is consistent | The short text describes the object sufficiently | |
39 | 039 | Inconsistency for logsys &1; delete all conn. for &1, create them again | Space: object requires documentation | |
40 | 040 | Connector &1 has no response fields. Search cannot return any results. | The short text describes the object sufficiently | |
41 | 041 | No crawler(s) available for connector &1 | The short text describes the object sufficiently | |
42 | 042 | Crawler &1 of the connector &2 has status '&3' | The short text describes the object sufficiently | |
43 | 043 | Index &1 of connector &2 is corrupt on Trex &3. | The short text describes the object sufficiently | |
44 | 044 | Corrupted index &1 for connector &2 was corrected on Trex &3. | The short text describes the object sufficiently | |
45 | 045 | Corrupted index &1 couldn't be repaired. Delete and Recreate conn &2 | The short text describes the object sufficiently | |
46 | 046 | The authorization index &1 is empty. Do indexing of authorization data | The short text describes the object sufficiently | |
47 | 047 | &1 of model &2 is inactive during a switch off of a field or node. | The short text describes the object sufficiently | |
48 | 048 | For &1 the following authorization update tasks have failed on &2: | The short text describes the object sufficiently | |
49 | 049 | Update of authorization index &1 has terminated unsuccessfully | The short text describes the object sufficiently | |
50 | 050 | Update of normalized authorization index &1 has terminated unsuccessfully | The short text describes the object sufficiently | |
51 | 051 | Object USER_AUTHORITY did not get updated for authorization object &1 | The short text describes the object sufficiently | |
52 | 052 | Database trigger activation for authorization check &1 was unsuccessful | The short text describes the object sufficiently | |
53 | 058 | The short text describes the object sufficiently |
History
Last changed on/by | 20140121 | SAP | |
SAP Release Created in | 730 |