WTC Subsystem Messages配置报错集锦

               **WTC Subsystem Messages**

The WTC1.0 catalog contains messages in the range BEA180000 - BEA189999. Messages in this catalog are part of the weblogic.wtc Internationalization package and theweblogic.wtc Localization package.
BEA-180000 Info: Start parsing the configuration MBean info.
Description WTC will now be initialized according to the MBean config info entered.
Cause All other initialization has completed and now this method is ready to begin reading its own configuration info.
Action No action required.

BEA-180001 Info: WTC finished parsing the configuration MBean info.
Description WTC finished initialization according to the MBean config info entered.
Cause All WTC configuration MBeans were parsed without any problems.
Action No action required.

BEA-180002 Error: Invalid attributes exception trying to create Subcontext: iae
Description Invalid attributes exception when trying to create sub-context.
Cause An attempt was made to add an attribute set that has been specified incompletely or incorrectly.
Action Internal error. Contact Oracle Customer Support.

BEA-180003 Error: Naming exception error: ne
Description Naming exception while creating sub-context.
Cause Specified name can not be resolved.
Action Internal error. Contact Oracle Customer Support.

BEA-180004 Error: Name already bound error: nabe
Description Failed to bind Tuxedo or Corba connection factory to JNDI.
Cause The name used by the Tuxedo connection factory or Tuxedo CORBA connection factory already bonded to another object.
Action Do not use the same name as Tuxedo or Tuxedo CORBA connection factory.

BEA-180005 Error: Invalid attributes exception when binding connection factory: iae
Description Invalid attributes exception occurred when trying to create Tuxedo or Tuxedo CORBA connection factroy.
Cause An attempt was made to add an attribute set that has been specified incompletely or incorrectly.
Action Internal error. Contact Oracle Customer Support.

BEA-180006 Error: Naming excepting error: nae
Description Naming exception occurred while binding Tuxedo and Tuxedo CORBA connection factory to the JNDI.
Cause Specified name can not be resolved.
Action Internal error. Contact Oracle Customer Support.

BEA-180007 Error: Unable to register the resource with transaction manager: se
Description Unable to register the resource with transaction manager.
Cause WTC is not running with server transaction manager.
Action Contact Oracle Customer Support.

BEA-180008 Error: A transaction identifier exists for a non-existing domain accesspoint.
Description A transaction identifier exists for a non-existing remote Tuxedo domain.
Cause The remote Tuxedo domain involved in the transaction is no longer in the WTC configuration.
Action Manually correct the transaction or temporarily add the remote Tuxedo domain back to the configuration and wait for the transaction to complete, if the removal of the remote Tuxedo domain is intentional. Otherwise, add the Tuxedo domain back to the configuration.

BEA-180009 Error: Could not complete the execution for MBean named: mbname
Description The processing of the MBean configuration could not complete.
Cause The definition contains some input information that is not consistent with the usage model.
Action Check the MBean definition to see if the individual attributes are consistent with the rest of the MBean definitions.

BEA-180010 Error: Could not create a TDMLocalTDomain exceptioninfo
Description The TDMLocalTDomain constructor failed to create a new instance.
Cause The AccessPoint attribute definition for the WTCLocalTuxDom MBean is invalid.
Action Check the AccessPoint attribute of the WTCLocalTuxDom MBean.

BEA-180011 Error: Could not create a TDMRemoteTDomain exceptioninfo.
Description The TDMRemoteTDomain constructor failed to create a new instance.
Cause The AccessPoint attribute definition for the WTCRemoteTuxDom MBean is invalid.
Action Check the AccessPoint attribute of the WTCRemoteTuxDom MBean.

BEA-180012 Error: The LocalTDomain ltdname is not known.
Description Can not continue setting up the TDMRemote object because the LocalTDomain is not valid.
Cause The LocalAccessPoint attribute for the WTCRemoteTuxDom MBean is not a valid name for a LocalTDomain.
Action Verify the WTCRemoteTuxDom MBean definition has a valid name for the LocalAccessPoint Attribute.

BEA-180013 Error: The LocalTDomain ltdname is not known.
Description Can not continue setting up the TDMExport object because the LocalTDomain is not valid.
Cause The LocalAccessPoint attribute for the WTCExport MBean is not a valid name for a LocalTDomain.
Action Verify the WTCExport MBean definition has a valid name for the LocalAccessPoint Attribute.

BEA-180014 Error: Could not create a TDMExport exceptioninfo.
Description The TDMExport constructor failed to create a new instance.
Cause The ResourceName attribute definition for the WTCExport MBean is invalid or the LocalTDomain is not usable.
Action Check the ResourceName attribute of the WTCExport MBean.

BEA-180015 Error: The LocalTDomain ltdname is not known.
Description Can not continue setting up the TDMImport object because the LocalTDomain is not valid.
Cause The LocalAccessPoint attribute for the WTCImport MBean is not a valid name for a LocalTDomain.
Action Confirm the WTCImport MBean definition has a valid name for the LocalAccessPoint Attribute.

BEA-180016 Error: The RemoteTDomain rtdname is not known.
Description Can not continue setting up the TDMImport object because the RemoteTDomain is not valid.
Cause The RemoteAccessPointList attribute for the WTCImport MBean does not contain a valid name for a RemoteTDomain.
Action Verify that the WTCImport MBean definition has valid names, a comma separated list, defined in the RemoteAccessPointList Attribute.

BEA-180017 Error: Could not create a TDMImport exceptioninfo.
Description The TDMImport constructor failed to create a new instance.
Cause The ResourceName attribute definition for the WTCImport MBean is invalid. The LocalTDomain or the RemoteTDomains are not usable.
Action Check the ResourceName attribute of the WTCImport MBean.

BEA-180018 Error: Missing passwordType Password or PasswordIV information.
Description passwordType Password and IV are both needed to generate correct information.
Cause The Password or PasswordIV attribute is not set.
Action Verify that the Password and PasswordIV attributes are valid.

