Skip navigation.

GP Messages 1200-1299

  Previous Next

1200

ERROR: Invalid length passed to _tuxdftcmpexp

Description

An internal error occurred.

Action

Contact BEA TUXEDO system Technical Support.

1201

ERROR: Failed to initialize deflate structure: (error/error_info)

Description

While initializing data structures for compression, an error occurred. One likely cause of the error is a dynamic memory allocation failure. Additional information is printing indicating the exact cause of the problem.

Action

Correct the reason for the failure.

1202

ERROR: Failed to destroy deflate structure: (error/error_info)

Description

While destroying data structures for compression, an error occurred. Additional information is printing indicating the reason for the failure.

Action

Correct the reason for the failure.

1203

ERROR: Failed to initialize inflate structure: (error/error_info)

Description

While initializing data structures for compression, an error occurred. One likely cause of the error is a dynamic memory allocation failure. Additional information is printing indicating the exact cause of the problem.

Action

Correct the reason for the failure.

1204

ERROR: Failed to destroy inflate structure: (error/error_info)

Description

While destroying data structures for compression, an error occurred. Additional information is printing indicating the reason for the failure.

Action

Correct the reason for the failure.

1205

ERROR: Failed to decompress message: (error/error_info)

Description

While decompressing a message, an error occurred. Additional information is printing indicating the reason for the failure.

Action

Correct the reason for the failure.

1206

ERROR: Invalid opcode val passed to _tuxdftcmpexp

Description

An internal error occurred.

Action

Contact BEA TUXEDO system Technical Support.

1207

ERROR: Memory allocation error

Description

An attempt dynamically to allocate memory from the operating system failed while trying processing a network 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.

1208

ERROR: Memory allocation error

Description

An attempt dynamically to allocate memory from the operating system failed while trying processing a network 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.

1209

ERROR: Memory allocation error: error_info

Description

An attempt dynamically to allocate memory from the operating system failed while trying processing a network 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.

1210

ERROR: Memory allocation error: error_info

Description

An attempt dynamically to allocate memory from the operating system failed while trying processing a network 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.

1211

ERROR: Memory allocation error: error_info

Description

An attempt dynamically to allocate memory from the operating system failed while trying processing a network 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.

1212

ERROR: Could not expand multiple messages

Description

While processing network messages, an internal error occurred.

Action

Contact your BEA TUXEDO system Technical Support.

1214

ERROR: Memory allocation error: error_info

Description

An attempt dynamically to allocate memory from the operating system failed while trying processing a network 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.

1215

ERROR: Cannot compile event expression expr, error=errstr

Description

An invalid event expression was detected in a subscription record.

Action

The Event Server failed to compile the event expression expr. The error string returned from _gp_recomp() is printed in the userlog message.

See Also

tpsubscribe(3c), _gp_recomp(3c)

1216

WARN: Memory allocation failure

Description

An attempt dynamically to allocate memory from the operating system failed while creating file internal storage required to compress or decompress a message. This message is only warning when it is related to a compression request since the message may simply be sent uncompressed. If this situation occurs during decompression, then an error message will follow this one in the userlog file indicating that decompression has 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.

Additionally, if a large number of files are specified to be loaded into the file cache, then this may contribute to any memory problems experienced in the use of load_files. Reduction of the file list may help alleviate the problem.

As a last resort, you may need to turn off data compression. The use of data compression trades increased use of CPU and memory for decreased use of the network and/or message queues. If memory limitations are being reached, then compression may need to be disabled.

1217

WARN: Memory allocation failure

Description

An attempt dynamically to allocate memory from the operating system failed while creating file internal storage required to compress or decompress a message. This message is only warning when it is related to a compression request since the message may simply be sent uncompressed. If this situation occurs during decompression, then an error message will follow this one in the userlog file indicating that decompression has 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.

Additionally, if a large number of files are specified to be loaded into the file cache, then this may contribute to any memory problems experienced in the use of load_files. Reduction of the file list may help alleviate the problem.

As a last resort, you may need to turn off data compression. The use of data compression trades increased use of CPU and memory for decreased use of the network and/or message queues. If memory limitations are being reached, then compression may need to be disabled.

See Also

BEA TUXEDO Administrator's Guide

1218

