Message Number list used by SAP ABAP Class CX_ESH_BIN_CONTENT_ERROR (Exception Class for CL_ESH_BINARY_CONTENT)
SAP ABAP Class
CX_ESH_BIN_CONTENT_ERROR (Exception Class for CL_ESH_BINARY_CONTENT) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | ESH_ADM_BIN_MSG - 055 | Parameter error for DPS: All URLs skipped | ||
| 2 | ESH_ADM_BIN_MSG - 057 | MIME type is invalid | ||
| 3 | ESH_ADM_BIN_MSG - 058 | For URL &1 bypass of TREX wanted but not possible due to HTTPS | ||
| 4 | ESH_ADM_BIN_MSG - 059 | Wrong construction for content URL of document service | ||
| 5 | ESH_ADM_BIN_MSG - 062 | Error during determination of DPS path | ||
| 6 | ESH_ADM_BIN_MSG - 064 | Error in Web service framework (DPS) | ||
| 7 | ESH_ADM_BIN_MSG - 080 | Creation of DPS HTTP client: Argument not found | ||
| 8 | ESH_ADM_BIN_MSG - 081 | Creation of DPS HTTP client: Plug-in not active | ||
| 9 | ESH_ADM_BIN_MSG - 082 | Creation of DPS HTTP client: Internal error | ||
| 10 | ESH_ADM_BIN_MSG - 083 | Sending to DPS client: Invalid state | ||
| 11 | ESH_ADM_BIN_MSG - 084 | Sending to DPS client: HTTP processing unsuccessful | ||
| 12 | ESH_ADM_BIN_MSG - 085 | Sending to DPS client: HTTP invalid timeout | ||
| 13 | ESH_ADM_BIN_MSG - 086 | Sending to DPS client: General error | ||
| 14 | ESH_ADM_BIN_MSG - 087 | Receiving from DPS client: Communication unsuccessful | ||
| 15 | ESH_ADM_BIN_MSG - 088 | Receiving from DPS client: Invalid state | ||
| 16 | ESH_ADM_BIN_MSG - 089 | Receiving from DPS client: HTTP processing unsuccessful | ||
| 17 | ESH_ADM_BIN_MSG - 090 | Receiving from DPS client: General error | ||
| 18 | ESH_ADM_BIN_MSG - 091 | Response from DPS client was code "&1" reason "&2" | ||
| 19 | ESH_ADM_BIN_MSG - 108 | Error during determination of path in current URL (DPS) | ||
| 20 | ESH_ADM_BIN_MSG - 109 | Error during determination of WS endpoint via connector conversion (DPS) | ||
| 21 | ESH_ADM_BIN_MSG - 110 | Creation of DPS HTTP client: Destination not found | ||
| 22 | ESH_ADM_BIN_MSG - 111 | Creation of DPS HTTP client: No authority for destination | ||
| 23 | ESH_ADM_BIN_MSG - 112 | Sending to DPS client: HTTP communication failure | ||
| 24 | ESH_ADM_BIN_MSG - 122 | Creation of HTTP client: Argument not found | ||
| 25 | ESH_ADM_BIN_MSG - 123 | Creation of HTTP client: Plug-in not active | ||
| 26 | ESH_ADM_BIN_MSG - 124 | Creation of HTTP client: Internal error | ||
| 27 | ESH_ADM_BIN_MSG - 126 | Creation of HTTP client (dest): Destination not found (destination &1) | ||
| 28 | ESH_ADM_BIN_MSG - 127 | Creation of HTTP client (dest): No authorization for destination &1 | ||
| 29 | ESH_ADM_BIN_MSG - 130 | Sending to client: HTTP communication failure (destination &1) | ||
| 30 | ESH_ADM_BIN_MSG - 131 | Sending to client: Invalid state (destination &1) | ||
| 31 | ESH_ADM_BIN_MSG - 132 | Sending to client: HTTP processing unsuccessful (destination &1) | ||
| 32 | ESH_ADM_BIN_MSG - 133 | Sending to client: HTTP invalid timeout (destination &1) | ||
| 33 | ESH_ADM_BIN_MSG - 134 | Sending to client: General error (destination &1) | ||
| 34 | ESH_ADM_BIN_MSG - 135 | Receiving from client: Communication unsuccessful (destination &1) | ||
| 35 | ESH_ADM_BIN_MSG - 136 | Receiving from client: Invalid state (destination &1) | ||
| 36 | ESH_ADM_BIN_MSG - 137 | Receiving from client: HTTP processing unsuccessful (destination &1) | ||
| 37 | ESH_ADM_BIN_MSG - 138 | Receiving from client: General error (destination &1) | ||
| 38 | ESH_ADM_BIN_MSG - 139 | Response from client was code "&1" reason "&2" (destination &3) | ||
| 39 | ESH_ADM_BIN_MSG - 144 | Error occurred during indexing: Connector ID could not be determined | ||
| 40 | ESH_ADM_BIN_MSG - 145 | Error occurred during indexing: Destination could not be determined | ||
| 41 | ESH_ADM_BIN_MSG - 146 | Logical port &1 does not exist any more | ||
| 42 | ESH_ADM_BIN_MSG - 147 | No properties available for log.port &1. Check if service is available | ||
| 43 | ESH_ADM_BIN_MSG - 148 | Parameter 'content_url' does not exist | ||
| 44 | ESH_ADM_BIN_MSG - 149 | Error during connectivity creation in adapter &1 | ||
| 45 | ESH_ADM_BIN_MSG - 150 | Error occurred during indexing: Path could not be determined | ||
| 46 | ESH_ADM_BIN_MSG - 152 | Error during indexing for URL-related binary data: no connection | ||
| 47 | ESH_ADM_BIN_MSG - 153 | Error during indexing for URL-related binary data: no software component | ||
| 48 | ESH_ADM_BIN_MSG - 154 | Error during indexing for URL-related binary data: no object type | ||
| 49 | ESH_ADM_BIN_MSG - 155 | Error during indexing for URL-related binary data: internal error | ||
| 50 | ESH_ADM_BIN_MSG - 156 | Error during indexing for URL/xstring binary data: key not found | ||
| 51 | ESH_ADM_BIN_MSG - 157 | Error during indexing for xstring binary data: no connection | ||
| 52 | ESH_ADM_BIN_MSG - 158 | Error during indexing for xstring binary data: no software component | ||
| 53 | ESH_ADM_BIN_MSG - 159 | Error during indexing for xstring binary data: no object type | ||
| 54 | ESH_ADM_BIN_MSG - 160 | Error during indexing for xstring binary data: no source data | ||
| 55 | ESH_ADM_BIN_MSG - 161 | Error during indexing for xstring binary data: no xstring attribute | ||
| 56 | ESH_ADM_BIN_MSG - 162 | Error during indexing for xstring binary data: no target data | ||
| 57 | ESH_ADM_BIN_MSG - 163 | Error during indexing for xstring binary data: no language data | ||
| 58 | ESH_ADM_BIN_MSG - 164 | Error during indexing for xstring binary data: no attribute for mime type | ||
| 59 | ESH_ADM_BIN_MSG - 165 | Error during indexing for xstring binary data: internal error in TREX | ||
| 60 | ESH_ADM_BIN_MSG - 166 | Error during indexing for URL-related binary data: no data | ||
| 61 | ESH_ADM_BIN_MSG - 167 | Error during indexing for URL-related binary data: internal error in TREX | ||
| 62 | ESH_ADM_BIN_MSG - 168 | Error during indexing for URL-related binary data: no node name | ||
| 63 | ESH_ADM_BIN_MSG - 169 | Error during indexing for URL-related binary data: no application log | ||
| 64 | ESH_ADM_BIN_MSG - 170 | Error during indexing for xstring binary data: no node name | ||
| 65 | ESH_ADM_BIN_MSG - 171 | Error during indexing for xstring binary data: no application log | ||
| 66 | ESH_ADM_BIN_MSG - 172 | Error during indexing for URL-related binary data: no connector | ||
| 67 | ESH_ADM_BIN_MSG - 173 | Error during indexing for URL-related binary data: URL &1 not valid | ||
| 68 | ESH_ADM_BIN_MSG - 175 | TREX destination error: &1 (TREX code &2) | ||
| 69 | ESH_ADM_BIN_MSG - 177 | Resolving KPRO URL: HTTP internal error | ||
| 70 | ESH_ADM_BIN_MSG - 178 | Resolving KPRO URL: HTTP communication failure | ||
| 71 | ESH_ADM_BIN_MSG - 179 | Resolving KPRO URL: HTTP connection failed | ||
| 72 | ESH_ADM_BIN_MSG - 180 | Resolving KPRO URL: HTTP timeout | ||
| 73 | ESH_ADM_BIN_MSG - 181 | Resolving KPRO URL: TCPIP error | ||
| 74 | ESH_ADM_BIN_MSG - 182 | Resolving KPRO URL: Data error | ||
| 75 | ESH_ADM_BIN_MSG - 183 | Resolving KPRO URL: System failure | ||
| 76 | ESH_ADM_BIN_MSG - 184 | Resolving KPRO URL: Undefined error | ||
| 77 | ESH_ADM_BIN_MSG - 185 | Resolving KPRO URL: Conversion failure | ||
| 78 | ESH_ADM_BIN_MSG - 186 | Resolving KPRO URL: Undefined error during Conversion | ||
| 79 | ESH_ADM_BIN_MSG - 187 | Resolving KPRO URL: Response from client was code "&1" reason "&2" | ||
| 80 | ESH_ADM_BIN_MSG - 188 | DPS related destination &1 does not exist | ||
| 81 | ESH_ADM_BIN_MSG - 189 | Internal error reading RFC destination &1 | ||
| 82 | ESH_ADM_BIN_MSG - 191 | Error in URL parsing during HEAD call | ||
| 83 | ESH_ADM_BIN_MSG - 192 | Creation of HTTP client in HEAD call: Argument not found | ||
| 84 | ESH_ADM_BIN_MSG - 193 | Creation of HTTP client in HEAD call: Plug-in not active | ||
| 85 | ESH_ADM_BIN_MSG - 194 | Creation of HTTP client in HEAD call: Internal error | ||
| 86 | ESH_ADM_BIN_MSG - 195 | Sending to client during HEAD call: HTTP communication failure | ||
| 87 | ESH_ADM_BIN_MSG - 196 | Sending to client during HEAD call: Invalid state | ||
| 88 | ESH_ADM_BIN_MSG - 197 | Sending to client during HEAD call: HTTP processing unsuccessful | ||
| 89 | ESH_ADM_BIN_MSG - 198 | Sending to client during HEAD call: HTTP invalid timeout | ||
| 90 | ESH_ADM_BIN_MSG - 199 | Sending to client during HEAD call: General error | ||
| 91 | ESH_ADM_BIN_MSG - 200 | Receiving from client during HEAD call: Communication unsuccessful | ||
| 92 | ESH_ADM_BIN_MSG - 201 | Receiving from client during HEAD call: Invalid state | ||
| 93 | ESH_ADM_BIN_MSG - 202 | Receiving from client during HEAD call: HTTP processing unsuccessful | ||
| 94 | ESH_ADM_BIN_MSG - 203 | Receiving from client during HEAD call: General error | ||
| 95 | ESH_ADM_BIN_MSG - 204 | Response from client during HEAD call was code "&1" reason "&2" | ||
| 96 | ESH_ADM_BIN_MSG - 207 | The content for the URL exceeds maximum size (see aplication log) | ||
| 97 | ESH_ADM_BIN_MSG - 208 | The content for the xstring exceeds maximum size (default 100 MB) | ||
| 98 | ESH_ADM_BIN_MSG - 210 | Repository ID for KPRO not found during URL indexing | ||
| 99 | ESH_ADM_BIN_MSG - 211 | Document ID for KPRO not found during URL indexing | ||
| 100 | ESH_ADM_BIN_MSG - 212 | Bad storage type in HEAD call for KPRO during URL indexing | ||
| 101 | ESH_ADM_BIN_MSG - 213 | Bad request in HEAD call for KPRO during URL indexing | ||
| 102 | ESH_ADM_BIN_MSG - 214 | Unauthorized for KPRO HEAD call during URL indexing | ||
| 103 | ESH_ADM_BIN_MSG - 215 | Document not found during KPRO HEAD call in URL indexing | ||
| 104 | ESH_ADM_BIN_MSG - 216 | Conflict during KPRO HEAD call in URL indexing | ||
| 105 | ESH_ADM_BIN_MSG - 217 | Internal server error during KPRO HEAD call in URL indexing | ||
| 106 | ESH_ADM_BIN_MSG - 218 | HTTP server error during KPRO HEAD call in URL indexing | ||
| 107 | ESH_ADM_BIN_MSG - 219 | Signature error during KPRO HEAD call in URL indexing | ||
| 108 | ESH_ADM_BIN_MSG - 220 | Configuration error during KPRO HEAD call in URL indexing | ||
| 109 | ESH_ADM_BIN_MSG - 221 | Hierarchy error during KPRO HEAD call in URL indexing | ||
| 110 | ESH_ADM_BIN_MSG - 222 | Parameter error during KPRO HEAD call in URL indexing | ||
| 111 | ESH_ADM_BIN_MSG - 223 | General error during KPRO HEAD call in URL indexing | ||
| 112 | ESH_SEARCH - 241 | Error occurred during indexing: Path could not be determined | ||
| 113 | ESH_SEARCH - 242 | Multiple occurence of endpoint in content URL of document service | ||
| 114 | ESH_SEARCH - 243 | Wrong construction for content URL of document service |