BEA-180019 Error: The LocalTDomain ltdname is not known.
Description Can not continue setting up the TDMPasswd object because the LocalTDomain is not valid.
Cause The LocalAccessPoint attribute for the WTCPassword MBean is not a valid name for a LocalTDomain.
Action Verify that the WTCPassword MBean definition has a valid name for the LocalAccessPoint Attribute.

BEA-180020 Error: The RemoteTDomain rtdname is not known.
Description Can not continue setting up the TDMImport object because the RemoteTDomain is not valid.
Cause The RemoteAccessPoint attribute for the WTCPassword MBean is not a valid name for a RemoteTDomain.
Action Verify that the WTCPassword MBean definition has a valid name for the RemoteAccessPoint Attribute.

BEA-180021 Error: Could not create a TDMPasswd exceptioninfo.
Description The TDMPasswd constructor failed to create a new instance.
Cause The LocalTDomain or the RemoteTDomain is not usable.
Action Check the LocalAccessPoint and RemoteAccessPoint attributes of the WTCPassword MBean.

BEA-180022 Error: Could not set up thefield table information for TDMResources: exceptioninfo.
Description An unsuccessful attempt was made to set up a FldTbls array using the WTCResources MBean.
Cause The fully qualified name for any field table may be incorrect or it can not be found.
Action Check the FldTblClass definitions of the WTCResources MBean and verify that the fully qualified name given is correct, that it is consistent with the current CLASSPATH usage, and that the system is able to access it.

BEA-180023 Error: Commit of xid failed with status xae.
Description WTC failed to commit the transaction with status xae.
Cause The transaction became a heuristic hazard, or the resource manager encountered an error.
Action Correct the transaction manually if it became a heuristic hazard, or correct the resource manager problem.

BEA-180024 Error: Unable to reply to unknown transaction with exception caught: tpe.
Description Failed to send a reply to remote Tuxedo domain for a transaction that WTC no longer knows about.
Cause The connection to the remote Tuxedo domain already terminated, or an IOException occurred while writing to the network.
Action If the TPException is TPEPROTO, then try to reboot the remote Tuxedo domain. If the TPException is TPESYSTEM, then check the network connection.

BEA-180025 Error: Unknown field type requested fieldtype.
Description The field type being used is not one that is defined in the TypedFML Class.
Cause TypedFML32 data is possibly being used instead of TypedFML.
Action Verify the type of input data.

BEA-180026 Error: While trying to use FML data, caught this Ferror exception: exceptioninfo
Description While trying to use FML data, caught this Ferror exception: exceptioninfo
Cause The data was not created correctly.
Action Verify the data passed into this method.

BEA-180027 Error: While trying to use FML data, caught an Unknown exception: exceptioninfo
Description While trying to use FML data, caught an Unknown exception: exceptioninfo
Cause The data was not created correctly.
Action Verify the data passed into this method.

BEA-180028 Error: Unknown field type requested fieldtype.
Description The field type being used is not one that is defined in the TypedFML32 Class.
Cause Possibly TypedFML data is being used instead of TypedFML32.
Action Verify the type of input data.

BEA-180029 Error: Caught this Ferror exception: exceptioninfo. Additional exception info found: exceptiondetail
Description Caught an Ferror exception while processing TypedFML32 data.
Cause The data was not created correctly.
Action Verify the data passed into this method.

BEA-180030 Error: While trying to use FML32 data, caught an Unknown exception: exceptioninfo
Description While trying to use FML32 data, caught an Unknown exception: exceptioninfo
Cause The data was not created correctly.
Action Verify the data passed into this method.

BEA-180031 Error: Xml argument is null.
Description Xml argument is null.
Cause Did not initialize argument passed in.
Action Check the xml argument passed in.

BEA-180032 Error: The FldTbl[] input argument is null or an empty array.
Description The FldTbl[] input argument is null or an empty array.
Cause Did not initialize argument passed in.
Action Check the FldTbl[] argument passed in.

BEA-180033 Error: TypedFML argument is null.
Description TypedFML argument is null.
Cause Did not initialize argument passed in.
Action Check the TypedFML argument passed in.

BEA-180034 Error: Error occurred while searching xmlinput for the document root element.
Description An error occurred while searching for the document root element in the XML input string.
Cause The input XML string was not formatted correctly.
Action Check for other errors listed that should indicate what was unacceptable about the XML input.

BEA-180035 Error: TypedFML32 argument is null.
Description TypedFML32 argument is null.
Cause Did not initialize argument passed in.
Action Check the TypedFML32 argument passed in.

BEA-180036 Error: XML input xmlinput caused SAX parser exception exceptioninfo
Description XML input xmlinput caused SAX parser exception exceptioninfo
Cause The DOM parser did not like the XML string that it received.
Action Check the SAX exception info returned and the XML string entered.

BEA-180037 Error: XML input xmlinput caused IO exception exceptioninfo.
Description XML input xmlinput caused IO exception exceptioninfo.
Cause The XML string was not convertible to an InputSource() class.
Action Check the IO exception info returned and the XML string entered.

BEA-180038 Error: XML input xmlinput caused an unknown exception exceptioninfo.
Description XML input xmlinput caused an unknown exception exceptioninfo.
Cause The XML string was not able to be parsed.
Action Check the exception info returned and the XML string entered.

BEA-180039 Error: The DOM parser returned a null value for input xmlinput.
Description The DOM parser returned a null value for input xmlinput.
Cause The input may not be a valid XML string.
Action Check the string passed to the parser.

BEA-180040 Error: Could not get a top document element from input xmlinput.
Description Parser could not return the top element of the document tree that represents the start of the XML input.
Cause The XML input does not have any elements defined.
Action Verify that the input string has a proper definition for a root element.