ERROR: Memory allocation failure

Description

An attempt dynamically to allocate memory from the operating system failed while trying to read an environment file. Look for subsequent messages indicating the problem file.

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.

1219

ERROR: Unable to open TUXCONFIG file to Resources section

Description

While attempting to read the application password, the WSL or WSH had a problem opening the RESOURCES section of the TUXCONFIG file.

Action

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 the BEA TUXEDO system. Shut down the system, remove the file, and recreate it with tmloadcf.

1220

ERROR: Unable to open Resources section of TUXCONFIG file

Description

While attempting to read the application password, the WSL or WSH had a problem reading the RESOURCES section of the TUXCONFIG file.

Action

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 TUXEDO System. Shut down the system, remove the file, and recreate it with tmloadcf.

1221

ERROR: Possibly corrupted key in database

Description

An invalid password was detected while the WSH or WSL was reading the TUXCONFIG file.

Action

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 the BEA TUXEDO system. Shut down the system, remove the file, and recreate it with tmloadcf.

1222

ERROR: Error while decrypting password

Description

An invalid password was detected while the WSH or WSL was reading the TUXCONFIG file.

Action

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 the BEA TUXEDO system. Shut down the system, remove the file, and recreate it with tmloadcf.

1223

ERROR: Invalid password in TUXCONFIG file

Description

An invalid password was detected while the WSH or WSL was reading the TUXCONFIG file.

Action

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 the BEA TUXEDO system. Shut down the system, remove the file, and recreate it with tmloadcf.

1224

ERROR: Invalid parameter

Description

An error occurred while encrypting the application password

Action

Contact your BEA TUXEDO system Technical Support.

1225

ERROR: Memory allocation failure

Description

While creating an encryption schedule the system ran out of memory.

Action

Check the memory on the system where the process was running.

1226

ERROR: Invalid parameter

Description

An error occurred while encrypting the application password

Action

Contact your BEA TUXEDO system Technical Support.

1227

ERROR: Invalid parameter

Description

An error occurred while manipulating the application password

Action

Contact your BEA TUXEDO system Technical Support.

1228

ERROR: Memory allocation failure

Description

While creating a key the system ran out of memory.

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.

1229

ERROR: Invalid parameter

Description

An error occurred while getting a session key.

Action

Contact your BEA TUXEDO system Technical Support.

1230

ERROR: Memory allocation failure

Description

While creating a session key the system ran out of memory.

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.

1231

ERROR: Reply queue full

Description

ud or ud32 ran out of space for concurrent requests to the system.

Action

At most fifty request can be made simultaneously to the system from ud or ud32. Limit the number of requests made by ud or ud32 to 50.

1232

ERROR: Memory allocation failure

Description

malloc failed in the encryption subsystem

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.

1233

ERROR: Could not create random algorithm object

Description

Could not create the object used for generating random numbers

Action

Check the memory of the system.

1234

ERROR: Could not use MD5 random algorithm

Description

The encryption subsystem could not find the MD5 algorithm

Action

Contact your BEA TUXEDO system Technical Support.

1235

ERROR: Could not initialize random algorithm

Description

A failure occurred in the encryption subsystem

Action

Contact your BEA TUXEDO system Technical Support.

1236

ERROR: Could not get random seed

Description

A failure occurred in the encryption subsystem

Action

Contact your BEA TUXEDO system Technical Support.

1237

ERROR: Could not update random algorithm

Description

A failure occurred in the encryption subsystem

Action

Contact your BEA TUXEDO system Technical Support.

1238

ERROR: Memory allocation error

Description

A memory failure occurred in the encryption subsystem

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.

1239

ERROR: New encryption buffer, but offset(offset) is not zero

Description

A routine in the encryption subsystem was called in an improper context

Action

Contact your BEA TUXEDO system Technical Support.

1241

ERROR: An error occurred in the encryption subsystem code(code)

Description

An error occurred in the encryption subsystem

Action

Contact your BEA TUXEDO system Technical Support with the code number ready.

1242

ERROR: New encryption buffer, but offset(offset) is not zero

Description

A routine in the encryption subsystem was called in an improper context

Action

Contact your BEA TUXEDO system Technical Support.

1244

ERROR: Invalid packet from network

Description

