WEBGUI Messages 2900-2999
|
|
|
2900
ERROR: actSet: call failed..., tperrno=tperrno: error string
Description
The GUI made a tpacall(3c) that failed. Look at surrounding entries in the ULOG to determine the cause of the failure. This is a critical error. The ongoing Activation, Deactivation or Migration action will not succeed.
Action
Contact BEA Customer Support and provide them with a description of action being performed along with relevant ULOGs.
See Also
tpacall(3c)
2901
ERROR: actGetState: GET call failed...
Description
The GUI was unable to access the Tuxedo System/T MIB. Look at surrounding entries in the ULOG to determine the cause of the failure. This is a critical error. The ongoing Activation, Deactivation or Migration action will not succeed.
Action
Contact your BEA Technical Support and provide them with a description of action being performed along with relevant ULOGs.
See Also
tpacall(3c)
2902
WARN: guimib_tpterm failed,tperrno = error
Description
The GUI was unable to do a tpterm(3c) from the application. Look at surrounding entries in the ULOG to determine the cause of the tpterm(3c) failure. This is a non-critical, internal error in the wgated process and will not affect the GUI's functionality or performance.
Action
No action is needed.
See Also
tpterm(3c)
2903
WARN: guimib_tpterm failed,tperrno = error
Description
The GUI was unable to do a tpterm(3c) from the application. Look at surrounding entries in the ULOG to determine the cause of the tpterm(3c) failure. This is a non-critical, internal error in the WGATED process and will not affect the GUI's functionality or performance.
Action
No action is needed.
See Also
tpterm(3c)
2904
ERROR: LmidToPmid: GET call failed...
Description
The GUI tried to access the Tuxedo System/T MIB to retrieve attributes of a Machine. This call has failed. Look at surrounding entries in the ULOG to determine the cause of the failure. This is a non-critical error and does not affect the GUI's functionality or performance. However, because of this error, the Progress Window of the ongoing Activation, Deactivation or Migration action, while displaying status messages, might display the LMIDs rather than PMIDs for some sites in the application.
Action
No action is needed.
2905
ERROR: CONFTOOL: Could not get MIB attributes
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2906
ERROR: CONFTOOL: Could not set MIB attributes
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2908
ERROR: CONFTOOL: cfSetupGwMsg() failed.
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2910
ERROR: CONFTOOL: cfSetupGwMsg() failed.
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2912
ERROR: CONFTOOL: Bad class for NEW object
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2913
ERROR: Could not find occurrence number of attribute attributename
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2914
WARN: guimib_tpterm failed,tperrno = error
Description
The GUI was unable to do a tpterm(3c) from the application. Look at surrounding entries in the ULOG to determine the cause of the tpterm(3c) failure. This is a non-critical, internal error in the wgated process and will not affect the GUI's functionality or performance.
Action
No action is needed.
See Also
tpterm(3c)
2915
ERROR: guimib_tpterm failed,tperrno = error
Description
The GUI was unable to do a tpterm(3c) from the application. Look at surrounding entries in the ULOG to determine the cause of the tpterm(3c) failure. This is a critical, internal error in the GUI and because of this, the ongoing Domain-level deactivation will not succeed.
Action
Contact your BEA Technical Support and provide them with a description of action being performed and relevant ULOGs.
See Also
tpterm(3c)
2916
WARN: unknown protocol received
Description
The GUI's server side received an unknown message from the JAVA front-end of the GUI. This is an internal error in the GUI and may or may not affect the GUI's functionality or performance.
Action
Contact BEA Customer Support and provide a description of the action being performed when this error was seen.
2917
ERROR: tpsetunsol failed: tperrno
Description
The GUI was unable to setup a handler to receive unsolicited notifications. Look at surrounding entries in the ULOG to determine the reason for the failure. This error will not affect the GUI's performance or functionality in any way. However, because of this error, the GUI will not display notification messages that are sent by Tuxedo when server processes are booted/shutdown/restarted etc.
Action
Look in the ULOG to determine why the unsolicited notification handler could not be set up.
See Also
tpsetunsol(3c), tpchkunsol(3c)
2918
ERROR: guimib_tpterm failed,tperrno = error
Description
The GUI was unable to do a tpterm(3c) from the application. Look at surrounding entries in the ULOG to determine the cause of the tpterm(3c) failure. This is a critical, internal error in the GUI and because of this, the ongoing Domain-level deactivation will not succeed.
Action
Contact BEA Customer Support and provide them with a description of action being performed and relevant ULOGs.
See Also
tpterm(3c)
2919
ERROR: isEvtBrkrActive: GET call failed
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2920
ERROR: TUXDIR not set in initialization file
Description
The ini file requires the TUXDIR entry. For more information, consult the documentation for wlisten.
Action
Specify the TUXDIR in the ini file.
2921
ERROR: Could not open ini file
Description
The BEA Tuxedo WEB GUI initialization file could not be opened.
Action
Check the permission of the file. Make sure you have read and write privileges.
2922
WARN: guimib_tpterm failed,tperrno = error
Description
The GUI was unable to do a tpterm(3c) from the application. Look at surrounding entries in the ULOG to determine the cause of the tpterm(3c) failure. This is a non-critical, internal error in the wgated process and will not affect the GUI's functionality or performance.
Action
No action is needed.
See Also
tpterm(3c)
2923
WARN: unknown protocol received
Description
The GUI's server side received an unknown message from the JAVA front-end of the GUI. This is an internal error in the wgated process and may or may not affect the GUI's functionality or performance.
Action
Contact BEA Customer Support and provide a description of the action being performed when this error was seen.
2924
ERROR: migrate: Get failed..cannot continue..
Description
The GUI was unable to access the Tuxedo System/T MIB. Look at the surrounding entries in the ULOG and messages in the Progress Window to determine the cause of the failure. This is a critical, internal error in the GUI and because of this, the ongoing Migration action will fail.
Action
Contact BEA Customer Support and provide them with a description of the action being performed and relevant ULOGs.
See Also
tpterm(3c)
2925
ERROR: migrate: Set call failed..cannot continue..
Description
The GUI was unable to access the Tuxedo MIB. Look at the surrounding entries in the ULOG and messages in the Progress Window to determine the cause of the failure. This is a critical, internal error in the GUI and because of this, the ongoing Migration action will fail.
Action
Contact BEA Customer Support and provide them with a description of the action being performed and relevant ULOGs.
See Also
tpterm(3c)
2926
ERROR: Cannot open ini file
Description
The BEA Tuxedo WEB GUI initialization file could not be opened.
Action
Check the permission of the file. Make sure you have read and write privileges.
2927
ERROR: Cannot open ini file
Description
The BEA Tuxedo WEB GUI initialization file could not be opened.
Action
Check the permission of the file. Make sure you have read and write privileges.
2928
ERROR: Cannot open tmp file: filename
Description
The file could not be opened.
Action
Check the permission of the file. Make sure you have read and write privileges.
2929
ERROR: Cannot replace .ini file with tmp file
Description
The BEA Tuxedo WEB GUI initialization file could not be opened.
Action
Check the permission of the file. Make sure you have read and write privileges.
2930
ERROR: getAppqspaces: MIB request on T_APPQSPACE failed
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2931
ERROR: getDevices: MIB request on T_APPQSPACE failed
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2932
ERROR: getAppqspaces: MIB request failed
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2933
ERROR: Cannot open ini file
Description
The BEA Tuxedo WEB GUI initialization file could not be opened.
Action
Check the permission of the file. Make sure you have read and write privileges.
2934
ERROR: MIB request failed
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2935
ERROR: sendGetChildrenMssg: TA_ERROR was not found in the MIB buffer
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2936
ERROR: sendGetChildrenMssg: MIB request failed with TA_ERROR=number
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2937
ERROR: GETWLS: MIB request failed
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2938
ERROR: GETWLS: MIB request failed
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2939
ERROR: GETWLS: MIB request failed
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2940
ERROR: checkLmidStr: GET call failed
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2941
ERROR: checkLmidStr: TA_LMID not returned in GET call
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2944
ERROR: could not get domain info
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2945
ERROR: tpinit failed
Description
BEA Tuxedo WEB GUI internal error.
Action
Contact BEA Customer Support.
2946
ERROR: Memory reallocation failure
Description
An attempt to dynamically allocate memory has failed.
Action
Make sure that the operating system parameters are set correctly for the amount of memory that can be used by a process. Reduce the amount of memory usage on the machine or increase the amount of physical memory in the system.
2947
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory has failed.
Action
Make sure that the operating system parameters are set correctly for the amount of memory that can be used by a process. Reduce the amount of memory usage on the machine or increase the amount of physical memory in the system.
2948
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory has failed.
Action
Make sure that the operating system parameters are set correctly for the amount of memory that can be used by a process. Reduce the amount of memory usage on the machine or increase the amount of physical memory in the system.
2949
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory has failed.
Action
Make sure that the operating system parameters are set correctly for the amount of memory that can be used by a process. Reduce the amount of memory usage on the machine or increase the amount of physical memory in the system.
2950
ERROR: Memory allocation failure
Description
The wgated(1) process was unable to allocate sufficient memory to store perform web-based administrative tasks. As a result of this failure, wgated(1) will report an error to the Java client, provided that further memory allocation errors do not prevent it from doing so.
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.
2951
ERROR: Memory allocation failure
Description
The wgated(1) process was unable to allocate sufficient memory to store perform web-based administrative tasks. As a result of this failure, wgated(1) will report an error to the Java client, provided that further memory allocation errors do not prevent it from doing so.
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.
2952
ERROR: Memory allocation failure
Description
The wgated(1) process was unable to allocate sufficient memory to perform web-based administrative tasks. As a result of this failure, wgated(1) will report an error to the Java client, provided that further memory allocation errors do not prevent it from doing so.
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.
2953
ERROR: Memory allocation failure
Description
The wgated(1) process was unable to allocate sufficient memory to perform web-based administrative tasks. As a result of this failure, wgated(1) will report an error to the Java client, provided that further memory allocation errors do not prevent it from doing so.
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.
 |
 |
 |