BEA-180041 Error: Could not get a tag name for the root element in XML input xmlinput.
Description Could not get a tag name for the root element in XML input xmlinput.
Cause The XML input does not have a tag name for the root element.
Action Verify that the root element has a proper definition.

BEA-180042 Error: Internal TypedFML data is null.
Description Internal TypedFML data is null.
Cause Did not initialize internal data using XMLtoFML() API.
Action Use XMLtoFML to initialize internal data.

BEA-180043 Error: Xml element name is null.
Description Xml element name is null.
Cause The XML element information was not properly defined
Action Check the XML element definition.

BEA-180044 Error: XML element value is null for the element name xmltagname.
Description XML element value is null for the element name xmltagname.
Cause The XML element information was not properly defined.
Action Check the XML element definition.

BEA-180045 Error: Internal TypedFML32 data is null.
Description Internal TypedFML32 data is null.
Cause Did not initialize internal data using XMLtoFML32() API.
Action Use XMLtoFML32 to initialize internal data.

BEA-180046 Info: debuginfo
Description Uncatalogued debug message. Do not change.
Cause Debugging. Do not change.
Action No action required.

BEA-180047 Error: tBridge must have at least one redirect command.
Description The tBridge must be given at least one redirect command; otherwise it has nothing to do.
Cause Improper configuration of the tBridge.
Action User must configure at least one redirect command in the WTC_CONFIG for the tBridge section.

BEA-180048 Error: tBridge cannot find the TuxedoConnectionFactory.
Description The JNDI lookup for the TuxedoConnectionFactory has failed.
Cause The WTC has not be properly configured.
Action Review the WTC documentation and restart the WTC.

BEA-180049 Error: tBridge cannot locate the WLXT option for translation.
Description The tBridge was told to use the WLXT translator. However, this option could not be located.
Cause The WLXT package might not be loaded or in the proper CLASSPATH.
Action Install the WLXT and properly configure the translator option.

BEA-180050 Error: tBridge internal FML/XML conversion failed.
Description The internal tBridge FML/XML translator has failed to convert the buffer.
Cause The syntax of the incoming message could not be understood.
Action Correct the message syntax and retry.

BEA-180051(retired) Warning: Unable to cancel ON_STARTUP connection retry.
Description This message no longer used.
Cause This message no longer used.
Action This message no longer used.

BEA-180052 Error: Unable to cancel ON_STARTUP connection retry due to: exceptioninfo.
Description Unable to cancel open connection retry object for ON_STARTUP connection policy.
Cause Unable to delete timer service object for ON_STARTUP connection policy during connection termination.
Action Contact Oracle Customer Support.

BEA-180053 Error: Failure occurred during token creating token_token_type.
Description An internal error occurred while trying to create security token.
Cause Internal error.
Action Contact Oracle Customer Support to report this problem with token type information found in the log message.

BEA-180054 Error: Failure occurred while reading the received Domain security token_token_type.
Description An internal error occurred while reading the received security token.
Cause Internal error.
Action Contact Oracle Customer Support to report this problem with token type information found in the log message.

BEA-180055 Error: Received unexpected token type, error information(token_type, error_type, data)
Description Received a token that WTC does not expect to receive or that contains incorrect information.
Cause The cause can be that WTC communicates with a newer version of the TDomain protocol or unknown alien protocol, or a breach of security attempt is being detected.
Action Verify who is trying to connect to this WTC and determine whether there is a security violation or need to upgrade WTC to newer version.

BEA-180056 Error: atntd(1) crypto error: exceptioninfo
Description Encountered error during encryption.
Cause Not enough free memory space to continue, or internal error.
Action Try to force garbage collection, and remove some services to reduce memory usage. If the problem persists, contact Oracle Customer Support.

BEA-180057 Error: Invalid return challenge.
Description The challenge returned by remote Tuxedo domain is not valid.
Cause This is caused by an incorrect configuration and mismatched password.
Action Correct the configuration and the password.

BEA-180058 Error: atntd(3) io error: exceptioninfo
Description Encountered IO operation error while doing encryption.
Cause Internal system error.
Action Contact Oracle Customer Support.

BEA-180059 Error: atntd(2) crypto error: exceptioninfo
Description Encountered error during encryption.
Cause Not enough free memory space to continue or internal error.
Action Try to force garbage collection, and remove some services to reduce memory usage. If problem persists, contact Oracle Customer Support.

BEA-180060(retired) Error: Invalid type (type) or subtype (subtype) string for hint.
Description Received an invalid user data buffer type or subtype.
Cause Unsupported buffer type or subtype.
Action Correct the application buffer type to use the supported buffer type or subtype.

BEA-180061(retired) Error: _tmpostrecv failed: hint
Description Failed to do post receive processing on the user data.
Cause It could be memory allocation failure, or the field ID for the FML, FML32 does not exist in the class file.
Action Check the class file and system memory usage.

BEA-180062(retired) Error: Received a buffer of unknown type: hintindex.
Description This message no longer used.
Cause This message no longer used.
Action This message no longer used.

BEA-180063 Error: Invalid handler address length: length.
Description The handler address length is not the same as expected.
Cause The client did not talk to a valid listener.
Action Check the listener address and correct the configuration.

BEA-180064(retired) Error: Unable to decode WSRPCRQ due to exception: exceptioninfo.
Description This message no longer used.
Cause This message no longer used.
Action This message no longer used.

BEA-180065(retired) Error: Unable to decode WSINIT_RP due to exception: exceptioninfo.
Description This message no longer used.
Cause This message no longer used.
Action This message no longer used.

BEA-180066(retired) Error: Unable to decode initial integer discriminator. Caught exception: exceptioninfo
Description This message no longer used.
Cause This message no longer used.
Action This message no longer used.

BEA-180067 Error: WSRPCRQ discrim descrim is invalid.
Description Invalid WSRPCRQ discriminator.
Cause Client is not talking to a valid handler.
Action Check the configuration and correct the error.

