![]() |
![]() |
|
|
100 |
ERROR: Bad Type Id TypeId. | |
|
Description |
The object reference is invalid or corrupted. Exception None. |
Action |
Re-create the repository or recover from a previous version. | |
103 |
ERROR: Transport error `TransportError'. | |
|
Description |
A transport error has occurred.
Exception |
Action |
Verify the operation of the transport. | |
104 |
ERROR: Specified arguments do not match defined arguments. | |
|
Description |
The arguments for the operation invocation do not match the arguments defined for the operation (that is, too many arguments, too few arguments, inconsistent data type or direction, and so on).
Exception |
Action |
Verify that the specified arguments match those defined for the operation. | |
105 |
ERROR: Specified method not found on implementation skeleton. | |
|
Description |
The specified method could not be called from the implementation invoke routine because the method was not found.
Exception |
Action |
Verify that the method is defined for the implementation, and that the correct servant is used for invocation. Regenerate the implementation skeleton if necessary. | |
108 |
ERROR: Unknown node `Node' specified. | |
|
Description |
An unregistered node name was specified.
Exception |
Action |
Make sure the node specified is registered. | |
109 |
ERROR: Dynamic load is not supported on this platform. | |
|
Description |
The platform does not support dynamic loading. |
Action |
Contact BEA Customer Support. | |
110 |
ERROR: The shared library `Name' could could not be dynamically loaded. | |
|
Description |
The ImagePath WLE registry parameter for a WLE loadable component or subsystem could not be dynamically loaded.
Exception |
Action |
Verify that the dynamic library can be loaded. Check privileges, system constraints, and so on. | |
111 |
ERROR: The specified server is already registered. | |
|
Description |
The server failed to connect because the requested socket was already in use. |
Action |
Restart the server, or contact BEA Customer Support. | |
112 |
ERROR: Bad dynamic library specification. | |
|
Description |
The name of the specified dynamic library is invalid.
Exception |
Action |
Verify the name and path for the dynamic library. | |
113 |
ERROR: The underlying transport could not be initialized. | |
|
Description |
The underlying transport (for example, TCP/IP) could not be initialized. Exception None. |
Action |
Verify the operation of the transport. Make sure that the appropriate software is installed and that it is running. | |
114 |
ERROR: An internal software error occurred. | |
|
Description |
An internal software error occurred. The operation was not completed.
Exception |
Action |
Contact BEA Customer Support. | |
115 |
ERROR: Bad object name `ObjectName'. | |
|
Description |
The specified object name is not a valid WLE object name (for example, illegal characters, bad format, too many characters, and so on).
Exception |
Action |
Specify a valid object name. | |
116 |
ERROR: Transport handle is invalid. | |
|
Description |
An unexpected transport error occurred. |
Action |
Contact BEA Customer Support. | |
117 |
ERROR: Transport level communication failed. | |
|
Description |
Communication to a server has failed. This failure, in many cases, is due to a timeout while a method is being completed.
Exception |
Action |
Check the server you are attempting to communicate with. In addition, verify the operation of the network. If the method is long running, try calling it asynchronously. | |
118 |
ERROR: The requested server was not found or is not accessible on the network. | |
|
Description |
The WLE software could not locate the requested server on the network.
Exception |
Action |
Verify that the server is running and is available on the network transport. | |
119 |
ERROR: Exceeded marshalling buffer. | |
|
Description |
The marshalling buffer was exceeded.
Exception |
Action |
Contact BEA Customer Support. | |
120 |
ERROR: The transport message was not properly identified. | |
|
Description |
The message received on the transport was not identified as a WLE message.
Exception |
Action |
Contact BEA Customer Support. | |
121 |
ERROR: Invalid argument. | |
|
Description |
This message occurs when an invalid argument is specified.
Exception |
Action |
Verify the arguments passed in. | |
122 |
ERROR: Specified result does not match defined result. | |
|
Description |
The result for the method invocation does not match the result defined for the method.
Exception |
Action |
Verify that the specified result matches that defined for the operation. | |
123 |
ERROR: String length is greater than the bound. | |
|
Description |
The length of the string exceeds the bound specified for the type in the OMG IDL statements.
Exception |
Action |
Verify the length. Either change the bound in the type definition in the OMG IDL statements or set the string to be of a length less than or equal to the bound. | |
124 |
ERROR: An invalid type was specified for an ANY argument. | |
|
Description |
An argument of type ANY was specified with an invalid type field.
Exception |
Action |
Verify the ANY argument. Make sure that the argument type is a valid typecode. | |
125 |
ERROR: Specified number of arguments do not match defined number of arguments. | |
|
Description |
The number of arguments for the invocation does not match the number of arguments defined for the operation.
Exception |
Action |
Verify that the number of specified arguments matches those defined for the operation. | |
126 |
ERROR: Specified argument name `ArgumentName' does not match defined argument name. | |
|
Description |
The name of the argument does not match the name of the argument defined for the operation.
Exception |
Action |
Verify that the names of the specified arguments match those defined for the operation. | |
127 |
ERROR: Specified argument type does not match defined argument type for `ArgumentName'. | |
|
Description |
The type of the argument does not match the type of the argument defined for the operation.
Exception |
Action |
Verify that the type of the specified argument matches that defined for the operation. | |
128 |
ERROR: TypeCode ID not found. | |
|
Description |
The TypeCode was not found in any of the TypeCode lookup routines. Without the TypeCode, the data cannot be marshaled or unmarshaled.
Exception |
Action |
Verify that the id is from a type or an exception known to the client or the server. If you are using DII instead of stubs, ensure that the TypeCode lookup routine has been registered. | |
129 |
ERROR: Transport level send timeout. | |
|
Description |
Communication between server and client has failed. This failure is due to a timeout that occurs while the client is attempting to send an invoke request or the server is attempting to send a reply to an invoked request.
Exception |
Action |
Check the client or server with which you are attempting to communicate. In addition, verify the operation of the network. If the method is long running, try invoking the method asynchronously. | |
130 |
ERROR: The object is constrained to be local. | |
|
Description |
An attempt was made to use an object that is constrained to be local in a context where nonlocal information is required.
Exception |
Action |
Do not use a local object for an operation that may require going across the wire. | |
132 |
INFO: No more items. | |
|
Description |
No keys or named values are available. Exception None. |
Action |
The enumeration of keys or named values has reached the end of the items. | |
133 |
ERROR: The registry key is invalid. | |
|
Description |
An unexpected error occurred while reading or writing the registry. |
Action |
Contact BEA Customer Support. | |
134 |
ERROR: Could not create key `val'. | |
|
Description |
An error occurred when writing the registry. |
Action |
Administrative privileges are required for administrative functions, such as reordering interceptors. Contact BEA Customer Support. | |
135 |
ERROR: Could not delete key `val'. | |
|
Description |
An error occurred when modifying the registry. |
Action |
Administrative privileges are required for administrative functions, such as reordering interceptors. Contact BEA Customer Support. | |
136 |
ERROR: Could not modify key `val'. | |
|
Description |
An error occurred when modifying `val' in the registry. |
Action |
Administrative privileges are required for administrative functions, such as reordering interceptors. Contact BEA Customer Support. | |
137 |
ERROR: Could not find key `val'. | |
|
Description |
An error occurred when looking up `val' in the registry. |
Action |
Check the spelling of the data being looked up (for example, the interceptor name). Contact BEA Customer Support. | |
138 |
ERROR: Could not create named value `val'. | |
|
Description |
An error occurred when creating a new value in the registry. |
Action |
Administrative privileges are required for administrative functions, such as reordering interceptors. Contact BEA Customer Support. | |
139 |
ERROR: Could not delete named value `val'. | |
|
Description |
An error occurred when modifying `val' in the registry. |
Action |
Administrative privileges are required for administrative functions, such as reordering interceptors. Contact BEA Customer Support. | |
140 |
ERROR: Could not modify named value `val'. | |
|
Description |
An error occurred when modifying `val' in the registry. |
Action |
Administrative privileges are required for administrative functions, such as reordering interceptors. Contact BEA Customer Support. | |
141 |
ERROR: Could not find named value `val'. | |
|
Description |
An error occurred when looking up `val' in the registry. |
Action |
Check the spelling of the data being looked up (for example, the interceptor name). Contact BEA Customer Support. | |
142 |
ERROR: Could not connect to `val' registry. | |
|
Description |
An unexpected error occurred when accessing the `val' registry. |
Action |
Contact BEA Customer Support. | |
143 |
ERROR: Access is denied. | |
|
Description |
The user does not have the privileges required for the access. |
Action |
Administrative privileges are required for administrative functions, such as reordering interceptors. Contact BEA Customer Support. | |
144 |
ERROR: Error closing key. | |
|
Description |
An unexpected error occurred when modifying the registry. |
Action |
The disk may be full. Contact BEA Customer Support. | |
145 |
ERROR: Subkeys for key are still open. | |
|
Description |
An unexpected error occurred while modifying the registry. |
Action |
Contact BEA Customer Support. | |
146 |
ERROR: The registry data is invalid for specified key. | |
|
Description |
An unexpected error occurred while modifying the registry. |
Action |
Contact BEA Customer Support. | |
147 |
ERROR: Registry `RegistryName' not found. | |
|
Description |
The specified registry partition was not found.
Exception |
Action |
Verify the registry partition name and that the registry partition exists. | |
149 |
ERROR: OA already exists. | |
|
Description |
Internal error only. An Object Adapter with the same name already exists.
Exception |
Action |
Contact BEA Customer Support. | |
150 |
ERROR: OA does not exist. | |
|
Description |
Internal error only. An Object Adapter with the specified name does not exist.
Exception |
Action |
Contact BEA Customer Support. | |
152 |
ERROR: OA not active. | |
|
Description |
Internal error only. An Object Adapter is not active.
Exception |
Action |
Contact BEA Customer Support. | |
153 |
ERROR: OA is suspended. | |
|
Description |
Internal error only. An Object Adapter is suspended.
Exception |
Action |
Contact BEA Customer Support. | |
154 |
ERROR: OA queue is too large. | |
|
Description |
An Object Adapter has exceeded the size of the internal queue.
Exception |
Action |
Contact BEA Customer Support. | |
155 |
ERROR: OA object not found. | |
|
Description |
An Object Adapter object ID was not found.
Exception |
Action |
Ensure that the Object is active in the server. | |
156 |
ERROR: OA Servant not active. | |
|
Description |
Internal error only. An Object Adapter object servant was not active.
Exception |
Action |
Contact BEA Customer Support. | |
157 |
ERROR: OA Servant not unique. | |
|
Description |
Internal error. An Object Adapter object servant was not unique.
Exception |
Action |
Contact BEA Customer Support. | |
158 |
ERROR: Server Request discarded. | |
|
Description |
An Object Adapter discarded the server request and the request was not processed.
Exception |
Action |
None. | |
159 |
ERROR: Object is not a ServantActivator. | |
|
Description |
The servant manager is not a
Exception |
Action |
Verify that a ServantActivator object is specified in the call to | |
160 |
ERROR: Object is not a ServantLocator. | |
|
Description |
The servant manager is not a
Exception |
Action |
Verify that a ServantLocator object is specified in the call to | |
161 |
ERROR: Object is not a AdapterActivator. | |
|
Description |
The servant manager is not a
Exception |
Action |
Verify that an AdapterActivator object is specified in the call to the activator. | |
163 |
ERROR: An error was returned by Tuxedo. | |
|
Description |
The BEA TUXEDO system returned an error. For more information, see the minor code and the user log (
Exception |
Action |
None | |
164 |
ERROR: 'ObjectName' is not an operation in the interface. | |
|
Description |
You specified an operation name that is defined in the interface, but is not an operation.
Exception |
Action |
Ensure that the specified name is an operation in the interface. | |
165 |
ERROR: The ORB is not initialized. | |
|
Description |
A client application must initialize the ORB before using it. |
Action |
Add an appropriate ORB_init() call in your C++ application, or an ORB.init() in your Java application. | |
166 |
ERROR: Unknown URL type specified. | |
|
Description |
The type of the CORBA URL specified (corbaloc, corbaname, etc.) is not valid according to the CORBA specific ation. |
Action |
Correct the format of URL specified. | |
167 |
ERROR: Unknown URL protocol specified. | |
|
Description |
Description: The protocol part of the CORBA URL specified (IIOP or RIR) is not valid. |
Action |
Correct the format of URL specified. | |
168 |
ERROR: Bad URL address specified. | |
|
Description |
The address part of the CORBA URL specified is not valid. |
Action |
Correct the format of URL specified. | |
169 |
ERROR: The specified URL is malformed. | |
|
Description |
The CORBA URL specified could not be parsed correctly. |
Action |
Correct the format of URL specified. | |
170 |
ERROR: Support Interface val Not Found. | |
|
Description |
In a valuetype definition, a supports clause was found listing one or more CORBA interfaces whose operations and attributes should be included in this valuetype definition. The interface name could not be found. |
Action |
Edit the IDL to include a definition of this interface before the valuetype definition. | |
171 |
ERROR: The specified initial service is unknown. | |
|
Description |
The service specified by a remote client using either -ORBInitRef or -ORBDefaultInitRef was not found. |
Action |
Consult the documentation for a list of valid service names. |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|