CMDTUX Messages 4100-4199
|
|
4102
ERROR: TUXCONFIG is not set.
Description
tpaclcvt(1) must be run on configured systems. Furthermore, the TUXCONFIG variable must point to the BEA TUXEDO configuration file.
Action
Configure the application (see ubbconfig(5) and tmloadcf(1)). Set your TUXCONFIG variable appropriately. Run tmloadcf(1). Then re-run the command that caused this error.
4103
ERROR: Application must be configured.
Description
tpaclcvt(1) must be run on configured systems. Furthermore, the TUXCONFIG variable must point to the BEA TUXEDO configuration file.
Action
Configure the application (see ubbconfig(5) and tmloadcf(1)). Set your TUXCONFIG variable appropriately. Run tmloadcf(1). Then re-run the command that caused this error.
4104
ERROR: Error retrieving application directory.
Description
tpaclcvt(1) must be run on configured systems. Furthermore, the TUXCONFIG variable must point to the BEA TUXEDO configuration file.
Action
Configure the application (see ubbconfig(5) and tmloadcf(1)). Set your TUXCONFIG variable appropriately. Run tmloadcf(1). Then re-run the command that caused this error.
4105
ERROR: tpaclcvt cannot be run on an active application.
Description
tpaclcvt(1) must be run on a system that is not booted.
Action
Bring the BEA TUXEDO system down using tmshutdown(1). Then re-run this command.
4106
INFO: Converting filename...
Description
tpaclcvt(1) is converting the given group file.
Action
Be patient.
4107
ERROR: Could not open filename.
Description
tpaclcvt(1) could not find the group file to be converted.
Action
Be sure the name of the file to be converted is correct and that this file exists. Re-run the command.
4108
INFO: Converting filename...
Description
tpaclcvt(1) is converting the given user file.
Action
Be patient.
4109
ERROR: Could not open filename.
Description
tpaclcvt(1) could not find the user file to be converted.
Action
Be sure the name of the file to be converted is correct and that this file exists. Re-run the command.
4110
ERROR: Could not create filename.
Description
tpaclcvt(1) could not create the ACL user file.
Action
There are several kernel parameters which could cause this error. Two obvious ones include the maximum allowed size for files and the number of allowable open file descriptors. Disk space could also be a problem. Increase the appropriate kernel parameters or buy a new disk, then try the command again.
4111
ERROR: Could not get information on application.
Description
When tpaclcvt(1) was attempting to get information about the current BEA TUXEDO configuration, an unexpected error occurred.
Action
Make sure your TUXCONFIG variable is set correctly and that your BEA TUXEDO configuration file is valid. If the command continues to return this error, call BEA TUXEDO system Technical Support.
4113
ERROR: Only the TUXEDO administrator can run this command.
Description
tpacladd(1), tpaclmod(1), and tpacldel(1) can only be run by the BEA TUXEDO administrator.
Action
Log into the system as the BEA TUXEDO administrator and re-run this command.
4114
ERROR: Only the TUXEDO administrator can run this command.
Description
tpgrpadd(1), tpgrpmod(1), and tpgrpdel(1) can only be run by the BEA TUXEDO system administrator.
Action
Log into the system as the BEA TUXEDO administrator and re-run this command.
4115
ERROR: Only the TUXEDO administrator can run this command.
Description
tpusradd(1), tpusrmod(1), and tpusrdel(1) can only be run by the BEA TUXEDO administrator.
Action
Log into the system as the BEA TUXEDO administrator and re-run this command.
4116
ERROR: Only the TUXEDO administrator can run this command.
Description
tpaclcvt(1) can only be run by the BEA TUXEDO administrator.
Action
Log into the system as the BEA TUXEDO administrator and re-run this command.
4117
INFO: User id -1 found for username. Generating valid unique id.
Description
Under BEA TUXEDO system security, user identification numbers of -1 were valid. However, the ACL users cannot have -1 as a user identification number. When converting a user file using tpaclcvt(1), user identification numbers of -1 are mapped to valid user identification numbers.
Action
In order to specify particular user identification numbers, use tpusrmod(1).
4118
ERROR: Could not get appropriate user identification number.
Description
User identification numbers are only valid within the range 1 to 131,071. If tpaclcvt(1) cannot generate a unique number within this range, then no more users can be added to the system.
Action
Delete users before calling tpaclcvt(1).
4119
ERROR: tpalloc() failed; tperrno=tperrno
Description
The event server failed to allocate memory for an FML32 buffer.
Action
Make sure that 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.
See Also
tpalloc(3c)
4120
ERROR: tpcall() to svc failed. tperrno=tperrno
Description
The event server couldn't call service svc.
Action
The event server periodically garbage collects stale subscriptions of clients that terminated without unsubscribing. It makes a call to svc to determine if a client is alive. This message states that the service call failed.
See Also
TM_MIB(5), TMSYSEVT(5), TMUSREVT(5)
4126
ERROR: Authentication level must be USER_AUTH, ACL or MANDATORY_ACL.
Description
The BEA TUXEDO system-supplied AUTHSVR failed because the SECURITY parameter in the ubbconfig(5) file was set to NONE or APP_PW. In order for the AUTHSVR to properly authorize users, the SECURITY parameter must be set to USER_AUTH, ACL, or MANDATORY_ACL.
Action
Change the SECURITY setting in the ubbconfig(5) file to USER_AUTH, ACL, or MANDATORY_ACL. Run tmloadcf(1) on the new ubbconfig file and boot the system again.
4127
ERROR: In ACL or MANDATORY_ACL levels, the password file must be filename
Description
ACL and MANDATORY_ACL have a fixed authentication file name relative to the APPDIR of the machine. However, the -f option to AUTHSVR specified a different filename while authentication was ACL or MANDATORY_ACL. This is an error which will cause AUTHSVR to fail.
Action
Change the CLOPT line of the AUTHSVR to remove the -f option. The appropriate authentication file will be used by default. Reboot the AUTHSVR.
4128
ERROR: Unable to advertise AUTHSVC.
Description
AUTHSVR attempts to advertise AUTHSVC if the authentication level is USER_AUTH. If an error occurs when attempting to advertise this service, then this error is returned.
Action
Increase the MAXSERVICES parameter in the ubbconfig(5) file. Run tmloadcf(1) on the new file. Reboot the application. If this error occurs consistently, contact BEA TUXEDO system Technical Support.
4129
INFO: AUTHSVR terminating
Description
The AUTHSVR is terminating normally.
Action
No action required.
4130
INFO: Authentication failed for user username/clientname
Description
The given username/clientname attempted to log into the BEA TUXEDO system and was denied access by the AUTHSVR.
Action
Do whatever is appropriate for attempted security break-ins in the application.
4131
WARN: Wildcard username and/or clientname presented
Description
The wildcard character "*" was presented as either the username or clientname in the TPINIT buffer.
Action
If wildcard characters are appropriate for the security scheme to which your application adheres, then this warning can be ignored. Otherwise, do whatever is appropriate in the security scheme of your application.
4132
WARN: Duplicate id [username/clientname] in password file.
Description
When generating the cache which the AUTHSVR uses to authenticate users, a duplicate entry was found in the authentication file.
Action
Use tpusradd(1), tpusrmod(1), and tpusrdel(1) to maintain the user password files. NEVER edit these files manually.
4133
ERROR: Cannot open password file filename
Description
AUTHSVR could not open the given password file. This file may have been removed accidentally or may have been renamed.
Action
If the password file cannot be found, then it is assumed that there are no users in the BEA TUXEDO system. When users are added via tpusradd(1), then the password file will be created and this error will no longer appear.
4134
ERROR: Memory allocation error.
Description
AUTHSVR could not allocate memory.
Action
Make sure enough memory exists on the system running the AUTHSVR. If it appears that there should be enough memory to run AUTHSVR, and this error happens consistently, contact the BEA TUXEDO system Technical Support.
4135
ERROR: Cannot open file file for writing
Description
The event server couldn't open file file for writing the subscription database.
Action
The event server writes a new copy of the subscription database in the temporary file file. Then, it links this file to the control file specified in the UBBCONFIG file. This message indicates that the server couldn't open the temporary file for writing. Check the file system parameters and take corrective action.
4136
ERROR: .SysServerDied: servername, group srvgrp, id srvid server died
Description
This message indicates that the server specified above died abnormally and the BBL detected this condition in its periodic scan of the BB.
Action
Debug the server and fix the problem before it is restarted again.
See Also
EVENT_MIB(5), TM_MIB(5)
4137
INFO: .SysGroupState: Group name on lmid state change to newstate
Description
A TMIB request to change the state of a group, name, to a new state, newstate its associated machine lmid completed successfully.
Action
No action required.
See Also
TM_MIB(5)
4138
ERROR: Cannot open file file for appending subscription
Description
The event server appends new subscriptions to the end of the control file. This message states that the control file file was inadvertently removed while the server is running.
Action
Prevent such errors from happening by protecting the APPDIR directory. Since this file serves as a backup copy of subscriptions in an application running only a primary event server, it is important that this file be protected.
4139
ERROR: Could not find /etc/passwd
Description
Under the authentication level USER_AUTH, if the AUTHSVR cannot find the user file relative to APPDIR, then it attempts to use /etc/passwd for authentication. If AUTHSVR cannot find the /etc/passwd file, it fails.
Action
Make sure that either the user file relative to APPDIR has been created using tpusradd(1) or that the /etc/passwd file is readable by the BEA TUXEDO system administrator.
4143
ERROR: Subscription matches an already existing subscription
Description
An attempt was made to subscribe to an entry that matches one in the event server's list.
Action
Check the tpsubscribe(3c) and EVENT_MIB(5) reference pages for more detailed explanation.
See Also
tpsubscribe(3c), EVENT_MIB(5)
4144
ERROR: Fielded buffer access error Ferror32
Description
The event server failed to perform Fchg32 on an FML32 buffer.
Action
Contact your BEA TUXEDO system Technical Support and provide the Ferror32 Ferror32.
4145
ERROR: Fielded buffer access error Ferror32
Description
The event server failed to perform Fchg32 on an FML32 buffer.
Action
Contact your BEA TUXEDO system Technical Support and provide the Ferror32 Ferror32.
4146
ERROR: Fielded buffer access error Ferror32
Description
The event server failed to perform Fchg32 on an FML32 buffer.
Action
Contact your BEA TUXEDO system Technical Support and provide the Ferror32 Ferror32.
4147
ERROR: Fielded buffer access error Ferror32
Description
The event server failed to perform Fchg32 on an FML32 buffer.
Action
Contact your BEA TUXEDO system Technical Support and provide the Ferror32 Ferror32.
4148
ERROR: Fielded buffer access error Ferror32
Description
The event server failed to perform Fchg32 on an FML32 buffer.
Action
Contact your BEA TUXEDO system Technical Support and provide the Ferror32 Ferror32.
4149
ERROR: Must specify TA_QCTL_DEQ_TIME if TA_QCTL_QTIME_ABS is set
Description
If the notification mechanism selected for a subscription is to place a message in a BEA TUXEDO system reliable queue, then TA_QCTL_DEQ_TIME must be specified if TA_QCTL_QTIME_ABS is chosen.
Action
Correct the error and re-issue the subscription.
See Also
tpsubscribe(3c), tpenqueue(3c), EVENT_MIB(5)
4150
ERROR: Can't specify both TA_QCTL_QTIME_ABS and TA_QCTL_QTIME_REL
Description
If the notification mechanism selected for a subscription is to place a message in a BEA TUXEDO system reliable queue, then either TA_QCTL_QTIME_ABS or TA_QCTL_QTIME_REL can be chosen.
Action
Correct the error and re-issue the subscription.
See Also
tpsubscribe(3c), tpenqueue(3c), EVENT_MIB(5)
4151
ERROR: Must specify TA_QCTL_DEQ_TIME if TA_QCTL_QTIME_REL is set
Description
If the notification mechanism selected for a subscription is to place a message in a BEA TUXEDO system reliable queue, then TA_QCTL_DEQ_TIME must be specified if TA_QCTL_QTIME_REL is chosen.
Action
Correct the error and re-issue the subscription.
See Also
tpsubscribe(3c), tpenqueue(3c), EVENT_MIB(5)
4152
ERROR: Value of TA_QCTL_PRIORITY is out of range
Description
If the notification mechanism selected for a subscription is to place a message in a BEA TUXEDO system reliable queue, then TA_QCTL_PRIORITY must be in a valid range.
Action
Correct the error and re-issue the subscription.
See Also
tpsubscribe(3c), tpenqueue(3c), EVENT_MIB(5)
4153
ERROR: No such subscription exists
Description
An attempt was made to do a GET operation on one of the EVENT_MIB classes, and no records match the specified criteria.
Action
Correct the error and re-issue the subscription.
See Also
EVENT_MIB(5)
4154
ERROR: Failed to get generic request parameters
Description
The event server couldn't translate the user-supplied FML32 buffer into a view representation. This can occur either due to view description files being inadvertently deleted or due to internal system error.
Action
If no view description files have been deleted from the TUXDIR tree, contact your BEA TUXEDO system Technical Support.
See Also
EVENT_MIB(5)
4155
ERROR: Invalid class specified
Description
The event server received a request for subscribe/unsubscribe directly without either calling tpsubscribe/tpunsubscribe or making a MIB request to .TMIB service.
Action
You can subscribe/unsubscribe by using EVENT API or EVENT_MIB. Correct the error and re-issue the request.
See Also
EVENT_MIB(5)
4156
ERROR: Memory allocation failure
Description
Memory allocation failed for an FML32 buffer.
Action
Make sure that 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.
4157
ERROR: Invalid operation (operation) specified for /Admin request
Description
The event server received a request for subscribe/unsubscribe directly without either calling tpsubscribe/tpunsubscribe or making a MIB request to .TMIB service.
Action
You can subscribe/unsubscribe by using EVENT API or EVENT_MIB. Correct the error and re-issue the request.
See Also
tpsubscribe(3c), TM_MIB(5), EVENT_MIB(5)
4160
ERROR: Could not initialize threaded BRIDGE
Description
An attempt to initialize the networking software from the BRIDGE failed.
Action
Make sure that the correct networking software is installed on the system and that the network is accessible.
4162
ERROR: Invalid -o option
Description
tmunloadcf was run with an undocumented administrative option.
Action
Re-run the command without the -o option, or contact your BEA TUXEDO system Technical Support if you think that you need this option.
See Also
tmunloadcf(1)
4163
ERROR: Can't open output file filename: system_error
Description
tmunloadcf failed to open the name filename. The associated system_error is printed.
Action
Check that there is space in the file system associated with filename and re-run the command.
See Also
tmunloadcf(1)
4171
ERROR: Current work directory path name is too long
Description
The full pathname for the current directory in which tmunloadcf is being run is longer than 256 characters.
Action
Change the directory structure such that the pathname is less than 256 characters, and re-run the command.
4172
ERROR: Absolute path name of the output file is too long
Description
The full pathname for a file generated by tmunloadcf is longer than 256 characters.
Action
Change the directory structure such that the pathname is less than 256 characters, and re-run the command.
4174
ERROR: Could not initialize network
Description
An attempt to initialize the networking software while trying to access the tagent failed. This could be in any of the administrative processes including the BBL, DBBL, or BRIDGE (as indicated by the userlog message).
Action
Make sure that the correct networking software is installed on the system and that the network is accessible.
4175
ERROR: Could not initialize network
Description
An attempt to initialize the networking software from tlisten (the BEA TUXEDO system network listener) failed.
Action
Make sure that the correct networking software is installed on the system and that the network is accessible.
4178
ERROR: can't fdopen yyout, system_error
Description
On NetWare, the error output of tmloadcf could not be redirected to the standard output.
Action
Ensure that there are enough file descriptors available. Try re-running the command, or contact your BEA TUXEDO system Technical Support.
4179
ERROR: can't fdopen output file, system_error
Description
On NetWare, the error output of tmunloadcf could not be redirected to the standard output.
Action
Ensure that there are enough file descriptors available. Try re-running the command, or contact your BEA TUXEDO system Technical Support.
4180
ERROR: can't execute command
Description
The buildserver command was unable to execute the system compiler. The command that buildserver attempted to execute is given as part of the error message.
Action
Verify that the compiler has been installed on the machine, that it is executable, and that the directory containing the compiler is included in the PATH environment variable. If the name of the compiler is other than the standard cc, set and export the CC shell variable to the proper name of the compiler. Otherwise, verify that the CC shell variable is not set to some extraneous value.
See Also
buildserver(1)
4181
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc failed while executing buildserver.
Action
Ensure that 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.
4182
ERROR: Cannot boot old release site (lmid) in non-interoperability mode
Description
An attempt was made to boot a System 5 version of BEA TUXEDO system with a System 6 version of BEA TUXEDO system with the TUXINTEROP environment variable set to "N". This is not allowed. The system running the older release is printed.
Action
Shut down the application and unset the TUXINTEROP environment variable before re-booting, or upgrade the system in question. Contact your BEA TUXEDO system Technical Support.
4183
ERROR: Older release sites cannot join application in non-interoperability mode
Description
An attempt was made to boot a System 5 version of BEA TUXEDO system with a System 6 version of BEA TUXEDO system with the TUXINTEROP environment variable set to "N". This is not allowed. The system running the older release is printed.
Action
Shut down the application and unset the TUXINTEROP environment variable before re-booting, or upgrade the system in question. Contact your BEA TUXEDO system Technical Support.
4184
ERROR: Sites using Oracle Tuxedo 10gR3 or earlier cannot join an application when services contain long service names
Description
An attempt was made to boot an older Oracle Tuxedo version when one or more services have already been advertised in the current domain. This is not permitted. If one or more Oracle TUXEDO releases earlier than 11gR1 coexists in the current domain, the service name length must be less than 15 characters.
Action
Shut down servers advertising long service names or un-advertise services with long names via tmadmin.
4186
ERROR: Cannot set TA_SUSPTIME without suspending connection
Description
An /AdminAPI call accessing the T_BRIDGE class of the TM_MIB(5) with a specified value for the TA_SUSPTIME attribute was disallowed because it accompanied a TA_STATE change to a TA_STATE value other than SUSPENDED.
Action
Omit the TA_SUSPTIME value from the request if you are changing TA_STATE to either ACTIVE or INACTIVE. Otherwise, change the TA_STATE value on the original request to SUSPENDED.
See Also
MIB(5), TM_MIB(5)
4187
ERROR: Cannot set TA_SUSPTIME for unsuspended connection
Description
An /AdminAPI call accessing the T_BRIDGE class of the TM_MIB(5) with a specified value for the TA_SUSPTIME attribute was disallowed because it referenced an occurrence not already in the SUSPENDED state.
Action
Omit the TA_SUSPTIME value from the request or suspend the connection before making the request.
See Also
MIB(5), TM_MIB(5)
4188
WARN: server built without the -s option cannot advertise services.
Description
The buildserver command was run without specifying the -s command line option to indicate service entry points and or services to be advertised for the server. Without at least specifying the service entry points (C functions or COBOL programs), the server will not be able to advertise any services at boot-time or run-time.
Action
Re-run the command specifying services with the -s option.
See Also
buildserver (1)
 |
 |
 |