BEA-180068 Error: Invalid WSRPCRQ type type.
Description The type of discriminator is not supported.
Cause Client is not talking to a valid handler.
Action Check the configuration and correct it.

BEA-180069 Error: Unable to read type. Caught exception: exceptioninfo.
Description Unable to read data in the buffer type type.
Cause General IO exception.
Action Please read the exception description to determine the actual cause and act accordingly.

BEA-180070 Warning: TypeFML32 got a pointer of unknown type type. Will replace with null.
Description TypeFML32 got a pointer of unknown type type. Will replace with null.
Cause Incorrectly written application with unknown data type.
Action Correct the problem with the data type in the application.

BEA-180071 Warning: Invalid Typed FML32 field fieldno. Equals null.
Description Invalid Typed FML32 field fieldno. Equals null.
Cause Incorrectly constructed embedded FML32 buffer in the FML32 buffer.
Action Check the source of the embedded FML32 buffer, and correct the problem.

BEA-180072 Debug: +++++ title(arraylength) +++++
Description Marker to indicate start of debugging for TDumpByte.
Cause Debugging. Do not change.
Action No action required.

BEA-180073 Debug: +++++ END +++++
Description Marker to indicate end of debugging for TDumpByte.
Cause Debugging. Do not change.
Action No action required.

BEA-180074 Error: tpinit buffer not received.
Description tpinit buffer not received.
Cause The server is likely talking to an invalid handler.
Action Check the configuration and correct the problem.

BEA-180075 Error: Invalid receive size recvsize.
Description The received transaction data is smaller than expected.
Cause Remote Tuxedo Domain Gateway is not valid.
Action Check the configuration of the remote Tuxedo domain and correct the error.

BEA-180076 Error: Unable to format password. Caught exception: exceptioninfo.
Description Caught IO exception while formating password.
Cause An I/O error occurred.
Action Check for system memory usage and see if force garbage collection is possible. If problem persists, contact Oracle Customer Support.

BEA-180077 Error: Unable to close domain socket. Caught exception: exceptioninfo.
Description Caught IO exception while closing the connection to remote Tuxedo domain.
Cause An I/O error occurred while closing the socket.
Action Check your network and system environment. If problem persists, contact Oracle Customer Support.

BEA-180078 Warning: Dropping OWS_AREPLY on ground.
Description Could not find the handle for ACALL reply.
Cause The ACALL request already timed out.
Action This message is informational only.

BEA-180079 Error: rsession.run read_tfmh failed.
Description Failed to properly receive message header.
Cause The received message header is not properly formatted or failed to decompress the data.
Action Check the configuration of the remote Tuxedo domain and correct any problem in the configuration. Make sure you are talking to a supported version of remote Tuxedo domain. Also, check the network for possible network dropping of the packet. If problem persists, contact Oracle Customer Support.

BEA-180080 Error: rsession.run tmmsg.ws not provided.
Description The received message header is missing the required WebLogic Server information.
Cause Not talking to a valid remote Tuxedo domain.
Action Check the remote Tuxedo domain configuration and correct the problem.

BEA-180081 Error: Unexpected close on rsession socket. Caught exception: exceptioninfo
Description Caught I/O exception while processing the message header.
Cause An I/O error occurred while reading the message header from input stream.
Action Check system memory usage and force garbage collection. If problem persists, contact Oracle Customer Support.

BEA-180082 Error: Unable to close wsh socket. Caught exception: exceptioninfo.
Description Caught I/O exception and unable to close WSH socket by client.
Cause An I/O error occurred.
Action Check the network and system configuration.

BEA-180083 Error: Unknown TCM type received: tcmtype.
Description Received a TCM with an unsupported buffer type tcmtype.
Cause WTC is communicating with an unsupported Tuxedo version.
Action Check the configuration and correct the error.

BEA-180084 Error: Unable to write TCM. Caught exception: exceptioninfo.
Description Caught I/O exception while writing TCM to output data stream.
Cause An I/O error occurred.
Action Check the system memory usage and force garbage collection.

BEA-180085 Error: Unable to send unsolicited acknowledgment. Caught exception: exceptioninfo.
Description Caught I/O exception while writing an unsolicited acknowledgment to data output staream.
Cause An I/O error occurred.
Action Check system memory usage.

BEA-180086 Info: Accepted Connection from remote domain domid.
Description Connection to remote domain established.
Cause Connection request was received from a remote domain.
Action No action required.

BEA-180087 Info: Established a connection to a remote domain domid.
Description Connection to a remote domain established.
Cause Initiate the connection request to a remote domain.
Action No action required.

BEA-180088 Error: Error occurred while building mtype message.
Description Error encountered during build of outgoing message.
Cause This is an internal error.
Action Contact Oracle Customer Support.

BEA-180089 Error: Error occurred while decoding mtype message.
Description Error encountered during decoding of incoming message.
Cause This is an internal error.
Action Contact Oracle Customer Support.

BEA-180090 Error: Remote domain domid rejected the connection request.
Description Remote domain detected an authentication failure and rejected the connection request.
Cause User configuration error.
Action Check both side configurations to see whether a mismatch exists in the configuration, including the password.

BEA-180091 Error: Rejected remote domain domid connection request.
Description Local domain detected an authentication failure and rejected the connection request.
Cause User configuration error.
Action Check both side configurations to see whether a mismatch exists in configuration, including the password.

BEA-180092 Error: Failed security validation with remote domain domid.
Description Security validation failed.
Cause User configuration error, unauthorized access.
Action Check both side configurations to see if a mismatch exists in the configuration, including password.

BEA-180093 Error: Naming exception occurred during lookup of the admin name: exceptioninfo.
Description A naming exception occurred during lookup of the admin name: exceptioninfo.
Cause The specified name can not be resolved.
Action Contact Oracle Customer Support.

