500
ERROR: Invalid status given
Description
A status was passed to the update routine that was neither suspended nor not suspended.
Action
Check for corrupted shared memory or an invalid IPCKEY (wrong application).
501
ERROR: Memory allocation failure
malloc failed when an attempt was made to acquire space for a table large enough to hold a long word entry for all the services in a server.
malloc
Check for corrupted shared memory, inappropriate sysgen memory or process parameters, or if there are too many running processes.
502
malloc failed when an attempt was made to acquire space for a table large enough to hold a long word entry for each service in a MSSQ set. A status update was being attempted.
503
ERROR: Cannot find DBBL
An attempt was made to send a message to the DBBL, and its whereabouts could not be ascertained either from the BB or from a BRIDGE process.
Check for a partitioned network, corrupted shared memory, or if all administrative processes are running.
505
ERROR: Send/receive error on remote procedure call
A message send failed. The message send failure may have resulted from a message type switch function failure, from an invalid message length, or from a low level message send failure.
Check for a partitioned network, corrupted shared memory, if all the administrative processes are running, or if the sysgen parameters for messages are appropriate.
506
Two attempts were made to send a message to a D(BBL) and both attempts failed. Either the recipient was not active (alive), or the sending of the message send itself failed. The message send failure may have resulted from a message type switch function failure, from an invalid message length, or from a low level message send failure.
515
ERROR: Null message buffer, cannot dispatch service
The run server function, which continually dequeues messages (service requests), called the server dispatch routine with a null message pointer. This means that the dequeuing of a message failed.
System message resources may be corrupted.
516
ERROR: Unknown service request name
The server dispatch function calls a high level service dispatch which attempts to find the entry point address of the service and cannot. The server dispatch function records this error.
Shared memory may be corrupted, or the ipc application key is not correct.
517
ERROR: Failed sending reply
The server dispatch function calls a high level service dispatch which attempts to find the entry point address of the service and cannot. The server dispatch function conveys this error to the caller via a message (reply). If the message send fails, this message appears.
System message resources may be exhausted, the application may be partitioned, or shared memory is corrupted.
518
ERROR: Service 'name' failed to call tpreturn or tpforward
The server dispatch function calls the service. Control returning after this call is an indication that tpreturn failed (it does a longjmp and should never return after the call), or tpforward failed (it gives up control to another server). These are the only two ways a service can surrender control after processing a service.
tpreturn
longjmp
tpforward
The stack in the service became corrupted. Try running the service under a debugger.
See Also
tpsvrdone(3c)
tpsvrdone
521
ERROR: Clients cannot call tpsvrdone
The process invoking the default server termination function is a client (should be a server).
The default server termination library function was linked into a process not identified in the SERVERS section of the configuration file, or shared memory is corrupted.
SERVERS
tpservice(3c)
tpservice
522
INFO: Default tpsvrdone() function used
This message indicates that the system-provided default server exit routine was used in stopping the server.
No action required
523
ERROR: tpclose failed
The tpclose function failed in the default server exit function, tpsvrdone.
tpclose
An error occurred in closing the resource manager associated with this server's group. The CLOSEINFO parameter in the GROUPS section of the configuration may not be correct, or the resource manager may not be available.
CLOSEINFO
GROUPS
524
ERROR: Only servers allowed to call tpsvrinit
The process invoking the default server initialization function is not a TUXEDO System/T server.
The default server initialization library function was linked into a process not identified in the SERVERS section of the configuration file, or shared memory is corrupted.
525
INFO: Default tpsvrinit() function used
This message indicates that the system-provided default server initialization routine was used in starting the server.
530
ERROR: NULL service name, cannot dispatch service request
The service start routine, called by the start work routine (which is called by the service dispatch routine), failed because the dispatched message contained no service request name.
Verify that the application ipc key is correct, or that not more than one application is using the same ipc key, or some other failure occurred with the associated message queues.
531
ERROR: Function address set to -1
The service start routine, called by the start work routine (which is called by the service dispatch routine), failed because the bulletin board entry for the requested service function address contains a zero.
Verify that the application ipc key is correct, or that not more than one application is using the same ipc key.
532
ERROR: Invalid message pointer given
The service dispatch routine passed the service start work routine a null pointer due to a TPESYSTEM error that occurred earlier. This occurred in either a (D)BBL or server and indicates that a corrupt or invalid message was received.
TPESYSTEM
Verify that the correct machine types are set, or that the application ipc key is correct, or that not more than one application is using the same ipc key.
533
ERROR: Cannot execute service, address not known
During the service dispatch, the service start function returned null indicating a failure. This could be due to a null service name appearing in the dispatched message, or the requested service cannot be found, or the bulletin board could not be locked.
Verify that the application ipc key is correct, or that not more than one application is using the same ipc key, or that the service is advertised.
534
ERROR: Work completed, cannot stop twice
When a service returns from dispatch, a flag is checked to see if the service was started successfully. If this flag is not set, the above error message appears. This flag is only turned on if the service starts, and turned off only when the service done function completes. Either the service never started or the service done function was called more than once.
Check the ulog for additional information about server failures.
ulog
536
ERROR: Unable to create request queue
An internal function used to create a UNIX system message queue for Inter-Process Communications failed.
Check with your UNIX System Administrator and increase the appropriate message parameter for your system. The possible parameters that may need to be increased are MSGMAX, MSGMNB, MSGMNI, MSGSSZ, and MSGSEG.
MSGMAX
MSGMNB
MSGMNI
MSGSSZ
MSGSEG
537
ERROR: Unable to create reply queue
BEA TUXEDO Installation Guide
538
ERROR: Unable to remove request queue queue_id (errno=err_val)
An internal function used to remove a UNIX system message queue for Inter-Process Communications failed. The UNIX system function msgctl returned an error.
msgctl
Contact your UNIX System Administrator.
539
ERROR: Unable to remove reply queue queue_id (errno=errno_val)
An internal function used to remove a UNIX System message queue for Inter-Process Communications failed. The UNIX System function msgctl returned an error.
540
ERROR: TUXCONFIG environment value (string) does not match
configuration file (string)
The TUXCONFIG parameter defined in the TUXEDO System/T configuration file does not match the current TUXCONFIG shell environment variable.
TUXCONFIG
Set the TUXCONFIG variable in your current shell to match the value defined in the configuration file and then export it. Re-create the binary configuration file by executing tmloadcf and then tmboot.
tmloadcf
tmboot
tmboot(1), tmloadcf(1), ubbconfig(5)
ubbconfig
541
WARN: Server group_name/server_id terminated
A server has died. The BEA TUXEDO system will attempt to clean or restart the server according to the specification of the server in the configuration.
ubbconfig(5)
542
WARN: Bulletin Board update error error_val
A server had died. The BEA TUXEDO system was attempting to clean or restart the server according to the specification of the server in the configuration. The server was either non-restartable, or the generation count was exceeded.
Determine why the server is dying. If required, modify the configuration file to increase the generation count and/or make the server restartable.
543
544
ERROR: Unable to delete server group_name/server_id
A non-restartable server had died. The BEA TUXEDO system was attempting to clean up after the aforementioned incident, but both the clean-up as well the removal of resources allocated to the server failed.
Contact your BEA TUXEDO system Technical Support.
545
ERROR: Unable to update Bulletin Board, error: error_val
The BEA TUXEDO system attempted to update the server table that resides in UNIX System shared memory. The update was not successful. Either the server information provided was invalid, or an attempted lock on the TUXEDO System/T bulletin board was unsuccessful.
Contact your BEA TUXEDO system Technical Support
546
547
ERROR: Unable to clean up BBL processes
The BEA TUXEDO system attempted to clean up a system process, an action not permitted at that point.
548
ERROR: Unable to clean up BRIDGE processes
The BEA TUXEDO system attempted to clean up a system process, an action not permitted at that point
549
ERROR: Unable to clean up processes on remote node(s)
The BEA TUXEDO system attempted to clean up processes that are running on a remote computer, and that operation is not permitted at that point.
550
WARN: Cleaning up restartable server group_name/server_id
The BEA TUXEDO system is about to clean up a server that was defined to be restartable.
No action required.
551
WARN: Cleaning up server group_name/server_id
The TUXEDO System is about to clean up a server table entry.
552
WARN: TUXDIR environment variable not set
The BEA TUXEDO system environment variable TUXDIR was not set.
TUXDIR
Set and export the environment variable TUXDIR and repeat the operation.
553
ERROR: Multi-processor operation sysmulti failed - errno=error_val
The TUXEDO System/T application was running on a multi-processor environment. While attempting to use the sysmulti function, an error was detected.
sysmulti
554
555
ERROR: Unable to exec command - errno=errno_val
The BEA TUXEDO system attempted to execute the cleanupsrv process. The UNIX System library function system() failed.
cleanupsrv
system
556
ERROR: Unable to determine ID of server to be removed
The BEA TUXEDO system attempted to remove a server process, but was unable to determine its ID.
557
INFO: Server group_name/server_id being restarted
The BEA TUXEDO system is restarting a server process.
558
ERROR: Restarting a remote server not permitted
The application is trying to remote restart a server process. This operation is not permitted.
559
ERROR: TUXDIR environment variable not set for restartsrv process
The BEA TUXEDO system environment variable, TUXDIR, is not set. Because of this the restartsrv process cannot be executed.
restartsrv
Set and export the TUXDIR environment variable and repeat the operation.
561
ERROR: Multi-processor operation sysmulti failed - errno=errno_val
562
563
564
ERROR: Unable to exec command application RCMD command errno=errno_val
The BEA TUXEDO system attempted to execute the application-specified RCMD command associated with the server to be restarted. The UNIX System library function system() used for this operation failed.
RCMD
575
ERROR: Unable to reset semaphore for sem key_val, errno errno_val
The BEA TUXEDO system was in the process of cleaning up a registry slot for a process. While doing the aforementioned operation, the semaphore used for that process had to be reset. The semaphore operation semctl failed.
semctl
576
ERROR: Unable to remove queue for process pid
The BEA TUXEDO system was in the process of cleaning up a registry slot for a process. A part of this clean up involves removing queues used by that process. The operation used to remove the queue failed.
577
ERROR: Unable to register because the slot is already owned by another process
While registering a process, a conflict arose with regard to a slot in the registry table. Another process already owned that slot.
578
579
ERROR: Unable to obtain the registry slot owned by process
The BEA TUXEDO system was attempting to restart a server. In so doing, the system was unable to determine the registry table slot that was originally used by the restarting process.
580
ERROR: Attempt to take over registry table entry of non-restarting process
The BEA TUXEDO system attempted to use a registry table slot in a manner that is not permitted. Re-using a registry table slot is permitted for servers that are restarting, but not for a server that is defined to be non-restartable.
581
ERROR: Migrating and given an old pid when none expected
The BEA TUXEDO system was attempting to find a registry table slot for a restarting server, but the server was set up to migrate.
582
ERROR: Unable to register, registry table full
The BEA TUXEDO system was attempting to find a registry table slot for a process, but the registry table was full.
Increase the MAXACCESSERS parameter in the UBBCONFIG file, rebuild the TUXCONFIG file, then reboot the application and try again.
MAXACCESSERS
UBBCONFIG
ubbconfig(5), tmboot(1)
583
ERROR: Not a privileged user, incorrect permissions
The user attempted to execute TUXEDO System/T functions that are reserved for users with the correct permissions, but was not authorized to do so.
ubbconfig(5), tmadmin(1)
tmadmin
584
ERROR: Invalid registry table slot index passed, unable to register
When a process attempts to register with the BEA TUXEDO system, the administrative process(es) supplied update the internal registry table. In this instance, the registry table index to be used exceeded the number of MAXACCESSERS specified in the configuration file.
Increase the value of the MAXACCESSERS parameter in the UBBCONFIG file, rebuild the TUXCONFIG file, reboot the TUXEDO System/T application, and repeat the operation(s).
585
ERROR: Invalid registry table slot index passed, unable to unregister
The BEA TUXEDO system administrative process attempted to unregister a process, but failed in doing so because the index into the registry table to be used was outside the bounds of the registry table.
586
ERROR: Unable to unregister process pid - errno errno_val
tperrno tperror_val
The BEA TUXEDO system administrative process attempted to unregister a process, but failed.
587
INFO: Process pid that is unregistering has ticket ticket
The process that is unregistering from the TUXEDO System/T application is holding a ticket for the user-level semaphore. The ticket value will be cleared as part of the unregistration.
588
ERROR: Unable to open TUXCONFIG file
The TUXEDO System/T administrative process was unable to open the TUXCONFIG file.
589
ERROR: Unable to read the *RESOURCES section of the TUXCONFIG file
The TUXEDO System/T administrative process was unable to read the RESOURCES section of the TUXCONFIG file.
RESOURCES
590
ERROR: Unable to read the TUXCONFIG file, version type mismatch
The TUXEDO System/T administrative process was unable to read the TUXCONFIG file because of a mismatch of version types.
591
ERROR: Unable to read the TUXCONFIG file, release mismatch
The TUXEDO System/T administrative process was unable to read the TUXCONFIG file because the BEA TUXEDO system release number stored in the TUXCONFIG file did not match the release number compiled into the system.
592
ERROR: Invalid model stored in the TUXCONFIG file, must be SHM or MP
The MODEL parameter value stored in the TUXCONFIG file was not MP or SHM.
MODEL
MP
SHM
Check the configuration file and ensure that the MODEL parameter value in the RESOURCES section is MP or SHM.
593
ERROR: Unable to map ID of a PE to ipckey
The BEA TUXEDO system was unable to determine the PE and IPCKEY mapping for a particular PE
594
ERROR: Unable to locate PE entry in the Bulletin Board
The BEA TUXEDO system was unable to locate information for a PE in the Bulletin Board.
595
ERROR: No 'string' entry in table_name table
The BEA TUXEDO system was unable to locate information for the specified string in the Bulletin Board table specified. It may be that the server was built with an inappropriate "-b {shm|mp}" option; for example, a server built with "-b shm" will produce the message:
-b
{shm|mp}
-b shm
No 'MP' entry in model table.
when booted in a MP application.
buildserver(1)
buildserver
596
ERROR: [NULL service name used to get service information]
A BEA TUXEDO system internal function was used to retrieve service information from the services table, but a NULL service name was used.
597
ERROR: [Unable to open the *SERVICES section table]
A BEA TUXEDO system internal function was used to retrieve service information from the services table, but the open failed.
598
ERROR: [Unable to read information from the *SERVICES section table]
599
ERROR: Maximum number of types/subtypes, number, has been exceeded
The maximum number of types/subtypes permitted for a particular TUXEDO System/T service has been exceeded.
Review the configuration file, verify that all services use less than the maximum number of types/subtypes, and rebuild the TUXCONFIG file.
ubbconfig(5), tmloadcf(1)