| 0 |
OEE0: No error
|
| 1000 |
OEE1000: Unable to write a GET request to ping the backend server using http://%1:%2/%3. Ping again
|
| 1001 |
OEE1001: Unable to read response headers from the backend server ping using http://%1:%2/%3. Pinging again
|
| 1002 |
OEE1002: Unexpected HTTP status code %1 from ping of backend server using http://%2:%3/%4. Pinging again
|
| 1003 |
OEE1003: Missing Content-Length header in response to backend server ping using http://%1:%2/%3. Pinging again
|
| 1004 |
OEE1004: Missing or malformed body found in response to backend server ping using http://%1:%2/%3. Pinging again
|
| 1005 |
OEE1005: Unable to find 'AVAILABLE=' in backend status ping response body from http://%1:%2/%3. Pinging again
|
| 1006 |
OEE1006: The Outbound Enabler does not recognize 'AVAILABLE=%1' in the response to the backend server status ping to http://%2:%3/%4.
Valid values are 1, T, TRUE, ON, 0, F, FALSE and OFF. Pinging again
|
| 1007 |
OEE1007: The Output Enabler backend server status ping to http://%1:%2/%3 reported service unavailable. Pinging again
|
| 1008 |
OEE1008: Unable to find nor shut down an Outbound Enabler for server '%1' of farm '%2' using relay server '%3%4'
|
| 1009 |
OEE1009: Unable to perform a network read from the Relay Server because of [MLC%1: %2]
|
| 1010 |
OEE1010: The Outbound Enabler cannot handle the WWW-Authenticate header in the response because of [MLC%1: %2]
|
| 1011 |
OEE1011: The Outbound Enabler cannot handle the Proxy-Authenticate header in the response because of [MLC%1: %2]
|
| 1012 |
OEE1012: The Outbound Enabler cannot handle the Authentication-Info header in the response because of [MLC%1: %2]
|
| 1013 |
OEE1013: The Outbound Enabler cannot handle the Proxy-Authentication-Info header in the response because of [MLC%1: %2]
|
| 1014 |
OEE1014: The length of an HTTP chunk length received from the Relay Server is too big
|
| 1015 |
OEE1015: An HTTP chunk length received from the Relay Server is malformed
|
| 1016 |
OEE1016: An HTTP chunk received from the Relay Server is missing a trailing CRLF
|
| 1017 |
OEE1017: The Outbound Enabler received an HTTP error status from the Relay Server:\r %1
|
| 1018 |
OEE1018: Outbound Enabler connections to the Relay Server Web server require HTTP authentication, but no credentials were
provided
|
| 1019 |
OEE1019: An Outbound Enabler connection to the Relay Server failed HTTP authentication
|
| 1020 |
OEE1020: Outbound Enabler connections to the Relay Server Web server are going through a proxy requiring proxy HTTP authentication,
but no credentials were provided
|
| 1021 |
OEE1021: An Outbound Enabler connection to the Relay Server failed HTTP proxy authentication
|
| 1022 |
OEE1022: The Outbound Enabler received an unexpected HTTP error status:\r %1
|
| 1023 |
OEE1023: The Outbound Enabler is missing the -cr http_password parameter
|
| 1024 |
OEE1024: The Outbound Enabler is missing the -cr http_proxy_password parameter
|
| 1025 |
OEE1025: The Outbound Enabler is missing the -cr http_userid parameter
|
| 1026 |
OEE1026: The Outbound Enabler is missing the -cr http_proxy_userid parameter
|
| 1027 |
OEE1027: The Outbound Enabler was unable to write an HTTP header to the Relay Server because of [MLC%1: %2]
|
| 1028 |
OEE1028: The Outbound Enabler was unable to write an HTTP body to the Relay Server because of [MLC%1: %2]
|
| 1029 |
OEE1029: The Outbound Enabler received an HTTP cookie or header from a client indicating the client cached it from a previous
Relay Server configuration. The unexpected Relay Server index is: %1
|
| 1030 |
OEE1030: The Outbound Enabler was unable to connect to the Relay Server using '%1' because of [MLC%2: %3]. Retrying
|
| 1031 |
OEE1031: The Outbound Enabler access was denied by the Relay Server
|
| 1032 |
OEE1032: Retry due to issue with the Relay Server
|
| 1033 |
OEE1033: The Outbound Enabler is unable to connect to the backend server at %1:%2 to ping it. Pinging again
|
| 1034 |
OEE1034: Communication error with backend server: '%1'
|
| 1035 |
OEE1035: Invalid tls_type %1 given to the Outbound Enabler's -cs switch. Only rsa is supported
|
| 1036 |
OEE1036: A network connection was closed by the Relay Server or an intermediary while the Outbound Enabler was reading from
it
|
| 1037 |
OEE1037: The Outbound Enabler -cr switch is missing the %1 parameter
|
| 1038 |
OEE1038: Invalid Outbound Enabler command line near '%1'
|
| 1039 |
OEE1039: The Outbound Enabler connection to the Relay Server using '%1' failed because of [MLC%2: %3]
|
| 1040 |
OEE1040: The Outbound Enabler was unable to initialize secure communications to the backend server because of [MLC%1: %2]
|
| 1041 |
OEE1041: The Outbound Enabler -cr switch does not specify a valid Relay Server. The HTTP response from the server has the
following headers: %1
|
| 1042 |
OEE1042: The Relay Server needs to be upgraded in order to be compatible with this Outbound Enabler
|
| 1043 |
OEE1043: The Relay Server at host '%1' lacks a %2 entry in the Relay Server configuration
|
| 1044 |
OEE1044: The Outbound Enabler was unable to determine the MAC addresses of this machine
|
| 1045 |
OEE1045: System error [SYS%1: %2] while %3 with the backend server for sidx=%4 socket=%5 sfp=%6
|
| 1046 |
OEE1046: Connecting to backend server at %1:%2 failed because of [MLC%3: %4]
|
| 1047 |
OEE1047: Error parsing the value of the Outbound Enabler -cs %1 parameter
|
| 1048 |
OEE1048: The communication between the Outbound Enabler and the backend server failed with [MLC%1: %2] while %3. sidx=%4 socket=%5
sfp=%6
|
| 1049 |
OEE1049: The request URL is too long. Request with sidx=%1 sfp=%2 is aborted
|
| 1050 |
OEE1050: Failed to lookup a session that has just started with ridx=%1 snum=%2 sfp=%3 on a %4 packet
|
| 1051 |
OEE1051: The Outbound Enabler was unable to access the session with ridx=%1 sidx=%2 snum=%3 sfp=%4 on a %5 packet due to %6
|
| 1052 |
OEE1052: The Outbound Enabler was unable to write a %1 packet to the Relay Server because of [MCL%2: %3]
|
| 1053 |
OEE1053: The Outbound Enabler was unable to flush a packet to the Relay Server because of [MLC%1: %2]
|
| 1054 |
OEE1054: The Outbound Enabler was unable to write a %5 packet with ridx=%1 sidx=%2 snum=%3 sfp=%4 failed because of [MLC%6:
%7]
|
| 1055 |
OEE1055: The Outbound Enabler was unable to create a session error packet with ridx=%1 sidx=%2 snum=%3 sfp=%4 err=%5 for Relay
Server index %6 as it cannot be found
|
| 10000 |
OEF10000: Failed to initialize socket library [MLC%1: %2]
|
| 10001 |
OEF10001: Out of memory
|
| 10002 |
OEF10002: The Outbound Enabler was unable to create shared memory directory for communicating shutdown
|
| 10003 |
OEF10003: The Outbound Enabler was unable to create shared memory for communicating shutdown
|
| 10004 |
OEF10004: The 'rsoe -s' command failed shutting down Outbound Enabler for server '%1' of farm '%2' using relay server '%3%4'
|
| 10005 |
OEF10005: Unable to load the Outbound Enabler support library: %1 -- %2
|
| 10006 |
OEF10006: The Outbound Enabler was unable to load required functions from the '%1' library
|
| 10007 |
OEF10007: Failed to initialize an Outbound Enabler support library '%1'
|
| 10008 |
OEF10008: Protocol error while reading %1 packet
|
| 10009 |
OEF10009: Reduced to lowest supported protocol version but the Relay Server is still not compatible
|
| 10010 |
OEF10010: Invalid opcode received from the Relay Server
|
| 10011 |
OEF10011: The Outbound Enabler was unable to load the %1 encryption library because of [%2]. Make it is installed properly
|
| 10012 |
OEF10012: The Outbound Enabler was unable to load function %1 from encryption library %2
|
| 10013 |
OEF10013: Encryption library version mismatch. Found version %1.%2 with implementation id %3
|
| 10014 |
OEF10014: Internal error: %1
|