BEA-180094 Error: tBridge failed to initialize JMS targetName queue.
Description The tBridge tried to locate and initialize the targetName queue, but an error was returned. The tBridge cannot continue.
Cause The JMS targetName queue does not exist or the JMS server is not running on the system.
Action Correct the JMS problem and restart the WTC tBridge.

BEA-180095 Error: The tBridge could not initialize the JMS sourceName queue.
Description A failure was reported from JMS during the initialization of the sourceName queue. This fromto thread of tBridge cannot continue.
Cause The sourceName queue can not exist in JMS or the JMS server may not be started.
Action Correct the JMS problem and restart the WTC tBridge.

BEA-180096 Error: The tBridge could not initialize the wlsErrorDestination JMS queue.
Description The tBridge received an error during initialization of the JMS wlsErrorDestination queue. The tBridge will continue, but this could result in the loss of message data.
Cause The JMS wlsErrorDestination queue may not be properly configured in WebLogic Server.
Action Correct the JMS problem and restart the WTC tBridge.

BEA-180097 Error: Due to a translation error, tBridge has redirected the message to the wlsErrorDestination.
Description The tBridge encountered a translation error and has redirected the message to the wlsErrorDestination queue.
Cause The cause of this error is a translation error detected from/to FML/XML.
Action Correct the message structure and resend the message.

BEA-180098 Error: The tBridge failed to send the message to wlsErrorDestination.
Description The tBridge failed to send the message that generated the error to the wlsErrorDestination. The message remains unacknowledged on the JMS input queue.
Cause The JMS wlsErrorDestination could be full or paused.
Action Recover the message from the sourceName JMS queue and resend.

BEA-180099 Error: The MinEncryptionBits is greater then MaxEncryptionBits in type domain id.
Description The configured MinEncryptionBits is greater than MaxEncryptionBits.
Cause User configuration error.
Action Use WebLogic Server console to modify WTC configuration so that it will use the correct values for Min and Max Encryption Bits.

BEA-180100 Error: Configuration Error: detail
Description Bad configuration information found.
Cause User configuration error.
Action Use WebLogic Server console to modify WTC configuration so that it will use the correct values for the corresponding error.

BEA-180101(retired) Error: At least one local domain must be defined.
Description No local domain is defined in this configuration.
Cause User configuration error.
Action Use WebLogic Server console to modify WTC configuration to add at least one local domain.

BEA-180102 Error: Duplicated local domain ID ldomid found.
Description Bad configuration information. Contains two local domains having the same ID.
Cause User configuration error.
Action Use WebLogic Server console to modify WTC configuration to use the unique ID for the local domain.

BEA-180103 Error: There are two remote domain rdomid with same local domain ldomid.
Description Bad configuration information found in the WTC configuration.
Cause User configuration error.
Action Use WebLogic Server console to modify the WTC configuration to remove the redundant entry or correct the configuration information.

BEA-180104 Error: Unsupported JMS message type.
Description The tBridge only supporters the JMS TextMessage and BytesMessage. All other types are rejected and not redirected to the error destination.
Cause The user has sent a JMS Stream or Mapped message type to the tBridge.
Action Correct the JMS message type and resend.

BEA-180105 Warning: A message has been dropped.
Description A message has been dropped by the WTC gateway. Other log messages should provide details on the reason the message was dropped.
Cause The most common cause of this failure is that an unrecognized buffer type has been received by the WTC gateway.
Action Modify the application to make sure that unknown buffer types are not sent to the WTC gateway.

BEA-180106 Error: Unable to find a transaction manager. Transaction recovery will not continue.
Description While attempting to recover transactions from Tuxedo into WebLogic Server, the system was unable to find the WebLogic Server transaction manager.
Cause A transaction manager could not be found.
Action Contact Oracle Customer Support.

BEA-180107 Warning: While attempting to recover transactions, the recover method failed.
Description While attempting to recover transactions, the recover method failed.
Cause The recover method on the WLS XA Resource threw an exception.
Action Contact Oracle Customer Support.

BEA-180108 Warning: WebLogic Server rollback had a failure: exception.
Description While attempting to recover transactions, the rollback method failed.
Cause The rollback method on the WLS XA Resource threw an exception.
Action Contact Oracle Customer Support.

BEA-180109 Error: Internal FML to XML conversion failed.
Description The message from Tuxedo /Q has been received. However, the translation from FML into XML has failed. The transaction has been rolled back, and the message remains in the Tuxedo queue.
Cause The FML buffer received from Tuxedo contained field buffer names that were not provided to WTC. Therefore, the name translation failed.
Action Verify that the field tables have been properly transfered as described in the WTC documentation.

BEA-180110 Error: Internal FML32 to XML conversion failed.
Description The message from Tuxedo /Q has been received. However, the translation from FML32 to XML has failed. The transaction has been rolled back, and the message remains in the Tuxedo queue.
Cause The FML32 buffer received from Tuxedo contained field buffer names that were not provided to WTC. Therefore, the name translation failed.
Action Verify the field tables have been properly transferred as described in the WTC documentation.

BEA-180111 Error: Internal FML to XML conversion failed.
Description The message from the Tuxedo service has been received. However, the translation from FML to XML has failed. The original message has been redirected to the designated JMS error queue.
Cause The FML buffer received from Tuxedo contained field buffer names that were not provided to WTC. Therefore, the name translation failed.
Action Verify the field tables have been properly transferred as described in the WTC documentation.

BEA-180112 Error: Internal FML32 to XML conversion failed.
Description The message from the Tuxedo service has been received. However, the translation from FML32 to XML has failed. The original message has been redirected to the designated JMS error queue.
Cause The FML32 buffer received from Tuxedo contained field buffer names that were not provided to WTC. Therefore, the name translation failed.
Action Verify the field tables have been properly transferred as described in the WTC documentation.

BEA-180113 Debug: msg
Description The message is for debug tracing.
Cause The message is for debug tracing.
Action No action is required.

