System Messages: LIBTUX Catalog 500-599


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
	Description	`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.
	Action	Check for corrupted shared memory, inappropriate sysgen memory or process parameters, or if there are too many running processes.

502	ERROR: Memory allocation failure
	Description	`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.
	Action	Check for corrupted shared memory, inappropriate sysgen memory or process parameters, or if there are too many running processes.

503	ERROR: Cannot find DBBL
	Description	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.
	Action	Check for a partitioned network, corrupted shared memory, or if all administrative processes are running.

505	ERROR: Send/receive error on remote procedure call
	Description	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.
	Action	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	ERROR: Send/receive error on remote procedure call
	Description	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.
	Action	Check for a partitioned network, corrupted shared memory, if all the administrative processes are running, or if the sysgen parameters for messages are appropriate.

515	ERROR: Null message buffer, cannot dispatch service
	Description	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.
	Action	System message resources may be corrupted.

516	ERROR: Unknown service request name
	Description	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.
	Action	Shared memory may be corrupted, or the ipc application key is not correct.

517	ERROR: Failed sending reply
	Description	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.
	Action	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*
	Description	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.
	Action	The stack in the service became corrupted. Try running the service under a debugger.
	See Also	`tpsvrdone`(3c)
521	ERROR: Clients cannot call tpsvrdone
	Description	The process invoking the default server termination function is a client (should be a server).
	Action	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.
	See Also	`tpservice`(3c)
522	INFO: Default tpsvrdone() function used
	Description	This message indicates that the system-provided default server exit routine was used in stopping the server.
	Action	No action required
	See Also	`tpservice`(3c)
524	ERROR: Only servers allowed to call tpsvrinit
	Description	The process invoking the default server initialization function is not a TUXEDO System/T server.
	Action	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.
	See Also	`tpservice`(3c)
525	INFO: Default tpsvrinit() function used
	Description	This message indicates that the system-provided default server initialization routine was used in starting the server.
	Action	No action required
	See Also	`tpservice`(3c)
530	ERROR: NULL service name, cannot dispatch service request
	Description	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.
	Action	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
	Description	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.
	Action	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
	Description	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.
	Action	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
	Description	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.
	Action	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
	Description	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.
	Action	Check the `ulog` for additional information about server failures.

536	ERROR: Unable to create request queue
	Description	An internal function used to create a UNIX system message queue for Inter-Process Communications failed.
	Action	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`.

537	ERROR: Unable to create reply queue
	Description	An internal function used to create a UNIX system message queue for Inter-Process Communications failed.
	Action	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`.
	See Also	Oracle TUXEDO Installation Guide
538	*ERROR: Unable to remove request queue queue_id* (errno=err_val)**
	Description	An internal function used to remove a UNIX system message queue for Inter-Process Communications failed. The UNIX system function `msgctl` returned an error.
	Action	Contact your UNIX System Administrator.

539	*ERROR: Unable to remove reply queue queue_id* (errno=errno_val)**
	Description	An internal function used to remove a UNIX System message queue for Inter-Process Communications failed. The UNIX System function `msgctl` returned an error.
	Action	Contact your UNIX System Administrator.

