![]() |
![]() |
|
|
4000 |
WARN: duplicate interface servicename passed in to be advertised... | |
|
Description |
An interface with the same Interface ID has already been registered with the WLE infrastructure. |
Action |
Check the application server code for any interface being specified more than once. | |
4001 |
WARN: interface ID servicename longer than max length allowed, truncating to number bytes... | |
|
Description |
The specified interface has an Interface ID longer than the allowed limit. |
Action |
Shorten the Interface ID length to allowed length. | |
4002 |
WARN: Implementation ID servicename of interface servicename longer than max length allowed, truncating to number bytes... | |
|
Description |
The specified interface has an Implementation ID longer than the allowed limit. |
Action |
Shorten the Implementation ID length to allowed length. | |
4003 |
ERROR: Memory allocation failure | |
|
Description |
The server process could not allocate virtual memory. |
Action |
Either reduce the memory usage on the machine or add more memory. Try increasing space on the swap device. | |
4004 |
ERROR: Internal error, could not determine address of default ORB function. | |
|
Description |
The server has encountered an internal error while registering its interfaces with the WLE infrastructure. Contact BEA Customer Support. |
Action |
Contact BEA Customer Support. | |
4005 |
ERROR: Internal error, could not set TMPROC values. | |
|
Description |
The server has encountered an internal error while registering its interfaces with the WLE infrastructure. |
Action |
Contact BEA Customer Support. | |
4006 |
ERROR: Internal error, could not get parameters for interface servicename | |
|
Description |
The server has encountered an internal error while registering its interfaces with the WLE infrastructure. |
Action |
Contact BEA Customer Support. | |
4008 |
ERROR: Internal error, could not advertise interfaces... | |
|
Description |
The server has encountered an internal error while registering its interfaces with the WLE infrastructure. |
Action |
Contact BEA Customer Support. | |
4009 |
ERROR: Interface servicename's policies not consistent across Group Group, could not advertise interfaces... | |
|
Description |
The specified interface is being offered by another server in the specified group with different deactivation or transaction policies. This is not allowed. |
Action |
Make sure all instances of the interface across all servers in the group have the same activation and transaction policies. | |
4010 |
ERROR: Bulletin Board limit reached, could not advertise interfaces... | |
|
Description |
Maximum number of interfaces in the application (as specified by the |
Action |
Increase this parameter to a higher value. This can be done at run time using the TMIB API or | |
4011 |
ERROR: [NULL interface name used to get interface information] | |
|
Description |
The server has encountered an internal error while registering its interfaces with the WLE infrastructure. |
Action |
Contact BEA Customer Support. | |
4012 |
ERROR: Maximum number of types/subtypes, val, has been exceeded | |
|
Description |
The maximum number of types/subtypes permitted for a particular Tuxedo System/T interface has been exceeded. The number allowed is val. |
Action |
Review the configuration file, verify that all interfaces use less than the maximum number of types/subtypes, and reload the | |
See Also |
| |
4013 |
ERROR: [Invalid buffer type information val] | |
|
Description |
The buffer type information provided in the configuration file for an interface entry was incorrect. |
Action |
Check the configuration file, verify that the buffer type provided is correct, and repeat the operation. | |
See Also |
| |
4014 |
ERROR: [Invalid buffer subtype information val] | |
|
Description |
The buffer subtype information provided in the configuration file for an interface entry was incorrect. |
Action |
Check the configuration file, verify that the buffer type provided is correct, and repeat the operation. | |
See Also |
| |
4015 |
ERROR: Memory allocation failure | |
|
Description |
The server process could not allocate virtual memory. |
Action |
Either reduce the memory usage on the machine or add more memory. Try increasing space on the swap device. | |
4016 |
ERROR: Interface parameter error in internal routine | |
|
Description |
The server has encountered an internal error while registering its interfaces with the WLE infrastructure. |
Action |
Contact BEA Customer Support. | |
4017 |
ERROR: Invalid interface information passed to internal routine | |
|
Description |
The server has encountered an internal error while registering its interfaces with the WLE infrastructure. |
Action |
Contact BEA Customer Support. | |
4018 |
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 swap space and physical memory on the machine. | |
4020 |
ERROR: tmrsvrs() returned multiple servers. | |
|
Description |
The server has encountered an internal error while registering its interfaces with the WLE infrastructure. |
Action |
Contact BEA Customer Support. | |
4021 |
WARN: Duplicate FACTORY routing criteria crit | |
|
Description |
A routing criteria crit,
buffer type combination typ was specified more than once
in the ROUTING section of the |
Action |
Correct the configuration file to remove the duplicate entry, and rerun
| |
See Also |
Administering the BEA Tuxedo System,
| |
4023 |
ERROR: Invalid interface information passed to internal routine | |
|
Description |
The server has encountered an internal error while unregistering interfaces with the WLE infrastructure. |
Action |
Contact BEA Customer Support. | |
4024 |
ERROR: invalid service name found | |
|
Description |
The server has encountered an internal error while reading the WLE Bulletin Board. |
Action |
Contact BEA Customer Support. | |
4026 |
ERROR: Internal error, could not set policies for interface servicename | |
|
Description |
The server has encountered an internal error while registering its interfaces with the WLE infrastructure. |
Action |
Contact BEA Customer Support. | |
4027 |
ERROR: [Memory allocation failure.] | |
|
Description |
The server process could not allocate virtual memory. |
Action |
Either reduce the memory usage on the machine or add more memory. Try increasing space on the swap device. | |
4028 |
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 swap space and physical memory on the machine. | |
4029 |
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 swap space and physical memory on the machine. | |
4030 |
WARN: Interface val's transaction policy setting of "IGNORE" or "NEVER" conflicts with "AUTOTRAN=Y" setting in UBBCONFIG file, turning off AUTOTRAN setting... | |
|
Description |
An interface has its transaction policy set to either |
Action |
Change either the setting in the | |
4031 |
ERROR: Internal error, process could not attach to bulletin board... | |
|
Description |
A process was booted with |
Action |
Contact BEA Customer Support. | |
See Also |
| |
4032 |
ERROR: Internal error, process could not detach from bulletin board... | |
|
Description |
A process was booted with |
Action |
Contact BEA Customer Support. | |
See Also |
| |
4033 |
ERROR: Internal error, process could not detach from bulletin board... | |
|
Description |
A process was booted with |
Action |
Contact BEA Customer Support. | |
See Also |
| |
4034 |
WARN: Interface val's transaction policy setting of "MANDATORY" conflicts with "AUTOTRAN=Y" setting in UBBCONFIG file, turning off AUTOTRAN setting... | |
|
Description |
An interface has its transaction policy set to either |
Action |
Change either the setting in the | |
4035 |
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 swap space and physical memory on the machine. | |
4036 |
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 swap space and physical memory on the machine. | |
4039 |
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 swap space and physical memory on the machine. | |
4040 |
WARN: interface ID val longer than max length allowed, truncating to val bytes... | |
|
Description |
The specified interface has an Interface ID longer than the allowed limit. |
Action |
Shorten the Interface ID length to the allowed length. | |
4041 |
WARN: Implementation ID val of interface val longer than max length allowed, truncating to val bytes... | |
|
Description |
The specified implementation ID of the specified interface is longer than the allowed limit. |
Action |
Shorten the Implementation ID length to the allowed length. | |
4042 |
WARN: interface val passed in to be unadvertised is not currently advertised by this server... | |
|
Description |
This Interface has NOT been previously registered with the WLE infrastructure. |
Action |
Check application code if Interface being unregistered had indeed been registered previously. | |
4043 |
WARN: duplicate interface val passed in to be unadvertised... | |
|
Description |
An interface having the same Interface ID has already been passed in to be unadvertised. |
Action |
Check application code if same Interface is being passed in repeatedly to be unregistered. | |
4044 |
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 swap space and physical memory on the machine. | |
4045 |
ERROR: Internal error, process could not attach to bulletin board... | |
|
Description |
A process was booted with |
Action |
Contact BEA Customer Support. | |
See Also |
| |
4046 |
ERROR: Internal error, invalid internal service name found in in-process table | |
|
Description |
An internal error has occurred while trying to unregister Interfaces. |
Action |
Contact BEA Customer Support. | |
4047 |
ERROR: Internal error, could not unadvertise interfaces... | |
|
Description |
An internal error has occurred while trying to unregister Interfaces. |
Action |
Contact BEA Customer Support. | |
4048 |
ERROR: Internal error, process could not detach from bulletin board... | |
|
Description |
A process was booted with |
Action |
Contact BEA Customer Support. | |
See Also |
| |
4049 |
ERROR: Internal error, in-process table corrupted... | |
|
Description |
An internal error has occurred while trying to (un)register Interfaces. |
Action |
Contact BEA Customer Support. | |
4050 |
ERROR: Internal error, process could not detach from bulletin board... | |
|
Description |
A process was booted with |
Action |
Contact BEA Customer Support. | |
See Also |
| |
4051 |
ERROR: Internal error, process could not detach from bulletin board... | |
|
Description |
A process was booted with |
Action |
Contact BEA Customer Support. | |
See Also |
| |
4052 |
ERROR: NULL input buffer not allowed for service 'service_name', which uses routing | |
|
Description |
An application program passed a NULL input buffer to the service service_name, which is defined in the configuration file as using routing. Since the null buffer is not a valid type to perform routing on, the service call was rejected with an error. |
Action |
Recode the service call that resulted in the error so that the input buffer is of one of the types specified in the routing criterion that is associated with this service in the UBBCONFIG file. | |
See Also |
| |
4053 |
ERROR: Routing function failed | |
|
Description |
The function used to perform data dependent routing during a service call returned an error. If using the Tuxedo System/T supplied routing functions, a previous userlog message will give more specifics as to the cause of the error. If the application administrator modified the buffer type switch to add additional routing functions, a previous userlog message may or may not be present. |
Action |
Refer to the previous message in the userlog for more information on the cause of the error. | |
See Also |
| |
4054 |
ERROR: Unknown group name returned from routing function | |
|
Description |
The function used to perform data dependent routing during a service call indicated that the current data is to be routed to a group name that does not exist. If using the routing functions for Tuxedo System/T supplied types, this should not happen. |
Action |
Contact BEA Customer Support. | |
4055 |
ERROR: No service 'service_name' in group 'group_name' | |
|
Description |
The service service_name is not offered as part of group group_name. This message may occur when the routing criterion associated with service service_name specifies one or more groups in which the service is not currently offered. |
Action |
Examine the routing criterion associated with service_name in the configuration file. Make certain that service service_name is offered in each group listed in the routing criterion. If the service is temporarily not available in a particular group, start the server(s) that offers service_name in that group. If service_name is not meant to be offered in a particular group, modify the routing criterion so that group is no longer listed. |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|