BEA-180114(retired) Error: Could not set up VIEW information for TDMResources: exceptioninfo.
Description An unsuccessful attempt was made to setup a VIEW table array for the WTCResources MBean.
Cause The fully qualified name for any VIEW table may be incorrect or it can not be found.
Action Check the ViewTblClass definitions of the WTCResources MBean and verify that the fully qualified name given is correct, that it is consistent with the current CLASSPATH usage, and that the system is able to access it.

BEA-180115 Error: The tBridge cannot parse the configuration MBeans: exceptionInfo.
Description The startup configuration for tBridge contained in the WTCtBridgeGlobal and WTCtBridgeRedirect MBeans could not be understood.
Cause The MBeans for tBridge contain invalid attributes.
Action Correct the attribute definitions for the tBridge MBeans.

BEA-180116 Error: The field table type specified tbltype is incorrect.
Description The FldTblClass type used is not one of the valid types, fml16 or fml32, allowed.
Cause The WTCStartup.getFldTbls() method was called with an invalid argument.
Action Verify that the Type argument for this is either "fml16" or "fml32".

BEA-180117 Error: The encoding encode is not supported. Java VM default encoding is used.
Description The encoding encode is not supported. Java VM default encoding is used.
Cause Specified encoding name is not supported.
Action Correct the encoding name and restart WebLogic Server.

BEA-180118 Error: Failed to find TPUSR file: fname.
Description The configured TPUSR file fname does not exist.
Cause The specified file TPUSR file does not exist.
Action Correct the configuration by specifying the correct TPUSR file or create it before using it.

BEA-180119 Error: The filename given is not a valid file: fname
Description The configured TPUSR file fname is not a file.
Cause Incorrect WTC TPUSR file configuration.
Action Correct the WTC TPUSR file configuration.

BEA-180120 Error: The file fname is not readable.
Description User does not have permission to read file fname.
Cause User does not have the read permission to read the configured TPUSR file.
Action Change the permissions of the TPUSR file.

BEA-180121 Error: Can not find file fname.
Description The file fname does not exist.
Cause The configured WTC TPUSR file does not exist.
Action Correct the WTC TPUSR file configuration or create the file.

BEA-180122 Error: No permission to read the file fname.
Description User does not have the permission to read the file fname.
Cause User does not have the read permission to read the configured TPUSR file.
Action Change the permissions of the TPUSR file.

BEA-180123 Error: File IO error for file fname, reason: detail.
Description Encountered file IO error while reading file fname.
Cause Corrupted or deleted file.
Action Correct the file corruption, or use a new TPUSR file.

BEA-180124 Error: The number given is not a valid number format: number
Description The configured cache size is not in a valid number format.
Cause The configured cache size is not in a valid number format.
Action Correct the configuration in WTC TpUsrFile.

