System Messages: LIBSCA Catalog 300-399
|
|
|
|
300 |
ERROR: ATMI Binding - Syntax error in buffertype output buffer specification | |
|
|
Description |
An error was detected when parsing a VIEW, X_COMMON, X_C_TYPE or VIEW32 buffer type specification. |
|
Action |
Correct the buffer specification. | |
|
See Also |
SALT SCA Programming Guide. | |
|
301 |
ERROR: Output buffer type buffertype incompatible with return type returntype | |
|
|
Description |
A discrepancy between the operation signature and buffer type has been detected. |
|
Action |
Verify that the buffer type defined in the binding.atmi element in SCDL is compatible with the method being invoked. | |
|
See Also |
SALT SCA Programming Guide. | |
|
302 |
ERROR: Output buffer type buffertype unsupported | |
|
|
Description |
The buffer type value entered is invalid. |
|
Action |
Make sure that the output buffer type value is valid and supported. | |
|
See Also |
ATMI binding element reference. | |
|
303 |
WARN: Application call terminated abnormally | |
|
|
Description |
An undefined application exception has been caught. |
|
Action |
Check application code. | |
|
See Also |
SALT SCA Programming Guide. | |
|
306 |
ERROR: Failed to initialize SCA runtime: errormessage | |
|
|
Description |
An internal error occurred when booting up a Tuxedo server hosting SCA components. |
|
Action |
Contact Oracle Technical Support. | |
|
307 |
ERROR: Fchg failed for field fieldname error errormessage | |
|
|
Description |
An internal error occurred when processing an FML or FML32 buffer in SCA data transformation. |
|
Action |
Contact Oracle Technical Support. | |
|
308 |
ERROR: Fchg failed for field fieldname error errormessage | |
|
|
Description |
An internal error occurred when processing an FML or FML32 buffer in SCA data transformation. |
|
Action |
Contact Oracle Technical Support. | |
|
309 |
ERROR: No current component | |
|
|
Description |
An internal error occurred when making a reference to an SCA component from within an SCA component. |
|
Action |
Contact Oracle Technical Support. | |
|
310 |
ERROR: No default component | |
|
|
Description |
The |
|
Action |
Set | |
|
See Also |
SALT SCA Programming Guide | |
|
311 |
ERROR: WSDL not found for uriname | |
|
|
Description |
The |
|
Action |
Check | |
|
312 |
ERROR: Cannot find WSDL for service servicename | |
|
|
Description |
The |
|
Action |
Check | |
|
313 |
ERROR: Failure to allocate FML32 buffer: errormessage | |
|
|
Description |
An internal error occurred when making an external Web Service call. |
|
Action |
Contact Oracle Technical Support. | |
|
314 |
ERROR: Failure to allocate FML32 buffer: errormessage | |
|
|
Description |
An internal error occurred when making an external Web Service call. |
|
Action |
Contact Oracle Technical Support. | |
|
315 |
ERROR: Cannot find FML field name for parameter parametername, errormessage | |
|
|
Description |
A field name cannot be determined when making a call to an external Web Service. |
|
Action |
Make sure that the environment is properly set, especially environment variables | |
|
See Also |
Configuring External Web Services. | |
|
316 |
ERROR: Failure to call the operationname operation: errormessage | |
|
|
Description |
An error occurred when calling a Web Service. |
|
Action |
Contact Oracle Technical Support. | |
|
317 |
ERROR: Failure to call the operationname operation: errormessage | |
|
|
Description |
An error occurred when calling a Web Service. The fault string is displayed as part of this message. |
|
Action |
No action required. | |
|
318 |
ERROR: Failure to call get the result field: errormessage | |
|
|
Description |
An internal error occurred when processing the reply from a Web Service. |
|
Action |
Contact Oracle Technical Support | |
|
319 |
ERROR: Cannot convert from bool parameter to type | |
|
|
Description |
The WSDL interface specifies a parameter that is not compatible with the C++ interface used. |
|
Action |
Verify that WSDL and C++ interfaces are compatible. | |
|
320 |
ERROR: Cannot convert from char parameter to type | |
|
|
Description |
The WSDL interface specifies a parameter that is not compatible with the C++ interface used. |
|
Action |
Verify that WSDL and C++ interfaces are compatible. | |
|
321 |
ERROR: Cannot convert from long parameter to type | |
|
|
Description |
The WSDL interface specifies a parameter that is not compatible with the C++ interface used. |
|
Action |
Verify that WSDL and C++ interfaces are compatible. | |
|
322 |
ERROR: Cannot convert from int parameter to type | |
|
|
Description |
The WSDL interface specifies a parameter that is not compatible with the C++ interface used. |
|
Action |
Verify that WSDL and C++ interfaces are compatible. | |
|
323 |
ERROR: Cannot convert from unsigned int parameter to type | |
|
|
Description |
The WSDL interface specifies a parameter that is not compatible with the C++ interface used. |
|
Action |
Verify that WSDL and C++ interfaces are compatible. | |
|
324 |
ERROR: Cannot convert from short parameter to type | |
|
|
Description |
The WSDL interface specifies a parameter that is not compatible with the C++ interface used. |
|
Action |
Verify that WSDL and C++ interfaces are compatible. | |
|
325 |
ERROR: Cannot convert from float parameter to type | |
|
|
Description |
The WSDL interface specifies a parameter that is not compatible with the C++ interface used. |
|
Action |
Verify that WSDL and C++ interfaces are compatible. | |
|
326 |
ERROR: Cannot convert from double parameter to type | |
|
|
Description |
The WSDL interface specifies a parameter that is not compatible with the C++ interface used. |
|
Action |
Verify that WSDL and C++ interfaces are compatible. | |
|
327 |
ERROR: Cannot convert from long double parameter to type | |
|
|
Description |
The WSDL interface specifies a parameter that is not compatible with the C++ interface used. |
|
Action |
Verify that WSDL and C++ interfaces are compatible. | |
|
328 |
ERROR: Cannot convert from string parameter to type | |
|
|
Description |
The WSDL interface specifies a parameter that is not compatible with the C++ interface used. |
|
Action |
Verify that WSDL and C++ interfaces are compatible. | |
|
329 |
ERROR: Cannot convert from char* parameter to type | |
|
|
Description |
The WSDL interface specifies a parameter that is not compatible with the C++ interface used. |
|
Action |
Verify that WSDL and C++ interfaces are compatible. | |
|
330 |
ERROR: Problem encoding data. Make sure the TPMBENC environment variable is set | |
|
|
Description |
The mapping of |
|
Action |
This is achieved by setting | |
|
See Also |
Environment Variables Used by FML and VIEWS | |
|
331 |
ERROR: Return type not compatible with interface return type | |
|
|
Description |
The WSDL interface specifies a return type that is not compatible with the C++ interface used. |
|
Action |
Verify that WSDL and C++ interfaces are compatible. | |
|
332 |
ERROR: Failure to get field: errormessage | |
|
|
Description |
An internal error occurred while processing a WebServices request. |
|
Action |
Contact Oracle Technical Support. | |
|
333 |
ERROR: Return type contains too many properties: errormessage | |
|
|
Description |
An attempt to call a Web Service operation with more than one return type has been made. This is currently not supported. |
|
Action |
Use a complex type to wrap more than one type. | |
|
334 |
ERROR: Failure to get field fieldname: errormessage | |
|
|
Description |
An internal error occurred while processing a WebServices request. |
|
Action |
Contact Oracle Technical Support. | |
|
335 |
ERROR: Failure to get field fieldname: errormessage | |
|
|
Description |
An internal error occurred while processing a WebServices request. |
|
Action |
Contact Oracle Technical Support. | |
|
336 |
ERROR: Index out of range | |
|
|
Description |
An internal error occurred while processing an Operation's parameters. |
|
Action |
Contact Oracle Technical Support. | |
|
337 |
ERROR: Parameter name not found | |
|
|
Description |
An internal error occurred while processing an Operation's parameters. |
|
Action |
Contact Oracle Technical Support. | |
|
344 |
ERROR: TUXDIR environment variable not set | |
|
|
Description |
The application requires that the |
|
Action |
Make sure that the runtime environment variable | |
|
345 |
ERROR: Cannot allocate space for root env | |
|
|
Description |
An internal error occurred when setting up the SCA runtime. |
|
Action |
Contact Oracle Technical Support. | |
|
346 |
ERROR: APPDIR environment variable not set | |
|
|
Description |
The application requires that the |
|
Action |
Make sure that the runtime environment variable | |
|
347 |
ERROR: Component 'componentname' not found | |
|
|
Description |
The specified component could not be found. |
|
Action |
Verify that the component mentioned in the error message can be found in one of the SCDL files. | |
|
348 |
ERROR: Cannot reconfigure runtime installation directory: directory | |
|
|
Description |
Re-setting the SCA runtime is not allowed. |
|
Action |
Verify that user code is not attempting to re-initialize the SCA runtime. | |
|
349 |
ERROR: Cannot reconfigure SCA system root: systemrootname | |
|
|
Description |
Re-setting the SCA runtime is not allowed. |
|
Action |
Verify that user code is not attempting to re-initialize the SCA runtime. | |
|
350 |
ERROR: Cannot reconfigure SCA system path: pathname | |
|
|
Description |
Re-setting the SCA runtime is not allowed. |
|
Action |
Verify that user code is not attempting to re-initialize the SCA runtime. | |
|
351 |
ERROR: Cannot reconfigure SCA system URI: componentname | |
|
|
Description |
Re-setting the SCA runtime is not allowed. |
|
Action |
Verify that user code is not attempting to re-initialize the SCA runtime. | |
|
352 |
ERROR: Cannot reconfigure main SCA component: componentname | |
|
|
Description |
Re-setting the SCA runtime is not allowed. |
|
Action |
Verify that user code is not attempting to re-initialize the SCA runtime. | |
|
353 |
ERROR: Component 'componentname' not found | |
|
|
Description |
The specified component could not be found. |
|
Action |
Verify that the component mentioned in the error message can be found in one of the SCDL files. | |
 |
 |
 |