WEBGUI Messages 16400-16499

16422

ERROR: BEA Administration Console event tool got unknown message: val

Description

In the wgated server, the message got from Java Applet Event tool was unknown.

Action

There may have been corruption of the data transmitted from the Java Applet to the wgated process.

16423

ERROR: BEA Administration Console event tool could not open new snapshot file val

Description

New creation of the snapshot file failed.

Action

Check to see if the path to the snapshot file is valid and available. Check for write permissions in the directory where the snapshot file is being created.

16424

ERROR: BEA Administration Console event tool could not reopen snapshot file val

Description

Re-opening of the snapshot file failed.

Action

Check to see if the path to the snapshot file is valid and available. Check for write permissions in the directory where the snapshot file is being created.

16425

ERROR: No license for BEA Administration Console

Description

License to run the BEA Administration Console is not available.

Action

Check the BEA license file. Contact BEA Customer Support for assistance with the license.

16429

INFO: BEA Administration Console Web Mini-Server startup

Description

The tuxwsvr web server is starting. This web server is used by the BEA Administration Console.

Action

No action is required by this message.

16450

ERROR: Incorrect data with SESSIONBEGIN message from the client

Description

The client (Administration Console) sends a SESSIONBEGIN message to the wgated server to establish communication. This error is displayed because the message is not in the proper SESSIONBEGIN message format.

Action

There is a possibility that the data sent by the Administration Console to the wgated server was corrupted or was tampered with. Please try again by exiting the browser and logging in to the Administration Console. If the problem persists, contact BEA Customer Support for assistance.

16451

ERROR: val value mismatch in SESSIONBEGIN message from the client

Description

The Administration Console sent incorrect value for the specified field in the SESSIONBEGIN message.

Action

Check the webgui.ini file for this value. Make sure that the TUXDIR environment variable is set properly. Confirm that the value of TUXDIR is same as the value shown in the browser's URL location field.

16453

ERROR: Send buffer encryption key not available

Description

In the wgated server, the encryption key for the send buffer was not found. The Administration Console and wgated server cannot establish communication at the specified level.

Action

Try reducing the encryption bit strength if it is safe to do so.

16454

ERROR: Receive buffer encryption key not available

Description

In the wgated server, the encryption key for the receive buffer was not found. The Administration Console and wgated server cannot establish communication at the specified level.

Action

Try reducing the encryption bit strength if it is safe to do so.

16455

ERROR: wgated received unknown message: 'val'

Description

The message received while establishing the initial connection was not valid. The connecting client may not be the Administration Console or the data on the network may be corrupted.

Action

Exit from the browser and try to launch the Administration Console again.

16456

ERROR: Incorrect data with SESSIONBEGIN message from the client

Description

The SESSIONBEGIN message is missing mandatory fields.

Action

Check the webgui.ini file for this value. Make sure that the TUXDIR environment variable is set properly. Confirm that the value of TUXDIR is same as the value shown in the browser's URL location field.

16457

ERROR: val value mismatch in SESSIONBEGIN message from the client

Description

Incorrect field value in the SESSIONBEGIN message. Unable to establish the Diffie-Hellman key exchange.

Action

Exit from the browser and try to launch the Administration Console again.

16458

ERROR: Unable to initialize public key subsystem

Description

An error occurred while initializing the public key subsystem. Many things could cause this failure, including a user implementation of a plug-in function returning a failure code.

Action

Ensure the registry is in a valid state with epifregedt. Ensure that the implementation of the plug-in function did not return an error code.

See Also

epifregedt, _ec_sec_map_proof, _ec_sec_pki_init