BEA-180125(retired) Error: LDAP Exception: e, h:p.
Description An exception occurred while trying to connect to the LDAP server (h:p>.
Cause The default WebLogic Server LDAP server is not available.
Action Correct the WebLogic Server configuration with the default BEA WebLogic Server security manager.

BEA-180126(retired) Info: LDAPException: e
Description LDAP exception occurred while disconnecting from LDAP server.
Cause The connection to LDAP server may be gone.
Action Verify whether the WebLogic Server embedded LDAP server is still functioning.

BEA-180127(retired) Error: The value number is not a valid number format for TUXEDO UID.
Description The configured UID is not in valid number format.
Cause The configured TUXEDO UID is not in valid number format.
Action Correct the configuration in the WebLogic Server user description.

BEA-180128(retired) Error: WebLogic Server user u record is missing Tuxedo UID information.
Description The configured Tuxedo user u does not contain keyword/value pair for describing Tuxedo UID.
Cause The configured WebLogic Server user does have the required keyword/value pair for Tuxedo UID.
Action Add the proper keyword/value pair for UID to the WebLogic Server user description field.

BEA-180129(retired) Error: The WebLogic Server user u record is missing Tuxedo GID information.
Description The configured Tuxedo user u does not contain keyword/value pair for describing Tuxedo GID.
Cause The configured WebLogic Server user does have the required keyword/value pair for Tuxedo GID.
Action Add the proper keyword/value pair for GID to the WebLogic Server user description field.

BEA-180130(retired) Error: The value number is not a valid number format for TUXEDO GID.
Description The configured GID is not in valid number format.
Cause The configured TUXEDO GID is not in valid number format.
Action Correct the configuration in the WebLogic Server user description.

BEA-180131(retired) Error: LDAP search exception: e
Description Exception occurred during LDAP search operation.
Cause The embedded LDAP server is not available.
Action Make sure the default WebLogic Server embedded LDAP server is running.

BEA-180132 Error: Custom AppKey generator class c not found.
Description The specified custom AppKey c can not be found.
Cause The configured custom AppKey class full path name is incorrect.
Action Make sure the configuration is correct and that the custom class exists.

BEA-180133 Error: AppKey plug-in initialization failed. Reason: e
Description The configured AppKey generator plug-in failed during initialization. Reason: e
Cause The most likely reason is that the user database is not available or the initialization parameter is incorrect.
Action Make sure that the user database is available and the configuration is correct.

BEA-180134 Error: Create new AppKey class e instance failed.
Description Create new AppKey class e instance failed.
Cause Either the class is not accessible, there is no permission to create a new instance of this class, or the class is not good.
Action Make sure the class is accessible with the correct permission. Also, the class must be based on the weblogic.wtc.jatmi.AppKey interface.

BEA-180135(retired) Error: Was not able to set the attrname attribute on the srvrmbname WTCServerMBean.
Description Got an InvalidAttributeValueException when trying to set the attrname attribute on the srvrmbname WTCServerMBean.
Cause The names provided result in invalid MBean information.
Action Check that the WTCServerMBean name listed is created and valid.

BEA-180136 Error: The attrname attribute on the mbname MBean is undefined but required.
Description Was not able to get the attrname attribute value from the mbname MBean.
Cause The attribute value is not defined but must be.
Action Check that the MBean attribute is set correctly.

BEA-180137 Error: The attrname attribute on the mbname MBean is set incorrectly.
Description The value of the attrname attribute from the mbname MBean is not valid.
Cause The attribute was defined improperly.
Action Check that the MBean attribute is set correctly.

BEA-180138 Error: The mbname MBean appears to contain previous defined import service info.
Description The mbname MBean appears to be a duplicate of previous import service info.
Cause The attributes defined on this MBean have already been used to defined and imported service.
Action Check that the Resourcename,RemoteAccessPointList, and LocalAccessPoint attributes arent all duplicated in another Import MBean.

BEA-180139 Error: A mbtype type MBean is not defined but is required to be.
Description A mbtype type MBean is not defined but is required to be.
Cause An MBean was not defined but is needed.
Action Check that an MBean type specified is defined in the configuration.

BEA-180140 Debug: Security: msg
Description Debug message concerning the security of sent and received TGIOP messages.
Cause Internal debug.
Action None.

BEA-180141 Error: Message header contains invalid magic number, connection closed.
Description The message header contains invalid magic number, close the connection.
Cause Either received invalid TDOMAIN PDU, or the remote domain gateway does not have network encoding enabled.
Action Make sure the locale access point is configured with the correct port number, and the remote gateway does not have the same MTYPE configured for this TDOMAIN session.

BEA-180142 Error: Local domain accessPtId in use. Cannot be deleted.
Description Local domain is referenced by another resource. It cannot be deleted.
Cause User configuration error.
Action Check for remote domains, imported or exported services or passwords that use this local domain.

BEA-180143 Error: Cannot find local domain accessPtId.
Description Cannot find local domain with the given access point name.
Cause User configuration error.
Action Check access point name.

BEA-180144 Error: Duplicate remote domain accessPtId. Cannot add.
Description Cannot add remote domain. Duplicate access point name.
Cause User configuration error.
Action Check access points and access point ids for existing domains.

BEA-180145 Error: Remote domain accessPtId in use. Cannot delete.
Description The remote domain is referenced by another resource or has an active connection. It cannot be deleted.
Cause User configuration error.
Action Shut down the connection to this remote domain. Check other resources that may reference this domain.

BEA-180146 Error: Remote domain accessPtId cannot be found.
Description The specified remote domain cannot be found.
Cause User configuration error.
Action Check the access point name for the remote domain.

BEA-180147 Error: Cannot find imported service resourceName.
Description Cannot find the specified imported service.
Cause User configuration error.
Action Check the name of the imported service.

BEA-180148 Error: Cannot find exported service resourceName
Description Cannot find specified exported service.
Cause User configuration error.
Action Check name of exported service.

BEA-180149 Error: Cannot find password entry mbName.
Description Cannot find specified password entry.
Cause User configuration error.
Action Check local and remote access point names.

BEA-180150 Error: Connection policy for rAccessPointId is INCOMING_ONLY.
Description Cannot start an outbound connection when the connection policy specifies INCOMING_ONLY.
Cause User error.
Action Check the access point id for the remote domain.

BEA-180151 Emergency: Cannot modify resource ResourceName. It may be in use.
Description Cannot modify resource. One of its associated domains has an active connection.
Cause There is an active connection that may use this resource.
Action Stop connections associated with this resource before attempting to delete.

BEA-180152 Error: Registration of notification listeners for the configured MBeans has failed.
Description Registration of notification listeners for the configured MBeans has failed.
Cause Internal system error.
Action Internal system error. Contact Oracle Customer Support.

BEA-180153 Warning: No valid host Inet address for WTC Remote Access Point rap.
Description There is no valid host internet address for WTC initiated outbound connection for the specified remote access point.
Cause configuration error.
Action Correct the WTC Remote Access Points network address list.

BEA-180154 Warning: No valid listening address configured for local access point lap.
Description There is no valid listening address configured for local access point.
Cause Internal system error.
Action Internal system error. Contact Oracle Customer Support.

BEA-180155 Warning: No more valid network address for TDomain session (lap, rap) to try to connect.
Description No more valid network address to use to connect from the specified local access point to the remote access point.
Cause Either there is a configuration error or the remote access point is not available, and can not be accessed using the configured information.
Action Correct the configuration, or boot the remote access point.

BEA-180156 Info: Failed to connect to remote access point(//host:port), try next address.
Description Connect to network address failed, will try the next address in the list.
Cause Either a configuration error, or the remote access point is not available at the address specified.
Action This message is informational and it tells the user it will try next network address to connect.

BEA-180157 Warning: Failed to connect to remote access point(//host:port), no more address to try.
Description Connect to network address failed, there is no more network address in the list for this remote access point to try.
Cause Either a configuration error, or the remote access point is not available at the address specified.
Action This message is warning, correct configuration or make the remote access point available.

BEA-180158 Warning: No more valid network address for load access point lap to listen.
Description No more valid network address to use to listen for the specified local access point.
Cause There is a configuration error.
Action Correct the configuration.

BEA-180159 Info: Failed to listen for local access point lap on address (//host:port), try next address.
Description Failed to create network address listening endpoint, will try the next address in the list.
Cause Either a configuration error, or simply as it is intended.
Action This message is informational and it tells the user it will try next network address to create listening endpoint.

BEA-180160 Warning: Failed to create listening endpoint for local access point lap on address (//host:port), no more address to try.
Description Create listening using the specified network address failed, there is no more network address in the list for this local access point to try.
Cause A configuration error.
Action Correct configuration.

BEA-180161 Error: Failed to find imported service for QSpace qspace, tBridge has redirected the message to the wlsErrorDestination.
Description The tBridge failed to find the imported service that represents the QSpace in Tuxedo domain.
Cause Incorrectly configured WTC Import.
Action Correct the configuration.

BEA-180162 Error: Cannot find imported service import, tBridge has redirected the message to the wlsErrorDestination.
Description The tBridge failed to find the requested Tuxedo service in WTC import service configuration.
Cause The cause of this error is a configuration error.
Action Correct the configuration.

BEA-180163 Error: Received Tuxedo reply uses the unsupported buffer type type, tBridge has redirected the message to the wlsErrorDestination.
Description The tBridge received the reply with unsupported buffer type from Tuxedo server.
Cause Tuxedo server returned reply with unsupported buffer type.
Action Modify the Tuxedo server to return the reply with WTC supported buffer type.

BEA-180164 Error: Failed to send message to JMS, tBridge has redirected the message to the WLSErrorDestination.
Description The tBridge encountered a JMS problem while sending message to JMS.
Cause The JMS replyQ is configured incorrectly.
Action Correct the configuration of the JMS queue to be used for tBridge reply queue.

BEA-180165 Info: TDomain session (ldom, rdom) disconnected because no KeepAlive Acknowledge received!
Description The TDomain session between specified local access point and remote access point became idle and exceeded the time allowed by the keep alive feature that is configured. And the keep alive feature exceeded the wait limit without receiving acknowledge so the connection is terminated.
Cause It is possible that there is a network outage.
Action Check the network connection between these two gateways whether it is connected.

BEA-180166 Warning: The remote gateway does not support Application Level KeepAlive, this feature is disabled for TDomain session (ldom, rdom)!
Description The TDomain session between specified local access point and remote access point is configured with optional KeepAlive. However, it is determined that remote gateway does not support Application KeepAlive feature so it is disabled.
Cause The remote gateway does not support this Application Level KeepAlive feature.
Action Update the remote gateway to a version of TUXEDO that support TDomain Application Level KeepAlive.

BEA-180167 Error: The imported resource res uses a TDomain session (ldom, rdom) that does not exist!
Description The imported resource is configured for a TDomain session between specified local access point and remote access point does not exist.
Cause Incorrectly configured imported resource.
Action Correct the configuration for the imported service.

BEA-180168 Error: A connection cannot be established between local domain ldom and remote domain rdom due to a problem with the local or remote password used to authenticate connections between these domains.
Description The WTCPasswordMbean did not contain valid passwords for the connection between the domains listed.
Cause Incorrectly configured domain passwords.
Action Encrypt correct local and remote passwords for the connection using the weblogic.wtc.gwt.genpasswd utility and use the results to configure a WTCPasswordMBean.

BEA-180169 Error: XA.end() failed: e
Description An error was encountered while closing the transaction branch.
Cause The transaction may have been marked ROLLBACK_ONLY
Action Inspect the application logic to find out the cause of the error.

BEA-180170 Error: Unexpected Exception while converting View s to XML: e
Description An error was encountered while processing the View buffer.
Cause Refer to the exception details.
Action Refer to the exception details.

BEA-180171 Warning: SSL Null ciphers are not enabled, will be upgrade to minimum 56 bits.
Description The SSL NULL ciphers are not enabled, but the WTC configuration requested it.
Cause The NULL cipher suites are disabled by SSL configuration.
Action User can ignore it since stronger encryption strength is allowed by WTC configuration, and also available by SSL. User can also choose to correct WTC configuration to use only 56 bits and stronger cipher suites or enable SSL NULL ciphers if that is desired.

BEA-180172 Error: SSL Null ciphers are not enabled.
Description The SSL NULL ciphers are not enabled, but the WTC configuration requires it.
Cause The NULL cipher suites are disabled by SSL configuration.
Action User must either enable the SSL NULL cipher suites explicitly, or changes WTC configuration to use stronger encryption cipher suites.

BEA-180173 Error: Invalid private key for identity alias alias from key store ks, detected by m
Description The SSL socket factory failed to get private key from key store.
Cause An invalid key store or the private key alias configure does not exist in the key store, or an incorrect private key store passphrase is configured.
Action Correct the key store or private key alias information in the configuration.

BEA-180174 Error: Invalid private key store fname, detected by m
Description The configured private key store either does not exist or is corrupted.
Cause The private key store configured does not exist, or is corrupted.
Action Correct the private key store configuration information.

BEA-180175 Error: Invalid trust certificate store fname, detected by m
Description The configured trust certificate store either does not exist or is corrupted.
Cause The private key store configured does not exist, or corrupted.
Action Correct the private key store configuration information.

BEA-180176 Error: Error occurred while retrieving trusted certificate from trust store fname, detected by m
Description Could not retrieve trust certificate from configured trust store.
Cause The configured trust certificate is corrupted or an incorrect passphrase is configured.
Action Correct the trust certificate store configuration information.

BEA-180177 Error: Error occurred while retrieving trusted certificates from WebLogic Server, detected by m
Description Could not retrieve trust certificates from WebLogic Server configured trust store.
Cause The configured trust certificate is corrupted or an incorrect passphrase is configured.
Action Correct the trust certificate store configuration information.

BEA-180178 Info: The requested encryption strength 256 bits of local access point m is not supported by LLE, downgrade to 128 bits.
Description The request minimum or maximum entryption strength is above the maximum supported LLE encryption strength, have to downgrade to use the maximum encryption strength supported by LLE and that is 128 bits.
Cause The configured encryption strength is not supported by Link Level Encryption.
Action Either change it to LLE supported strength or use SSL for connection privacy. LLE supports 0, 40, 56, and 128 bits encryption strength. SSL supports 0, 56, 128, and 256 bits encryption strength.

Copyright © 2007, 2009, Oracle Corporation and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
Oracle Fusion Middleware Oracle WebLogic Server Message Catalog
11g Release 1 (10.3.1)
Part Number E14397-01