An invalid buffer was given to the encryption subsystem

Action

Check the network. If it appears that the network is functioning properly, then contact your BEA TUXEDO system Technical Support.

1245

ERROR: Memory allocation error

Description

An memory error occurred in the encryption subsystem

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.

1246

ERROR: Could not generate negative encryption packet

Description

An error occurred during encryption negotiation

Action

Contact your BEA TUXEDO system Technical Support.

1247

ERROR: An error occurred in the encryption subsystem code (code)

Description

An error occurred in the encryption subsystem

Action

Contact your BEA TUXEDO system Technical Support with the code number ready.

1248

ERROR: The encryption packet is invalid

Description

An invalid buffer was given to the encryption subsystem

Action

Check the network. If it appears that the network is functioning properly, then contact your BEA TUXEDO system Technical Support.

1249

ERROR: Invalid packet from network (0xnum, num, num)

Description

An invalid buffer was given to the encryption subsystem

Action

Check the network. If it appears that the network is functioning properly, then contact your BEA TUXEDO system Technical Support. Make sure you have the three codes provided in the message.

1251

ERROR: Remote system returns an error (code)

Description

During the encryption negotiation process, the remote site had a fatal error.

Action

Check the diagnostic messages on the remote site.

1252

ERROR: An error occurred in the encryption subsystem code (code)

Description

An error occurred in the encryption subsystem

Action

Contact your BEA TUXEDO system Technical Support with the code number ready.

1253

ERROR: Invalid number of encryption bits

Description

An error occurred in the encryption subsystem

Action

Contact your BEA TUXEDO system Technical Support.

1254

ERROR: An error occurred in the encryption subsystem code (code)

Description

An error occurred in the encryption subsystem

Action

Contact your BEA TUXEDO system Technical Support with the code number ready.

1258

ERROR: internal error

Description

An error occurred in the encryption subsystem

Action

Contact your BEA TUXEDO system Technical Support.

1259

ERROR: Cannot authenticate, encryption is unavailable

Description

While attempting to perform an operation which requires authentication, it was determined that the MD5 algorithm used is not available.

Action

tlisten and the processes which may attempt to contact tlisten must be able to compute the MD5 hash of the password file. If MD5 is not available, the authentication process cannot be completed. You must disable tlisten authentication by removing the files $TUXDIR/udataobj/tlisten.pw and $APPDIR/.adm/tlisten.pw.

1260

ERROR: Encryption failure code at break point break-point

Description

While attempting to perform an operation which requires authentication, their was an error using the MD5 algorithm.

Action

Contact your BEA TUXEDO system Technical Support, with the values of code and break-point.

1261

ERROR: Badly aligned offset(offset) value

Description

An error occurred in the encryption subsystem

Action

Contact your BEA TUXEDO system Technical Support.

1262

ERROR: Bad encryption handle(handle)

Description

An error occurred when getting the first Diffie-Hellman packet.

Action

Contact your BEA TUXEDO system Technical Support, with the value of handle.

1263

ERROR: Encryption handle in unexpected state string

Description

An error occurred in the encryption subsystem

Action

Contact your BEA TUXEDO system Technical Support.

1264

ERROR: Invalid attempt to use 128-bit encryption

Description

A routine in the encryption subsystem was called in an improper context

Action

Contact your BEA TUXEDO system Technical Support.

1265

ERROR: Invalid attempt to use 128-bit encryption

Description

A routine in the encryption subsystem was called in an improper context

Action

Contact your BEA TUXEDO system Technical Support.

1267

ERROR: Invalid attempt to use 128-bit encryption

Description

A routine in the encryption subsystem was called in an improper context

Action

Contact your BEA TUXEDO system Technical Support.

1268

ERROR: Badly aligned offset(offset) value

Description

An error occurred in the encryption subsystem

Action

Contact your BEA TUXEDO system Technical Support.

1269

ERROR: The encryption packet is invalid

Description

An error occurred in the encryption subsystem

Action

Contact your BEA TUXEDO system Technical Support.

1270

ERROR: Bad encryption handle(num)

Description

An error occurred in the encryption subsystem

Action

Contact your BEA TUXEDO system Technical Support.

1271

ERROR: Encryption handle in unexpected state string

Description

