![]() |
![]() |
|
|
1417 |
ERROR: Cannot use the -d and -r options together | |
|
Description |
The |
Action |
Change the arguments to the | |
See Also |
| |
1420 |
ERROR: Unable to get user id | |
|
Description |
The |
Action |
Have the UNIX System administrator correct any problems related to the entry of the user invoking | |
See Also |
| |
1422 |
ERROR: Cannot determine authentication level | |
|
Description |
The |
Action |
Attempt to determine why the | |
See Also |
| |
1424 |
ERROR: Unable to obtain application password | |
|
Description |
The |
Action |
If the | |
See Also |
| |
1425 |
ERROR: Handle entry not found | |
|
Description |
The handle in the |
Action |
Check the application code to make sure that only handles obtained from the return of | |
1426 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to reallocate memory failed during a call to |
Action |
Check that size requested is not inappropriately large. If that is not the problem, check that the application is freeing unneeded buffers before attempting to allocate new buffers. | |
See Also |
| |
1427 |
ERROR: Cannot join application - permission denied | |
|
Description |
An ATMI function was called in a client before calling |
Action |
This is an application error. If the application has security turned on, then | |
See Also |
| |
1428 |
ERROR: Cannot join application - accesser limit exceeded | |
|
Description |
An ATMI function was called in a client before calling |
Action |
This is a application configuration problem. The number of accessers is too small and must be reconfigured to allow more clients. | |
See Also |
| |
1429 |
ERROR: Could not access file filename | |
|
Description |
An attempt to get the status of a file failed. This file was created for temporary storage of a reply message. This is an operating system error that could be a result of an accidental deletion of the file, a change in file permissions, or a hardware problem. |
Action |
Files created for this purpose have a prefix of W. Check for the existence of such files in the specified directory. If none are found, restart the client. | |
1430 |
ERROR: Unable to retrieve stored reply | |
|
Description |
An attempt to retrieve a stored conversation reply failed. This message was either stored in memory or in a temporary file. |
Action |
If the message was stored in memory, then this indicates an internal BEA TUXEDO system problem. In this case the client should be shut down and restarted. Your BEA TUXEDO system Technical Support should be informed. If the message was stored in a temporary file, this could indicate a permissions problem or a hardware failure. Consult your UNIX system administrator in this case. | |
1431 |
ERROR: Received conversational message not stored | |
|
Description |
The application has asked for a conversational reply with a connection descriptor unknown to the system. This error should have been detected in |
Action |
The application should be restarted. If the problem still occurs, contact your BEA TUXEDO system Technical Support. | |
1432 |
ERROR: Send of OWS_RECV message failed | |
|
Description |
An attempt to send a request to the Workstation Handler process failed. This could be a result of the network going down, the Workstation Handler process not running, or the site of the Workstation Handler going down. |
Action |
Shut the client down and attempt to reconnect. If this fails, contact your BEA TUXEDO system Technical Support. | |
1433 |
ERROR: Unable to save a conversational message reply | |
|
Description |
An attempt to save a conversational message reply failed. There are two possible causes. The first is that the environment variable |
Action |
In the first case, the value of | |
1434 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory to save a conversational message reply failed. |
Action |
The value of | |
1435 |
ERROR: Unable to store conversational message in temporary file | |
|
Description |
An attempt to save a conversational reply message in a temporary file has failed. If the application has the necessary permissions, then the device must be full. |
Action |
Check the setting of the environment variable | |
1436 |
ERROR: Invalid connection descriptor | |
|
Description |
An attempt was made to retrieve a message with an invalid connection descriptor. |
Action |
Check for an application error that would cause this situation. If no errors are found, contact your BEA TUXEDO system Technical Support. | |
1437 |
ERROR: Unable to read conversational message from temporary file | |
|
Description |
An attempt to process a conversational reply failed. Earlier messages indicate the exact nature of the problem. |
Action |
Look for earlier messages in the log file (e.g., 1429, 1016, 1077, or 1017). | |
1438 |
ERROR: Invalid connection descriptor | |
|
Description |
An attempt was made to retrieve a message with an invalid connection descriptor. |
Action |
Check for an application error that would cause this situation. If no errors are found, contact your BEA TUXEDO system Technical Support. | |
1439 |
ERROR: tpconnect() message send failure | |
|
Description |
An attempt to send a request to the Workstation Handler process failed during a |
Action |
Shut the client down and attempt to reconnect. If this fails, contact your BEA TUXEDO system Technical Support. | |
1440 |
ERROR: tpconnect() get reply failed | |
|
Description |
An attempt to receive an acknowledgment to a |
Action |
Shut the client down and attempt to reconnect. If this fails, contact your BEA TUXEDO system Technical Support. | |
1441 |
ERROR: Unable to send message | |
|
Description |
An attempt to send a request to the Workstation Handler process failed during a |
Action |
Shut the client down and attempt to reconnect. If this fails, contact your BEA TUXEDO system Technical Support. | |
1442 |
ERROR: Unable to get reply | |
|
Description |
An attempt to receive an acknowledgment to a |
Action |
Shut the client down and attempt to reconnect. If this fails, contact your BEA TUXEDO system Technical Support. | |
1443 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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. | |
1444 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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. | |
1445 |
ERROR: tpchkauth failed - Uunixerr = errno | |
|
Description |
An operating system error occurred while attempting to determine the level of authentication required by the application configuration. A code is printed indicating the specific UNIX System call that failed. These codes may be referenced in the header file |
Action |
Attempt to determine why the UNIX System call is failing. Often, this error will occur if the | |
See Also |
| |
1446 |
ERROR: Cannot create buffer - tpalloc() failed - errmsg | |
|
Description |
While executing |
Action |
The | |
See Also |
| |
1447 |
ERROR: Cannot become a client - tpinit() failed - errmsg | |
|
Description |
The |
Action |
The | |
See Also |
| |
1448 |
ERROR: tpalloc for TPINIT failed - errmsg | |
|
Description |
While executing |
Action |
The | |
See Also |
| |
1449 |
ERROR: Cannot start a transaction - tpbegin() failed - errmsg | |
|
Description |
|
Action |
The | |
See Also |
| |
1450 |
ERROR: Cannot commit transaction - tpcommit() failed - errmsg | |
|
Description |
|
Action |
The | |
See Also |
| |
1451 |
ERROR: tpalloc for TPINIT failed - errmsg | |
|
Description |
While executing |
Action |
The | |
See Also |
| |
1452 |
ERROR: Cannot become a client - tpinit() failed - errmsg | |
|
Description |
While executing |
Action |
The | |
See Also |
| |
1453 |
ERROR: Cannot create buffer - tpalloc() failed - errmsg | |
|
Description |
While executing |
Action |
The | |
See Also |
| |
1458 |
ERROR: Invalid installation - can't find file | |
|
Description |
This is an unauthorized BEA TUXEDO system installation. |
Action |
For a valid installation, contact your BEA TUXEDO system Technical Support. | |
1460 |
ERROR: SJIS conversion failed | |
|
Description |
Converting an unsolicited message from SJIS to EUC format failed. This indicates that the input data was invalid. |
Action |
Check that the application is generating valid SJIS format. | |
1461 |
ERROR: EUC conversion failed | |
|
Description |
Restoring an unsolicited message from EUC to SJIS format failed. This indicates that the input data was invalid. |
Action |
Since this is undoing the earlier action, this error should not occur. Call BEA TUXEDO system Technical Support. | |
1462 |
ERROR: EUC conversion failed | |
|
Description |
Converting a received message from EUC to SJIS format failed. This indicates that the input data was invalid. |
Action |
Check that the application server is generating valid EUC format. | |
1463 |
ERROR: SJIS conversion failed | |
|
Description |
Converting an unsolicited message to be transmitted from SJIS to EUC format failed. This indicates that the input data was invalid. |
Action |
Check that the application is generating valid SJIS format. | |
1464 |
ERROR: SJIS conversion failed | |
|
Description |
Converting a message to be transmitted from SJIS to EUC format failed. This indicates that the input data was invalid. |
Action |
Check that the application is generating valid SJIS format. | |
1465 |
ERROR: EUC conversion failed | |
|
Description |
Restoring a converted message from EUC to SJIS format failed. This indicates that the input data was invalid. |
Action |
Since this is undoing the earlier action, this error should not occur. Call BEA TUXEDO system Technical Support. | |
1467 |
ERROR: Unable to initialize type switch | |
|
Description |
Initialization of the Workstation client type switch failed. |
Action |
Look for earlier messages in the event log for more details (e.g., memory allocation failure). | |
See Also |
| |
1468 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system failed while processing an |
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. | |
1470 |
ERROR: tpcall() failed, tperrmsg | |
|
Description |
The command |
Action |
Determine from the specific cause of the error if the problem can be corrected administratively or is a transient problem (for example, a timeout). Contact your BEA TUXEDO system Technical Support for assistance if unsure of how to resolve the situation. | |
See Also |
Administering the BEA TUXEDO System, | |
1472 |
ERROR: Cannot map XID to string, invalid mchidshift setting | |
|
Description |
An error occurred when mapping an XID to string. |
Action |
This error should not normally occur. Call BEA TUXEDO system Technical support. | |
See Also |
| |
1473 |
ERROR: Cannot map XID string to structure on /WS platforms | |
|
Description |
A Workstation client called |
Action |
Re-write the client so that it no longer does this operation. If needed, write a service that does this operation on behalf of the client. | |
See Also |
| |
1474 |
WARN: Trace specification contains pattern; ignored | |
|
Description |
A trace specification includes a regular expression pattern. This feature is not supported on MAC workstations. |
Action |
Re-write the client to not use regular expressions in the trace specification. | |
See Also |
| |
1475 |
ERROR: Cannot convert message with unknown protocol num | |
|
Description |
A Workstation client received a message from a Workstation Handler (WSH) with an unknown protocol number, num. |
Action |
Check that the | |
1476 |
ERROR: Cannot convert message from protocol num1 to num2 | |
|
Description |
The Workstation client received a message to or from a Workstation Handler (WSH) with a protocol version that cannot be converted. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
1477 |
INFO: WS Handler has been shutdown | |
|
Description |
A Workstation client received a shutdown message from the Workstation Handler. Further operations will fail until the client re-joins the application. |
Action |
No action required. | |
See Also |
| |
1480 |
ERROR: Cannot convert message with unknown protocol num | |
|
Description |
A Workstation client received a message from a Workstation Handler (WSH) with an unknown protocol number, num. |
Action |
Check that the | |
1481 |
ERROR: Cannot convert message from protocol num1 to num2 | |
|
Description |
The Workstation client received a message to or from a Workstation Handler (WSH) with a protocol version that cannot be converted. |
Action |
Contact your BEA TUXEDO system Technical Support. |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|