BEA Tuxedo
System Messages
LIBTUX Catalog
700-1399
BEA Tuxedo Release 7.1
Document Edition 7.1
May 2000
Copyright
Copyright © 2000 BEA Systems, Inc. All Rights Reserved.
Restricted Rights Legend
This software and documentation is subject to and made available only pursuant to the terms of the BEA Systems
License Agreement and may be used or copied only in accordance with the terms of that agreement. It is against
the law to copy the software except as specifically allowed in the agreement. This document may not, in whole or
in part, be copied photocopied, reproduced, translated, or reduced to any electronic medium or machine readable
form without prior consent, in writing, from BEA Systems, Inc.
Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the BEA Systems
License Agreement and in subparagraph (c)(1) of the Commercial Computer Software-Restricted Rights Clause
at FAR 52.227-19; subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at
DFARS 252.227-7013, subparagraph (d) of the Commercial Computer Software--Licensing clause at NASA FAR
supplement 16-52.227-86; or their equivalent.
Information in this document is subject to change without notice and does not represent a commitment on the part
of BEA Systems. THE SOFTWARE AND DOCUMENTATION ARE PROVIDED "AS IS" WITHOUT
WARRANTY OF ANY KIND INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. FURTHER, BEA Systems DOES
NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THE
RESULTS OF THE USE, OF THE SOFTWARE OR WRITTEN MATERIAL IN TERMS OF CORRECTNESS,
ACCURACY, RELIABILITY, OR OTHERWISE.
Trademarks or Service Marks
BEA, ObjectBroker, TOP END, and Tuxedo are registered trademarks of BEA Systems, Inc. BEA Builder, BEA
Connect, BEA Manager, BEA MessageQ, BEA Jolt, M3, eSolutions, eLink, WebLogic, and WebLogic Enterprise
are trademarks of BEA Systems, Inc.
All other company names may be trademarks of the respective companies with which they are associated.
BEA Tuxedo System Messages LIBTUX Catalog
Document Edition
Date
Software Version
7.1
May 2000
BEA Tuxedo Release 7.1
LIBTUX Messages 700-799
700 ERROR: Invalid search key
Description An internal BEA TUXEDO system table was requested, and could not be read because an invalid search
key was passed to the low-level access routine.
Action
Contact your BEA TUXEDO system Technical Support.
701 ERROR: [Parameter error in internal routine]
Description One of the internal routines to modify structures in the TUXEDO System/T bulletin board received a
parameter that did not match any of the allowable values.
Action
Contact your BEA TUXEDO system Technical Support.
703 ERROR: Cannot get statistics on message queue number
Description A msgctl kernel call performing an IPC-STAT operation failed for message queue number.
Action
Contact your BEA TUXEDO system Technical Support.
704 ERROR: Operating system parameter for message queues too small
Description The UNIX System kernel parameters related to message queues are set too low.
Action
Check the kernel parameters related to message queue capacities, and increase if necessary. In particular,
check MSGMNB.
See Also
BEA TUXEDO Installation Guide
705 ERROR: No BRIDGE available for remote send
Description A BEA TUXEDO system process attempted to send a message to another machine, but the BRIDGE
system process could not be located.
Action
Shut down and reboot the BEA TUXEDO system on this machine.
709 ERROR: Memory allocation failure
Description An attempt dynamically to allocate memory from the operating system using malloc() failed while
searching for the BRIDGE system process’s server table entry.
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.
710 ERROR: Server table index out of range
Description A service could not be advertised because of an invalid internal handle identifying the server process
offering it.
Action
Contact your BEA TUXEDO system Technical Support.
711 ERROR: Server table index out of range
Description A service could not be advertised because of an internal data structure inconsistency.
Action
Contact your BEA TUXEDO system Technical Support.
712 ERROR: Memory allocation failure
Description An attempt dynamically to allocate memory from the operating system using malloc() failed while
advertising a service.
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.
713 ERROR: Queue parameter error in internal routine
Description One of the internal routines to manage TUXEDO System/T data structures received an invalid queue
table parameter. This should not occur during normal system operation.
Action
Contact your BEA TUXEDO system Technical Support.
715 ERROR: Cannot attach bulletin board - magic number mismatch
1
Description The process just attached to a shared memory region, expecting to find a BEA TUXEDO system bulletin
board. The header’s magic number indicates that it is not a valid bulletin board.
Action
Verify that the configuration file’s IPCKEY parameter is unique, and not being used by any other
software product on the machine. The UNIX ipcs utility may help diagnose the conflict.
716 ERROR: Cannot attach bulletin board - wrong release of software
Description The BEA TUXEDO system software has been updated on the machine, but this process has not been
rebuilt with the new libraries. It therefore cannot interpret the bulletin board data structures.
Action
Rebuild the process with updated BEA TUXEDO system libraries.
See Also
buildclient(1), buildserver(1), buildtms(1), buildwsh(1), buildmio(1)
717 ERROR: Cannot attach to or create shared memory
Description The calling process could not attach to the bulletin board’s shared memory. It then attempted to create
the bulletin board, but did not have the correct permissions to do so.
Action
Verify that the configuration file’s IPCKEY parameter is correct, and that the application is booted.
721 ERROR: Server group creation failure
Description A server group entry in the bulletin board could not be created due to an internal error.
Action
Contact your BEA TUXEDO system Technical Support.
722 ERROR: Cannot add subtype to bulletin board
Description A subtype could not be added to the bulletin board due to an internal error.
Action
Contact your BEA TUXEDO system Technical Support.
723 ERROR: Cannot add subtype: no more room in subtype table
Description The bulletin board’s subtype table is full, and a new subtype cannot be added.
Action
Increase the MAXBUFSTYPE parameter in the configuration file’s RESOURCES section.
724 ERROR: Service information invalid
Description A BEA TUXEDO system internal function was used to retrieve service information from the services
table, but a NULL service name was used.
Action
Contact your BEA TUXEDO system Technical Support for assistance.
725 ERROR: Server information invalid, does not exist
Description An internal error occurred while a service was being added to the bulletin board’s tables.
Action
Contact your BEA TUXEDO system Technical Support.
726 ERROR: Server information invalid, does not exist
Description An internal data structure inconsistency was detected while a service was being added to the bulletin
board’s tables.
Action
Contact your BEA TUXEDO system Technical Support.
727 ERROR: [Server parameter error in internal routine]
Description The internal routine to create a server table entry received invalid parameters. This should not happen
during normal system operation.
Action
Contact your BEA TUXEDO system Technical Support.
728 ERROR: [Queue parameter error in internal routine]
Description One of the internal routines to manage TUXEDO System/T data structures received an invalid queue
table parameter. This should not occur during normal system operation.
Action
Contact your BEA TUXEDO system Technical Support.
729 ERROR: Server not available, doing work
Description An attempt to create a server table entry failed because the server was busy.
Action
Wait until the server is no longer busy, and then retry the failed operation.
730 ERROR: No space for another queue table entry
2
Description There are no more queue table entries left in the system. The number of queue table entries is equal to
the maximum number of servers as specified in the UBBCONFIG file.
Action
Increase the maximum number of servers, as specified by the MAXSERVERS parameter in the
RESOURCES section of the UBBCONFIG file. This can be done by editing the configuration file and
reloading it with tmloadcf(1), or it can be done through dynamic administration using the
tmconfig(1) command.
See Also
ubbconfig(5), tmloadcf(1), tmconfig(1)
732 ERROR: BBL unstable or dead
Description The BBL (Bulletin Board Liaison) process is unstable or dead.
Action
Look for associated messages in the userlog related to the BBL. These may give more insight about the
problem. If using a multi-node configuration, make certain that the network is operating properly and
has sufficient bandwidth. Verify that the TUXEDO System/T administrator or the UNIX System
administrator did not kill the BBL process. Oftentimes, a network that is inoperative or slow may result
in a BBL response problem.
733 ERROR: [Type information invalid]
Description The internal routine to create an entry in the bulletin board types table was passed invalid parameters.
This should not happen during normal system operation.
Action
Contact your BEA TUXEDO system Technical Support.
734 ERROR: Cannot add to type table due to lack of space
Description There are no more type table entries left in the system. An attempt to add an additional type to the
bulletin board has failed due to a lack of space. The number of type table entries is equal to the number
specified in the UBBCONFIG file.
Action
Increase the maximum number of type table entries, as specified by the MAXBUFTYPE parameter in
the RESOURCES section of the UBBCONFIG file. This can be done by editing the configuration file
and reloading it with tmloadcf(1), or it can be done through dynamic administration using the
tmconfig(1) command.
See Also
ubbconfig(5), tmloadcf(1), tmconfig(1)
735 ERROR: [Queue parameter error in internal routine]
Description See message 728 for an explanation.
Action
See message 728 for an explanation.
736 ERROR: [Cannot delete entry from queue table due to invalid server association]
Description An attempt to delete an entry from the internal TUXEDO System/T queue table failed while attempting
to delete one of the servers associated with the queue. This should not happen during normal system
operation.
Action
Contact your BEA TUXEDO system Technical Support.
737 ERROR: [Invalid service information passed to internal routine]
Description One of the internal routines to manage TUXEDO System/T data structures received an invalid service
table parameter. This should not occur during normal system operation.
Action
Contact your BEA TUXEDO system Technical Support.
738 ERROR: [Invalid server information passed to internal routine]
Description One of the internal routines to manage TUXEDO System/T data structures received an invalid server
table parameter. This should not occur during normal system operation.
Action
Contact your BEA TUXEDO system Technical Support.
739 ERROR: [Inconsistent service/server associations in bulletin board]
Description The TUXEDO System/T bulletin board data structures contain an invalid service/server association.
This indicates a corruption of data structures and should not occur during normal system operation.
Action
Contact your BEA TUXEDO system Technical Support.
741 ERROR: Routing function failed
3
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
ubbconfig(5), tuxtypes(5)
742 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 your BEA TUXEDO system Technical Support.
743 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.
744 ERROR: Not attached to a Bulletin Board
Description The process producing this error message is not attached to the TUXEDO System/T configuration.
Action
If this message occurred in a client process, make sure that the process successfully invokes tpinit()
before issuing any other System/T calls (with the exception of calls noted as being specifically allowed
prior to tpinit()). If the error occurred within an administrative process or a server process, contact
your BEA TUXEDO system Technical Support.
745 ERROR: Process not attached to a Bulletin Board
Description See message 744 for an explanation.
Action
See message 744 for an explanation.
746 ERROR: Cannot lock Bulletin Board
Description A process was unable to lock the TUXEDO System/T shared memory data structures.
Action
Contact your BEA TUXEDO system Technical Support.
747 ERROR: Process not attached to Bulletin Board
Description See message 744 for an explanation.
Action
See message 744 for an explanation.
748 ERROR: Cannot unlock Bulletin Board
Description The process was unable to successfully unlock the TUXEDO System/T Bulletin Board. As a result of
this problem, other processes will be unable to lock the Bulletin Board. The most common cause of this
error is the accidental removal of some or all of the TUXEDO System/T semaphore sets.
Action
Ask the privileged users on your system (normally the TUXEDO System/T administrator and root)
whether they may have accidentally removed some IPC resources, perhaps through inadvertent use of
the UNIX System ipcrm(1) command. If no IPC resources have been accidentally removed, contact
your BEA TUXEDO system Technical Support.
749 ERROR: Cannot unlock Bulletin Board, not the locker
Description The process attempted to unlock the TUXEDO System/T Bulletin Board, but it was not the locker of the
Bulletin Board. Because of this, no change was made to the status of the Bulletin Board.
Action
Contact your BEA TUXEDO system Technical Support.
751 ERROR: semop system call failure for semaphore semno, errno = errno_val
4
Description A semop(2) system call failed for one of the semaphores that control access to TUXEDO System/T data
structures. The semno refers to the index of the semaphore within a particular set; this information may
be useful to support technicians. errno refers to the UNIX System error returned by the semop(2)
system call. This value can be very helpful to application administrators in diagnosing the cause of the
problem.
Action
Refer to the UNIX System intro(2) and semop(2) manual pages to translate the numeric value of
errno into a symbolic value and determine the possible causes of such an error. For example, errno
values of 22 (
752 ERROR: semop system call failure for semaphore semno, errno errno_val
Description See message 751 for an explanation.
Action
See message 751 for an explanation.
753 ERROR: [Invalid service information passed to internal routine]
Description See message 737 for an explanation. See message 737 for an explanation.
754
ERROR: Service does not match existing services offered
Description When a new server is added to an existing group of servers on an MSSQ set, the new server must offer
the same set of services as the existing servers, and these services must be performed by the same
service functions. Also, the executable for the new server must be the same file as the existing server(s)
on the queue, or a link to the same file. The server being started did not obey these restrictions.
Action
Make sure that the path name of the new server executable is the same as the path name for the existing
server(s) on the queue used by the new server. Determine the services currently advertised on the server
queue, and make sure that the new server offers the same set of services. The services currently offered
on a queue can be determined through the tmadmin(1) printservice command with the -q option.
See Also
tmadmin(1), ubbconfig(5)
755 ERROR: Restarting server cannot delete queue
Description A server being restarted by the restartsrv(1) command was unable to delete an entry from the
TUXEDO System/T queue table.
Action
Contact your BEA TUXEDO system Technical Support.
See Also
restartsrv(1)
756 ERROR: Cannot get status for server files new_server_executable and existing_server_executable
Description When adding a server to an MSSQ set on which there are already one or more servers executing, the
BEA TUXEDO system verifies that the new server either has the same file name as the existing
server(s) or is a link to these server(s). This latter check requires executing the UNIX System stat(2)
system call on the new server and an existing server. This call failed for one or both of these servers. As
a result of this failure, the new server will not be started.
Action
Make certain that both files listed in the error message exist, that all components in the path prefixes of
these files are directories, and that the user ID under which the new server is being started has search
permission on every directory in the path prefix. Refer to the UNIX System stat(2) reference page for
further information.
See Also
stat(2)
757 ERROR: Memory allocation failure
Description The BEA TUXEDO system received an error return when attempting to allocate memory from the
operating system
Action
Attempt to decrease the amount of memory required by TUXEDO System/T, or add more physical
memory to the machine. The amount of memory required by the BEA TUXEDO system is influenced by
the parameters given in the UBBCONFIG file. Refer to the Administering the BEA TUXEDO System for
further information. The number of processes running on a machine and the options given to those
processes also have a large effect on memory usage.
758 ERROR: Cannot find desired server to remove
Description While attempting to remove a server from the TUXEDO System/T bulletin board, the BEA TUXEDO
system was unable to find the server in its internal tables.
Action
Contact your BEA TUXEDO system Technical Support.
759 ERROR: Cannot find queue entry for server that is to be removed
5
Description While attempting to remove a server from the TUXEDO System/T bulletin board, the BEA TUXEDO
system was unable to find the queue associated with the server in its internal tables
Action
Contact your BEA TUXEDO system Technical Support.
760 ERROR: [Queue parameter error in internal routine]
Description See message 728 for an explanation.
Action
See message 728 for an explanation.
761 ERROR: [Queue parameter error in internal routine]
Description See message 728 for an explanation.
Action
See message 728 for an explanation.
762 ERROR: [Parameter error in internal routine]
Description One of the internal routines to modify structures in the TUXEDO System/T bulletin board received a
parameter that did not match any of the allowable values.
Action
Contact your BEA TUXEDO system Technical Support.
763 ERROR: [Server group parameter error in internal routine]
Description One of the internal TUXEDO System/T routines to manipulate server group parameters within the
bulletin board received an invalid input parameter. This should not happen during normal system
operation.
Action
Contact your BEA TUXEDO system Technical Support.
764 ERROR: [Server group parameter error in internal routine]
Description See message 763 for an explanation.
Action
See message 763 for an explanation.
765 ERROR: [Server group parameter error in internal routine]
Description See message 763 for an explanation.
Action
See message 763 for an explanation.
766 ERROR: [Parameter error in internal routine]
Description See message 762 for an explanation.
Action
See message 762 for an explanation.
767 ERROR: [Parameter error in internal routine]
Description See message 762 for an explanation.
Action
See message 762 for an explanation.
768 ERROR: [Invalid service information passed to internal routine]
Description See message 737 for an explanation.
Action
See message 737 for an explanation.
769 ERROR: [Invalid service information passed to internal routine]
Description See message 737 for an explanation.
Action
See message 737 for an explanation.
770 ERROR: [Invalid service information passed to internal routine]
Description See message 737 for an explanation.
Action
See message 737 for an explanation.
771 ERROR: [Invalid service information passed to internal routine]
Description See message 737 for an explanation.
Action
See message 737 for an explanation.
772 ERROR: Invalid search criteria given
Description See message 762 for an explanation.
Action
See message 762 for an explanation.
773 ERROR: Invalid server information given
6
Description This error occurs when a client or server is requesting to look up server table entries in the Bulletin
Board by SRVID and GROUPID, and supplies incorrect or NULL arguments. This happens if there is a
bug in the calling routine.
Action
Report this failure to your BEA TUXEDO system Technical Support.
774 ERROR: Invalid server information given
Description This error occurs when a client or server is requesting to look up server table entries in the Bulletin
Board by GROUP and MACHINE, and supplies incorrect or NULL arguments. This happens if there is a
bug in the calling routine.
Action
Report this failure to your BEA TUXEDO system Technical Support.
775 ERROR: Invalid queue information given
Description This error occurs when a client or server is requesting to look up server table entries in the Bulletin
Board by QUEUE name, and supplies incorrect or NULL arguments. This happens if there is a bug in the
calling routine.
Action
Report this failure to your BEA TUXEDO system Technical Support.
776 ERROR: Invalid server information given
Description This error occurs when a client or server is requesting to look up server table entries in the Bulletin
Board by using the rlink field or a TMID, and supplies incorrect or NULL arguments. This happens if
there is a bug in the calling routine.
Action
Report this failure to your BEA TUXEDO system Technical Support.
777 ERROR: Invalid search criteria given
Description This error occurs when a client or server is requesting to look up server table entries in the Bulletin
Board and supplies an incorrect or NULL scope argument. This happens if there is a bug in the calling
routine.
Action
Report this failure to your BEA TUXEDO system Technical Support.
778 ERROR: Invalid queue information given
Description This error occurs when a client or server is requesting to update queue table entries in the Bulletin Board
and supplies incorrect or NULL arguments. This happens if there is a bug in the calling routine.
Action
Report this failure to your BEA TUXEDO system Technical Support.
779 ERROR: Invalid server group information given
Description This error occurs when a client or server is requesting to update server group table entries in the Bulletin
Board and supplies incorrect or NULL arguments. This happens if there is a bug in the calling routine.
Action
Report this failure to your BEA TUXEDO system Technical Support.
780 ERROR: Invalid entry information given
Description This error occurs when a client or server is requesting to update the status of table entries in the Bulletin
Board and supplies incorrect or NULL arguments. This happens if there is a bug in the calling routine.
Action
Report this failure to your BEA TUXEDO system Technical Support.
781 ERROR: Invalid service information given
Description This error occurs when a client or server is requesting to update service table entries in the Bulletin
Board and supplies incorrect or NULL arguments. This happens if there is a bug in the calling routine.
Action
Report this failure to your BEA TUXEDO system Technical Support.
782 ERROR: Invalid server information given
Description This error occurs when a client or server is requesting to update server table entries in the Bulletin Board
and supplies incorrect or NULL arguments. This happens if there is a bug in the calling routine.
Action
Report this failure to your BEA TUXEDO system Technical Support.
788 ERROR: Memory allocation failure
Description An attempt dynamically to allocate memory from the operating system using malloc(3) failed.
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. Increase the space on the swap device.
See Also
malloc(3) in UNIX System reference manuals
789 ERROR: Memory allocation failure
7
Description An attempt dynamically to allocate memory from the operating system using malloc(3) failed.
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. Increase the space on the swap device.
See Also
malloc(3) in UNIX System reference manuals
790 ERROR: Memory allocation failure
Description An attempt dynamically to allocate memory from the operating system using malloc(3) failed.
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. Increase the space on the swap device.
See Also
malloc(3) in UNIX System reference manuals
791 ERROR: Memory allocation failure
Description An attempt dynamically to allocate memory from the operating system using malloc(3) failed.
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. Increase the space on the swap device.
See Also
malloc(3) in UNIX System reference manuals
792 ERROR: Memory allocation failure
Description An attempt dynamically to allocate memory from the operating system using malloc(3) failed.
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. Increase the space on the swap device.
See Also
malloc(3) in UNIX System reference manuals
793 ERROR: Memory allocation failure
Description An attempt dynamically to allocate memory from the operating system using malloc(3) failed.
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. Increase the space on the swap device.
See Also
malloc(3) in UNIX System reference manuals
8
LIBTUX Messages 1000-1099
1000 ERROR: System clock has been reset to prior time. Reset again to time after time.
Description The system clock as been reset such that the current time precedes the timestamps in the transaction log.
Action
Reset the system clock to the correct time. Retry the operation again, and if the problem persists,
contact your BEA TUXEDO system Technical Support.
1001 ERROR: Cannot receive reply because MSSQ is specified but REPLYQ is N
Description An error has occurred in receiving a reply from either a tpcall(3c) or tpacall(3c) because the
configuration file specifies that there should be no reply queue established for that particular server.
Action
If the server is expected to receive tpacall(3c) or tpcall(3c) replies, check and edit the
ubbconfig(5) file and specify REPLYQ=Y to establish a reply queue for that particular server. If the
server is not to receive replies, then use tpacall(3c) with the flags parameter set to TPNOREPLY.
See Also
ubbconfig(5), tpcall(3c), tpacall(3c)
1002 ERROR: tpforward called in conversational server; service error returned to originator
Description tpforward() cannot be used within a conversational service routine. The service returns
TPESVCERR or the TPEV_SVCERR event to the process on the other end of the conversation. The
conversation is terminated.
Action
The service routine should be changed to use tpreturn() instead of tpforward().
See Also
tpforward(3c), tprecv(3c), tpsend(3c)
1003 ERROR: xa_end flags returned error status
Description This message is issued if the process receiving a reply encounters an error upon calling the database
resource manager with xa_end(). The transaction fails to commit. The message prints the error code that
the function returned.
Action
Contact your BEA TUXEDO system Technical Support or your database system vendor.
1004 ERROR: xa_abort returned error
Description This message is issued when BEA TUXEDO tries unsuccessfully to rollback a transaction via
xa_rollback() after receiving a reply. The message prints the error code that the function returned.
Action
Contact your BEA TUXEDO system Technical Support or your database system vendor. See the
userlog for more information on the outcome of the transaction. Also, use tmadmin’s printtrans
command to find out more information about the transaction.
1005 INFO: Switched to dip-in based notification
Description When the client is joining the application, the specified or default notification is set to signal based. But
to use signal based notification, the userid must be the administrator’s. This message alerts the switch in
the notification mechanism.
Action
No action necessary.
1006 INFO: Using dip-in based notification instead of application default setting
Description When the client is joining the application, the notification mechanism is set to signal based (the
application default). But to use signal based notification, the user must be the administrator. This
message alerts the switch in the notification mechanism.
Action
No action necessary.
1007 INFO: Notification mechanism unknown. Switching to dip-in based notification
Description The notification mechanism is not specified, so the default (dip-in based) is used.
Action
No action necessary.
1013 ERROR: Migration failed: invalid type
Description The migration type code passed to the migration function is not valid.
Action
Contact your BEA TUXEDO system Technical Support.
1014 ERROR: Migration failed: Memory allocation failure
9
Description An attempt to dynamically allocate memory from the operating system using malloc() failed while
setting up a temporary data structure for the server table entry.
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.
1015 ERROR: Migration failed: Memory allocation failure
Description An attempt to dynamically allocate memory from the operating system using malloc() failed while
setting up a temporary data structure for the server group entry.
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.
1016 ERROR: Migration failed: Memory allocation failure
Description An attempt to dynamically allocate memory from the operating system using malloc() failed while
setting up a temporary data structure for the group process table.
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.
1017 ERROR: Migration failed: no group name
Description The group name passed to the migration function was empty.
Action
Verify that the group name for the migration request is valid. If so, contact your BEA TUXEDO system
Technical Support.
See Also
tmadmin(1)
1018 ERROR: Migration failed: bad group name, tperrno = tperrno_val
Description The group name passed to the migration function was invalid.
Action
Verify that the group name for the migration request is valid. If so, contact your BEA TUXEDO system
Technical Support.
See Also
tmadmin(1)
1019 ERROR: Migration failed: no machine name
Description The machine name passed to the migration function was empty.
Action
Verify that the machine name for the migration request is valid. If so, contact your BEA TUXEDO
system Technical Support.
See Also
tmadmin(1)
1020 ERROR: Migration failed: bad machine name, tperrno = tperrno_val
Description The machine name passed to the migrate function was invalid.
Action
Verify that the machine name for the migration request is valid. If so, contact your BEA TUXEDO
system Technical Support.
1021 ERROR: Migration failed: invalid current location
Description The entry in the server group table for the current lmid (the location that the servers are to be migrated
from) is invalid.
Action
Contact your BEA TUXEDO system Technical Support.
1023 ERROR: Migration failed: cannot update server group information
Description An attempt failed trying to update the entry or entries in the server group table.
Action
Contact your BEA TUXEDO system Technical Support.
1024 ERROR: Migration failed: cannot update server information
Description While updating the local bulletin board, an error occurred. This error could be caused by the following:
A failure to lock the bulletin board.
Queue or server information could not be retrieved.
Action
The failure to unlock the bulletin board.
Check the userlog for more information.
10
1026 ERROR: Migration failed: cannot migrate group on machine
Description A request to migrate the server group(s) to the BBL on the alternate location has failed. This error could
be caused by the following:
The failure to retrieve information from the bulletin board.
The request message itself could not be built.
Action
A failure occurred during the send/receive of the request.
Check the userlog for more information.
1027 ERROR: Migration failed: cannot retrieve new server information
Description The verification of the alternate location has failed. The bulletin board has been checked for
consistency, and one of the following errors has happened:
A timeout occurred before the information could be verified.
A lock was not granted for the bulletin board.
The server information could not be retrieved.
The bulletin board lock could not be released.
Action
The server has been "cleaning up" for an inordinate period of time.
Check the userlog for additional information to properly diagnose this error.
1029 ERROR: Migration failed: cannot find BBL information for lmid
Description An attempt to retrieve the server table entry for the servers to be migrated failed. The requested entry
was not found. This error is probably the result of an internal corruption of the bulletin board and not
the result of anything the user has done.
Action
Contact your BEA TUXEDO system Technical Support.
1030 ERROR: Migration failed: cannot retrieve BBL information for lmid, tperrno = tperrno_val
Description An attempt to retrieve the server table entry for the servers to be migrated failed. This error is probably
the result of an internal corruption of the bulletin board and not the result of anything the user has done.
Action
Contact your BEA TUXEDO system Technical Support.
1031 ERROR: Migration failed: cannot make request message
Description Creating an internal system message for the migrating servers fails. This error is due to the inability to
allocate enough memory for the 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 physical memory usage on the
machine or increase the amount of physical memory on the machine.
1032 ERROR: Migration failed: cannot send service request to BBL on lmid
Description The service request to start the migrating servers on the new site has failed.
Action
Check the userlog for additional information to determine the proper action to be taken.
1033 ERROR: Migration failed: invalid response from BBL on lmid
Description The response for the request to start the migrated servers on lmid returns an error. The bulletin board on
the machine lmid was unstable at the time of the migration request and therefore was aborted.
Action
Check the status of the bulletin board on lmid by using the tmadmin() sub-command printserver. If
the system is still running, try the command again and if it fails again, contact your BEA TUXEDO
system Technical Support. Otherwise, the machine lmid must be restarted before a migration may occur.
See Also
tmadmin(1)
1034 ERROR: Migration failed: invalid response from BBL on lmid, tperrno = tperrno_val
11
Description The response for the request to start the migrated servers on lmid returns an unknown status code. The
bulletin board on the machine lmid was unstable at the time of the migration request and therefore was
aborted.
Action
Check the status of the bulletin board on lmid by using the tmadmin() sub-command printserver. If
the system is still running, try the command again and if it fails again, contact your BEA TUXEDO
system Technical Support. Otherwise, the machine lmid must be restarted before a migration may occur.
See Also
tmadmin(1)
1035 ERROR: Migration failed: cannot lock BB, tperrno = tperrno_val
Description While confirming that all relevant servers are shut down for migration, the lock for the bulletin board
has not been granted.
Action
This may be the result of a transitive failure of a process attached to the bulletin board. Try the
command again; if this fails, contact your BEA TUXEDO system Technical Support.
1036 ERROR: Migration failed: cannot retrieve server information, tperrno = tperrno_val
Description While confirming that all relevant servers are shut down for migration, the server information in the
bulletin board cannot be retrieved.
Action
This may be the result of a transitive failure of a process attached to the bulletin board. Try the
command again; if this fails, contact your BEA TUXEDO system Technical Support.
1037 ERROR: Migration failed: server not shutdown
Description While attempting to migrate server(s) to another machine, the system is unable to process this request
because a server remains running. All of the servers affected by this request must be shut down before a
migration command is issued.
Action
Shut down the desired servers with the relocate (-R) option and retry the request.
1038 ERROR: Migration failed: cannot unlock BB, tperrno = tperrno_val
Description While attempting to update internal information of server(s) to be migrated, the local bulletin board is
unable to be unlocked.
Action
This may be the result of a transitive failure of a process attached to the bulletin board. Try the
command again; if this fails, contact your BEA TUXEDO system Technical Support.
1039 ERROR: Migration failed: cannot lock BB, tperrno = tperrno_val
Description While attempting to update internal information of server(s) to be migrated, the local bulletin board is
unable to be locked.
Action
This may be the result of a transitive failure of a process attached to the bulletin board. Try the
command again; if this fails, contact your BEA TUXEDO system Technical Support.
1040 ERROR: Migration failed: cannot retrieve queue information, tperrno = tperrno_val
Description While attempting to update the queue table entry of the servers to be migrated, the queue table entry
cannot be retrieved. This error is probably the result of an internal corruption of the bulletin board and
not the result of anything the user has done.
Action
Contact your BEA TUXEDO system Technical Support.
1041 ERROR: Migration failed: cannot update server information, tperrno = tperrno_val
Description While attempting to update the server table entry for the servers to be migrated, the required entry
cannot be retrieved. This error is probably the result of an internal corruption of the bulletin board and
not the result of anything the user has done.
Action
Contact your BEA TUXEDO system Technical Support.
1042 ERROR: Migration failed: cannot unlock BB, tperrno = tperrno_val
Description While attempting to update internal information of server(s) to be migrated, the local bulletin board is
unable to be unlocked.
Action
This may be the result of a transitive failure of a process attached to the bulletin board. Try the
command again; if this fails, contact your BEA TUXEDO system Technical Support.
1043 ERROR: Migration failed: time out occurred
12
Description During the verification of the alternate location after the servers have been migrated, a failure has
occurred. The verification request has timed out.
Action
Check the status of the bulletin board on the alternate location. This may be accomplished by using the
tmadmin() subcommand printserver. If this location is still running, try the migrate command again
and if a failure occurs, contact your BEA TUXEDO system Technical Support. If the alternate location
doesn’t respond, you will have to reboot this site before migration may occur.
See Also
tmadmin(1)
1044 ERROR: Migration failed: cannot lock BB, tperrno = tperrno_val
Description During the migration verification of the alternate location after the servers have been migrated, a failure
has occurred. The bulletin board was not able to be locked.
Action
This may be the result of a transitive failure of a process attached to the bulletin board. Try the
command again; if this fails, contact your BEA TUXEDO system Technical Support.
1045 ERROR: Migration failed: server(server_id/group_id) failed to migrate, tperrno = tperrno_val
Description The bulletin board of an alternate location reported that the server information requested was not found.
This error is probably the result of an internal corruption of the bulletin board and not the result of
anything the user has done.
Action
Contact your BEA TUXEDO system Technical Support.
1046 ERROR: Migration failed: cannot retrieve server (server_id/group_id) information, tperrno = tperrno_val
Description The bulletin board of an alternate location reported that the server information requested was not found.
This error is probably the result of an internal corruption of the bulletin board and not the result of
anything the user has done.
Action
Contact your BEA TUXEDO system Technical Support.
1047 ERROR: Migration failed: cannot unlock BB, tperrno = tperrno_val
Description During the migration verification of the alternate location after the servers have been migrated, a failure
has occurred. The bulletin board was not able to be unlocked (or released).
Action
This may be the result of a transitive failure of a process attached to the bulletin board. Try the
command again; if this fails, contact your BEA TUXEDO system Technical Support.
1048 ERROR: Migration failed: server (server_id/group_id) still cleaning
Description The verification of the alternate location has failed because the server server_id is still cleaning up its
entries in the bulletin board.
Action
Contact your BEA TUXEDO system Technical Support.
1052 ERROR: Request/response request received in conversational server
Description A message request was received by a conversational server from a request/response server.
Action
Verify that the service name used in a tpcall, tpacall, or tpforward belongs to a request/response server
and not a conversational server.
1053 ERROR: Conversational request received in request/response server
Description A message request was received by a request/response server from a conversational server.
Action
Verify that the service name in tpconnect belongs to a conversational server and not a request/response
server.
1055 ERROR: Memory allocation failure
Description While attempting to restart a server, the BEA TUXEDO system needed to allocate a memory buffer.
This memory allocation failed.
Action
Contact your UNIX Administrator.
1056 ERROR: Char range with MAX as lower value has values out of order
Description If MAX is specified for the char lower routing range, then its corresponding upper routing range must
also be specified as MAX. That is: MAX - MAX: server_group
Action
Check the char routing range in the ROUTING section of the UBBCONFIG file. If MAX is specified
for the lower routing range, then its corresponding upper routing range must be MAX.
See Also
ubbconfig(5)
1057 ERROR: Char range with MIN as upper value has values out of order
13
Description If MIN is specified for the char upper routing range, then its corresponding lower routing range must
also be specified as MIN. That is: MIN - MIN: server_group
Action
Check the char routing range in the ROUTING section of the UBBCONFIG file. If MIN is specified for
the upper routing range, then its corresponding lower routing range must be MIN.
See Also
ubbconfig(5)
1058 ERROR: Range values out of order for the packed decimal routing data
Description The range values for the packed decimal routing data are out order, that is, the upper range value is less
than the lower range value.
Action
Check routing range values for the packed decimal routing data in your UBBCONFIG file. The lower
range value must be less than or equal to the upper range value.
See Also
decimal(3c), ubbconfig(5)
1059 ERROR: Invalid format for decimal
Description The data for a decimal routing range is specified incorrectly.
Action
Check routing range decimal data in the ROUTING section of the UBBCONFIG file. The data must be
in the correct format.
See Also
decimal(3c)
1060 ERROR: Cannot have a ’-’ in front of MAX or MIN
Description The routing range cannot have a ’-’ sign in front of the MAX or MIN value.
Action
Check the routing range data in the ROUTING section of the UBBCONFIG file. Remove any ’-’ sign in
front of the MAX or MIN value.
See Also
ubbconfig(5)
1061 ERROR: Cannot have a ’-’ and a ’+’ sign in front of a number
Description The routing range cannot have both a ’-’ and a ’+’ sign in front of a number.
Action
Check the routing range data in the ROUTING section of the UBBCONFIG file. If a ’-’ and a ’+’ sign
are both in front of a number, remove the ’+’ sign.
See Also
ubbconfig(5)
1065 ERROR: xa_end TMSUSPEND returned errstring
Description The process called xa_end() just prior to blocking for a reply message. This would happen, for
example, when an XA server does a tpcall() to another server. An unexpected return code,
errstring, was returned from xa_end().
Action
Contact your BEA TUXEDO system Technical Support or database system vendor.
1066 ERROR: xa_start TMRESUME returned errstring
Description The process called xa_start() just after receiving a reply message. This would happen, for example,
when an XA server does a tpcall() to another server. An unexpected return code, errstring, was
returned from xa_start().
Action
Contact your BEA TUXEDO system Technical Support or database system vendor.
1067 ERROR: Request/response service name matches conversational service name
Description An error occurred while a service was being added to the bulletin board’s tables. The same service
name cannot be used for both conversational and request/response types of services.
Action
Rename the services being offered so that the each service name is used consistently throughout the
system as either conversational or request/response.
See Also
tpcall(3c), tpconnect(3c)
1074 ERROR: Connection information invalid
Description This error occurs when a client or server is requesting to create a connection table entry in the Bulletin
Board and supplies incorrect or NULL arguments. This happens if there is a bug in the calling routine.
Action
Report this failure to your BEA TUXEDO system Technical Support.
1076 ERROR: Tried to set up a duplicate connection
Description This error occurs when a client or server is requesting to create a connection table entry in the Bulletin
Board and tries to set up a duplicate entry. This happens if there is a bug in the calling routine.
Action
Report this failure to your BEA TUXEDO system Technical Support.
1077 ERROR: Bad event: status
14
Description This error occurs when tprecv(3c) gets a message from the other end of a conversation and the
tperrno information in the message header is set to TPEEVENT and the event is set to an invalid event.
Action
Report this failure to your BEA TUXEDO system Technical Support.
1078 ERROR: errno TPEEVENT but event flag not set
Description This error occurs when tprecv(3c) gets a message from the other end of a conversation and the tperrno
information in the message header is set to TPEEVENT and the event is set to zero.
Action
Report this failure to your BEA TUXEDO system Technical Support.
1079 ERROR: Failed to create connection
Description This error occurs when tpconnect(3c) fails to add a connection table entry into the Bulletin Board.
This can happen if the table is full.
Action
Increase the number of connection table entries in the Bulletin Board by increasing the MAXCONV
parameter in the UBBCONFIG file.
See Also
ubbconfig(5)
1080 WARN: Failed to disconnect process pid
Description This error occurs when a conversational disconnect event is sent by a server to a client on the same
machine via a message, and the server is unable to send the message to the client. The client could have
died before the disconnect event is sent or if there is an error queueing the message.
Action
Check the UNIX message queue kernel parameters and increase them if necessary.
1081 ERROR: Failed to allocate space for disconnect msg
Description This error occurs when a conversational disconnect message is sent to the BBL and there is not enough
memory in the system to allocate the 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. Increase the space on the swap device.
See Also
malloc(3) in UNIX reference manuals
1082 ERROR: Disconnect failed, couldn’t find BBL
Description This error occurs when a conversational disconnect message has to be sent to the BBL and the server
table entry for the BBL is missing from the Bulletin Board. This is a severe error and the system is
unstable.
Action
Contact the BEA TUXEDO system administrator and restart the BEA TUXEDO system.
1083 ERROR: Disconnect failed, message send/receive error
Description This error occurs when a conversational disconnect event is sent by a process to the remote BBL via a
message, and the server is unable to send the message to the BBL. This can happen if the limit on the
number of bytes on the message queue is reached.
Action
Check the UNIX system message queue kernel parameters and increase them if necessary.
1084 ERROR: Failed to get acknowledgement message for connection
Description This error occurs when a conversational client or server issues a tprecv(3c) with TPRECVONLY.
This requires an acknowledgment from the other connection. If there is a failure in getting that
acknowledgment, this message is printed. This could happen if the UNIX message queue has reached its
capacity. This could also happen if the remote server for that connection could not be started.
Action
Check the UNIX message queue kernel parameters and increase them if necessary. Check the userlog
for error messages regarding the remote server.
1085 ERROR: Invalid mid value during spawn
Description While getting ready to spawn a conversational server, the calling process failed to retrieve its machine
table entry. The machine identifier that is used to retrieve the entry is invalid. The conversational server
will therefore not be spawned.
Action
Look through the userlog to see if there are other messages related to this failure. If so, refer to the
appropriate system messages. Otherwise, contact your BEA TUXEDO system Technical Support.
1086 ERROR: Argument vector formation error during spawn
15
Description While getting ready to spawn a conversational server, the calling process failed to build the command
line arguments for that server. An attempt to dynamically allocate memory from the operating system
using malloc(3) or realloc(3) failed while building the command line. The conversational server
will therefore not be spawned.
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.
1087 ERROR: aout=aout: too many arguments
Description While getting ready to spawn a conversational server, the calling process failed to set the argument
vector for that server. The calling process attempted to pass more than 256 arguments to the
conversational server. The conversational server will therefore not be spawned.
Action
Make sure the number of arguments passed to the conversational server is not greater than 256. Note
that the system may be adding up to eight arguments to the command line obtained from the
configuration file.
See Also
ubbconfig(5)
1088 ERROR: spawn error: cannot fork
Description The calling process failed to spawn a conversational server. The call to fork(2) failed.
Action
The system-imposed limit on the total number of processes under execution by a single user may be
exceeded. In this case you may either reduce the number of processes the BEA TUXEDO system
application administrator is running on the system or increase the total number of processes allowed per
user by reconfiguring the UNIX kernel.
See Also
fork(2) in UNIX reference manuals
1089 ERROR: Cannot exec, executable file not found
Description The calling process failed to spawn a conversational server. The call to exec(2) failed. The
conversational server to be spawned does not exist.
Action
Make sure the conversational server is in the application directory.
See Also
exec(2) in UNIX reference manuals, ubbconfig(5)
1090 ERROR: Cannot exec, network send error
Description The calling process failed to spawn a conversational server due to a networking problem.
Action
Make sure the network has not been partitioned and that the remote site is booted. If the remote site is
not booted, call tmboot(1). If the remote site is booted, use tmadmin(1) to determine the status of the
network, and reconnect the remote site if necessary.
See Also
exec(2) in UNIX reference manuals, tmadmin(1), tmboot(1), ubbconfig(5)
1091 WARN: process id=pid ... Assume started (network).
Description The calling process attempted to spawn a conversational server. The conversational server with a
process ID of pid is believed to have been started. However the calling process did not receive an
acknowledgment.
Action
Make sure a conversational server with process ID pid is running. If not, look for a core dump in the
application directory.
1092 WARN: process id=pid ... Assume started (pipe).
Description The calling process attempted to spawn a conversational server. The conversational server with a
process ID of pid is believed to have been started. However the calling process did not receive an
acknowledgment.
Action
Make sure a conversational server with process ID pid is running. If not, look for a core dump in the
application directory.
1094 ERROR: No BBL available, cannot boot
Description The calling process failed to spawn a conversational server. The BBL is not active.
Action
Make sure the BBL is booted on the site the conversational server is being spawned. Use tmadmin(1)
to check the status of the application. If the BBL needs to be booted, use tmboot(1).
See Also
tmadmin(1), tmboot(1)
1095 ERROR: No DBBL available, cannot boot
16
Description The calling process failed to spawn a conversational server. The DBBL is not active on the master site.
Action
Make sure the DBBL is booted on the master site. Use tmadmin(1) to check the status of the
application.
See Also
tmadmin(1)
1096 ERROR: Spawning process failed.
Description The calling process failed to spawn a conversational server.
Action
Look through the userlog to see if there are other messages related to this failure. If so, refer to the
appropriate system messages. Otherwise, contact your BEA TUXEDO system Technical Support.
See Also
See Messages No. 1097 and 1098 below
1097 ERROR: Process process at site failed with /T error (errmsg)
Description The calling process failed to spawn a conversational server, process. The spawned server failed on site
site.
Action
Take corrective measures based on errmsg.
1098 ERROR: Process process at site failed with code code
Description The calling process failed to spawn a conversational server, process. The spawned server failed on site
site.
Action
Take corrective measures based on error code code.
1099 ERROR: Cannot process a message with an unknown release, release
Description An invalid release number, release, was found in a message while being converted. Interoperability
allows a single application to have multiple (two) releases of the BEA TUXEDO system exist on
different nodes and interoperate with one another. The conversion is done by either the sender, if it has
the latest software, or the receiver.
Action
Check the release of the BEA TUXEDO system software and make sure that the master and backup
nodes are running the later release. Also make sure the TUXDIR parameter is set correctly in the
configuration file.
See Also
BEA TUXEDO Administrator’s Guide
17
LIBTUX Messages 1100-1199
1100 ERROR: Cannot send a message to a site with an unknown release, release
Description The BEA TUXEDO system is trying to convert a message to the message format of an unknown
release: release. Interoperability allows a single application to have multiple (two) releases of the BEA
TUXEDO system exist on different nodes and interoperate with one another. The conversion is done by
either the sender, if it has the latest software, or the receiver.
Action
Contact your BEA TUXEDO system Technical Support.
See Also
BEA TUXEDO Administrator’s Guide
1104 ERROR: Memory allocation failure
Description An attempt dynamically to allocate memory from the operating system using malloc() failed while
converting Bulletin Board data to the BEA TUXEDO system Release 4.1 format.
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.
1108 ERROR: BBL not available on requested lmid (site)
Description The calling process failed in tpbroadcast(3c) while trying to get the server table entry of the BBL
on LMID site from the Bulletin Board. This is most likely due to the fact that the BBL on LMID site is
not running.
Action
Boot the BBL on LMID site.
See Also
tpbroadcast(3c)
1109 ERROR: Could not retrieve BBL from specified lmid (site)
Description The calling process failed in tpbroadcast(3c) while trying to get the server table entry of the BBL
on LMID site from the Bulletin Board.
Action
Consult your BEA TUXEDO system Technical Support.
See Also
tpbroadcast(3c)
1114 ERROR: Unsolicited signal handler unable to get BB parameters
Description The calling process failed to get from the Bulletin Board the signal to be used for signal-based
notification. This error may have occurred while the client was attempting to join the application, using
tpinit(3c), or while making an ATMI call prior to joining the application, or if the system the client
is running on does not support reliable signals.
Action
Parse through the user log to see if there are other messages related to this failure. If so, refer to the
appropriate system messages. Otherwise, consult your BEA TUXEDO system Technical Support.
See Also
tpinit(3c), ubbconfig(5)
1115 ERROR: Invalid USIGNAL parameter in BB
Description The calling process retrieved an invalid signal number from the Bulletin Board. This signal was to be
used for signal-based notification.
Action
Parse through the userlog to see if there are other messages related to this failure. If so, refer to the
appropriate system messages. Otherwise, consult your BEA TUXEDO system Technical Support.
1117 ERROR: Unable to check for unsolicited messages, tperrno = tperrno
Description The calling process failed while checking for an unsolicited message upon receipt of a signal indicating
that an unsolicited message had arrived. tperrno is set to the TUXEDO System/T error code that was
returned by the system after trying to get the unsolicited message.
Action
tperrno is most likely set to TPESYSTEM or TPEOS. In this case, parse through the userlog to find the
exact nature of the failure as described in another message.
See Also
tpchkunsol(3c)
1118 ERROR: Unable to check for unsolicited messages, tperrno = tperrno
18
Description The calling process failed while checking for unsolicited messages. tperrno is set to the BEA TUXEDO
system error code that was returned by the system after failing to check for unsolicited messages.
Action
tperrno is most likely set to TPESYSTEM or TPEOS. In this case, parse through the userlog to find the
exact nature of the failure as described in another message.
See Also
tpchkunsol(3c)
1119 ERROR: tpsetunsol() not called, dropping unsolicited message
Description The calling process failed to set the method of handling unsolicited messages prior to receiving its first
unsolicited message. The unsolicited message will therefore be dropped since the system does not know
what to do with it.
Action
Make sure the calling process calls tpsetunsol(3c) as soon as it joins the application.
See Also
tpchkunsol(3c), tpsetunsol(3c)
1122 ERROR: No space in Bulletin Board
Description The calling process failed to join the application due to the lack of space in the registry table portion of
the Bulletin Board.
Action
If the calling process is an application client, the administrator will need to increase MAXACCESSERS
in the RESOURCES section of the configuration file. If the calling process is a server, the administrator
will need to increase MAXACCESSERS and/or MAXSERVERS in the RESOURCES section of the
configuration file. Note that MAXACCESSERS specifies the maximum number of processes that can
have access to a Bulletin Board on a particular machine at any one time. MAXSERVERS specifies the
maximum number of servers to be accommodated by the entire application at any one time.
See Also
ubbconfig(5)
1187 ERROR: Invalid parameter passed to internal routine
Description One of the internal routines to manage TUXEDO System/T data structures received an invalid
parameter. This should not occur during normal system operation.
Action
Contact your BEA TUXEDO system Technical Support.
See Also
tmconfig(1)
1198 ERROR: Cannot detach: operating system error: errno = errno_val.
Description The application is running with the TMPROTECTED SYSTEM_ACCESS value. Detaching from the
bulletin board failed.
Action
Check the errno_val to determine why the detach failed.
1199 ERROR: Cannot re-attach: operating system error: errno = errno_val.
Description The application is running with the TMPROTECTED SYSTEM_ACCESS value. The client or server
was unable to re-attach to the bulletin board. This probably indicates that the application was shut down
(abnormally) while the client or server was not attached.
Action
Check the errno_val to determine the reason for the failure. Check with the administrator to see if the
application was shut down.
19
LIBTUX Messages 1200-1299
1200 ERROR: Cannot re-attach BB - process lost its BB slot while detached
Description The application is running with the TMPROTECTED SYSTEM_ACCESS value. After reattaching to
the bulletin board, the context for the client or server does not match. This indicates that either the
bulletin board is corrupted or the application was re-booted while the client or server was not attached.
Action
Check with the administrator to see if the application was re-booted. Contact your BEA TUXEDO
system Technical Support.
1201 ERROR: Cannot re-attach BB - magic number mismatch
Description The application is running with the TMPROTECTED SYSTEM_ACCESS value. After reattaching to
the bulletin board, the wrong magic number was found. This indicates that either the bulletin board is
corrupted or a new release of the application was booted while the client or server was not attached.
Action
Contact your BEA TUXEDO system Technical Support.
1202 ERROR: Cannot re-attach BB - wrong release of software
Description The application is running with the TMPROTECTED SYSTEM_ACCESS value. After reattaching to
the bulletin board, the wrong release was found. This indicates that either the bulletin board is corrupted
or a new release of the application was booted while the client or server was not attached.
Action
Contact your BEA TUXEDO system Technical Support.
1203 WARN: Cannot override system default access method PROTECTED
Description The application called tpinit with the TPSA_FASTPATH flag set, but the configuration has
SYSTEM_ACCESS set to PROTECTED,NO_OVERRIDE. tpinit will ignore this flag and run in
TPSA_PROTECTED mode.
Action
Change the application to use TPSA_PROTECTED mode, or contact the administrator about allowing
overriding of the SYSTEM_ACCESS mode.
See Also
tpinit(3c), ubbconfig(5)
1204 WARN: Cannot override system default access method FASTPATH
Description The application called tpinit with the TPSA_PROTECTED flag set, but the configuration has
SYSTEM_ACCESS set to FASTPATH, NO_OVERRIDE. tpinit will ignore this flag and run in
TPSA_FASTPATH mode.
Action
Change the application to use TPSA_FASTPATH mode, or contact the administrator about allowing
overriding of the SYSTEM_ACCESS mode.
See Also
tpinit(3c), ubbconfig(5)
1205 WARN: Unable to open MACHINE ENVFILE filename for reading
Description In the process of booting a server, the ENVFILE specified in the MACHINES section on the
configuration could not be opened for reading. The server will still be booted, but the environment will
not be modified.
Action
Check the machine environment file to see that it exists in the correct directory with the right name and
with read permission for the configuration administrator. It may be necessary to shut down the server
and re-start it with the correct environment.
See Also
tmboot(1), tmshutdown(1), ubbconfig(5)
1214 ERROR: Cannot perform deferred type/subtype resolution in global tables (type/subtype)
Description The application is running with the TMPROTECTED SYSTEM_ACCESS value. An operation was
done on a typed buffer, but checking of the type/subtype was deferred. When the checking was finally
done, the type/subtype was not recognized by the system.
Action
Contact your BEA TUXEDO system Technical Support.
1219 ERROR: Invalid parameter
Description An invalid parameter was passed to an internal routine during security processing.
Action
Contact your BEA TUXEDO system Technical Support.
1220 ERROR: Memory allocation failure
20
Description An attempt dynamically to allocate memory from the operating system using malloc() failed during
security processing.
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.
1222 ERROR: Unable to open TUXCONFIG file to Resources section
Description While trying to read the configuration file during security processing, the program was unable to open
the RESOURCES section.
Action
Contact your BEA TUXEDO system Technical Support.
1223 ERROR: Unable to open Resources section of TUXCONFIG file
Description While trying to read the configuration file during security processing, the program was unable to read
the RESOURCES section.
Action
Contact your BEA TUXEDO system Technical Support.
1224 ERROR: Possibly corrupted key in database
Description The system key created and stored in the file APPDIR/.adm/.keydb for use by the WSH in security
applications has become corrupted. This error disables the WSH from being able to handle new
incoming connections from workstation clients. Note that current implementations of the security
interfaces within the BEA TUXEDO system will not generate this error, but future ones may if they
have more stringent requirements on the key characteristics used for encryption.
Action
Shut down the application on the offending site, and remove the binary TUXCONFIG file and the key
database APPDIR/.adm/.keydb. Then reboot the site; this will automatically re-create the security key
information correctly.
See Also
BEA TUXEDO Administrator’s Guide
1225 ERROR: Error while decrypting password
Description The security information stored and accessed by the TUXEDO System/T has become corrupted and
cannot be processed correctly by the WSH in order to allow workstation clients to access the
application. This error disables the WSH from being able to handle new incoming connections from
workstation clients.
Action
Shut down the application on the offending site, and remove the binary TUXCONFIG file and the key
database APPDIR/.adm/.keydb. Then reboot the site; this will automatically re-create the security key
information correctly. If this does not clear the problem, then remove TUXCONFIG and security
information from all sites and reboot.
See Also
BEA TUXEDO Administrator’s Guide
1226 ERROR: Invalid password in TUXCONFIG file
Description The security information stored and accessed by the TUXEDO System/T has become corrupted and
cannot be processed correctly by the WSH in order to allow workstation clients to access the
application. This error disables the WSH from being able to handle new incoming connections from
workstation clients.
Action
Shut down the application on the offending site, and remove the binary TUXCONFIG file and the key
database APPDIR/.adm/.keydb. Then reboot the site; this will automatically re-create the security key
information correctly. If this does not clear the problem, then remove TUXCONFIG and security
information from all sites and reboot.
See Also
BEA TUXEDO Administrator’s Guide
1227 ERROR: Unable to open TUXCONFIG file to read MACHINES section
Description While trying to read the application password, the program was unable to find the *MACHINES section
in the configuration file. This should not occur.
Action
Contact your BEA TUXEDO system Technical Support.
1233 ERROR: Unable to shutdown, clients/servers still attached
21
Description The BBL was unable to shut itself down because clients and/or servers are still attached to the Bulletin
Board. It is the BBL ’s responsibility to clean up and remove the Bulletin Board prior to terminating.
However, the Bulletin Board was not removed since clients and/or servers were still attached to it.
Action
First, make sure all application servers have been shut down prior to attempting to shut down the BBL.
The tmadmin(1) printserver (psr) command can be used to print server statistics. Shut down all
application servers on that site using tmshutdown(1) with the -l option. Second, make sure all
application clients have terminated. The tmadmin(1) printclient (pclt) command can be used to
print client statistics. The application administrator can force the BBL to shut down, by invoking the
tmshutdown(1) command with the -c option. The -c option will allow for the BBL to be shut down
even if clients are still attached to the Bulletin Board.
1236 WARN: TMDEBUG contains non-numeric characters in first number
Description The format of the TMDEBUG variable is invalid. The allowable formats for TMDEBUG are:
number number:regular_expression number1-number2 number1-number2:regular_expression
If number is specified, debugging messages with levels less than or equal to number will be printed.
If number1 and number2 are specified, debugging messages with levels between number1 and
number2, inclusive, will be printed. If regular_expression is appended to the numeric part of
the argument, only those messages matching regular_expression will be printed.
Action
Make sure the TMDEBUG variable is valid. TMDEBUG may be incorrectly set and exported in the
environment. It may also be incorrectly set in an environment file using the ENVFILE parameter in the
*MACHINES or *SERVERS section of the configuration file.
See Also
ubbconfig(5)
1237 WARN: TMDEBUG contains non-numeric characters in 2nd part of range
Description See Message 1236 above.
Action
See Message 1236 above.
1238 WARN: TMDEBUG regular expression invalid. Ignoring regular expression.
Description See Message 1236 above.
Action
See Message 1236 above.
1239 ERROR: Failed to change group via setgid()
Description The calling process failed to change its group ID while trying to become the administrator. The effective
user ID of the calling process is super-user.
Action
Make sure the calling process has permission to change its group ID to the group ID the BEA TUXEDO
system application administrator belongs to.
See Also
setgid(2) in UNIX reference manuals
1240 ERROR: Failed to change user via setuid()
Description The calling process failed to change its user ID while trying to become the administrator. The effective
user ID of the calling process is super-user.
Action
Make sure the calling process has permission to change its user ID to the user ID the BEA TUXEDO
system application administrator belongs to.
See Also
setuid(2) in UNIX system reference manuals
1241 ERROR: Memory allocation failure
Description An attempt dynamically to allocate memory from the operating system using malloc() failed.
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.
1242 ERROR: Invalid table type
Description The calling process failed to open a configuration table in the TUXCONFIG file. An invalid table type
was passed to the system routine responsible for opening configuration tables.
Action
Contact your BEA TUXEDO system Technical Support.
1243 ERROR: Invalid table type
22
Description The calling process failed to close a configuration table in the TUXCONFIG file. An invalid table type
was passed to the system routine responsible for closing configuration tables.
Action
Contact your BEA TUXEDO system Technical Support.
1244 ERROR: Invalid table type
Description The calling process failed to seek a configuration table in the TUXCONFIG file. An invalid table type
was passed to the system routine responsible for seeking configuration tables.
Action
Contact your BEA TUXEDO system Technical Support.
1245 ERROR: Invalid table type
Description The calling process failed to write a configuration table in the TUXCONFIG file. An invalid table type
was passed to the system routine responsible for writing configuration tables.
Action
Contact your BEA TUXEDO system Technical Support.
1246 ERROR: More than one wild card in entry ranges
Description The calling process found more than one wild card in the ranges string, ranges, while parsing the string
based on a packed decimal field type.
Action
Make sure there is no more than one wild card in the ranges string ranges.
See Also
ubbconfig(5)
1247 ERROR: Cannot have a ’-’ in front of MAX or MIN
Description While attaching to the Bulletin Board and loading all of the information that is in the TUXCONFIG file
into the Bulletin Board, the calling process failed to get a data routing entry. The failure occurred while
parsing a range string into data based on the field type information of one of the entries in the
ROUTING section of the configuration file. The calling process was unable to create the data routing
entry.
Action
Make sure the RANGES parameter in the ROUTING section of the UBBCONFIG file is valid. The
range strings may not contain a ’-’ in front of MIN or MAX.
See Also
ubbconfig(5)
1248 ERROR: Cannot have a ’-’ in front of MAX or MIN
Description While attaching to the Bulletin Board and loading all of the information that is in the TUXCONFIG file
into the Bulletin Board, the calling process failed to get a data routing entry. The failure occurred while
parsing a range string into data based on the field type information of one of the entries in the
ROUTING section of the configuration file. The calling process was unable to create the data routing
entry.
Action
Make sure the RANGES parameter in the ROUTING section of the UBBCONFIG file is valid. The
range strings may not contain a ’-’ in front of MIN or MAX.
See Also
ubbconfig(5)
1249 ERROR: Cannot have a ’-’ in front of MAX or MIN
Description While attaching to the Bulletin Board and loading all of the information that is in the TUXCONFIG file
into the Bulletin Board, the calling process failed to get a data routing entry. The failure occurred while
parsing a range string into data based on the field type information of one of the entries in the
ROUTING section of the configuration file. The calling process was unable to create the data routing
entry.
Action
Make sure the RANGES parameter in the ROUTING section of the UBBCONFIG file is valid. The
range strings may not contain a ’-’ in front of MIN or MAX.
See Also
ubbconfig(5)
1250 ERROR: Cannot have a ’-’ in front of MAX or MIN
Description While attaching to the Bulletin Board and loading all of the information that is in the TUXCONFIG file
into the Bulletin Board, the calling process failed to get a data routing entry. The failure occurred while
parsing a range string into data based on the field type information of one of the entries in the
ROUTING section of the configuration file. The calling process was unable to create the data routing
entry.
Action
Make sure the RANGES parameter in the ROUTING section of the UBBCONFIG file is valid. The
range strings may not contain a ’-’ in front of MIN or MAX.
See Also
ubbconfig(5)
1251 ERROR: Cannot have a ’-’ and a ’+’ sign in front of a number
23
Description While attaching to the Bulletin Board and loading all of the information that is in the TUXCONFIG file
into the Bulletin Board, the calling process failed to get a data routing entry. The failure occurred while
parsing a range string into data based on the field type information of one of the entries in the
ROUTING section of the configuration file. The calling process was unable to create the data routing
entry.
Action
Make sure the RANGES parameter in the ROUTING section of the UBBCONFIG file is valid. The
range strings may not have ’-+’ in front of number.
See Also
ubbconfig(5)
1253 ERROR: shmat failure: errno = errno, key = ipckey
Description The calling process failed to create/attach to the Bulletin Board while invoking the shmat(2) system
call. shmat(2) returned with errno set to errno.
Action
shmat(2) will fail and not attach to the Bulletin Board if one or more of the following are true:
An invalid argument was passed (EINVAL). In this case contact your BEA TUXEDO system
Technical Support.
The operation was denied to the calling process (EACCESS). In this case make sure the calling
process has permission to attach to the Bulletin Board.
The available data space is not large enough to accommodate the shared memory segment
(ENOMEM). In this case the system administrator may have to reconfigure the UNIX kernel to
allow for more shared memory space.
The number of shared memory segments attached to the calling process would exceed the
system-imposed limit (EMFILE). In this case the system administrator may have to reconfigure
the UNIX kernel to allow for more shared memory space.
See Also
shmat(2) in UNIX reference manuals
1254 ERROR: shmget(creat) failure: errno = errno, key = key
Description The calling process failed to create/get to the Bulletin Board while invoking the shget(2) system call
with key set to key and the IPC_CREAT flag set. shmget(2) returned with errno set to errno.
Action
shmget(2) will fail if one or more of the following are true:
An invalid argument was passed (EINVAL). In this case contact your BEA TUXEDO system
Technical Support. One specific case where this occurs is if the OS value for SHMMIN is set too
high (in general, it should always be set to 1).
The operation was denied to the calling process (EACCESS). In this case make sure the calling
process has permission to create/attach to the Bulletin Board.
A shared memory identifier does not exist for key (ENOENT). In this case contact your BEA
TUXEDO system Technical Support.
The system limit on shared memory identifiers was reached (ENOSPC). In this case the system
administrator may have to reconfigure the UNIX kernel to allow for more shared memory
identifiers.
The amount of available memory is not sufficient (ENOMEM). In this case the system
administrator may have to reconfigure the UNIX kernel to allow for more shared memory space.
See Also
shmget(2) in UNIX reference manuals
1255 ERROR: shmctl(chown) failure: errno = errno, key = key
24
Description The calling process failed to perform a shared memory control operation on the Bulletin Board while
invoking the shmctl(2) system call with the IPC_SET flag set. The calling process was unable to set
the user ID, group ID, and mode of the Bulletin Board. shmctl(2) returned with errno set to errno.
Action
shmctl(2) will fail if one or more of the following are true:
An invalid argument was passed (EINVAL). In this case contact your BEA TUXEDO system
Technical Support.
The operation was denied to the calling process (EACCESS). In this case make sure the calling
process has permission to perform operations on the Bulletin Board.
Not enough memory (ENOMEM). In this case the system administrator may have to reconfigure
the UNIX kernel to allow for more shared memory space.
See Also
shmctl(2) in UNIX reference manuals
1256 ERROR: shmat failure: errno = errno, id = id
Description The calling process failed to create/attach to the Bulletin Board while invoking the shmat(2) system
call. shmat(2) was called with shmid set to id and returned with errno set to errno.
Action
shmat(2) will fail and not attach to the Bulletin Board if one or more of the following are true:
An invalid argument was passed (EINVAL). In this case contact your BEA TUXEDO System
Technical Support.
The operation was denied to the calling process (EACCESS). In this case make sure the calling
process has permission to attach to the Bulletin Board.
The available data space is not large enough to accommodate the shared memory segment
(ENOMEM). In this case the system administrator may have to reconfigure the UNIX kernel to
allow for more shared memory space.
The number of shared memory segments attached to the calling process would exceed the
system-imposed limit (EMFILE). In this case the system administrator may have to reconfigure
the UNIX kernel to allow for more shared memory space.
See Also
shmat(2) in UNIX reference manuals
1257 ERROR: func: bad value of _gp_fsoffset variable or supplied offset
Description An invalid VTOC file system offset was passed to func.
Action
Make sure the FSOFFSET environment variable is set correctly. If the problem persists after resetting
the FSOFFSET environment variable, contact your BEA TUXEDO system Technical Support.
1259 ERROR: Memory allocation failure
Description An attempt dynamically to allocate memory from the operating system using malloc() failed.
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: Service request problem: func
Description The calling process failed in a BEA TUXEDO system internal function called func while trying to add a
new service table entry.
Action
Look through the userlog for other messages related to this failure. If found, refer to the appropriate
system messages. If not, consult your BEA TUXEDO system Technical Support.
1261 ERROR: Service request problem: string
Description The calling process failed in a BEA TUXEDO system internal function because of string while trying to
add a new service table entry.
Action
Look through the userlog for other messages related to this failure. If found, refer to the appropriate
system messages. If not, consult your BEA TUXEDO system Technical Support.
1262 ERROR: Permission denied to boot server
25
Description When security is turned on, that is, the SECURITY parameter is specified in the RESOURCES section
of the application configuration file, a server may only be booted by the administrator of the application.
This means that the user ID and group ID of the user attempting to boot the server should match the user
ID and group ID of the application administrator. If they do not match, the server will fail to boot and
exit gracefully.
Action
Make sure that the TUXCONFIG environment variable is set correctly. If it is pointing to the right
application, make sure that the UID and GID parameters are properly set in the RESOURCES section of
the configuration file. Also verify that the ID of the user that is attempting to boot the server is set
correctly using the UNIX id(1) command.
See Also
ubbconfig(5)
1263 ERROR: tpsvrinit() returned in transaction mode
Description The application server has been placed in transaction mode during its initialization in tpsvrinit().
tpsvrinit() returned while still in transaction mode. The BEA TUXEDO system will therefore
abort the outstanding transaction and the application server will exit gracefully. Since tpsvrinit()
is called after the server has joined the application, transactions may be defined in this routine.
However, the transaction must have completed prior to tpsvrinit() returning.
Action
Verify that if a transaction is started in tpsvrinit(), it should also be completed prior to
tpsvrinit() returning. If tpbegin() is called in tpsvrinit(), make sure that either
tpabort() or tpcommit() is also called.
See Also
tpservice(5c)
1264 WARN: Ticket stuck high - retrying
Description While monitoring the integrity of the Bulletin Board, the BBL found a BEA TUXEDO system user level
semaphore with no owner. In addition, another process was waiting to be served. The BBL must
therefore become the owner of the semaphore and delegate it to the waiting process. While trying to do
so, the BBL failed to lock the Bulletin Board, and will attempt to lock it again.
Action
No action required.
1265 WARN: Ticket stuck high - resetting
Description While monitoring the integrity of the Bulletin Board, the BBL found a BEA TUXEDO system user level
semaphore with no owner. In addition, another process was waiting to be served. The BBL must
therefore become the owner of the semaphore and delegate it to the waiting process. The BBL managed
to lock the Bulletin Board, transfer the ownership of the semaphore, and adjust the statistics.
Action
No action required.
1266 WARN: Ticket stuck high - retrying
Description While monitoring the integrity of the Bulletin Board, the BBL found a BEA TUXEDO system user level
semaphore with no owner. In addition, another process was waiting to be served. The BBL must
therefore become the owner of the semaphore and delegate it to the waiting process. While trying to do
so, the BBL failed to lock the Bulletin Board, and will attempt to lock it again.
Action
No action required.
1274 ERROR: tpreturn xa_end TMFAIL returned errstring
Description During a call to tpreturn() in transaction mode with the TPFAIL flag, a call to xa_end with the
TMFAIL flag failed with the specified errstring.
Action
Check the error reporting mechanism for the associated resource manager to determine the cause of the
problem.
1275 ERROR: tpreturn TPESVCERR xa_end TMSUCCESS returned errstring
Description During a call to tpreturn() in transaction mode with the TPSUCCESS flag, a call to xa_end with
the TMSUCCESS flag failed with the specified errstring. A service error will be returned to the client.
Action
Check the error reporting mechanism for the associated resource manager to determine the cause of the
problem.
1276 WARN: Forcing deletion of table entries for server group/id
Description A server died and the administrative processes were unable to restart or clean up after the server. The
server and service entries for the server will be deleted from the bulletin board.
Action
No action required.
1277 ERROR: NULL input buffer not allowed for service ’service_name’, which uses routing
26
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
tpcall(5c), ubbconfig(5)
1278 ERROR: Cannot join application - permission denied
Description An ATMI function was called in a client before calling tpinit(), and an attempt to join the
application failed. The client cannot join the application because it does not have permission to do so or
because it did not supply the correct application password. Permission may be denied based on an
invalid application password, failure to pass application specific authentication, or use of restricted
names.
Action
This is an application error. If the application has security turned on, then tpinit() must be called
explicitly with a TPINIT buffer supplying a valid password before calling any other ATMI functions.
See Also
tpinit(5c)
1279 ERROR: Cannot join application - accesser limit exceeded
Description An ATMI function was called in a client before calling tpinit(), and an attempt to join the
application failed. The client cannot join the application because of space limitations.
Action
This is a application configuration problem. The number of accessers is too small and must be
reconfigured to allow more clients.
See Also
ubbconfig(5)
1285 WARN: tpreturn message send blocked, will try file transfer
Description A server process encountered a message queue blocking condition when returning a message to the
client via tpreturn().
Action
The system will automatically attempt to return the message using a temporary file. Performance may be
degraded if this occurs frequently. Check the kernel parameters related to message queue size, and
increase them if necessary.
See Also
BEA TUXEDO Installation Guide and Message No. 1286 below.
1286 ERROR: tpreturn could not send reply errno_val
Description A server process encountered an error when returning a reply message to the client via tpreturn().
The reply message has been discarded, which may cause the client to time out or block forever waiting
for the lost message. The cause may be that the message queue size is too small to receive the reply.
Action
Check the kernel parameters related to message queue size, and increase them if necessary.
See Also
BEA TUXEDO Installation Guide
1287 ERROR: Failure to allocate memory for file message transfer, size size
Description When receiving a message that was transferred in a file because it was too large to put on a message
queue, tprealloc() failed to allocate a typed buffer big enough to hold the 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.
1288 ERROR: File transfer creat failed, file=filename, errno=errno_val
Description The UNIX kernel call creat() failed on filename. This temporary file was being created to transfer a
large message between two BEA TUXEDO system processes on the same machine.
Action
Check temporary directory’s permissions. Check disk space and inode counts for the temporary file
system.
1289 ERROR: File transfer write failed, file=filename, errno=errno_val
Description The UNIX kernel call write() failed on filename. This temporary file was being written to transfer a
large message between two BEA TUXEDO system processes on the same machine.
Action
Check directory and file permissions for the temporary files. Check disk space and inode counts for the
temporary file system.
1290 ERROR: File transfer close failed, file=filename, errno=errno_val
27
Description The UNIX kernel call close() failed on filename after it had been written. This temporary file was
being used to transfer a large message between two BEA TUXEDO system processes on the same
machine.
Action
Check disk space and inode counts for the temporary file system.
1291 ERROR: File transfer fstat failed, file=filename, errno=errno_val
Description The UNIX kernel call fstat() failed on filename. This temporary file was being used to transfer a
large message between two System/T processes on the same machine.
Action
Check directory and file permissions for the temporary files, disk space and inode counts for the
temporary file system, the PERM parameter in the RESOURCES section of the configuration file, and
check for any cron job or other process that might be deleting files from the temporary file directory.
1292 ERROR: File transfer open failed, file=filename, errno=errno_val
Description The UNIX kernel call open() failed on filename. This temporary file was being used to transfer a large
message between two System/T processes on the same machine.
Action
Check directory and file permissions for the temporary files, the PERM parameter in the RESOURCES
section of the configuration file, and check for any cron job or other process that might be deleting files
from the temporary file directory.
1293 ERROR: File transfer read failed, file=filename, errno=errno_val
Description The UNIX kernel call read() failed on filename. This temporary file was being used to transfer a large
message between two System/T processes on the same machine. It either could not be read, or the
wrong number of bytes were read.
Action
Check directory and file permissions for the temporary files, disk space and inode counts for the
temporary file system, the PERM parameter in the RESOURCES section of the configuration file, and
for any cron job or other process that might be deleting files from the temporary file directory.
1294 ERROR: File transfer close failed, file=filename, errno=errno_val
Description The UNIX kernel call close() failed on filename after it had been read. This temporary file was being
used to transfer a large message between two System/T processes on the same machine.
Action
Contact your BEA TUXEDO system Technical Support.
1295 WARN: File transfer unlink failed, file=filename, errno=errno_val
Description The UNIX kernel call unlink() failed on filename after it had been read. This temporary file was
being used to transfer a large message between two System/T processes on the same machine. Although
the transfer succeeded, the file could not be unlinked (deleted), and still is present in the system’s
temporary file directory. This might cause the file system to fill up.
Action
Check directory and file permissions for the temporary files. If the sticky bit is set for the directory, one
user might not be able to delete another user’s files. Check the PERM parameter in the RESOURCES
section of the configuration file. As a temporary measure, delete filename manually. It is no longer
needed by the BEA TUXEDO system. If there are many such files, schedule a cron job to periodically
delete files older than a certain threshold.
1296 WARN: Cannot retrieve own server group table entry
28
Description While booting, a server was unable to retrieve its own server table entry. This particular failure by itself
will not cause the server to be incapable of processing service requests, but may be indicative of
problems elsewhere in the system.
If the output from tmboot(1) indicates that a prior attempt to boot this same server on a different node
had failed, the location of the server group in the bulletin board and the TUXCONFIG file will not be
updated to reflect the current location of this server. The server will still be active and able to receive
requests, but the first subsequent attempt to migrate the server will restart the server on the same
processor where it is now running. Once this first subsequent migration occurs, the server location will
be stored consistently. Also, if the configuration is shut down and rebooted, tmboot(1) will first
attempt to start this server group on the processor where it is not now running. (Note that the condition
mentioned in this paragraph will not normally be the case.)
Action
In the normal case, where tmboot(1) did not indicate that automatic server migration had occurred for
this server’s group, no action is required. However, this condition is likely to be indicative of problems
elsewhere in the system. If tmboot(1) did indicate that automatic server group migration took place for
this server’s group, the administrator may wish to shut down and restart this server group so that the
group location is stored consistently.
See Also
tmboot(1), tmadmin(1)
1297 INFO: Boot process migrating location of group group_name to machine machine_name
Description The tmboot(1) process was unable to successfully boot group group_name on its current machine.
Therefore, tmboot(1) is migrating the location of this group to its alternate machine, machine_name.
The first server in the group to be booted writes this message to the userlog. The group’s migration is
also noted in the output from tmboot(1). The group will remain located on machine_name until it is
manually migrated to its former machine by the administrator, or until a subsequent tmboot(1) detects
that the group is unable to run on machine machine_name, but is able to run on the original machine
name.
Action
No action required.
See Also
tmboot(1)
29
LIBTUX Messages 1300-1399
1301 WARN: Cannot update server group location as listed in bulletin board
Description While booting, a server process noticed that it was being booted on the processor listed as the backup
processor for that server’s group. (This situation occurs when tmboot(1) is unable to boot the server
group on the processor listed as the current processor for that group.) The server attempted to update the
location of the group as stored in the bulletin board, but was unable to make the message required to
update this information. This particular failure by itself will not cause the server to be incapable of
processing service requests, but may be indicative of problems elsewhere in the system. The server will
still be active and able to receive requests, but the first subsequent attempt to migrate the server will
restart the server on the same processor where it is now running. Once this occurs, the server location
will be stored consistently. Unless otherwise indicated by another error, the location of the server group
will be stored properly in the TUXCONFIG file.
Action
The administrator may choose to allow the servers in the group reporting this error to continue running,
or may elect to shut down and restart the server group so that the group location is stored consistently in
the bulletin board.
See Also
tmboot(1), tmadmin(1)
1302 ERROR: Commit error due to outstanding handles
Description An attempt to commit a transaction with outstanding handles failed.
Action
This is an application error. Make sure there are no outstanding handles before calling tpcommit().
1308 ERROR: TUXCONFIG environment variable must be an absolute pathname.
Description The application specified a value for the TUXCONFIG environment variable that is a simple or relative
pathname, not beginning with slash (/).
Action
Change the TUXCONFIG environment variable to be an absolute pathname and re-execute the
program.
1309 ERROR: tpcommit failed to send message to TMS server
Description The application called tpcommit(), which tried to send a request to the transaction manager server
for processing. No entry was found for the transaction manager server.
Action
Check the userlog for other messages indicating why the request failed. Check that the transaction
manager servers are available for all resource managers involved in the application service.
See Also
tpcommit(3c)
1351 ERROR: Performed tpforward() with outstanding conversations
Description The application called tpforward() while there were outstanding conversations (for example, after
calling tpconnect() but before receiving a disconnect).
Action
Correct the application such that tpforward() is called only after all conversations and
asynchronous request responses have been processed.
See Also
tpconnect(3c), tpforward(3c)
1354 ERROR: Another application is using IPC key ipckey
Description The IPC key, ipckey, specified in the RESOURCES section of the UBBCONFIG file is being used by
another BEA TUXEDO system application.
Action
Change the IPCKEY value, reload the configuration file, and boot the application.
See Also
tpenqueue(3c)
1355 ERROR: Cannot find *MACHINES entry for MASTER master
Description When joining the application, a client or server cannot find the configuration entry for the MASTER
machine, master.
Action
This should not occur since it is checked when the configuration is loaded or updated. Contact your
BEA TUXEDO system Technical Support.
See Also
ubbconfig(5)
1367 ERROR: Expired TUXEDO System Binary License
30
Description The TUXEDO System/T master binary is not properly licensed, or the expiration date on an evaluation
copy has been reached.
Action
Contact your BEA TUXEDO system Technical Support.
1372 ERROR: tpsuspend xa_end returned errstring
Description The call to xa_end from within tpsuspend returned the XA error value errstring.
Action
Check the error reporting mechanism for the associated resource manager to determine the cause of the
problem. Contact your BEA TUXEDO system Technical Support or resource manager vendor.
1373 ERROR: Wrong transaction state statestring
Description tpsuspend was called while the transaction was not in an active state (for example, tpabort or
tpcommit had already been called).
Action
Correct the application such that it does not call tpsuspend unless it is the current owner of the
transaction.
See Also
tpsuspend(3c)
1374 ERROR: tpresume xa_start flags flagval returned errstring
Description The call to xa_start from within tpresume with the XA flag value flagval (either TMJOIN or
TMNOFLAGS) returned the XA error value errstring.
Action
Check the error reporting mechanism for the associated resource manager to determine the cause of the
problem. Contact your BEA TUXEDO system Technical Support or resource manager vendor.
1376 WARN: variable value "string" in environment does not match configuration "string"
Description While putting variables into the environment for either the machine or server ENVFILE file, the
TUXCONFIG, TUXOFFSET, TUXDIR, or APPDIR variable was encountered and its value did not
match the associated value in the configuration file. This variable cannot be overridden in the
ENVFILE and its value is taken from the *MACHINES section of the configuration file for the
associated machine. The modified value will not be put into the environment.
Action
No action required.
See Also
ubbconfig(5)
1378 ERROR: Transaction counter <= 0
Description As part of starting a new transaction, the system makes a unique transaction identifier that is based, in
part, on a system counter. If for some reason the counter was corrupted, this message is printed.
Action
Contact your BEA TUXEDO system Technical Support. The bulletin board shared memory has
probably been corrupted by a stray pointer or some other problem. Consider running tmadmin’s
bbclean command to verify the sanity of this site’s bulletin board.
See Also
tmadmin(1)
1380 ERROR: Still in transaction
Description A service routine explicitly started a transaction but did not commit or abort it before calling
tpreturn. The transaction was aborted by the system, and the caller received a TPESVCERR return
code.
Action
Modify the service routine to resolve the transaction before calling tpreturn.
See Also
tpreturn(3c)
1381 ERROR: Cannot lock bulletin board
Description As part of tpreturn’s processing in transaction mode, an attempt to lock the bulletin board failed.
The transaction was aborted.
Action
Check for corrupted shared memory, an invalid application IPCKEY, or if two applications are using
the same IPCKEY.
1382 ERROR: Cannot unlock bulletin board
Description As part of tpreturn’s processing in transaction mode, an attempt to unlock the bulletin board failed.
The transaction was aborted.
Action
Check for corrupted shared memory, an invalid application IPCKEY, or if two applications are using
the same IPCKEY.
1383 ERROR: Cannot get counter value for new transaction
31
Description As part of starting a new transaction, the system makes a unique transaction identifier that is based, in
part, on a system counter. If for some reason the counter was corrupted, this message is printed.
Action
Contact your BEA TUXEDO system Technical Support. The bulletin board shared memory has
probably been corrupted by a stray pointer or some other problem. Consider running tmadmin’s
bbclean command to verify the sanity of this site’s bulletin board.
See Also
tmadmin(1)
1384 ERROR: xa_start flags flags returned errcode
Description This message is issued if a process attempting to start a new transaction encounters an error when
calling the database resource manager’s xa_start() routine. The transaction fails to begin. The
message prints the flags passed to xa_start() and the error code that xa_start() returned.
Action
Contact your BEA TUXEDO system Technical Support or your database system vendor. The database
system documentation or error logs may contain more information about why xa_start() failed.
1385 ERROR: xa_end returned errcode
Description This message is issued if a process attempting to commit a transaction encounters an error when calling
the database resource manager’s xa_end() routine. The transaction will be aborted. The message
prints the error code that xa_end() returned.
Action
Contact your BEA TUXEDO system Technical Support or your database system vendor. The database
system documentation or error logs may contain more information about why xa_end() failed.
1386 ERROR: xa_abort returned errcode
Description This message is issued if a process attempting to commit a transaction could not lock the bulletin board.
It then attempted to roll back the transaction, and encountered an error when calling the database
resource manager’s xa_rollback() routine [previously known as xa_abort()]. The message
prints the error code that xa_rollback() returned.
Action
Contact your BEA TUXEDO system Technical Support or your database system vendor. The database
system documentation or error logs may contain more information about why xa_rollback()
failed.
1387 ERROR: xa_commit returned errcode
Description This message is issued if a process attempting to commit a transaction encountered an error when
calling the database resource manager’s xa_commit() routine. The message prints the error code that
xa_commit() returned.
Action
Contact your BEA TUXEDO system Technical Support or your database system vendor. The database
system documentation or error logs may contain more information about why xa_commit() failed.
1388 ERROR: Wrong transaction state state
Description This message is issued when a transaction cannot be committed because the process is in an invalid
transaction state (that is, a protocol violation). The process may have already called tpcommit(3c) or
tpabort(3c) to resolve the transaction’s state, and therefore is no longer in transaction mode. This
message also prints out the current transaction state.
Action
See the userlog for more information about this transaction’s completion. Also, use tmadmin’s
printtrans command to find out more information about the transaction.
1389 ERROR: xa_end returned errcode
Description This message is issued if a process attempting to abort a transaction encounters an error when calling
the database resource manager’s xa_end() routine. The message prints the error code that
xa_end() returned.
Action
Contact your BEA TUXEDO system Technical Support or your database system vendor. The database
system documentation or error logs may contain more information about why xa_end() failed.
1390 ERROR: Too many groups in transaction, cannot add groupname
Description An error has occurred while attempting to add a group to a transaction because the maximum number of
groups allowed in a transaction (16 groups) has been reached. The transaction will be aborted.
Action
If possible, reduce the number of groups required for the particular operation, or call some of them with
the TPNOTRAN flag. Using tpenqueue() may allow some work involving additional groups to be
done later as part of another transaction. If that is not possible, contact your BEA TUXEDO system
Technical Support.
1391 WARN: tpreturn called outside service routine
32
Description tpreturn() was called in an invalid context.
Action
Modify the application code calling tpreturn().
See Also
tpreturn(3c)
1392 WARN: tpreturn called with invalid flags 0xflags
Description tpreturn() was called with an invalid flag parameter. This userlog message is issued because
control will not return to the service routine. Instead, the process invoking the service routine will
receive a TPESVCERR return code.
Action
Modify the application code calling tpreturn().
See Also
tpreturn(3c)
1393 WARN: tpreturn called with TPEXIT
Description tpreturn() was called with the TPEXIT flag value. This userlog message is issued because control
will not return to the service routine, and the server process will be restarted. The process invoking the
service routine will receive a TPESVCERR return code.
Action
Contact the application developer to learn why the server process failed and requested a restart.
See Also
tpreturn(3c)
1394 WARN: tpreturn called with invalid rval number
Description tpreturn() was called with an invalid rval parameter. This userlog message is issued because
control will not return to the service routine. Instead, the process invoking the service routine will
receive a TPESVCERR return code.
Action
Modify the application code calling tpreturn().
See Also
tpreturn(3c)
1395 WARN: tpreturn failed because connection not SENDONLY
Description tpreturn() was called in an invalid conversational context. The caller should be in SENDONLY
mode when attempting to successfully end the conversation. This userlog message is issued because
control will not return to the service routine. Instead, the process invoking the service routine will
receive a TPESVCERR return code.
Action
Modify the application logic so that the service routine has SENDONLY control of the conversation
before calling tpreturn().
See Also
tpconnect(3c), tpreturn(3c)
1396 WARN: tpreturn failed because subordinate conversations open
Description tpreturn() was called in an invalid conversational context. The caller should successfully end all
conversations it initiated before calling tpreturn() with TPSUCCESS. This userlog message is
issued because control will not return to the service routine. Instead, the process invoking the service
routine will receive a TPESVCERR return code.
Action
Modify the application logic so that the service routine ends all conversations it started before calling
tpreturn().
See Also
tpconnect(3c), tpreturn(3c)
1397 WARN: tpreturn transaction processing failure
Description tpreturn() encountered a transaction processing error, and the transaction will be aborted (if it has
not been already). One possible cause might be the service routine ran for a very long time, and the
transaction timed out before tpreturn() was called. This userlog message is issued because control
will not return to the service routine. The process invoking the service routine will receive an error
return code.
Action
See the userlog for more information about this transaction’s completion. Also, use tmadmin’s
printtrans command to find out more information about the transaction.
See Also
tmadmin(1)
1398 WARN: tpforward called outside service routine
Description tpforward() was called in an invalid context.
Action
Modify the application code calling tpforward().
See Also
tpforward(3c)
1399 WARN: tpforward called with invalid flags 0xflags
33
Description tpforward() was called with an invalid flag parameter. This userlog message is issued because
control will not return to the service routine. Instead, the process invoking the service routine will
receive a TPESVCERR return code.
Action
Modify the application code calling tpforward().
See Also
tpforward(3c)
34
Open as PDF
Similar pages