![]() |
![]() |
|
|
1200 |
INFO: Transaction received HEURISTIC MIX result from remote domain val | |
|
Description |
The Domain gateway received a heuristic mix message indicating that part of the transaction committed and part of the transaction rolled back. This may cause an inconsistency in the application data. |
Action |
No action required. | |
1201 |
INFO: Transaction received HEURISTIC HAZARD result from remote domain val | |
|
Description |
The Domain gateway received a heuristic hazard message indicating that the outcome of part of the transaction is uncertain. This may cause an inconsistency in the application data. |
Action |
No action required. | |
1202 |
ERROR: Bad message from sub. Closing file descriptor | |
|
Description |
An invalid message was received in the Domain gateway. The gateway connection will be closed. |
Action |
Ensure that the TYPE values are set correctly if encoding is needed between domains. | |
1203 |
ERROR: Memory allocation failure for decompression | |
|
Description |
An attempt dynamically to allocate memory from the operating system failed while decompressing a received message. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1204 |
ERROR: Memory allocation failure for decompression | |
|
Description |
An attempt dynamically to allocate memory from the operating system failed while decompressing a received message. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1205 |
ERROR: Unable to obtain remote domain entry from shmem | |
|
Description |
While compressing a message, the entry for the remote domain could not be found (to determine the compression limit). |
Action |
This error should not occur. Contact BEA Customer Support. | |
1206 |
ERROR: Memory allocation failure for compression | |
|
Description |
An attempt dynamically to allocate memory from the operating system failed while compressing a message. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1207 |
ERROR: Unable to obtain remote domain entry from shmem | |
|
Description |
While compressing a message, the entry for the remote domain could not be found (to determine the compression limit). |
Action |
This error should not occur. Contact BEA Customer Support. | |
1208 |
ERROR: Memory allocation failure for compression | |
|
Description |
An attempt dynamically to allocate memory from the operating system failed while compressing a message. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1209 |
ERROR: Memory allocation failure for decompression | |
|
Description |
An attempt dynamically to allocate memory from the operating system failed while decompressing a message. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1210 |
ERROR: decompression failed | |
|
Description |
An error occurred while decompressing a message. |
Action |
Check for other errors in the event log. | |
1211 |
ERROR: Failed to destroy inflate structure | |
|
Description |
An error occurred while decompressing a message. |
Action |
Check for other errors in the event log. | |
1214 |
WARN: Corrupted Communication Control data detected! | |
|
Description |
An error occurred in the information associated with the domain connection. |
Action |
Contact BEA Customer Support. | |
1215 |
WARN: Communication to remote domain <rdom> already disconnected | |
|
Description |
A message was sent to a domain that has already disconnected from the local domain. |
Action |
Re-try the operation. | |
1218 |
ERROR: memory allocation failed for compression | |
|
Description |
The Domain Gateway library software detected an error while trying to compress a message. The process was unable to allocate enough virtual memory for the operation. |
Action |
Attempt to identify and stop any extraneous processes to free up virtual memory on your system. | |
See Also |
| |
1219 |
ERROR: compression fails...continuing | |
|
Description |
The Domain Gateway library software detected an error while trying to compress a message. An internal function call returned a failure. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
See Also |
| |
1220 |
ERROR: memory allocation failure in decompression | |
|
Description |
The Domain Gateway library software detected an error while trying to decompress a message. The process was unable to allocate enough virtual memory for the operation. |
Action |
Attempt to identify and stop any extraneous processes to free up virtual memory on your system. | |
See Also |
| |
1221 |
ERROR: decompression of message failed | |
|
Description |
The Domain Gateway library software detected an error while trying to decompress a message. An internal function call returned a failure. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
See Also |
| |
1222 |
ERROR: uncompressed message reallocation failed | |
|
Description |
The Domain Gateway library software detected an error while trying to decompress a message. The process was unable to allocate enough virtual memory for the operation. |
Action |
Attempt to identify and stop any extraneous processes to free up virtual memory on your system. | |
See Also |
| |
1224 |
ERROR: Minimum encryption (number of bits) is larger than 0, but the link level package is not installed | |
|
Description |
The Domain Gateway library software detected an error while trying to process a connect operation. The minimum number of encryption bits number of bits specified in the |
Action |
Correct the configuration so that the minimum number of encryption bits is consistent with the link level security package in use. | |
See Also |
| |
1226 |
ERROR: Could not allocate encryption handle | |
|
Description |
The Domain Gateway library software detected an error while trying to process a connect operation. The encryption handle could not be allocated. An internal function call returned a failure. A more descriptive error messages will be issued by the failing routine. |
Action |
Check the surrounding error messages for more descriptive error information. | |
See Also |
| |
1229 |
ERROR: Encryption negotiation failure | |
|
Description |
The Domain Gateway library software detected an error while trying to receive a message. An error was detected in the encryption flag settings. The encryption flags are all zero. |
Action |
Ensure that the encryption bit settings in the | |
See Also |
| |
1230 |
ERROR: Unable to generate first diffie-hellman packet | |
|
Description |
The Domain Gateway library software detected an error while trying to send a message. An internal function call for encryption returned a failure. Additional error messages from the failing routine will be issued prior to this message. |
Action |
Check the messages from the failing routine for more specific information regarding the cause of this error. | |
See Also |
| |
1231 |
ERROR: Could not allocate encryption handle | |
|
Description |
The Domain Gateway library software detected an error while trying to receive a message. An error was detected in the internal routine to allocate an encryption handle. A more specific message will be issued by the failing routine. |
Action |
Check the surrounding error messages for additional information. | |
See Also |
| |
1232 |
ERROR: Memory allocation error | |
|
Description |
The Domain Gateway library software detected an error while trying to receive a message. The process was unable to allocate enough virtual memory for the operation. |
Action |
Attempt to identify and stop any extraneous processes to free up virtual memory on your system. | |
See Also |
| |
1233 |
ERROR: Unable to generate second diffie-hellman packet | |
|
Description |
The Domain Gateway library software detected an error while trying to send a message. An internal function call for encryption returned a failure. Additional error messages from the failing routine will be issued prior to this message. |
Action |
Check the messages from the failing routine for more specific information regarding the cause of this error. | |
See Also |
| |
1234 |
ERROR: Unexpected link level encryption failure | |
|
Description |
The Domain Gateway library software detected an error while trying to send a message. An internal function call for encryption returned a failure. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
See Also |
| |
1236 |
ERROR: Encryption negotiation failure | |
|
Description |
The Domain Gateway library software detected an error while trying to receive a message. An error was detected in the encryption flag settings. The encryption flags are all zero. |
Action |
Ensure that the encryption bit settings in the | |
See Also |
| |
1237 |
ERROR: Invalid security level | |
|
Description |
The Domain Gateway library software detected an error while trying to receive a message. An invalid encryption level was detected. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
See Also |
| |
1238 |
ERROR: Unexpected link level encryption failure | |
|
Description |
The Domain Gateway library software detected an error while trying to receive a message. An internal function call for encryption returned a failure. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
See Also |
| |
1240 |
ERROR: Minimum encryption (number of bits) is larger than 0, but the link level package is not installed | |
|
Description |
The Domain Gateway library software detected an error while trying to process a receive operation. The minimum number of encryption bits number of bits specified in the |
Action |
Correct the configuration so that the minimum number of encryption bits is consistent with the link level security package in use. | |
See Also |
| |
1241 |
ERROR: Invalid parameter, tdom_link is NULL | |
|
Description |
GWTDOMAIN detects an internal error, or possible data corruption when it does a network open call. |
Action |
Contact your BEA Customer Support. | |
1242 |
ERROR: Invalid parameter, tdom_link contains NULL pointer | |
|
Description |
GWTDOMAIN detects an internal error, or possible data corruption when it does a network open call. |
Action |
Contact your BEA Customer Support. | |
1243 |
WARN: Open domain_name address ip_port failed, Network error(0xerror_code) | |
|
Description |
|
Action |
If the configuration contains multiple address entries for the specified domain, the | |
1244 |
WARN: No more NW address to try | |
|
Description |
|
Action |
The administrator should check whether the configuration is correct, and whether any other process already uses the port number. | |
1245 |
INFO: Try next one, device device_name address ip_address | |
|
Description |
This is informational. It tells the user that |
Action |
Nothing. | |
1246 |
ERROR: Invalid parameter, tdom_link is NULL | |
|
Description |
|
Action |
Contact your BEA Customer Support. | |
1247 |
ERROR: Invalid parameter, tdom_link contains NULL pointer | |
|
Description |
|
Action |
Contact your BEA Customer Support. | |
1249 |
WARN: Connect to domain_name address ip_addr failed, Network error(0xerrno) | |
|
Description |
|
Action |
Check the network, and check proper configuration. And also make sure the remote domain | |
1252 |
ERROR: Unable to obtain transaction entry from shared memory (rollback) | |
|
Description |
The /Domain transaction table entry for this transaction was not found in the /Domain shared memory tables when trying to process a transaction rollback. This could be caused if a stray message was received for a transaction that was already aborted. |
Action |
If the | |
1254 |
ERROR: Unable to determine locality of transaction | |
|
Description |
The |
Action |
This is an internal error with no associated user action. | |
See Also |
| |
1256 |
WARN: Unable to create local txid in shared memory for transaction recovery | |
|
Description |
The |
Action |
Modify the configuration to allow for more concurrent transactions. | |
1257 |
ERROR: Unable to decrypt message | |
|
Description |
The gateway is unable to decrypt a message sent from a remote domain. The message was encrypted using Link Level Encryption. |
Action |
Check the remote domain ULOG to see if the message is being properly encrypted by the gateway process. | |
1258 |
ERROR: Unable to process buffers | |
|
Description |
The Domain Gateway library software detected an error while trying to receive a message. An internal function call for encryption returned a failure. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
See Also |
| |
1259 |
ERROR: Memory allocation failure for encryption | |
|
Description |
An attempt to dynamically allocate memory from the operating system failed while attempting to create an encrypted message. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1260 |
ERROR: Memory allocation error | |
|
Description |
An attempt to dynamically allocate memory from the operating system failed. This is occurring in the routine where the software is attempting to open the gateway's listening endpoint. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1261 |
ERROR: Can not allocate network descriptor | |
|
Description |
An attempt to dynamically allocate memory from the operating system failed. This is occurring in the routine where the software is attempting to open a connection to a remote gateway. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1265 |
WARN: Unable to create local txid in shared memory for transaction recovery | |
|
Description |
The |
Action |
Modify the configuration to allow for more concurrent transactions. | |
1267 |
ERROR: Unable to convert old style network buffer. Error code val | |
|
Description |
The gateway received a message from a remote gateway running on a older TUXEDO release. In attempting to convert the message to the newer protocol, an error was encountered. |
Action |
Check that the message is being sent by a valid domain gateway process. | |
1268 |
ERROR: Unable to switch to new protocol | |
|
Description |
During the initial protocol exchange between gateways, the gateway attempts to set the protocol level of the remote gateway and an error is encountered. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
1269 |
ERROR: Unable to switch to new protocol | |
|
Description |
During the initial protocol exchange between gateways, the gateway attempts to set the protocol level of the remote gateway and an error is encountered. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
1270 |
ERROR: connections structure initialization failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system failed. This is occurring in the gateway's network initialization routine. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
1271 |
ERROR: Unable to initialize encryption key | |
|
Description |
The gateway is encountering an error initializing the |
Action |
Check the preceding ULOG message(s) for information on why the | |
1272 |
ERROR: Unable to encrypt challenge value | |
|
Description |
The gateway, when attemping to encrypt the |
Action |
Check the preceding ULOG message(s) for information on why the | |
1273 |
ERROR: Unable to initialize encryption key | |
|
Description |
The gateway, when attempting to initialize the encryption key during initial protocol exchange when security is |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
1274 |
ERROR: Unable to encrypt challenge value | |
|
Description |
The gateway, when attempting to encrypt the challenge value during initial protocol exchange for |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
1275 |
ERROR: Failed to convert buffer | |
|
Description |
The gateway is failing to convert an outbound TMS message to an older protocol version. The gateway is communicating with a remote gateway that does not support the newer protocol version and therefore needs to convert to an older protocol. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
1276 |
ERROR: Unable to presend transaction buffer | |
|
Description |
The gateway is failing to convert an outbound message to an older protocol version. The gateway is communicating with a remote gateway that does not support the newer protocol version and therefore needs to convert to an older protocol. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
1278 |
ERROR: Could not allocate a message | |
|
Description |
An attempt to dynamically allocate memory from the operating system failed. This is occurring in the gateway's mesage send routine. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1279 |
ERROR: Could not allocate a domain header | |
|
Description |
An attempt to dynamically allocate memory from the operating system failed. This is occurring in the gateway's mesage send routine, while trying to add the domains header. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1280 |
ERROR: Could not allocate a domain header | |
|
Description |
An attempt to dynamically allocate memory from the operating system failed. This is occurring in the gateway's mesage send routine, while trying to add the domains security header. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1281 |
ERROR: Failed to convert buffer | |
|
Description |
The gateway is failing to convert an outbound buffer to an older protocol version. The gateway is communicating with a remote gateway that does not support the newer protocol version and therefore needs to convert to an older protocol. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
1282 |
ERROR: Memory allocation failure for compression | |
|
Description |
An attempt dynamically to allocate memory from the operating system failed while compressing a message. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1283 |
ERROR: Could not encode header | |
|
Description |
The gateway is unable to encode the meta-header of an outbound message. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
1284 |
ERROR: Unable to find domains header | |
|
Description |
The gateway is failing to convert an outbound buffer to an older protocol version, because the buffer does not contain the domains header. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
1285 |
ERROR: Unable to find security header | |
|
Description |
The gateway is failing to convert an outbound buffer to an older protocol version, because the buffer does not contain the domains security header and security is turned on. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
1286 |
ERROR: Error converting message to old style. Error code val | |
|
Description |
The gateway is failing to convert an outbound message to an older protocol version. The gateway is communicating with a remote gateway that does not support the newer protocol version and therefore needs to convert to an older protocol. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
1287 |
ERROR: Unable to find domains header | |
|
Description |
The gateway received a message from a remote gateway with no domains header. |
Action |
Check the remote domain ULOG for further diagnosis. | |
1288 |
ERROR: Bad message from val. Closing file descriptor | |
|
Description |
The gateway received an incorrectly formatted message from a remote gateway. |
Action |
Check the remote domain ULOG for further diagnosis. | |
1289 |
ERROR: Unable to remove domains header | |
|
Description |
An internal error occurred while attempting to remove domain information from a message. |
Action |
Contact BEA Customer Support. | |
See Also |
| |
1290 |
ERROR: Unable to remove domains header | |
|
Description |
The gateway is unable to strip the domains header from the message. The header must be stripped by the gateway before forwarding the message to a TUXEDO server. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
1291 |
ERROR: Invalid input buffer | |
|
Description |
The gateway is unable to locate the TUXEDO header in an outbound message. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
1292 |
ERROR: Memory allocation error | |
|
Description |
An attempt dynamically to allocate memory from the operating system failed while preparing to send a message. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1293 |
ERROR: Invalid message format | |
|
Description |
The |
Action |
Contact BEA Customer Support. | |
See Also |
| |
1294 |
ERROR: Invalid message format | |
|
Description |
The gateway detected that the format of the oubound message is invalid. This was discovered while trying to add header information. |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
1295 |
ERROR: Unable to intialize administration key for domain val | |
|
Description |
The gateway is encountering an error initializing the |
Action |
Check the preceding ULOG message(s) for information on why the | |
1296 |
ERROR: Unable to intialize administration key for domain val | |
|
Description |
The gateway is encountering an error initializing the |
Action |
Check the preceding ULOG message(s) for information on why the | |
1297 |
ERROR: Unable to decrypt challange from val | |
|
Description |
The gateway, when attempting to decrypt the challenge value during initial protocol exchange for |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
1298 |
ERROR: Unable to decrypt challange from val | |
|
Description |
The gateway, when attempting to decrypt the challenge value during initial protocol exchange for |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. | |
1299 |
ERROR: Unable to intialize administration key for domain val | |
|
Description |
The gateway is encountering an error initializing the |
Action |
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message. |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|