540	*ERROR: TUXCONFIG environment value (string) does not match configuration file (string)*
	Description	The `TUXCONFIG` parameter defined in the TUXEDO System/T configuration file does not match the current `TUXCONFIG` shell environment variable.
	Action	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`.
	See Also	`tmboot`(1), `tmloadcf`(1), `ubbconfig`(5)
541	*WARN: Server group_name/server_id* terminated**
	Description	A server has died. The Oracle TUXEDO system will attempt to clean or restart the server according to the specification of the server in the configuration.
	Action	No action required
	See Also	`ubbconfig`(5)
542	WARN: Bulletin Board update error error_val
	Description	A server had died. The Oracle 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.
	Action	Determine why the server is dying. If required, modify the configuration file to increase the generation count and/or make the server restartable.
	See Also	`ubbconfig`(5)
543	WARN: Bulletin Board update error error_val
	Description	A server had died. The Oracle 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.
	Action	Determine why the server is dying. If required, modify the configuration file to increase the generation count and/or make the server restartable.
	See Also	`ubbconfig`(5)
544	ERROR: Unable to delete server group_name/server_id
	Description	A non-restartable server had died. The Oracle 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.
	Action	Contact your Oracle TUXEDO system Technical Support.

545	ERROR: Unable to update Bulletin Board, error: error_val
	Description	The Oracle 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.
	Action	Contact your Oracle TUXEDO system Technical Support

546	ERROR: Unable to update Bulletin Board, error: error_val
	Description	The Oracle 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.
	Action	Contact your Oracle TUXEDO system Technical Support

547	ERROR: Unable to clean up BBL processes
	Description	The Oracle TUXEDO system attempted to clean up a system process, an action not permitted at that point.
	Action	Contact your Oracle TUXEDO system Technical Support

548	ERROR: Unable to clean up BRIDGE processes
	Description	The Oracle TUXEDO system attempted to clean up a system process, an action not permitted at that point
	Action	Contact your Oracle TUXEDO system Technical Support

549	ERROR: Unable to clean up processes on remote node(s)
	Description	The Oracle TUXEDO system attempted to clean up processes that are running on a remote computer, and that operation is not permitted at that point.
	Action	Contact your Oracle TUXEDO system Technical Support

550	WARN: Cleaning up restartable server group_name/server_id
	Description	The Oracle TUXEDO system is about to clean up a server that was defined to be restartable.
	Action	No action required.

551	WARN: Cleaning up server group_name/server_id
	Description	The TUXEDO System is about to clean up a server table entry.
	Action	No action required.

552	WARN: TUXDIR environment variable not set
	Description	The Oracle TUXEDO system environment variable `TUXDIR` was not set.
	Action	Set and export the environment variable `TUXDIR` and repeat the operation.
	See Also	Oracle TUXEDO Installation Guide
553	ERROR: Multi-processor operation sysmulti failed - errno=error_val
	Description	The TUXEDO System/T application was running on a multi-processor environment. While attempting to use the `sysmulti` function, an error was detected.
	Action	Contact your UNIX System Administrator.

554	ERROR: Multi-processor operation sysmulti failed - errno=error_val
	Description	The TUXEDO System/T application was running on a multi-processor environment. While attempting to use the `sysmulti` function, an error was detected.
	Action	Contact your UNIX System Administrator.

555	ERROR: Unable to exec command - errno=errno_val
	Description	The Oracle TUXEDO system attempted to execute the `cleanupsrv` process. The UNIX System library function `system`() failed.
	Action	Contact your UNIX System Administrator.

556	ERROR: Unable to determine ID of server to be removed
	Description	The Oracle TUXEDO system attempted to remove a server process, but was unable to determine its ID.
	Action	Contact your Oracle TUXEDO system Technical Support

557	*INFO: Server group_name/server_id* being restarted**
	Description	The Oracle TUXEDO system is restarting a server process.
	Action	No action required.

558	ERROR: Restarting a remote server not permitted
	Description	The application is trying to remote restart a server process. This operation is not permitted.
	Action	No action required

559	ERROR: TUXDIR environment variable not set for restartsrv process
	Description	The Oracle TUXEDO system environment variable, `TUXDIR`, is not set. Because of this the `restartsrv` process cannot be executed.
	Action	Set and export the `TUXDIR` environment variable and repeat the operation.

561	ERROR: Multi-processor operation sysmulti failed - errno=errno_val
	Description	The TUXEDO System/T application was running on a multi-processor environment. While attempting to use the `sysmulti` function, an error was detected.
	Action	Contact your UNIX System Administrator.

562	ERROR: Multi-processor operation sysmulti failed - errno=errno_val
	Description	The TUXEDO System/T application was running on a multi-processor environment. While attempting to use the `sysmulti` function, an error was detected.
	Action	Contact your UNIX System Administrator.

563	ERROR: Unable to exec command - errno=errno_val
	Description	The TUXEDO System/T application was running on a multi-processor environment. While attempting to use the `sysmulti` function, an error was detected.
	Action	Contact your UNIX System Administrator.

564	ERROR: Unable to exec command application RCMD command - errno=errno_val
	Description	The Oracle 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.
	Action	Contact your UNIX System Administrator.

575	ERROR: Unable to reset semaphore for sem key_val, errno errno_val
	Description	The Oracle 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.
	Action	Contact your Oracle TUXEDO system Technical Support

576	ERROR: Unable to remove queue for process pid
	Description	The Oracle 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.
	Action	Contact your Oracle TUXEDO system Technical Support

577	ERROR: Unable to register because the slot is already owned by another process
	Description	While registering a process, a conflict arose with regard to a slot in the registry table. Another process already owned that slot.
	Action	Contact your Oracle TUXEDO system Technical Support

578	ERROR: Unable to register because the slot is already owned by another process
	Description	While registering a process, a conflict arose with regard to a slot in the registry table. Another process already owned that slot.
	Action	Contact your Oracle TUXEDO system Technical Support

579	ERROR: Unable to obtain the registry slot owned by process
	Description	The Oracle 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.
	Action	Contact your Oracle TUXEDO system Technical Support

580	ERROR: Attempt to take over registry table entry of non-restarting process
	Description	The Oracle 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.
	Action	Contact your Oracle TUXEDO system Technical Support

581	ERROR: Migrating and given an old pid when none expected
	Description	The Oracle TUXEDO system was attempting to find a registry table slot for a restarting server, but the server was set up to migrate.
	Action	Contact your Oracle TUXEDO system Technical Support

582	ERROR: Unable to register, registry table full
	Description	The Oracle TUXEDO system was attempting to find a registry table slot for a process, but the registry table was full.
	Action	Increase the `MAXACCESSERS` parameter in the `UBBCONFIG` file, rebuild the `TUXCONFIG` file, then reboot the application and try again.
	See Also	`ubbconfig`(5), `tmboot`(1)
583	ERROR: Not a privileged user, incorrect permissions
	Description	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.
	Action	Contact your Oracle TUXEDO system Technical Support
	See Also	`ubbconfig`(5), `tmadmin`(1)
584	ERROR: Invalid registry table slot index passed, unable to register
	Description	When a process attempts to register with the Oracle 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.
	Action	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).
	See Also	`ubbconfig`(5)
585	ERROR: Invalid registry table slot index passed, unable to unregister
	Description	The Oracle 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.
	Action	Contact your Oracle TUXEDO system Technical Support

586	ERROR: Unable to unregister process pid - errno errno_val tperrno tperror_val
	Description	The Oracle TUXEDO system administrative process attempted to unregister a process, but failed.
	Action	Contact your Oracle TUXEDO system Technical Support

587	INFO: Process pid that is unregistering has ticket ticket
	Description	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.
	Action	No action required.

588	ERROR: Unable to open TUXCONFIG file
	Description	The TUXEDO System/T administrative process was unable to open the `TUXCONFIG` file.
	Action	Contact your Oracle TUXEDO system Technical Support

589	*ERROR: Unable to read the RESOURCES section of the TUXCONFIG file**
	Description	The TUXEDO System/T administrative process was unable to read the `RESOURCES` section of the `TUXCONFIG` file.
	Action	Contact your Oracle TUXEDO system Technical Support

590	ERROR: Unable to read the TUXCONFIG file, version type mismatch
	Description	The TUXEDO System/T administrative process was unable to read the `TUXCONFIG` file because of a mismatch of version types.
	Action	Contact your Oracle TUXEDO system Technical Support

591	ERROR: Unable to read the TUXCONFIG file, release mismatch
	Description	The TUXEDO System/T administrative process was unable to read the `TUXCONFIG` file because the Oracle TUXEDO system release number stored in the `TUXCONFIG` file did not match the release number compiled into the system.
	Action	Contact your Oracle TUXEDO system Technical Support

592	ERROR: Invalid model stored in the TUXCONFIG file, must be SHM or MP
	Description	The `MODEL` parameter value stored in the `TUXCONFIG` file was not `MP` or `SHM`.
	Action	Check the configuration file and ensure that the `MODEL` parameter value in the `RESOURCES` section is `MP` or `SHM`.
	See Also	`ubbconfig`(5)
593	ERROR: Unable to map ID of a PE to ipckey
	Description	The Oracle TUXEDO system was unable to determine the PE and IPCKEY mapping for a particular PE
	Action	Contact your Oracle TUXEDO system Technical Support

594	ERROR: Unable to locate PE entry in the Bulletin Board
	Description	The Oracle TUXEDO system was unable to locate information for a PE in the Bulletin Board.
	Action	Contact your Oracle TUXEDO system Technical Support

595	*ERROR: No 'string' entry in table_name* table**
	Description	The Oracle 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: `No 'MP' entry in model table.` when booted in a `MP` application.
	Action	Contact your Oracle TUXEDO system Technical Support
	See Also	`buildserver`(1)
596	ERROR: [NULL service name used to get service information]
	Description	A Oracle TUXEDO system internal function was used to retrieve service information from the services table, but a NULL service name was used.
	Action	Contact your Oracle TUXEDO system Technical Support

597	*ERROR: [Unable to open the SERVICES section table]**
	Description	A Oracle TUXEDO system internal function was used to retrieve service information from the services table, but the open failed.
	Action	Contact your Oracle TUXEDO system Technical Support.

598	*ERROR: [Unable to read information from the SERVICES section table]**
	Description	A Oracle TUXEDO system internal function was used to retrieve service information from the services table, but the open failed.
	Action	Contact your Oracle TUXEDO system Technical Support.

599	*ERROR: Maximum number of types/subtypes, number, has been exceeded*
	Description	The maximum number of types/subtypes permitted for a particular TUXEDO System/T service has been exceeded.
	Action	Review the configuration file, verify that all services use less than the maximum number of types/subtypes, and rebuild the `TUXCONFIG` file.
	See Also	`ubbconfig`(5), `tmloadcf`(1)