SAP ABAP Message Class ESH_ADM_BIN_MSG (ESH_ADM_BIN_MSG)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-EIM-ESH (Application Component) NetWeaver Enterprise Search
⤷
S_ESH_ENG_MONITORING_ADMIN (Package) Monitoring and Admin Component
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-EIM-ESH (Application Component) NetWeaver Enterprise Search⤷
S_ESH_ENG_MONITORING_ADMIN (Package) Monitoring and Admin Component 
Attributes
| Message class |  |
ESH_ADM_BIN_MSG |
| Short Description |  |
|
| Changed On |  |
20130531 |
| Last Changed At |  |
091201 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 2 | 001 |
Enter a value for the following key parameter &1 | The short text describes the object sufficiently | |
| 3 | 002 |
Record for keys &1 &2 &3 &4 does not exist | The short text describes the object sufficiently | |
| 4 | 003 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 5 | 004 |
Connector with key ID &1 type &2 could not be found | The short text describes the object sufficiently | |
| 6 | 005 |
Namespace with key ID &1 could not be found | The short text describes the object sufficiently | |
| 7 | 006 |
Object type of software component &1 with key ID &2 could not be found | The short text describes the object sufficiently | |
| 8 | 007 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 9 | 008 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 10 | 009 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 11 | 010 |
Parameter &1 could not be found in generic connectivity database | The short text describes the object sufficiently | |
| 12 | 011 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 13 | 012 |
Record with key &1 &2 &3 is locked for user &4 | The short text describes the object sufficiently | |
| 14 | 013 |
Error during determination of common data for connector &1 type &2 | The short text describes the object sufficiently | |
| 15 | 014 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 16 | 015 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 17 | 016 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 18 | 017 |
Web service (proxy &1) not available | The short text describes the object sufficiently | |
| 19 | 018 |
No root node for software component &1 object type &2 | The short text describes the object sufficiently | |
| 20 | 019 |
Not authorized to change DPS templates | The short text describes the object sufficiently | |
| 21 | 020 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 22 | 021 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 23 | 022 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 24 | 023 |
No data available for restart | The short text describes the object sufficiently | |
| 25 | 024 |
Connection GUID could not be determined | The short text describes the object sufficiently | |
| 26 | 025 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 27 | 026 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 28 | 027 |
Scenario &1 is not valid | The short text describes the object sufficiently | |
| 29 | 028 |
Status &1 is not valid | The short text describes the object sufficiently | |
| 30 | 029 |
Error during creation of error GUID | The short text describes the object sufficiently | |
| 31 | 030 |
No MIME type for current xstring | The short text describes the object sufficiently | |
| 32 | 031 |
Initial value for current xstring | The short text describes the object sufficiently | |
| 33 | 032 |
No key fields for current xstring | The short text describes the object sufficiently | |
| 34 | 033 |
Error during conversion of xstring | The short text describes the object sufficiently | |
| 35 | 034 |
Internal error concerning key fields for xstring | The short text describes the object sufficiently | |
| 36 | 035 |
Internal error concerning language field for xstring | The short text describes the object sufficiently | |
| 37 | 036 |
Default language for current xstring taken from TREX | The short text describes the object sufficiently | |
| 38 | 037 |
No language for current xstring; not even default language | The short text describes the object sufficiently | |
| 39 | 038 |
Error from TREX with code &1 | The short text describes the object sufficiently | |
| 40 | 039 |
Content of xstring could not be converted into HTML; TREX code &1 | The short text describes the object sufficiently | |
| 41 | 040 |
Reorganization could not be done | The short text describes the object sufficiently | |
| 42 | 041 |
Error during conversion of timestamp | The short text describes the object sufficiently | |
| 43 | 042 |
At least one error occurred during indexing of file data (xstring or URL) | Space: object requires documentation | |
| 44 | 043 |
No MIME type for current URL | The short text describes the object sufficiently | |
| 45 | 044 |
No MIME type for current DPS URL | The short text describes the object sufficiently | |
| 46 | 045 |
At least one error occurred during indexing of file data (xstring or URL) | The short text describes the object sufficiently | |
| 47 | 046 |
No MIME type for current URL | The short text describes the object sufficiently | |
| 48 | 047 |
Initial value for current URL | The short text describes the object sufficiently | |
| 49 | 048 |
No key fields for current URL | The short text describes the object sufficiently | |
| 50 | 049 |
Internal error concerning language field for URL | The short text describes the object sufficiently | |
| 51 | 050 |
Default language for current URL taken from TREX | The short text describes the object sufficiently | |
| 52 | 051 |
No language for current URL; not even default language | The short text describes the object sufficiently | |
| 53 | 052 |
Content of URL could not be converted into HTML; TREX code &1 | The short text describes the object sufficiently | |
| 54 | 053 |
Return code 401 for URL: URL no longer valid or authorization issue | The short text describes the object sufficiently | |
| 55 | 054 |
No MIME type for current URL in DPS | The short text describes the object sufficiently | |
| 56 | 055 |
Parameter error for DPS: All URLs skipped | The short text describes the object sufficiently | |
| 57 | 056 |
Initial value for current URL in DPS | The short text describes the object sufficiently | |
| 58 | 057 |
MIME type is invalid | The short text describes the object sufficiently | |
| 59 | 058 |
For URL &1 bypass of TREX wanted but not possible due to HTTPS | The short text describes the object sufficiently | |
| 60 | 059 |
Wrong construction for content URL of document service | The short text describes the object sufficiently | |
| 61 | 060 |
Multiple occurrence of endpoint in content URL of DPS URL | The short text describes the object sufficiently | |
| 62 | 061 |
Wrong construction for content URL of document service, path not in URL | The short text describes the object sufficiently | |
| 63 | 062 |
Error during determination of DPS path | The short text describes the object sufficiently | |
| 64 | 063 |
Error occurred during indexing: Connector ID could not be determined | The short text describes the object sufficiently | |
| 65 | 064 |
Error in Web service framework (DPS) | The short text describes the object sufficiently | |
| 66 | 065 |
Logical port &1 does not exist anymore (DPS) | The short text describes the object sufficiently | |
| 67 | 066 |
No properties available for log.port &1 (DPS). Is service is available? | The short text describes the object sufficiently | |
| 68 | 067 |
Error getting handle for application log | The short text describes the object sufficiently | |
| 69 | 068 |
Parameter object type does not exist in DPS URL | The short text describes the object sufficiently | |
| 70 | 069 |
Error getting instance for application log | The short text describes the object sufficiently | |
| 71 | 070 |
Parameter content_url does not exist in DPS URL | The short text describes the object sufficiently | |
| 72 | 071 |
Parameter destination does not exist in DPS URL | The short text describes the object sufficiently | |
| 73 | 072 |
Parameter error_guid does not exist in DPS URL | The short text describes the object sufficiently | |
| 74 | 073 |
Parameter connector_id does not exist in DPS URL | The short text describes the object sufficiently | |
| 75 | 074 |
Parameter connector_type does not exist in DPS URL | The short text describes the object sufficiently | |
| 76 | 075 |
Parameter bin_node_id does not exist in DPS URL | The short text describes the object sufficiently | |
| 77 | 076 |
Parameter bin_attr_id does not exist in DPS URL | The short text describes the object sufficiently | |
| 78 | 077 |
Parameter bin_created_on does not exist in DPS URL | The short text describes the object sufficiently | |
| 79 | 078 |
Parameter bin_performance_data does not exist in DPS URL | The short text describes the object sufficiently | |
| 80 | 079 |
Parameter debug_mode does not exist in DPS URL | The short text describes the object sufficiently | |
| 81 | 080 |
Creation of DPS HTTP client: Argument not found | The short text describes the object sufficiently | |
| 82 | 081 |
Creation of DPS HTTP client: Plug-in not active | The short text describes the object sufficiently | |
| 83 | 082 |
Creation of DPS HTTP client: Internal error | The short text describes the object sufficiently | |
| 84 | 083 |
Sending to DPS client: Invalid state | The short text describes the object sufficiently | |
| 85 | 084 |
Sending to DPS client: HTTP processing unsuccessful | The short text describes the object sufficiently | |
| 86 | 085 |
Sending to DPS client: HTTP invalid timeout | The short text describes the object sufficiently | |
| 87 | 086 |
Sending to DPS client: General error | The short text describes the object sufficiently | |
| 88 | 087 |
Receiving from DPS client: Communication unsuccessful | The short text describes the object sufficiently | |
| 89 | 088 |
Receiving from DPS client: Invalid state | The short text describes the object sufficiently | |
| 90 | 089 |
Receiving from DPS client: HTTP processing unsuccessful | The short text describes the object sufficiently | |
| 91 | 090 |
Receiving from DPS client: General error | The short text describes the object sufficiently | |
| 92 | 091 |
Response from DPS client was code "&1" reason "&2" | The short text describes the object sufficiently | |
| 93 | 092 |
Error calling "HTTP_GET" for URL | The short text describes the object sufficiently | |
| 94 | 093 |
Error during creation of GUID for binary error log in DPS scenario | The short text describes the object sufficiently | |
| 95 | 094 |
Error during save of application log | The short text describes the object sufficiently | |
| 96 | 095 |
No key fields for current URL in DPS scenario | The short text describes the object sufficiently | |
| 97 | 096 |
Internal error concerning language field for URL in DPS scenario | The short text describes the object sufficiently | |
| 98 | 097 |
Default language for current URL taken from TREX in DPS scenario | The short text describes the object sufficiently | |
| 99 | 098 |
No language for current URL (DPS); not even default language | The short text describes the object sufficiently | |
| 100 | 099 |
Content of URL (DPS) could not be converted into HTML; TREX code &1 | The short text describes the object sufficiently | |
| 101 | 100 |
Error calling "HTTP_GET" for URL in DPS scenario | The short text describes the object sufficiently | |
| 102 | 101 |
Parameter sysrel_id does not exist in DPS URL | The short text describes the object sufficiently | |
| 103 | 102 |
Parameter mime type does not exist in DPS URL | The short text describes the object sufficiently | |
| 104 | 103 |
Parameter table_index does not exist in DPS URL | The short text describes the object sufficiently | |
| 105 | 104 |
URL is in HTTPS protocol. This is not possible in this scenario | The short text describes the object sufficiently | |
| 106 | 105 |
General error calling TREX (preprocessor stellant) for xstring | The short text describes the object sufficiently | |
| 107 | 106 |
General error calling TREX (preprocessor stellant) for URL | The short text describes the object sufficiently | |
| 108 | 107 |
General error calling TREX (preprocessor stellant) for URL (DPS) | The short text describes the object sufficiently | |
| 109 | 108 |
Error during determination of path in current URL (DPS) | The short text describes the object sufficiently | |
| 110 | 109 |
Error during determination of WS endpoint via connector conversion (DPS) | The short text describes the object sufficiently | |
| 111 | 110 |
Creation of DPS HTTP client: Destination not found | The short text describes the object sufficiently | |
| 112 | 111 |
Creation of DPS HTTP client: No authority for destination | The short text describes the object sufficiently | |
| 113 | 112 |
Sending to DPS client: HTTP communication failure | The short text describes the object sufficiently | |
| 114 | 113 |
Receiving from DPS client: Response with code &1 and reason &2 | The short text describes the object sufficiently | |
| 115 | 114 |
MIME type mismatch: Given &1 received &2 (DPS) | The short text describes the object sufficiently | |
| 116 | 115 |
Error occurred during indexing: Connectivity could not be determined | The short text describes the object sufficiently | |
| 117 | 116 |
Conversion error in TREX during conversion of DPS URL into HTML | The short text describes the object sufficiently | |
| 118 | 117 |
General error in TREX during conversion of DPS URL into HTML | The short text describes the object sufficiently | |
| 119 | 118 |
Conversion error in TREX during conversion of xstring into HTML | The short text describes the object sufficiently | |
| 120 | 119 |
General error in TREX during conversion of xstring into HTML | The short text describes the object sufficiently | |
| 121 | 120 |
No destinations available for any URL | The short text describes the object sufficiently | |
| 122 | 121 |
At least one URL without destination | The short text describes the object sufficiently | |
| 123 | 122 |
Creation of HTTP client: Argument not found | The short text describes the object sufficiently | |
| 124 | 123 |
Creation of HTTP client: Plug-in not active | The short text describes the object sufficiently | |
| 125 | 124 |
Creation of HTTP client: Internal error | The short text describes the object sufficiently | |
| 126 | 125 |
Creation of HTTP client (dest): Argument not found (destination &1) | The short text describes the object sufficiently | |
| 127 | 126 |
Creation of HTTP client (dest): Destination not found (destination &1) | The short text describes the object sufficiently | |
| 128 | 127 |
Creation of HTTP client (dest): No authorization for destination &1 | The short text describes the object sufficiently | |
| 129 | 128 |
Creation of HTTP client (dest): Plug-in not active (destination &1) | The short text describes the object sufficiently | |
| 130 | 129 |
Creation of HTTP client (dest): Internal error (destination &1) | The short text describes the object sufficiently | |
| 131 | 130 |
Sending to client: HTTP communication failure (destination &1) | The short text describes the object sufficiently | |
| 132 | 131 |
Sending to client: Invalid state (destination &1) | The short text describes the object sufficiently | |
| 133 | 132 |
Sending to client: HTTP processing unsuccessful (destination &1) | The short text describes the object sufficiently | |
| 134 | 133 |
Sending to client: HTTP invalid timeout (destination &1) | The short text describes the object sufficiently | |
| 135 | 134 |
Sending to client: General error (destination &1) | The short text describes the object sufficiently | |
| 136 | 135 |
Receiving from client: Communication unsuccessful (destination &1) | The short text describes the object sufficiently | |
| 137 | 136 |
Receiving from client: Invalid state (destination &1) | The short text describes the object sufficiently | |
| 138 | 137 |
Receiving from client: HTTP processing unsuccessful (destination &1) | The short text describes the object sufficiently | |
| 139 | 138 |
Receiving from client: General error (destination &1) | The short text describes the object sufficiently | |
| 140 | 139 |
Response from client was code "&1" reason "&2" (destination &3) | The short text describes the object sufficiently | |
| 141 | 140 |
MIME type mismatch: Given &1 received &2 | The short text describes the object sufficiently | |
| 142 | 141 |
Conversion error in TREX during conversion of URL into HTML | The short text describes the object sufficiently | |
| 143 | 142 |
General error in TREX during conversion of URL into HTML | The short text describes the object sufficiently | |
| 144 | 143 |
There is no MIME type for at least one URL | The short text describes the object sufficiently | |
| 145 | 144 |
Error occurred during indexing: Connector ID could not be determined | The short text describes the object sufficiently | |
| 146 | 145 |
Error occurred during indexing: Destination could not be determined | The short text describes the object sufficiently | |
| 147 | 146 |
Logical port &1 does not exist any more | The short text describes the object sufficiently | |
| 148 | 147 |
No properties available for log.port &1. Check if service is available | The short text describes the object sufficiently | |
| 149 | 148 |
Parameter 'content_url' does not exist | The short text describes the object sufficiently | |
| 150 | 149 |
Error during connectivity creation in adapter &1 | The short text describes the object sufficiently | |
| 151 | 150 |
Error occurred during indexing: Path could not be determined | The short text describes the object sufficiently | |
| 152 | 151 |
MIME type &1 is not supported | The short text describes the object sufficiently | |
| 153 | 152 |
Error during indexing for URL-related binary data: no connection | The short text describes the object sufficiently | |
| 154 | 153 |
Error during indexing for URL-related binary data: no software component | The short text describes the object sufficiently | |
| 155 | 154 |
Error during indexing for URL-related binary data: no object type | The short text describes the object sufficiently | |
| 156 | 155 |
Error during indexing for URL-related binary data: internal error | The short text describes the object sufficiently | |
| 157 | 156 |
Error during indexing for URL/xstring binary data: key not found | The short text describes the object sufficiently | |
| 158 | 157 |
Error during indexing for xstring binary data: no connection | The short text describes the object sufficiently | |
| 159 | 158 |
Error during indexing for xstring binary data: no software component | The short text describes the object sufficiently | |
| 160 | 159 |
Error during indexing for xstring binary data: no object type | The short text describes the object sufficiently | |
| 161 | 160 |
Error during indexing for xstring binary data: no source data | The short text describes the object sufficiently | |
| 162 | 161 |
Error during indexing for xstring binary data: no xstring attribute | The short text describes the object sufficiently | |
| 163 | 162 |
Error during indexing for xstring binary data: no target data | The short text describes the object sufficiently | |
| 164 | 163 |
Error during indexing for xstring binary data: no language data | The short text describes the object sufficiently | |
| 165 | 164 |
Error during indexing for xstring binary data: no attribute for mime type | The short text describes the object sufficiently | |
| 166 | 165 |
Error during indexing for xstring binary data: internal error in TREX | The short text describes the object sufficiently | |
| 167 | 166 |
Error during indexing for URL-related binary data: no data | The short text describes the object sufficiently | |
| 168 | 167 |
Error during indexing for URL-related binary data: internal error in TREX | The short text describes the object sufficiently | |
| 169 | 168 |
Error during indexing for URL-related binary data: no node name | The short text describes the object sufficiently | |
| 170 | 169 |
Error during indexing for URL-related binary data: no application log | The short text describes the object sufficiently | |
| 171 | 170 |
Error during indexing for xstring binary data: no node name | The short text describes the object sufficiently | |
| 172 | 171 |
Error during indexing for xstring binary data: no application log | The short text describes the object sufficiently | |
| 173 | 172 |
Error during indexing for URL-related binary data: no connector | The short text describes the object sufficiently | |
| 174 | 173 |
Error during indexing for URL-related binary data: URL &1 not valid | The short text describes the object sufficiently | |
| 175 | 174 |
Error during determination of sysrel &1 | The short text describes the object sufficiently | |
| 176 | 175 |
TREX destination error: &1 (TREX code &2) | The short text describes the object sufficiently | |
| 177 | 176 |
To check the MIME type, the following class was called: &1 | The short text describes the object sufficiently | |
| 178 | 177 |
Resolving KPRO URL: HTTP internal error | The short text describes the object sufficiently | |
| 179 | 178 |
Resolving KPRO URL: HTTP communication failure | The short text describes the object sufficiently | |
| 180 | 179 |
Resolving KPRO URL: HTTP connection failed | The short text describes the object sufficiently | |
| 181 | 180 |
Resolving KPRO URL: HTTP timeout | The short text describes the object sufficiently | |
| 182 | 181 |
Resolving KPRO URL: TCPIP error | The short text describes the object sufficiently | |
| 183 | 182 |
Resolving KPRO URL: Data error | The short text describes the object sufficiently | |
| 184 | 183 |
Resolving KPRO URL: System failure | The short text describes the object sufficiently | |
| 185 | 184 |
Resolving KPRO URL: Undefined error | The short text describes the object sufficiently | |
| 186 | 185 |
Resolving KPRO URL: Conversion failure | The short text describes the object sufficiently | |
| 187 | 186 |
Resolving KPRO URL: Undefined error during Conversion | The short text describes the object sufficiently | |
| 188 | 187 |
Resolving KPRO URL: Response from client was code "&1" reason "&2" | The short text describes the object sufficiently | |
| 189 | 188 |
DPS related destination &1 does not exist | The short text describes the object sufficiently | |
| 190 | 189 |
Internal error reading RFC destination &1 | The short text describes the object sufficiently | |
| 191 | 190 |
To check the file size, the following class was called: &1 | The short text describes the object sufficiently | |
| 192 | 191 |
Error in URL parsing during HEAD call | The short text describes the object sufficiently | |
| 193 | 192 |
Creation of HTTP client in HEAD call: Argument not found | The short text describes the object sufficiently | |
| 194 | 193 |
Creation of HTTP client in HEAD call: Plug-in not active | The short text describes the object sufficiently | |
| 195 | 194 |
Creation of HTTP client in HEAD call: Internal error | The short text describes the object sufficiently | |
| 196 | 195 |
Sending to client during HEAD call: HTTP communication failure | The short text describes the object sufficiently | |
| 197 | 196 |
Sending to client during HEAD call: Invalid state | The short text describes the object sufficiently | |
| 198 | 197 |
Sending to client during HEAD call: HTTP processing unsuccessful | The short text describes the object sufficiently | |
| 199 | 198 |
Sending to client during HEAD call: HTTP invalid timeout | The short text describes the object sufficiently | |
| 200 | 199 |
Sending to client during HEAD call: General error | The short text describes the object sufficiently | |
| 201 | 200 |
Receiving from client during HEAD call: Communication unsuccessful | The short text describes the object sufficiently | |
| 202 | 201 |
Receiving from client during HEAD call: Invalid state | The short text describes the object sufficiently | |
| 203 | 202 |
Receiving from client during HEAD call: HTTP processing unsuccessful | The short text describes the object sufficiently | |
| 204 | 203 |
Receiving from client during HEAD call: General error | The short text describes the object sufficiently | |
| 205 | 204 |
Response from client during HEAD call was code "&1" reason "&2" | The short text describes the object sufficiently | |
| 206 | 205 |
The content for the following URL exceeded maximum size (default 100 MB): | The short text describes the object sufficiently | |
| 207 | 206 |
&1&2&3&4 | The short text describes the object sufficiently | |
| 208 | 207 |
The content for the URL exceeds maximum size (see aplication log) | The short text describes the object sufficiently | |
| 209 | 208 |
The content for the xstring exceeds maximum size (default 100 MB) | The short text describes the object sufficiently | |
| 210 | 210 |
Repository ID for KPRO not found during URL indexing | The short text describes the object sufficiently | |
| 211 | 211 |
Document ID for KPRO not found during URL indexing | The short text describes the object sufficiently | |
| 212 | 212 |
Bad storage type in HEAD call for KPRO during URL indexing | The short text describes the object sufficiently | |
| 213 | 213 |
Bad request in HEAD call for KPRO during URL indexing | The short text describes the object sufficiently | |
| 214 | 214 |
Unauthorized for KPRO HEAD call during URL indexing | The short text describes the object sufficiently | |
| 215 | 215 |
Document not found during KPRO HEAD call in URL indexing | The short text describes the object sufficiently | |
| 216 | 216 |
Conflict during KPRO HEAD call in URL indexing | The short text describes the object sufficiently | |
| 217 | 217 |
Internal server error during KPRO HEAD call in URL indexing | The short text describes the object sufficiently | |
| 218 | 218 |
HTTP server error during KPRO HEAD call in URL indexing | The short text describes the object sufficiently | |
| 219 | 219 |
Signature error during KPRO HEAD call in URL indexing | The short text describes the object sufficiently | |
| 220 | 220 |
Configuration error during KPRO HEAD call in URL indexing | The short text describes the object sufficiently | |
| 221 | 221 |
Hierarchy error during KPRO HEAD call in URL indexing | The short text describes the object sufficiently | |
| 222 | 222 |
Parameter error during KPRO HEAD call in URL indexing | The short text describes the object sufficiently | |
| 223 | 223 |
General error during KPRO HEAD call in URL indexing | The short text describes the object sufficiently | |
| 224 | 224 |
KPRO scenario: Global switch for resolution of URLs on TREX activated | The short text describes the object sufficiently | |
| 225 | 225 |
To check switch of URL resolution, the following class was called: &1 | The short text describes the object sufficiently |
History
| Last changed on/by | |
20130531 | SAP |
| SAP Release Created in | 730 |
