>
LIBTUX メッセージ 6200-6299
|
|
6200
ERROR:Invalid buffer passed to workstation encode/decode routine
ERROR: ワークステーションの符号化/復号化のルーチンに渡されたバッファが無効です。
説明
An invalid buffer was passed by the system into an internal encoding routine.
アクション
BEA Customer Support にお問い合わせください。
6201
ERROR: Unable to get bulletin board parameters
説明
While attempting to initialize the public key subsystem, a process attempted to get bulletin board parameters to determine the proper SEC_PRINCIPAL_NAME, SEC_PRINCIPAL_LOCATION, or SEC_PRINCIPAL_PASSVAR variable to use. However, the process failed to retrieve the bulletin board parameters.
アクション
BEA Customer Support にお問い合わせください。
6202
ERROR:Invalid environment. Check TUXCONFIG in environment and UBBCONFIG.
ERROR: 無効な環境です。UXCONFIG ファイルと UBBCONFIG ファイルを確認してください。
説明
While attempting to initialize the public key subsystem, a process attempted to get bulletin board parameters to determine the proper SEC_PRINCIPAL_NAME, SEC_PRINCIPAL_LOCATION or SEC_PRINCIPAL_PASSVAR variable to use. However, the environment of the process was incorrect.
アクション
Ensure that your TUXCONFIG environment variable matches the TUXCONFIG variable for the local machine in the UBBCONFIG.
関連項目
tmunloadcf
6203
ERROR:Unable to initialize registry
ERROR: レジストリを初期化できません。
説明
システムがレジストリを初期化できませんでした。
アクション
BEA Customer Support にお問い合わせください。
関連項目
epifreg, epifregedt
6204
ERROR:Could not initialize public key subsystem
ERROR: 公開鍵のサブシステムを初期化できません。
説明
An error occurred while initializing the public key subsystem. Causes for this failure can include a user implementation of a plug-in function returning a failure code.
アクション
Ensure the registry is in a valid state using epifregedt. Ensure the implementation of the plug-in function did not return an error code.
関連項目
epifregedt, _ec_sec_map_proof,
_ec_sec_pki_init
6205
WARN:Server initialization function did not call tx_open() or tpopen() or this call failed
WARN: サーバの初期化関数では tx_open() または tpopen() が呼び出されなかったか、あるいは呼び出しに失敗しました。
説明
This single-threaded server is part of a group that has an associated resource manager, and the server initialization function tpsvrinit(3c) either did not make a call to tx_open(3c) or tpopen(3c) to open the resource manager, or else this call failed. (Note that the default versions of tpsvrinit(3c) and tpsvrthrinit(3c) include a call to tx_open(3c) for all single-threaded servers.) As a result of this failure, this thread of control will not be able to participate in BEA Tuxedo global transactions.
アクション
Include a call to tx_open(3c) or tpopen(3c) within your server initialization function if not already present, or investigate the reason why the existing call failed.
関連項目
tpsvrinit(3c), tpopen(3c), tx_open(3c)
6206
WARN:Server thread initialization function did not call tx_open() or tpopen() or this call failed
WARN: サーバ・スレッドの初期化関数では tx_open() または tpopen() が呼び出されなかったか、あるいは呼び出しに失敗しました。
説明
This multi-threaded server is part of a group that has an associated resource manager, and the server thread initialization function tpsvrthrinit(3c) either did not make a call to tx_open(3c) or tpopen(3c) to open the resource manager, or else this call failed. (Note that the default version of tpsvrthrinit(3c) includes a call to tx_open(3c).) As a result of this failure, this thread of control will not be able to participate in BEA Tuxedo global transactions.
アクション
Include a call to tx_open(3c) or tpopen(3c) within your server thread initialization function if not already present, or investigate the reason why the existing call failed.
関連項目
tpsvrthrinit(3c), tpopen(3c), tx_open(3c)
6207
WARN:Destruction of public-key subsystem failed
WARN: 公開鍵のサブシステムを削除できませんでした。
説明
An error occurred while trying to destroy the public key subsystem. The plug-in point implementing the destructor function may have failed.
アクション
Contact your Security Service Interface Provider to get more information on the functionality of the public key subsystem destructor.
6212
WARN:Unable to invoke audit postop on security failure
WARN: セキュリティ障害の発生時に audit postop を呼び出せません。
説明
A call to the audit_postop() plugin security function during initialization failed. This call was being attempted after the failure of authentication security. No audit of the attempt was able to be performed/recorded.
アクション
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 authentication failure, if the failure was not intended, check the registration, authentication configuration, and returns from the authentication security functions.
関連項目
epifregedt, epifreg
6213
WARN:Unable to invoke audit postop on security failure
WARN: セキュリティ障害の発生時に audit postop を呼び出せません。
説明
A call to the audit_postop() plugin security function on a service operation failed. This call was being attempted due to a deny or failure return from the authorize_postop() plugin security function call, performed prior to a call to tpforward(). No audit of the failure was able to be performed/recorded.
アクション
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 authorize_postop() deny or failure, if the denial was not intended, check the registration, authorization configuration, and return from the authorize_postop() function.
関連項目
epifregedt, epifreg
6214
WARN:Unable to invoke audit postop on service completion
WARN: サービスの完了時に audit postop を呼び出せません。
説明
A call to the audit_postop() plugin security function on a service operation failed. This call was being attempted after the operation execution, prior to a call to tpforward(). No audit of the failure was able to be performed/recorded.
アクション
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.
関連項目
epifregedt, epifreg
6215
WARN:Unable to invoke audit postop on security failure
WARN: セキュリティ障害の発生時に audit postop を呼び出せません。
説明
A call to the audit_postop() plugin security function on a service operation failed. This call was being attempted due to a deny or failure return from the authorize_preop() plugin security function call. No audit of the failure was able to be performed/recorded.
アクション
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 authorize_preop() deny or failure, if the denial was not intended, check the registration, authorization configuration, and return from the authorize_preop() function.
関連項目
epifregedt, epifreg
6216
WARN:Unable to invoke audit preop on service invocation
WARN: サービスの起動時に audit preop を呼び出せません。
説明
A call to the audit_preop() plugin security function on a service operation failed. This call was being attempted prior to the operation execution. No audit of the attempt was able to be performed/recorded.
アクション
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.
関連項目
epifregedt, epifreg
6218
WARN:Unable to invoke audit postop on sevice completion
WARN: サービスの完了時に audit postop を呼び出せません。
説明
A call to the audit_postop() plugin security function on a service operation failed. This call was being attempted after the operation execution. No audit of the completion of the operation was able to be performed/recorded.
アクション
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.
関連項目
epifregedt, epifreg
6219
WARN:Destruction of audit subsystem failed
WARN: 監査サブシステムを削除できませんでした。
説明
A call to the destroy function of the auditing plugin security function failed. This call was being attempted while a server was shutting down.
アクション
Check the registration of the auditing plugin. If the plugin used is not the default supplied plugin, check with the supplier of the plugin code to ensure proper implementation of the destructor function.
関連項目
epifregedt, epifreg
6220
WARN:Destruction of authorization subsystem failed
WARN: オーソライゼーション・サブシステムを削除できませんでした。
説明
A call to the destroy function of the authorization plugin security function failed. This call was being attempted while a server was shutting down.
アクション
Check the registration of the authorization plugin. If the plugin used is not the default supplied plugin, check with the supplier of the plugin code to ensure proper implementation of the destructor function.
関連項目
epifregedt, epifreg
6221
WARN:Destruction of authentication subsystem failed
WARN: 認証用のサブシステムを削除できませんでした。
説明
A call to the destroy function of the authentication plugin security function failed. This call was being attempted while a server was shutting down.
アクション
Check the registration of the authentication plugin. If the plugin used is not the default supplied plugin, check with the supplier of the plugin code to ensure proper implementation of the destructor function.
関連項目
epifregedt, epifreg
6222
ERROR:JRW Unable to read key
ERROR: JRW がキーを読み取れません。
説明
The system was unable to read the key from the TUXCONFIG file. The TUXCONFIG file may be corrupted.
アクション
If the TUXCONFIG file is not corrupted, contact BEA Customer Support.
6223
ERROR:JRW Unable to generate decryption schedule
ERROR: JRW が復号化スケジュールを生成できません。
説明
The system was unable to generate a decryption schedule.
アクション
BEA Customer Support にお問い合わせください。
6224
ERROR:JRW Unable to decrypt password
ERROR: JRW がパスワードを復号化できません。
説明
The system was unable to decrypt a SEC_PRINCIPAL_PASSWORD value from the TUXCONFIG file. This may happen if the TUXCONFIG file has been corrupted.
アクション
If the TUXCONFIG file is not corrupted, contact your Tuxedo System Technical Support.
6225
ERROR:Unable to open TUXCONFIG file to Resources section
ERROR: RESOURCES セクション用に TUXCONFIG ファイルをオープンできません。
説明
The system was unable to open the TUXCONFIG. Either it has been removed, or has been corrupted.
アクション
If the TUXCONFIG file is not corrupted, contact your Tuxedo System Technical Support.
6226
ERROR:Unable to open Resources section of TUXCONFIG file
ERROR: TUXCONFIG ファイルの RESOURCES セクションをオープンできません。
説明
The system was unable to read the TUXCONFIG. Either it has been removed, or has been corrupted.
アクション
If the TUXCONFIG file is not corrupted, contact your Tuxedo System Technical Support.
6227
ERROR:Possibly corrupted key in database
ERROR: データベース内に破損したキーがあると思われます。
説明
The key used to encrypt passwords in the TUXCONFIG file is corrupted.
アクション
Regenerate your last TUXCONFIG file from a UBBCONFIG file.
6228
ERROR:Error while decrypting password
ERROR: パスワードの復号化のエラー
説明
The system could not decrypt a password found in the TUXCONFIG file. The TUXCONFIG file may have been corrupted.
アクション
If the TUXCONFIG file is not corrupted, contact your Tuxedo System Technical Support.
6230
ERROR:Could not acquire authorization token
ERROR: 認証トークンを取得できません。
説明
A fatal error occured while retrieving an authorization token from the AAA provider.
アクション
Contact your AAA (authentication, authorization, auditing) security provider. If you are using the default AAA security provider provided by BEA Systems, Inc., then contact BEA Customer Support.
6231
ERROR:Could not acquire auditing token
ERROR: 監査トークンを取得できません。
説明
A fatal error occured while retrieving an auditing token from the AAA provider.
アクション
Contact your AAA (authentication, authorization, auditing) security provider. If you are using the default AAA security provider provided by BEA Systems, Inc., then contact BEA Customer Support.
6232
ERROR:FML32 error val adding AAA tokens with code val
ERROR: AAA トークンを追加する際に FML32 エラー val が発生しました。エラー・コードは val です。
説明
A system error occurred when trying to attach the authorization and auditing tokens to a message during the sending of the message.
アクション
If the plugin used is the default supplied plugin, contact BEA Customer Support. If the plugin used is not the default supplied plugin, check with the supplier of the plugin code to be sure the format of the tokens is valid.
6233
ERROR:Memory allocation failure with code val
ERROR: メモリを確保できません。エラー・コードは val です。
説明
An attempt to allocate space for a security token failed.
アクション
Make sure the operating system parameters are set correctly for the amount of memory on the machine and for 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 and/or swap space on the machine.
6234
ERROR:Authentication fails with error code val
ERROR: 認証が異常終了しました。エラー・コードは val です。
説明
A process that authenticates with itself, such as a server or a native client, was unable to complete the authentication.
アクション
Contact BEA Customer Support. Report the value of val to technical support.
6235
ERROR:Error interoperating with older site. Error code val
ERROR: 古いサイトと相互運用できません。エラー・コードは val です。
説明
The system was unable to interoperate with a site older than Tuxedo Release 7.1. The error code is val. This usually happens when a server receives a request from an older site.
アクション
Contact BEA Customer Support. Report the value of val to technical support.
6236
WARN:Unable to invoke audit postop on service invocation failure
WARN: サービスの起動エラーが発生したときに audit postop を呼び出せません。
説明
The audit postop for a service invocation failed.
アクション
Contact your AAA (authentication, authorization, auditing) security provider. If you are using the default AAA security provider provided by BEA Systems, Inc., then contact BEA Customer Support.
6237
ERROR: Memory allocation error
説明
An attempt to allocate space for an authorization token failed.
アクション
Make sure the operating system parameters are set correctly for the amount of memory on the machine and for 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 and/or swap space on the machine.
6238
ERROR: Memory allocation error
説明
An attempt to allocate space for an auditing token failed.
アクション
Make sure the operating system parameters are set correctly for the amount of memory on the machine and for 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 and/or swap space on the machine.
6239
ERROR:Use -t server option to interoperate with sites older than 7.1
ERROR: 7.1 より前のサイトと相互運用するには、-t サーバ・オプションを使用してください。
説明
A request from a site older than BEA Tuxedo Release 7.1 arrived at a server. However, the -t servopts option was not specified. In order to close a possible security hole, the administrator must explicitly tell the server that it is allowed to accept requests from older sites.
アクション
If you wish to allow the server to interoperate with sites older than 7.1 then the CLOPT for the server must contain -t before the -- option.
関連項目
servopts
6240
ERROR:Unable to acquire credentials. Error code val1, minor_status val2
ERROR: クリデンシャルを取得できません。エラー・コードは val1、 minor_status val2 です。
説明
The workstation client or workstation handler was unable to acquire credentials. The engine error code was val1 and the GSSAPI minor status code was val2.
アクション
Contact your AAA (authentication, authorization, auditing) security service provider. If you are using the default AAA security service from BEA, contact BEA Customer Support. Report val1 and val2 to technical support.
6241
ERROR:Unable to get machine information for administrative client
ERROR: 管理用クライアントのマシン情報を取得できません。
説明
Administrative clients acquire their name from the *MACHINE section of the TUXCONFIG file. This administrative client was unable to read the TUXCONFIG file.
アクション
BEA Customer Support にお問い合わせください。
6242
ERROR:Invalid user password
ERROR: ユーザ・パスワードが無効です。
説明
The password in the TPINIT->data field was incorrect. Either the AUTHSVR rejected the password or the corresponding user is unknown to the system.
アクション
Try a different user name or password.
6243
ERROR:Unable to establish security context. Error code val, minor_status val
ERROR: セキュリティ・コンテキストを確立できません。エラー・コード val、minor_status val です。
説明
The workstation client or workstation handler was unable to establish a security context. The engine error code was val1 and the GSSAPI minor status code was val2.
アクション
Contact your AAA (authentication, authorization, auditing) security service provider. If you are using the default AAA security service from BEA, contact BEA Customer Support. Report val1 and val2 to technical support.
6244
ERROR:Application password does not match
ERROR: アプリケーション・パスワードが一致しません。
説明
The password in the TPINIT->passwd field was incorrect.
アクション
Verify the password and retry the operation.
6246
ERROR:Insecure protocol detected
ERROR: セキュリティで保護されていないプロトコルが検出されました。
説明
An insecure security protocol has been detected between two different processes. The Tuxedo System registry is misconfigured.
アクション
BEA Customer Support にお問い合わせください。
6247
ERROR:Unable to establish security context. Error code val, minor_status val
ERROR: セキュリティ・コンテキストを確立できません。エラー・コード val、minor_status val です。
説明
The native client or server was unable to establish a security context. The engine error code was val1 and the GSSAPI minor status code was val2.
アクション
Contact your AAA (authentication, authorization, auditing) security service provider. If you are using the default AAA security service from BEA, contact BEA Customer Support. Report val1 and val2 to technical support.
6248
ERROR:Insecure protocol detected
ERROR: セキュリティで保護されていないプロトコルが検出されました。
説明
An insecure security protocol has been detected between two different processes. The Tuxedo System registry is misconfigured.
アクション
BEA Customer Support にお問い合わせください。
6249
ERROR:Unable to establish security context. Error code val1, minor_status val2
ERROR: セキュリティ・コンテキストを確立できません。エラー・コードは val1、 minor_status val2 です。
説明
The native client or server was unable to establish a security context. The engine error code was val1 and the GSSAPI minor status code was val2.
アクション
Contact your AAA (authentication, authorization, auditing) security service provider. If you are using the default AAA security service from BEA, contact BEA Customer Support. Report val1 and val2 to technical support.
6250
ERROR:The WSH does not posses the proper application password
ERROR: WSH には正しいアプリケーション・パスワードが指定されていません。
説明
The workstation client has discovered that the WSH does not posses the application password. The WSH may be an imposter, or data corruption may have occured on the wire.
アクション
The WSH was not able to authenticate itself to the workstation client. A security attack may be underway. BEA Customer Support にお問い合わせください。
6251
ERROR:A workstation client does not have a proper application password
ERROR: ワークステーション・クライアントには正しいアプリケーション・パスワードが指定されていません。
説明
The password in the TPINIT->passwd field of a workstation client was incorrect.
アクション
A security attack may be underway. The client should be given the proper application password. BEA Customer Support にお問い合わせください。
6252
ERROR:A workstation client does not have a proper application password
ERROR: ワークステーション・クライアントには正しいアプリケーション・パスワードが指定されていません。
説明
The password in the TPINIT->passwd field of a workstation client was incorrect.
アクション
A security attack may be underway. The client should be given the proper application password. BEA Customer Support にお問い合わせください。
6253
ERROR:Unable to resolve interception sequence (val)
ERROR: インターセプション・シーケンス (val) を解決できません。
説明
The authorization fan-out implementation could not discover the list of intercepting implementations.
アクション
Contact BEA Customer Support and report val.
6254
ERROR:Unable to allocate array of val handles
ERROR: val ハンドルの配列を割り当てられません。
説明
A call to calloc failed while attempting to allocate an array of val handles.
アクション
Check that your system has enough physical or virtual memory to complete the operation. If you believe your system has enough memory for the operation and that the malloc arena has not been corrupted by user code, contact your BEA Customer Support.
6255
ERROR:Unable to resolve interception sequence (val)
ERROR: インターセプション・シーケンス (val) を解決できません。
説明
The authorization fan-out implementation could not discover the list of intercepting implementations.
アクション
Contact BEA Customer Support and report val.
6256
ERROR:tpsvrthrinit() failed
ERROR: tpsvrthrinit() が異常終了しました。
説明
A call to tpsvrthrinit() failed. As a result of this failure, the thread in which the failure occurred will exit. This failure may be caused by an application-defined tpsvrthrinit() function returning -1.
アクション
Check prior specific tpsvrthrinit() messages or verify the return code from an application-defined tpsvrthrinit() function.
関連項目
tpsvrthrinit(3c)
6257
ERROR:tpsvrthrinit() returned in transaction mode
ERROR: tpsvrthrinit() がトランザクション・モードで復帰しました。
説明
An application server dispatched thread has been placed in transaction mode during its initialization in an application-defined tpsvrthrinit() function. tpsvrthrinit() returned while still in transaction mode. BEA Tuxedo will abort the outstanding transaction and the thread where the error occurred will exit.
アクション
Fix the coding of the application-define tpsvrthrinit() function so that it commits or aborts any transaction started in this function before returning.
関連項目
tpsvrthrinit(3c)
6258
ERROR:tpsvrthrinit() failed with outstanding message handles
ERROR: tpsvrthrinit() は異常終了しました。メッセージ・ハンドルが未処理です。
説明
A call to tpsvrthrinit(), although returning success, failed to receive all outstanding reply messages and therefore has outstanding handles. As a result of this error, the thread in which the error occurred will exit. This error should only happen when an application-defined tpsvrthrinit() function is used.
アクション
Fix the coding of the application-defined tpsvrthrinit() function so that it does not return with outstanding handles.
関連項目
tpsvrthrinit(3c)
6259
ERROR:tpsvrthrinit() failed with open conversations
ERROR: tpsvrthrinit() は異常終了しました。会話はオープンの状態です。
説明
A call to tpsvrthrinit(), although returning success, had one or more conversations open at the time of return. As a result of this error, the thread in which the error occurred will exit. This error should only happen when an application-defined tpsvrthrinit() function is used.
アクション
Fix the coding of the application-defined tpsvrthrinit() function so that it does not return with open conversations.
関連項目
tpsvrthrinit(3c)
6260
ERROR:tpsvrinit() failed with open conversations
ERROR: tpsvrinit() は異常終了しました。会話はオープンの状態です。
説明
A call to tpsvrinit(), although returning success, had one or more conversations open at the time of return. As a result of this error, the server will exit. This error should only happen when an application-defined tpsvrinit() function is used.
アクション
Fix the coding of the application-defined tpsvrinit() function so that it does not return with open conversations.
関連項目
tpsvrinit(3c)
6261
ERROR:An application association may not issue tpgetrply(TPGETANY) concurrently with tpgetrply for a specific cd
ERROR: アプリケーションの関連付けでは、tpgetrply(TPGETANY) と特定の cd の tpgetrply が同時に発行されない場合があります。
説明
In a multithreaded application, two threads associated with the same BEA Tuxedo context issued concurrent tpgetrply() calls. The first tpgetrply() call tried to retrieve a reply for a specific call descriptor. While this call was still outstanding, a second tpgetrply() call tried to retrieve a reply for any outstanding call descriptor. This is not allowed by the system. As a result, the second tpgetrply() wrote this userlog message and returned -1 with tperrno set to TPEPROTO.
アクション
Change the coding of the application so that this case does not occur. One possibility is to specify a specific handle on all tpgetrply() calls, which is allowed even if the calls are performed concurrently. Another possibility is to dedicate one thread in each context to retrieve all replies for that context. Other valid possibilities also exist.
関連項目
tpgetrply(3c)
6262
ERROR:An application association may not issue multiple concurrent tpgetrply(TPGETANY) calls
ERROR: アプリケーションの関連付けでは、複数の tpgetrply(TPGETANY) 呼び出しが同時に発行されない場合があります。
説明
In a multithreaded application, two threads associated with the same
BEA Tuxedo context issued concurrent tpgetrply() calls with the TPGETANY flag. This is not allowed by the system. As a result, the second tpgetrply() call wrote this userlog message and returned -1 with tperrno set to TPEPROTO.
アクション
Change the coding of the application so that this case does not occur. One possibility is to specify a specific handle on all tpgetrply() calls, which is allowed even if the calls are performed concurrently. Another possibility is to dedicate one thread in each context to retrieve all replies for that context. Other valid possibilities also exist.
関連項目
tpgetrply(3c)
6263
ERROR:An application association may not issue tpgetrply for a specific cd concurrently with tpgetrply(TPGETANY)
ERROR: アプリケーションの関連付けでは、特定の cd の tpgetrply と tpgetrply(TPGETANY) が同時に発行されない場合があります。
説明
In a multithreaded application, two threads associated with the same BEA Tuxedo context issued concurrent tpgetrply() calls. The first tpgetrply() call tried to retrieve a reply for any outstanding call descriptor. While this call was still outstanding, a second tpgetrply() call tried to retrieve a reply for a specific call descriptor. This is not allowed by the system. As a result, the second tpgetrply() call wrote this userlog message and returned -1 with tperrno set to TPEPROTO. The call descriptor specified by the second tpgetrply() call is still valid until retrieved by either the first tpgetrply() call or some tpgetrply() call issued in the future.
アクション
Change the coding of the application so that this case does not occur. One possibility is to specify a specific handle on all tpgetrply() calls, which is allowed even if the calls are performed concurrently. Another possibility is to dedicate one thread in each context to retrieve all replies for that context. Other valid possibilities also exist.
関連項目
tpgetrply(3c)
6264
ERROR:Unable to establish security context. Error code val, minor_status val
ERROR: セキュリティ・コンテキストを確立できません。エラー・コード val、minor_status val です。
説明
The native client or server was unable to establish a security context. The engine error code was val1 and the GSSAPI minor status code was val2.
アクション
Contact your AAA (authentication, authorization, auditing) security service provider. If you are using the default AAA security service from BEA, contact BEA Customer Support. Report val1 and val2 to technical support.
6265
ERROR:Invalid return from _tmpresend2. Required size (required) less than given size (given)
ERROR: _tmpresend2 から返された値が無効です。必須サイズ (required) が指定されたサイズ (given) より小さい値になっています。
説明
The _tmpresend2 function in the buffer type switch can ask the system for more space if necessary. However, it must always ask for more space than it was given. However, in this case required is less than given.
アクション
Fix the implementation of _tmpresend2 to ensure more data is asked for than given.
関連項目
buffer(3i)
6266
ERROR:Token container error string-val/numeric-val
ERROR: トークン・コンテナ・エラー string-val/numeric-val です。
説明
The AAA security features pass tokens in an FML32 buffer. However, when construction this buffer, and FML32 error occurred. string-val is the string version of the FML error, while numeric-val is the numeric version of the error.
アクション
BEA Customer Support にお問い合わせください。
関連項目
Fchg32, Fadd32
6267
ERROR: Memory allocation error
説明
An attempt to allocate memory has failed. This occured while attempting to allocate memory in the server for a security token.
アクション
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 and/or swap space on the machine.
6268
ERROR:Token container error string-val
ERROR: トークン・コンテナ・エラー string-val です。
説明
An attempt to initialize the AAA container buffer with Finit32 failed. The error was string-val.
アクション
BEA Customer Support にお問い合わせください。
関連項目
Finit32
6269
ERROR:Token container error string-val
ERROR: トークン・コンテナ・エラー string-val です。
説明
An attempt to initialize the AAA container buffer with Finit32 failed. The error was string-val.
アクション
BEA Customer Support にお問い合わせください。
関連項目
Finit32
6270
ERROR:Memory allocation failure.
ERROR: メモリの割り当てに失敗しました。
説明
An attempt dynamically to allocate memory from the operating system failed.
アクション
オペレーティング・システムのパラメータが、マシンのメモリ量およびプロセスが使用できるメモリ量に関して正しく設定されているか確認してください。マシンのメモリ使用を減らすか、マシンの物理メモリ量を増やしてください。
6271
ERROR:Memory allocation failure.
ERROR: メモリの割り当てに失敗しました。
説明
An attempt dynamically to allocate memory from the operating system failed.
アクション
オペレーティング・システムのパラメータが、マシンのメモリ量およびプロセスが使用できるメモリ量に関して正しく設定されているか確認してください。マシンのメモリ使用を減らすか、マシンの物理メモリ量を増やしてください。
6272
ERROR: Unable to get bulletin board parameters
説明
A failure to retrieve bulletin board parameters occurred while attempting to shut down the audit and authorization subsystems.
アクション
BEA Customer Support にお問い合わせください。
6274
ERROR:TMNOTHREADS set to yes but multiple threads detected:string-val/string-val
ERROR: TMNOTHREADS が yes に設定されていますが、マルチ・スレッドが検出されました。string-val/string-val
説明
The setting of the TMNOTHREADS environment variable specifies the application to be single-threaded, but BEA Tuxedo has detected that the application is multi-threaded.
アクション
Set the TMNOTHREADS environment variable to match the application.
6275
ERROR:Unable to initialize public key subsystem (numeric-val)
ERROR: 公開鍵サブシステムを初期化できません。(numeric-val)
説明
An error occurred when initializing the public key subsystem. The specific error is indicated by the decimal number in the error message.
アクション
Make sure that your public key proof material is specified correctly. Resolve previous errors, if any occurred. Contact BEA Customer Support if you are unable to resolve this problem.
6276
ERROR:キーを読み取れません。
説明
The system was unable to read the key from the TUXCONFIG file. The TUXCONFIG file may be corrupted.
アクション
If the TUXCONFIG file is not corrupted, contact BEA Customer Support.
6277
ERROR:Unable to generate decryption schedule
ERROR: 復号化スケジュールを生成できません。
説明
The system was unable to generate a decryption schedule.
アクション
BEA Customer Support にお問い合わせください。
6278
ERROR:Unable to decrypt password
ERROR: パスワードを復号化できません。
説明
The system was unable to decrypt a SEC_PRINCIPAL_PASSWORD value from the TUXCONFIG file. This may happen if the TUXCONFIG file has been corrupted.
アクション
If the TUXCONFIG file is not corrupted, contact your Tuxedo System Technical Support.
 |
 |
 |