An error occurred in the encryption subsystem

Action

Contact your BEA TUXEDO system Technical Support.

1272

ERROR: Invalid attempt to use 128-bit encryption

Description

A routine in the encryption subsystem was called in an improper context

Action

Contact your BEA TUXEDO system Technical Support.

1273

ERROR: Invalid attempt to use 128-bit encryption

Description

A routine in the encryption subsystem was called in an improper context

Action

Contact your BEA TUXEDO system Technical Support.

1275

ERROR: Invalid attempt to use 128-bit encryption

Description

A routine in the encryption subsystem was called in an improper context

Action

Contact your BEA TUXEDO system Technical Support.

1276

ERROR: Bad encryption handle(num)

Description

An error occurred in the encryption subsystem

Action

Contact your BEA TUXEDO system Technical Support.

1277

ERROR: Encryption handle in unexpected state string

Description

An error occurred in the encryption subsystem

Action

Contact your BEA TUXEDO system Technical Support.

1278

ERROR: Invalid negotiation parameter from remote site

Description

An error occurred in the encryption subsystem

Action

Monitor your network for malicious use. Contact your BEA TUXEDO system Technical Support.

1283

ERROR: Service service not available in group gname

Description

The FML or FML32 default routing function _froute was called, found the group to route the request to, but found that the service service is not offered in that group.

Action

Make sure that the routing criteria specified for the FML or FML32 buffer type is correct. Offer service in group group. Make sure that service is not suspended.

1284

ERROR: Service service not available in group gname

Description

The VIEW or VIEW32 default routing function _vroute was called, found the group to route the request to, but found that the service service is not offered in that group.

Action

Make sure that the routing criteria specified for the VIEW or VIEW32 buffer type is correct. Offer service in group group. Make sure that service is not suspended.

1285

ERROR: Can't resolve host name in address address

Description

While attempting to resolve the host name portion of address, an error occurred.

Action

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.

1286

ERROR: Can't resolve port number in address address

Description

While attempting to resolve the port number portion of address, an error occurred.

Action

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.

1287

ERROR: Can't parse the address address

Description

While attempting to resolve address, an error occurred.

Action

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.

1288

ERROR: Invalid parameter from remote site

Description

An irregularity was detected in the encryption protocol

Action

Monitor your network for malicious use. Contact your BEA TUXEDO system Technical Support.

1289

ERROR: Invalid parameter from remote site

Description

An irregularity was detected in the encryption protocol

Action

Monitor your network for malicious use. Contact your BEA TUXEDO system Technical Support.

1290

ERROR: Invalid parameter from remote site

Description

An irregularity was detected in the encryption protocol

Action

Monitor your network for malicious use. Contact your Tuxedo System Technical Support.

1291

ERROR: Invalid parameter from remote site

Description

An irregularity was detected in the encryption protocol

Action

Monitor your network for malicious use. Contact your BEA TUXEDO system Technical Support.

1292

ERROR: Unknown address type: address

Description

The given address does not correspond to a type known by the system.

Action

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.

1293

ERROR: Can't convert the address address to binary format

Description

An error occurred while converting address to an internal binary representation.

Action

Contact your BEA TUXEDO system Technical Support.

1294

ERROR: Illegal character in the address address

Description

The port number portion of address had an illegal character.

Action

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 may also be a symbolic name, but must only have digits or alphanumeric letters. Change the port_number portion of address to comply with these formats.

1295

ERROR: Missing port number in the address address

Description

The port number portion of address is missing.

Action

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 may not be of zero length. Add the port_number portion of address to comply with this formats.

1296

ERROR: Port number cant be bigger than max-port in the address address

Description

The port number portion of address is too large.

Action

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.

1297

ERROR: Illegal character in the address address

Description

The port number portion of address had an illegal character.

Action

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 may also be a symbolic name, but must only have digits or alphanumeric letters. Change the port_number portion of address to comply with these formats.

1298

ERROR: Missing port number in the address address

Description

The port number portion of address is missing.

Action

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 may not be of zero length. Add the port_number portion of address to comply with this formats.

1299

ERROR: Port number cant be bigger than max-port in the address address

Description

The port number portion of address is too large.

Action

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.

 

Skip footer navigation  Back to Top Previous Next