![]() |
![]() |
|
|
4800 |
WARN: Failure changing job attributes. Using default attributes | |
|
Description |
The job attributes for the BRIDGE could not be set according to the Job Description in the AS400_JD file. The default job attributes will be used. |
Action |
Check the job log for the BRIDGE to determine the cause of the failure. | |
4801 |
WARN: DBBL should not be receiving notifications | |
|
Description |
The DBBL received a notification that was intented for the BBL. |
Action |
Please contact your BEA Customer Support. | |
4802 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system
using |
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. | |
4803 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system
using |
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. | |
4804 |
ERROR: Failed retrieving queue entries from BB | |
|
Description |
An error was returned from an attempt in retrieving queue entries from the BB. |
Action |
Please contact your BEA Customer Support. | |
4805 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system
using |
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. | |
4806 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system
using |
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. | |
4807 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system
using |
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. | |
4808 |
ERROR: Error creating message | |
|
Description |
An error was returned from an attempt to create a message buffer. |
Action |
Please contact your BEA Customer Support. | |
4809 |
ERROR: Error processing message | |
|
Description |
An error was return from an attempt to process a message buffer. |
Action |
Please contact your BEA Customer Support. | |
4810 |
ERROR: Error creating message | |
|
Description |
An error was returned from an attempt to create a message buffer. |
Action |
Please contact your BEA Customer Support. | |
4811 |
ERROR: Unable to retrieve server entries from BB | |
|
Description |
An error was returned from an attempt in retrieving server entries from the BB. |
Action |
Please contact your BEA Customer Support. | |
4812 |
ERROR: Unable to retrieve server entries from BB | |
|
Description |
An error was returned from an attempt in retrieving server entries from the BB. |
Action |
Please contact your BEA Customer Support. | |
4813 |
ERROR: Error sending message | |
|
Description |
An error was returned from an attempt in sending a system notification message. |
Action |
Please contact your BEA Customer Support. | |
4814 |
ERROR: Error sending message | |
|
Description |
An error was returned from an attempt in sending a system notification message. |
Action |
Please contact your BEA Customer Support. | |
4815 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system
using |
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. | |
4816 |
ERROR: Identifier for SEC_PRINCIPAL_LOCATION must be <= size characters in length | |
|
Description |
The SEC_PRINCIPAL_LOCATION field in the |
Action |
Ensure that the field is less than size characters. | |
See Also |
| |
4817 |
ERROR: Identifier for SEC_PRINCIPAL_PASSVAR must be <= size characters in length | |
|
Description |
The SEC_PRINCIPAL_PASSVAR field in the |
Action |
Ensure that the field is less than size characters. | |
See Also |
| |
4818 |
ERROR: Unable to retreive principal password in *RESOURCES section | |
|
Description |
There was an error retrieving the password for the SEC_PRINCIPAL_NAME
principal defined in the |
Action |
Please contact your BEA Customer Support. | |
See Also |
| |
4820 |
ERROR: Can not get password for principal | |
|
Description |
An error occurred while attempting to retrieve the password of principal from an environment variable or from a terminal. |
Action |
Please contact your BEA Customer Support. | |
See Also |
| |
4822 |
ERROR: Can not get password for val | |
|
Description |
An error occurred while attempting to re-retrieve the password of principal from an environment variable or from a terminal. |
Action |
Please contact your BEA Customer Support. | |
See Also |
| |
4823 |
WARN: Passwords do not match. Try again. | |
|
Description |
The two passwords typed at the terminal do not match. |
Action |
Be careful while typing passwords. | |
See Also |
| |
4824 |
ERROR: Too many failures to obtain password for principal. | |
|
Description |
|
Action |
Be careful while typing passwords. | |
See Also |
| |
4825 |
ERROR: Cannot create encryption key | |
|
Description |
|
Action |
Ensure the directory ${APPDIR}/.adm is writable by the person running
| |
See Also |
| |
4826 |
ERROR: Unable to read key | |
|
Description |
|
Action |
Ensure the directory ${APPDIR}/.adm is readable by the person running
| |
See Also |
| |
4827 |
ERROR: Cannot create encryption schedule for password of principal | |
|
Description |
A vital encryption operation failed while attempting to encrypt the password for principal. |
Action |
Please contact your BEA Customer Support. | |
See Also |
| |
4828 |
ERROR: Unable to encrypt password of principal | |
|
Description |
A vital encryption operation failed while attempting to encrypt the password for principal. |
Action |
Please contact your BEA Customer Support. | |
See Also |
| |
4830 |
ERROR: Identifier for SEC_PRINCIPAL_LOCATION must be <= size characters in length | |
|
Description |
The SEC_PRINCIPAL_LOCATION field in the |
Action |
Ensure that the field is less than size characters. | |
See Also |
| |
4832 |
ERROR: Identifier for SEC_PRINCIPAL_PASSVAR must be <= size characters in length | |
|
Description |
The SEC_PRINCIPAL_PASSVAR field in the |
Action |
Ensure that the field is less than size characters. | |
See Also |
| |
4834 |
ERROR: Identifier for SEC_PRINCIPAL_LOCATION must be <= size characters in length | |
|
Description |
The SEC_PRINCIPAL_LOCATION field in the |
Action |
Ensure that the field is less than size characters. | |
See Also |
| |
4836 |
ERROR: Identifier for SEC_PRINCIPAL_PASSVAR must be <= size characters in length | |
|
Description |
The SEC_PRINCIPAL_PASSVAR field in the |
Action |
Ensure that the field is less than size characters. | |
See Also |
| |
4837 |
ERROR: Unable to retreive principal password in *MACHINE section | |
|
Description |
There was an error retrieving the password for the SEC_PRINCIPAL_NAME
principal defined in the |
Action |
Please contact your BEA Customer Support. | |
See Also |
| |
4838 |
ERROR: Unable to retreive principal password in *GROUPS section | |
|
Description |
There was an error retrieving the password for the SEC_PRINCIPAL_NAME
principal defined in the |
Action |
Please contact your BEA Customer Support. | |
See Also |
| |
4840 |
ERROR: Identifier for SEC_PRINCIPAL_LOCATION must be <= size characters in length | |
|
Description |
The SEC_PRINCIPAL_LOCATION field in the |
Action |
Ensure that the field is less than size characters. | |
See Also |
| |
4842 |
ERROR: Identifier for SEC_PRINCIPAL_PASSVAR must be <= size characters in length | |
|
Description |
The SEC_PRINCIPAL_PASSVAR field in the |
Action |
Ensure that the field is less than size characters. | |
See Also |
| |
4843 |
ERROR: Unable to retreive principal password in *SERVERS section | |
|
Description |
There was an error retrieving the password for the SEC_PRINCIPAL_NAME
principal defined in the |
Action |
Please contact your BEA Customer Support. | |
See Also |
| |
4844 |
ERROR: Unable to read key | |
|
Description |
|
Action |
Ensure the directory ${APPDIR}/.adm is readable by the person running
| |
See Also |
| |
4845 |
WARN: BBL failed to wake up the blocking process - val. tperrno=val | |
|
Description |
The BBL found a blocking process and tried to format a message to wake up the process. The message generation failed and the blocking process will not be immediately awakened. The BBL will try to wake this process again on its next periodic scan if the process is still blocking. |
Action |
No action required. | |
4846 |
WARN: BBL failed to wake up the blocking process - val. tperrno=val | |
|
Description |
The BBL found a blocking process and tried to send a message to wake up the process. The message send failed and the blocking process will not be immediately awakened. Possible reasons for the failed message send include a message queue that is full or that has been removed. The BBL will try to wake this process again on its next periodic scan if the process is still blocking. |
Action |
No action required. | |
4847 |
ERROR: *ROUTING entry val - only VIEW, FML, X_C_TYPE, X_COMMON, or XML type is allowed in ROUTING section | |
|
Description |
The configuration file |
Action |
Modify the | |
See Also |
| |
4849 |
ERROR: Unable to initialize public key subsystem | |
|
Description |
|
Action |
Ensure the registry is in a consistent state with the
| |
See Also |
| |
4850 |
WARN: Unable to audit policy enforcement event | |
|
Description |
The event broker was unable to audit a security failure. |
Action |
Ensure the auditing plugin is properly registered in the registry. Ensure
the registry is in a consistent state with the | |
See Also |
| |
4851 |
ERROR: TMUSREVT has policy SIGNATURE_REQUIRED=signature-policy and ENCRYPTION_REQUIRED=encryption-policy but the input buffer was neither signed nor sealed | |
|
Description |
A posted message arrived at the TMUSREVT server that violated the policy constraints of the application. The user event broker has a signature policy of signature-policy and an encryption policy of encryption-policy. |
Action |
Determine why a posted message arrived at the user event broker that violates the policy, or change the policy. Remember that policy determination for the user event broker looks at the GROUP level, goes up to the MACHINE level and finally looks at the RESOURCE level. If any of those policies is Y, then the policy for the user event broker is Y. | |
See Also |
| |
4852 |
ERROR: TMUSREVT requires encryption but the input buffer is not encrypted | |
|
Description |
A posted message arrived at the user event broker that violated the policy constraints of the application. The user event broker has an encryption policy of Y. |
Action |
Determine why a posted message arrived at the user event broker that violates the policy, or change the policy. Remember that policy determination for the user event broker looks at the GROUP level, goes up to the MACHINE level and finally looks at the RESOURCE level. If any of those policies is Y, then the policy for the user event broker is Y. | |
See Also |
| |
4853 |
ERROR: Unable to decrypt message in order to determine signature status | |
|
Description |
A posted message arrived at the user event broker. The user event broker has a signature policy of Y. However, the posted message was encrypted, and the event broker does not have a valid decryption key. Therefore, the presence of digital signatures could not be verified. |
Action |
Using the public key plugin method, open a valid decryption key for the user event broker. Otherwise, ensure that messages posted to the user event broker requiring digital signatures are not encrypted. | |
See Also |
| |
4854 |
ERROR: Invalid public key context | |
|
Description |
The user event broker detected an invalid buffer while attempting to process a posted message. The user event broker has an encryption or signature policy of Y. |
Action |
Please contact your BEA Customer Support. | |
4855 |
ERROR: TMUSREVT requires encryption but the input buffer is not encrypted | |
|
Description |
A posted message arrived at the user event broker that violated the policy constraints of the application. The user event broker has an encryption policy of Y. |
Action |
Determine why a posted message arrived at the user event broker that violates the policy, or change the policy. Remember that policy determination for the user event broker looks at the GROUP level, goes up to the MACHINE level and finally looks at the RESOURCE level. If any of those policies is Y, then the policy for the user event broker is Y. | |
See Also |
| |
4856 |
ERROR: TMUSREVT requires a signature but the input buffer is not signed | |
|
Description |
A posted message arrived at the user event broker that violated the policy constraints of the application. The user event broker has a signature policy of Y. |
Action |
Determine why a posted message arrived at the user event broker that violates the policy, or change the policy. Remember that policy determination for the user event broker looks at the GROUP level, goes up to the MACHINE level and finally looks at the RESOURCE level. If any of those policies is Y, then the policy for the user event broker is Y. | |
See Also |
| |
4857 |
ERROR: Unable to initialize public key subsystem | |
|
Description |
The system processes |
Action |
Ensure the TUXDIR environment variable is set properly. Ensure the registry is configured properly. Ensure the shared or dynamically linked libraries which the registry references are available to the process. For example, ensure the LD_LIBRARY_PATH variable includes the name of the directory where the shared library resides if a relative library name is referenced in the registry. Other operating systems may use other environment variable to locate shared libraries. Consult the data sheet for your platform for the proper environment variable to set. | |
See Also |
| |
4858 |
ERROR: Unable to initialize public key subsystem | |
|
Description |
The system processes |
Action |
Ensure the TUXDIR environment variable is set properly. Ensure the registry is configured properly. Ensure the shared or dynamically linked libraries which the registry references are available to the process. For example, ensure the LD_LIBRARY_PATH variable includes the name of the directory where the shared library resides if a relative library name is referenced in the registry. Other operating systems may use other environment variable to locate shared libraries. Consult the data sheet for your platform for the proper environment variable to set. | |
See Also |
| |
4859 |
ERROR: Unable to initialize public key subsystem | |
|
Description |
The system processes |
Action |
Ensure the TUXDIR environment variable is set properly. Ensure the registry is configured properly. Ensure the shared or dynamically linked libraries which the registry references are available to the process. For example, ensure the LD_LIBRARY_PATH variable includes the name of the directory where the shared library resides if a relative library name is referenced in the registry. Other operating systems may use other environment variable to locate shared libraries. Consult the data sheet for your platform for the proper environment variable to set. | |
See Also |
| |
4860 |
WARN: the -n option is deprecated and will be removed in a future release | |
|
Description |
The |
Action |
Remove the | |
4863 |
ERROR: Unable to initialize public key subsystem | |
|
Description |
The system processes |
Action |
Ensure the TUXDIR environment variable is set properly. Ensure the registry is configured properly. Ensure the shared or dynamically linked libraries which the registry references are available to the process. For example, ensure the LD_LIBRARY_PATH variable includes the name of the directory where the shared library resides if a relative library name is referenced in the registry. Other operating systems may use other environment variable to locate shared libraries. Consult the data sheet for your platform for the proper environment variable to set. | |
See Also |
| |
4864 |
ERROR: Unable to initialize public key subsystem | |
|
Description |
The system processes |
Action |
Ensure the TUXDIR environment variable is set properly. Ensure the registry is configured properly. Ensure the shared or dynamically linked libraries which the registry references are available to the process. For example, ensure the LD_LIBRARY_PATH variable includes the name of the directory where the shared library resides if a relative library name is referenced in the registry. Other operating systems may use other environment variable to locate shared libraries. Consult the data sheet for your platform for the proper environment variable to set. | |
See Also |
| |
4865 |
ERROR: Unable to initialize public key subsystem | |
|
Description |
The system processes |
Action |
Ensure the TUXDIR environment variable is set properly. Ensure the registry is configured properly. Ensure the shared or dynamically linked libraries which the registry references are available to the process. For example, ensure the LD_LIBRARY_PATH variable includes the name of the directory where the shared library resides if a relative library name is referenced in the registry. Other operating systems may use other environment variable to locate shared libraries. Consult the data sheet for your platform for the proper environment variable to set. | |
See Also |
| |
4866 |
ERROR: Unable to initialize public key subsystem | |
|
Description |
The system processes |
Action |
Ensure the TUXDIR environment variable is set properly. Ensure the registry is configured properly. Ensure the shared or dynamically linked libraries which the registry references are available to the process. For example, ensure the LD_LIBRARY_PATH variable includes the name of the directory where the shared library resides if a relative library name is referenced in the registry. Other operating systems may use other environment variable to locate shared libraries. Consult the data sheet for your platform for the proper environment variable to set. | |
See Also |
| |
4867 |
ERROR: Cannot find service to which to forward request | |
|
Description |
A server cleanup was underway. The system was attempting to forward a request from the queue of the cleaned-up server. Information for the service which should be forwarded was missing or unable to be accessed. |
Action |
Examine the | |
4869 |
ERROR: FADDR parameter must be <= size characters | |
|
Description |
The FADDR field in the |
Action |
Ensure that the field is less than size characters. | |
See Also |
| |
4871 |
ERROR: FRANGE must be greater than or eqaul to zero and less than 65536 | |
|
Description |
The FRANGE field in the |
Action |
Correct the value for FRANGE. | |
See Also |
| |
4872 |
WARN: Unable to invoke audit postop on security failure | |
|
Description |
A call to the |
Action |
Check the registration of the auditing plugin. If the plugin used is the
default supplied plugin, check the userlog file and filesystem space. If the
plugin used is not the default supplied plugin, check with the supplier of
the plugin code.
In addition, because of the | |
See Also |
| |
4873 |
WARN: Unable to invoke audit preop on event posting | |
|
Description |
A call to the |
Action |
Check the registration of the auditing plugin. If the plugin used is the default supplied plugin, check the userlog file and filesystem space. If the plugin used is not the default supplied plugin, check with the supplier of the plugin code. | |
See Also |
| |
4874 |
ERROR: _dobbclean failed, couldn't find DBBL | |
|
Description |
Could not find structures/information associated with the DBBL. |
Action |
Contact your BEA Customer Support. | |
4875 |
ERROR: _dobbclean failed, couldn't find BBL | |
|
Description |
Could not find structures/information associated with the BBL. |
Action |
Contact your BEA Customer Support. | |
4876 |
ERROR: _dobbclean failed, message send/receive error | |
|
Description |
Sending of message to the BBL/DBBL to clean up and check status of local Bulletin Board failed. |
Action |
Check prior messages or check if message queue is blocked. If queue is blocked, system usage could be heavy and parameters may need to be tuned. | |
4877 |
ERROR: Use -t server option to interoperate with sites older than 7.1 | |
|
Description |
A request from a site older than 7.1 arrived at a server. However, the
|
Action |
If you wish to allow the server to interoperate with sites older than 7.1
then the | |
See Also |
| |
4878 |
ERROR: BBL bbclean cannot write the Bulletin Board for restarting the DBBL | |
|
Description |
While attempting to restart the |
Action |
Check free space and file permissions either in | |
4879 |
ERROR: DBBL tpsvrinit: error in reading the Bulletin Board image file, val errno= val | |
|
Description |
While attempting to start the |
Action |
Check file permissions of the Bulletin Board image file either in | |
See Also |
| |
4880 |
WARN: Unable to invoke audit postop on sevice completion | |
|
Description |
Calling of the |
Action |
Check the registration of the auditing plugin. If the plugin used is the default supplied plugin, check userlog file and filesystem space. If the plugin used is not the default supplied plugin, check with the supplier of the plugin code. | |
See Also |
| |
4881 |
ERROR: Getting server information from TUXCONFIG | |
|
Description |
When BBL scans the Bulletin Board, it will restart any dead servers that are
restartable. To do this it uses the |
Action |
Check the userlog for earlier related messages. | |
4882 |
ERROR: Reading server information from BB | |
|
Description |
When BBL scans the Bulletin Board, it will restart any dead servers that are
restartable. To do this it uses the |
Action |
Check the userlog for earlier related messages. | |
4883 |
ERROR: Sequencing servers to be restarted | |
|
Description |
When BBL scans the Bulletin Board, it will restart any dead servers that are
restartable. To do this it uses the |
Action |
Check the userlog for earlier related messages. | |
4884 |
ERROR: Could not identify sequence for grpid=group, srvid=id | |
|
Description |
To restart a server, the |
Action |
The shared memory may be corrupted. Contact your BEA TUXEDO system Technical Support. | |
4885 |
ERROR: Could not allocate memory for server list | |
|
Description |
To restart a server, the |
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. Re duce the memory usage on the machine or increase the amount of physical memory o n the machine. | |
See Also |
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|