4306
ERROR: Could not send saved messages to site
Description
While the BRIDGE or BSBRIDGE is negotiating the link level encryption parameters, messages to the remote BRIDGE are saved. An error occurred while sending these saved messages to the remote BRIDGE after the negotiation was complete.
BRIDGE
BSBRIDGE
Action
Check the network on the machine with the affected BRIDGE or BSBRIDGE.
4307
ERROR: Cannot ASCII encode password (errno = val)
An error occurred while converting a non-ASCII tlisten password file into ASCII for authentication purposes.
tlisten
Contact your BEA TUXEDO system Technical Support.
4308
ERROR: Invalid encryption negotiation flags
A process speaking to a tlisten sent an invalid link level encryption negotiation opcode.
The process on the remote site may be attempting to circumvent link level encryption. Monitor your network for malicious use. Contact your BEA TUXEDO system Technical Support.
4309
WARN: Invalid protocol response from site
site
The tlisten on the remote site sent an invalid link level encryption negotiation opcode.
The tlisten on the remote site may be attempting to circumvent link level encryption. Monitor your network for malicious use. Contact your BEA TUXEDO system Technical Support.
4310
ERROR: Could not get first Diffie-Hellman packet
The process attempting to contact the tlisten could not generate the first encryption packet.
4311
ERROR: NADDR parameter is not a correct internet address.
The NADDR parameter in the NETWORK section of the UBBCONFIG file was not in the correct format.
NADDR
NETWORK
UBBCONFIG
Any address in the NADDR field that starts with // must be a valid internet address. The following formats are recognized by the system: //host.name:port_number and //#.#.#.#:port_number. Other formats may be recognized. Change the NADDR field to comply with the known formats. If you believe that your address is in the proper format, contact your BEA TUXEDO system Technical Support.
//host.name:port_number
//#.#.#.#:port_number
4312
ERROR: NLSADDR parameter is not a correct internet address.
The NLSADDR parameter in the NETWORK section of the UBBCONFIG file was not in the correct format.
NLSADDR
Any address in the NLSADDR field which starts with // must be a valid internet address. The following formats are recognized by the system: //host.name:port_number and //#.#.#.#:port_number. Other formats may be recognized. Change the NLSADDR field to comply with the known formats. If you believe that your address is in the proper format, contact your BEA TUXEDO system Technical Support.
4313
ERROR: Remote node can't interpret internet address
A BEA TUXEDO system release greater than or equal to Release 6.3 attempted to send an internet address to an older release.
Releases of the BEA TUXEDO system prior to the Release 6.3 release do not understand the internet address naming schemes. When interoperating with an older release, the older method of specifying addresses must be used. Replace internet addresses with the older "0x" style of address.
0x
4314
ERROR: An error occurred when val attempted to access the service manager
While attempting to get the NT service name, an error occurred while opening the service manager.
4315
ERROR: An error occurred when val attempted to allocate memory
While attempting to get the NT service name the task ran out of memory.
Check the memory on the system where the command was run. If it seems that there should be enough memory for this operation, contact your BEA TUXEDO system Technical Support.
4316
ERROR: An error occurred when val attempted to set the service status
While attempting to set the NT service status an error occurred.
4317
ERROR: An error occurred when val attempted to register the service
While attempting to register the NT service an error occurred.
4318
4319
ERROR: An error occurred when val attempted to access the registry
While attempting to access the NT registry an error occurred.
4320
4321
ERROR: tlisten invalid internet network address
The address given to tlisten via the -l option was not in a valid internet address format.
-l
Any address given to the -l option which starts with // must be a valid internet address. The following formats are recognized by the system: //host.name:port_number and //#.#.#.#:port_number. Other formats may be recognized. Change the -l option to comply with the known formats. If you believe that your address is in the proper format, contact your BEA TUXEDO system Technical Support.
4322
ERROR: An error occurred when val attempted to start the service
While attempting to start the specified NT service an error occurred.
4323
INFO: Listener Process Started
The tlisten process has started properly
No action necessary.
4324
ERROR: can't create buffer - tpalloc() failed - val
A memory allocation failure occurred in tmconfig
tmconfig
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.
4325
ERROR: tpcall() failed, val
While tmconfig was processing a request, tpcall failed.
tpcall
Check the error code that tpcall returned. Check the userlog to see if any more information is available. Contact your BEA TUXEDO system Technical Support.
4328
ERROR: Memory allocation failure
While tlisten was allocating memory for the network address it ran out of memory.
4329
4330
ERROR: Illegal character in the address val
An illegal tlisten network address was specified.
Specify the tlisten network address with the -l option.
4331
ERROR: can't execute val
The AS400 could not execute the given command.
Check the command syntax to be sure it is proper. If it is proper and the executable referenced in the command line is currently executable, contact your BEA TUXEDO system Technical Support.
4332
4333
Memory allocation failed while building a server.
4334
The AS400 ran out of memory in the tmloadcf process.
tmloadcf
4335
4336
ERROR: Could not get application parameters
tmconfig could not find the TUXCONFIG file or could not read the TUXCONFIG file.
TUXCONFIG
Ensure that the TUXCONFIG environment variable points to the appropriate configuration file. If the configuration file does not exist, it can be created from the UBBCONFIG file using tmloadcf. If it does exist, the file may be corrupted, or may have been a file generated by an older release of BEA TUXEDO system. Shut down the system, remove the file, and recreate it with tmloadcf. If the trouble persists, contact your BEA TUXEDO system Technical Support.
4337
ERROR: TUXCONFIG is not set
The TUXCONFIG environment variable must be set for tmconfig to work properly
Set the TUXCONFIG environment variable to point to the TUXCONFIG file of the application which you would like to configure.
4338
The TUXCONFIG environment variable must be set for ud or ud32 to work properly
ud
ud32
Set the TUXCONFIG environment variable to point to the TUXCONFIG file of the application you would like to use ud or ud32 on.
4339
ud or ud32 could not find the TUXCONFIG file or could not read the TUXCONFIG file.
4340
ERROR: Could not establish network address val - check device and address
The BRIDGE process could not establish its listening address for incoming network connections.
Check the NADDR and BRIDGE parameters for this machine in the NETWORK section of the configuration file.
4341
ERROR: Missing port number in the address val
The BRIDGE process could not establish a connection to the remote machine and address. There may be networking problems, or the remote machine may have crashed.
Check network connectivity between the machines.
Check that the BRIDGE is running on the remote machine at the given address.
The BRIDGE process will automatically reestablish a connection between the machines on demand, when possible. To prevent thrashing, the link will be suspended for five minutes if an automatic reconnect attempt fails. No further automatic reconnection attempts are made during this interval. If desired, use tmadmin(1)'s reconnect command to initiate a reconnection attempt manually. Manual attempts are allowed during the five-minute suspension interval.
tmadmin
reconnect
4342
ERROR: Unable to reconnect to machine, address
The BRIDGE process could not reconnect to machine during recovery from a networking problem.
Check that the BEA TUXEDO system is running on machine.
The BRIDGE processes will automatically reestablish a connection between the machines on demand, when possible. To prevent thrashing, the link will be suspended for five minutes if an automatic reconnect attempt fails. No further automatic reconnection attempts are made during this interval.
If desired, use tmadmin(1)'s reconnect command to initiate a reconnection attempt manually. Manual attempts are allowed during the five-minute suspension interval.
See Also
Messages 1375 and 1374 and tmadmin (1)'s reconnect command
4343
ERROR: Could not establish listening endpoint address
tlisten could not establish an endpoint for listening at the given address.
Ensure that the listening endpoint is free for use by the tlisten process. If it is not, choose a different endpoint. On some operating systems, there is a long delay while the listening port is cleared. Wait 5 minutes, and try the command again.
4344
ERROR: Can't put FLDTBLDIR32 into environment
An error occurred while tmconfig32 was setting the FLDTBLDIR32 variable.
tmconfig32
FLDTBLDIR32
4345
ERROR: Can't put FIELDTBLS32 into environment
4346
ERROR: Cannot run command on /etc/passwd
command (tpaddusr, tpmodusr, or tpdelusr) was run with a filename of /etc/passwd. These commands may delete important information from /etc/passwd and cannot be used to modify it directly.
tpaddusr
tpmodusr
tpdelusr
/etc/passwd
Modify the /etc/passwd file directly using a text editor or use a different user file.
4347
While checking the status of the sbbl process, the DBBL or BBL ran out of memory.
sbbl
DBBL
BBL
4348
ERROR: An error has occurred in completing the MIB request
The sbbl was not able to finish a MIB request. The DBBL or BBL sent a message to that effect to the requestor.
Check the log for related messages.
4349
4350
INFO: BBL started on machine - Release val
This message indicates that a new machine has been booted and records the internal release number. This information may be useful to BEA TUXEDO system support, if necessary.
4351
INFO: BBL on machine - Release val
This message is printed by the DBBL during the first sanity check after midnight for each booted machine. This information may be useful to BEA TUXEDO system support, if necessary.
4352
WARN: Service name must be <= len characters in length; val will be truncated
While building a server, one of the specified service names is longer than the maximum allowed. The name will be truncated.
No action is required. However, it is recommended that the name be shortened to the maximum allowed, as indicated by the message.
4353
ERROR: Port number can't be bigger than max-port in the address address
The port number portion of address is too large.
Any address which starts with // must be a valid internet address. The following formats are recognized by the system: //host.name:port_number and //#.#.#.#:port_number. Other formats may be recognized. port_number must be less than max-port. Ensure that the port_number portion of address complies with this limit.
4354
ERROR: Can't parse the address address
While attempting to resolve address, an error occurred.
Any address which starts with // must be a valid internet address. The following formats are recognized by the system: //host.name:port_number and //#.#.#.#:port_number. Other formats may be recognized. Make sure that DNS is working properly in your network, and that the host name and port number portion of address can be located by your server.
4355
ERROR: Unable to determine license level
An error occurred while retrieving the current license attributes.
4356
ERROR: No license for /Events
You do not have a license to use /Events.
Purchase a license for /Events. If you believe that you own and have installed the license for /Events, contact your BEA TUXEDO system Technical Support.
4357
4358
4359
4360
ERROR: No license for Transactions
You do not have a license to use Transactions.
Purchase a license for Transactions. If you believe that you own and have installed the license for Transactions, contact your BEA TUXEDO system Technical Support.
4363
ERROR: Unable to allocate message buffer
Message allocation failed for getting a message buffer by sbbl when sending message to DBBL to update sbbl sanity table.
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.
4364
ERROR: Cannot get DBBL record from BB
sbbl cannot find DBBL entry in the Bulletin Board. The Bulletin Board may be corrupted.
4365
ERROR: cannot send msg to DBBL
sbbl cannot send message to DBBL to update sbbl sanity table.
4366
DBBL took actions to send an error message to the blocking MIB operation requestor when DBBL found an expired entry in the sbbl sanity table. The possible cause could be sbbl cannot successfully register with Bulletin Board.
Reduce the number of blocking MIB operation at the same time. If the problem still occurs contact your BEA TUXEDO system Technical Support.
4367
sbbl took actions to send an error message to the blocking MIB operation requestor when sbbl cannot successfully register with Bulletin Board as a regular client process.
Reduce the number of blocking MIBS operation at the same time. If the problem still occurs contact your BEA TUXEDO system Technical Support.
4368
ERROR: Could not allocate internal TPINIT typed buffer
Memory allocation failed for getting a TPINIT buffer by sbbl when registering with Bulletin Board as a regular client.
TPINIT
4369
WARN: DBBLWAIT * 2 is greater than BLOCKTIME. DBBLWAIT = val, BLOCKTIME = val
The value used for DBBLWAIT (* 2) is greater than the value in BLOCKTIME.
DBBLWAIT
BLOCKTIME
Check the values used for both variables and adjust accordingly.
4370
4371
ERROR: Can't resolve host name in address address
While attempting to resolve the host name portion of address, an error occurred.
Any address which starts with // must be a valid internet address. The following formats are recognized by the system: //host.name:port_number and //#.#.#.#:port_number. Other formats may be recognized. Make sure that DNS is working properly in your network, and that the host name portion of address can be located by your DNS server.
4372
ERROR: Unknown address type: address
The given address does not correspond to a type known by the system.
The BEA TUXEDO system understands several types of address format. Addresses which start with // must be internet addresses. Addresses which start with 0x are hexadecimal representations of the address. Other formats may or may not be understood by the BEA TUXEDO system.
4373
ERROR: Can't resolve port number in address address
While attempting to resolve the port number portion of address, an error occurred.
Any address which starts with // must be a valid internet address. The following formats are recognized by the system: //host.name:port_number and //#.#.#.#:port_number. Other formats may be recognized. Make sure that DNS is working properly in your network, and that the port number portion of address can be located by your server.
4374
ERROR: Can't convert the address address to binary format
An error occurred while converting address to an internal binary representation.
4393
ERROR: tprealloc for TPINIT failed - reason-code
ud or ud32 could not resize the TPINIT buffer
ud or ud32 may attempt to resize the TPINIT buffer when there is more user authentication data than expected. reason-code may provide insight into the cause of this failure. Make sure enough memory exists on the system running ud or ud32. If it appears that there should be enough memory to ud or ud32, and this error happens consistently, contact the BEA TUXEDO system Technical Support.
4376
WARN: Incompatible license information (val)
While booting a new node, the licensed features did not match those features licensed on the master node. This could potentially cause inconsistent results if the master node is migrated to this site or if certain capabilities are accessed from that site.
Ensure that the license file in $TUXDIR/udataobj on each machine in the application has the same features licensed to insure consistent behavior.
$TUXDIR/udataobj
4377
ERROR: Permissions violation on SET request
A permissions violation has occurred while attempting to process an /AdminAPI SET request on the indicated class object. The attribute TA_BADFLD is set on the reply to indicate the field that is in violation of permissions.
SET
TA_BADFLD
The administrator can tune permissions for any attribute user combination to the maximum supported by the system. However, write access is not supported on all attributes in all class object states. Therefore, the update may need to be delayed until the class object is in a different state.
4378
ERROR: temp file creation failed
Creation of a temporary file in tmconfig using crtsrcpf on the AS/400 failed.
crtsrcpf
Ensure that there is sufficient space in /qsys.lib/qtemp.lib and re-run the operation.
/qsys.lib/qtemp.lib
4379
4381
ERROR: You do not have a valid TUXEDO SDK license
buildclient(1) was running without having a valid BEA TUXEDO system SDK license (e.g., only an RTK license was installed).
buildclient
Buy a BEA TUXEDO system SDK license.
4382
buildserver(1) was running without having a valid BEA TUXEDO system SDK license (e.g., only an RTK license was installed).
buildserver
4383
An attempt to dynamically allocate memory from the operating system using malloc failed while parsing the UBBCONFIG file.
malloc
4384
4385
WARN: value val does not fit in character
While parsing the UBBCONFIG file, a hex escape sequence was found with a value larger than will fit in a single character (i.e., greater than 0xff).
0xff
Correct the value and re-run tmloadcf(1).
4386
WARN: dubious escape val
While parsing the UBBCONFIG file, a backslash escape preceding a character that is not a valid escape sequence (t, n, f, b, r, 0, backslash, n, x, or X).
4387
While parsing the UBBCONFIG file, an octal escape sequence was found with a value larger than will fit in a single character (i.e., greater than 0xff).
4388
4389
ERROR: string: -F option fails to reopen stderr
While running tmboot or tmshutdown on the AS/400, the program could not re-direct the standard error output into a file.
tmboot
tmshutdown
Re-run the operation. Ensure that there is sufficient file space.
4390
ERROR: Cannot open file file for reading
The event server couldn't open file file for reading the subscription database.
The event server reads a new copy of the subscription database from the temporary file file. This message indicates that the server couldn't open the temporary file for reading. Check the file system parameters and take corrective action.
4391
ERROR: can't open input file file
An error occurred attempting to open the input file specified as -ifile on the command line for ud or ud32.
-i
Make sure the input file file exists and is readable.
4392
ERROR: can't open output file file
An error occurred attempting to open the output file file for write as specified by -ofile on the command line for ud or ud32.
-o
Make sure file system limit has not been exceeded and user has write permissions for the directory in which the output file is to be created.