SAP ABAP Message Class ESH_ADAPT_MSG (Adapter Messages)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-EIM-ESH (Application Component) NetWeaver Enterprise Search
⤷
S_ESH_CONTENT_FED_ADAPTERS (Package) Adapters for Federated Search
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-EIM-ESH (Application Component) NetWeaver Enterprise Search⤷
S_ESH_CONTENT_FED_ADAPTERS (Package) Adapters for Federated Search 
Attributes
| Message class |  |
ESH_ADAPT_MSG |
| Short Description |  |
Adapter Messages |
| Changed On |  |
20130531 |
| Last Changed At |  |
091200 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
&1 | The short text describes the object sufficiently | |
| 2 | 001 |
Adapter &1: Error constructing the response | The short text describes the object sufficiently | |
| 3 | 002 |
Adapter &1: No KM connectors delivered for searching | The short text describes the object sufficiently | |
| 4 | 003 |
Error in connectivity manager of &1 | The short text describes the object sufficiently | |
| 5 | 004 |
Error during creation of the logical port for adapter &1 | The short text describes the object sufficiently | |
| 6 | 005 |
Error while getting indexes from KM: &1 | The short text describes the object sufficiently | |
| 7 | 006 |
No connectivity details available for adapter &1 | The short text describes the object sufficiently | |
| 8 | 007 |
Missing input parameters for defining a KM connectivity | The short text describes the object sufficiently | |
| 9 | 008 |
Error in index manager of &1. Index service not available | The short text describes the object sufficiently | |
| 10 | 009 |
Could not delete logical port &1 | The short text describes the object sufficiently | |
| 11 | 010 |
Error during metadata retrieval in adapter &1 | The short text describes the object sufficiently | |
| 12 | 011 |
Error during search in adapter &1 | The short text describes the object sufficiently | |
| 13 | 012 |
Error during response conversion in adapter &1 | The short text describes the object sufficiently | |
| 14 | 013 |
Missing input parameters for defining a WS connectivity | The short text describes the object sufficiently | |
| 15 | 014 |
Error during connectivity creation in adapter &1 | The short text describes the object sufficiently | |
| 16 | 015 |
Error during connectivity deletion in adapter &1 | The short text describes the object sufficiently | |
| 17 | 016 |
Error while accessing KM server/KM index management service | The short text describes the object sufficiently | |
| 18 | 017 |
Could not create handler for log.port &1. Check if KM system is available | The short text describes the object sufficiently | |
| 19 | 018 |
No properties available for log.port &1. Check if KM system is available | The short text describes the object sufficiently | |
| 20 | 019 |
No HTTP client could be created for destination &1 (by ping-destination) | The short text describes the object sufficiently | |
| 21 | 020 |
Ping for destination &1 unsuccessful with message &2 (by send) | The short text describes the object sufficiently | |
| 22 | 021 |
Ping for destination &1 unsuccessful with message &2 (by receive) | The short text describes the object sufficiently | |
| 23 | 022 |
Communication unsuccessful in adapter &1 | The short text describes the object sufficiently | |
| 24 | 023 |
Could not create handler for log.port &1. Check if WS is available | The short text describes the object sufficiently | |
| 25 | 024 |
No properties available for log.port &1. Check if WS is available | The short text describes the object sufficiently | |
| 26 | 025 |
Web service (proxy &1) not available | The short text describes the object sufficiently | |
| 27 | 026 |
Duplicate logical port name &1 | The short text describes the object sufficiently | |
| 28 | 027 |
Characters &1 are not allowed in logical port name | The short text describes the object sufficiently | |
| 29 | 028 |
Blanks are not allowed in logical port name | The short text describes the object sufficiently | |
| 30 | 029 |
Characters &1 and blanks are not allowed in logical port name | The short text describes the object sufficiently | |
| 31 | 030 |
Error calling the external HTTP service &1 | Space: object requires documentation | |
| 32 | 031 |
--> User account/authorization (S_RFCACL) is missing in back-end system | The short text describes the object sufficiently | |
| 33 | 032 |
Error building template type reference | The short text describes the object sufficiently | |
| 34 | 033 |
Error while structuring the display in the SAP List Viewer | The short text describes the object sufficiently | |
| 35 | 034 |
Logical port &1 cannot be deleted | Space: object requires documentation | |
| 36 | 035 |
Logical port &1 cannot be deleted | Space: object requires documentation | |
| 37 | 036 |
Action was completed successfully | The short text describes the object sufficiently | |
| 38 | 037 |
You are not authorized to delete logical ports for data provider services | The short text describes the object sufficiently | |
| 39 | 038 |
Records with connection GUID &1 could not be deleted | Space: object requires documentation | |
| 40 | 039 |
Logical port &1 is already synchronous | The short text describes the object sufficiently | |
| 41 | 040 |
Logical port &1 cannot be synchronized | Space: object requires documentation | |
| 42 | 041 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 43 | 042 |
Record with connection GUID &1 locked by user &2 | The short text describes the object sufficiently | |
| 44 | 043 |
Business object &1 is not supported in system &2 | The short text describes the object sufficiently | |
| 45 | 044 |
Error parsing the OpenSearch results | The short text describes the object sufficiently | |
| 46 | 045 |
Characters &1 are not allowed in RFC destination name | The short text describes the object sufficiently | |
| 47 | 046 |
Blanks are not allowed in RFC destination name | The short text describes the object sufficiently | |
| 48 | 047 |
Characters &1 and blanks are not allowed in RFC destination name | The short text describes the object sufficiently | |
| 49 | 048 |
RFC destination name must not be initial | The short text describes the object sufficiently | |
| 50 | 049 |
Internal error creating RFC destination &1 | The short text describes the object sufficiently | |
| 51 | 050 |
The authentication method for the RFC destination &1 requires logon data | The short text describes the object sufficiently | |
| 52 | 051 |
Character &1 is not allowed at position 1 in RFC destination name | The short text describes the object sufficiently | |
| 53 | 052 |
Internal error reading RFC destination &1 | The short text describes the object sufficiently | |
| 54 | 053 |
Internal error generating ID for RFC destination &1 | The short text describes the object sufficiently | |
| 55 | 054 |
Internal error deleting RFC destination &1 | The short text describes the object sufficiently | |
| 56 | 055 |
RFC destination &1 is locked by another user. Deletion not possible | The short text describes the object sufficiently | |
| 57 | 056 |
Logical port &1 does not exist | The short text describes the object sufficiently | |
| 58 | 057 |
Logical port name must not be initial | The short text describes the object sufficiently |
History
| Last changed on/by | |
20130531 | SAP |
| SAP Release Created in | 712 |
