Message Class 0001 - RPC C Runtime

Denotes an inconsistency within the EntireX RPC Runtime.

Contact Software AG support.

The EntireX RPC Runtime detected an invalid server address.

When using the C API erx.h:
The ERX_SERVER_ADDRESS structure of the EntireX RPC Runtime is not correct or was not correctly initialized. The medium must be ERX_TM_BROKER, ERX_TM_BROKER_LIBRARY or ERX_TM_CONNECTION.

The EntireX RPC Runtime API was called with an invalid connection or CallId.

When using the C API erx.h:
Check program and correct error.

The operating system could not satisfy a memory request.

Increase your memory resources and retry.

An ERXRegister API call can register a maximum of 256 threads at a time with the EntireX RPC Runtime within one process.

When using the C API erx.h:
Check program and correct error.

An ERXRegister API call is attempting to register a thread with the EntireX RPC Runtime twice.

When using the C API erx.h: It is not necessary to register a thread multiple times. However, it is required to register a thread once. We recommend having the number of ERXRegister/ERXUnregister calls occuring in pairs. If you insist on registering a thread twice, ignore this error. Check program and correct error.

Before a thread/process can use an EntireX RPC Runtime API function, the thread/process must be registered with the EntireX RPC ERXRegister API call.

• When using the C API erx.h:

  Check program and correct error.

• When using the DCOM Wrapper:

  Contact Software AG support.

An EntireX RPC Runtime API function was called with an invalid address or inconsistent parameter. The number n denotes the position of the inconsistent parameter within the API.

When using the C API erx.h:
Check program and correct error.

An EntireX RPC Runtime API function with corrupt memory was called. The internal data structures were not found.

• When using the C API erx.h:

  Check program and correct error.

• When using the DCOM Wrapper:

  Contact Software AG support.

During a conversational Remote Procedure Call there was a failure and another EntireX RPC Runtime ERXCall API call was issued.

When using the C API erx.h:
Close the Connection with the EntireX ERXDisconnect API function call.

One of the following occurred:

1. The memory area supplied for the EntireX RPC Runtime API is invalid. It could not be read from or written to.

2. An ERX_VDATA handle is corrupt.

• When using the C API erx.h:

  Check program and correct error.

• When using the DCOM Wrapper:

  Contact Software AG support.

The CallId for the EntireX RPC Runtime API function is invalid or corrupt.

• When using the C API erx.h:

  Check program and correct error.

• When using the DCOM Wrapper:

  Contact Software AG support.

The EntireX RPC Runtime API received an invalid parameter.There is an inconsistency between the template files, the header file erx.h or the EntireX RPC Runtime. The type of parameter is not supported.

• When using the C API erx.h:

  Re-generate the client proxy or server stubs with the correct template file client.tpl and server.tpl and compile and link it with the header file erx.h from the same EntireX RPC version.

• When using the DCOM Wrapper:

  Re-generate the DCOM server, using the correct template files.

The EntireX RPC Runtime API call received an invalid parameter. There is an inconsistency between the template files, the header file erx.h or the EntireX RPC Runtime.

The EntireX RPC Runtime is binary backward compatible. It must have the same or a higher EntireX version as the template and header files used.

• When using the C API erx.h:

  Re-generate the client proxy or server stubs with the correct template file client.tpl and server.tpl and compile and link it with the header file erx.h from the same EntireX RPC version.

• When using the DCOM Wrapper:

  Re-generate the DCOM server, using the correct template files.

An EntireX RPC Runtime API ERXWait call was issued and no RPC request was pending.

Check program and correct error.

The EntireX RPC Runtime API call received an invalid parameter. There is an inconsistency between the template files, the header file erx.h or the EntireX RPC Runtime. One of the following applies:

• The size of the first dimension of an array parameter must not be less than the size of the second dimension.

• The size of the second dimension of an array parameter must not be less than the size of the third dimension.

The EntireX RPC Runtime is binary backward compatible. It must have the same or a higher EntireX version as the template and header files used.

• When using the C API erx.h:

  Re-generate the client proxy or server stubs with the correct template file client.tpl and server.tpl and compile and link it with the header file erx.h from the same EntireX RPC version.

The timeout value must not be zero.

• When using the C API erx.h:

  The ERX_SERVER_ADDRESS structure of the EntireX RPC Runtime is not correct or was not correctly initialized. Check program and correct error.

• When using the DCOM Wrapper:

  Provide a valid timeout for the property TimeOut.

The EntireX RPC Runtime API ERXRegister call was issued with an invalid version.

The EntireX RPC Runtime is binary backward compatible. It must have the same or a higher EntireX version as the template and header files used.

• When using the C API erx.h:

  Use the appropriate ERX_Vnnn macro defined in the erx.h header file. Re-generate the client proxy or server stubs with the correct template file client.tpl and server.tpl and compile and link it with the header file erx.h from the same EntireX RPC version.

• When using the DCOM Wrapper:

  Re-generate the DCOM server, using the correct template files.

The EntireX RPC Runtime API call received an invalid parameter. There is an inconsistency between the template files, the header file erx.h or the EntireX RPC Runtime. The offending parameter (or one of its parents) is its own parent. The parameter definition is cyclic.

The EntireX RPC Runtime is binary backward compatible. It must have the same or a higher EntireX version as the template and header files used.

• When using the C API erx.h:

  Re-generate the client proxy or server stubs with the correct template file client.tpl and server.tpl and compile and link it with the header file erx.h from the same EntireX RPC version.

• When using the DCOM Wrapper:

  Re-generate the DCOM server, using the correct template files.

An error occurred while establishing the atexit function.

Contact Software AG support.

Tracing for the EntireX RPC Runtime could not be switched on. Either no trace destination had been entered, or the trace file could not be opened.

Contact your System Administrator.

No Library name was given.

• When using the C API erx.h:

  The ERX_SERVER_ADDRESS structure of the EntireX RPC Runtime is not correct or was not correctly initialized. When using the ERX_TM_BROKER_LIBRARY as the medium, szLibraryName must also be given. Check program and correct error.

• When using the DCOM Wrapper:

  Provide a valid library for the property Library.

No User ID was entered.

• When using the C API erx.h:

  The ERX_CLIENT_IDENTIFICATION structure of the EntireX RPC Runtime is not correct or was not correctly initialized. Check program and correct error.

• When using the DCOM Wrapper:

  Provide a valid user ID for the property UserID.

No Password was entered.

1. When using the C API erx.h:

   The ERX_CLIENT_IDENTIFICATION structure of the EntireX RPC Runtime is not correct or was not correctly initialized. Check program and correct error.

2. When using the DCOM Wrapper:

   Provide a valid password for the property PassWord.

This is an internal error.

Contact Software AG support.

This is an internal error.

Contact Software AG support.

The EntireX RPC Runtime API call received an invalid parameter. The direction specification must be one of the following: ERX_IN_PARM, ERX_OUT_PARM or ERX_INOUT_PARM.

The EntireX RPC Runtime is binary backward compatible. It must have the same or a higher EntireX version as the template and header files used.

• When using the C API erx.h: Re-generate the Client proxy or Server stubs with the correct template file client.tpl and server.tpl and compile and link it with the header file erx.h of the same EntireX RPC version.

• When using the DCOM Wrapper:

  Re-generate the DCOM server, using the correct template files.

A response was retrieved from the broker's Command/Info Service interface while an EntireX RPC API function ERXTerminateServer was executed.

See Broker Command and Information Services Error Codes.

This is an informational message of the EntireX RPC Runtime.

Contact Software AG support.

The EntireX RPC parameter definition is not consistent to the EntireX version registered with the EntireX RPC API ERXRegister function.

There is an inconsistency between the template files, the header file erx.h or the EntireX RPC Runtime.

• When using the C API erx.h:

  For all versions prior to ERX_V530, ERX_PARAMETER_DEFINITION (defined in erx.h of related version) must be used. For ERX_V530 and above ERX_PARAMETER_DEFINITION_V2 (defined in erx.h of related version) must be used. Re-generate the client proxy or server stubs with the correct template file client.tpl and server.tpl and compile and link it with the header file erx.h of the same EntireX RPC version.

• When using the DCOM Wrapper:

  Re-generate the DCOM server, using the correct template files.

This is an internal, informational message of the EntireX RPC Runtime.

Contact Software AG support.

This is an internal, informational message of the EntireX RPC Server.

Contact Software AG support.

This is an internal, informational message of the EntireX RPC Runtime.

Contact Software AG support.

This can be a result of a ERX_CC_PEEK command of the EntireX RPC Runtime API function ERXControl.

Program dependent.

This is an internal, informational message of the EntireX RPC Runtime.

Contact Software AG support.

While examinimg the string buffer, an error occurred within the EntireX RPC Runtime. The partner did not adhere to the metastructure <keyword>=<length>,<value>.

Contact Software AG support.

This is an internal, informational message of the EntireX RPC Runtime.

Contact Software AG support.

Your EntireX/Natural RPC server does not reply correctly to the EntireX RPC request.

Contact Software AG support.

The EntireX Broker Stub replied with the specified return codes, where <return-code> is the stub's function return code and <cb-return-code> is from the ACI field return code.

Check your configuration and correct the error.

The EntireX/Natural RPC server does not reply correctly to the INQUIRE call.

Contact Software AG support.

The request issued by the RPC client cannot be processed by the RPC server because the RPC server or - if it is being used - the broker conversion approach SAGTRPC does not support the required functionality.

If the broker conversion approach SAGTRPC is being used, the cause of the problem can be SAGTRPC or the RPC server. Check the version of the broker and the RPC server in use. Upgrade the broker and the RPC server to the latest version available.

If the broker conversion approach SAGTRPC is not being used, the cause of the problem is the RPC server. Check the version of the RPC server in use. Upgrade the RPC server to the latest version available.

Your EntireX Broker middleware (stub or kernel) does not support the Broker API version needed.

If possible, upgrade your EntireX Broker Middleware (Stub and Kernel) at least to ETB211.

There was an overflow of an unbounded array. The maximum array boundaries are determined in the Software AG IDL file.

Check the program and correct the error.

Accessing an unbounded array has caused an error. This can happen during marshalling/unmarshalling within the EntireX RPC Runtime or when accessing the erxArray... functions directly.

Either:

1. The unbounded array was destroyed by your program because of memory overwrites. Correct your program.

   or

2. An internal error occurred in the EntireX RPC Runtime. Contact Software AG support.

This is an internal, informational message of the EntireX RPC Server.

Contact Software AG support.

The ERX_PARAMETER_DEFINITION_Vx contains incorrect data in the usAttributes and usType fields.

Re-generate, compile and link your client stub.

The data type and attributes of the unbounded array built with erxArrayAlloc do not match the data type, length, dimensions or attributes determined in the Software AG IDL file.

Re-generate your client stub or create the unbounded array with the correct type, length, dimensions and attributes using erxArrayAlloc.

In the Software AG IDL file value ranges are defined for data types. The value you are trying to send is outside of the defined range. For example, it is not possible to send

• a negative value with data type NU or PU

• a value greater than 127 and less than -128 with I1

• a value greater than 32767 and less than -32768 with I2

• a value greater than 2147483647 and less than -2147483648 with I4.

Check the program and correct the error.

The indices you provided to access the unbounded array are out of bounds.

Check the program and correct the error.

The data provided for the unbounded array function does not conform to the rules of the data type. For example, the data provided for a data type P is not packed.

Check the program and correct the error.

The parameter preserve flag provided for the unbounded array function is invalid.

Check the program and correct the error.

The parameter dimension provided for the unbounded array function is invalid.

Check the program and correct the error.

The parameter provided for the unbounded array function is invalid.

Check the program and correct the error.

The parameter definition within the client stub is incorrect.

Re-generate your client stub with the IDL Compiler or EntireX DCOM Wrapper.

Initialization failed because EntireX Broker stub does not support SSL.

Use a stub which supports SSL or configure a transport method supported by the stub used.

Your EntireX Broker middleware (Stub or Kernel) does not support the Broker API version needed.

If possible, upgrade your EntireX Broker middleware (Stub and Kernel).

This is a user error. The name of the logical Broker ID must not contain a comma.

Correct the error and rerun your program.

This is a user error. The name of the logical Service must not contain a comma.

Correct the error and rerun your program.

The EntireX Broker stub could not be found in the environment.

Try again to install EntireX.

An invalid configuration file name or a wrong file type was used to start the RPC server.

Restart the server with correct configuration file.

This is an internal error of the RPC runtime and RPC server.

Contact Software AG support.

The RPC server you are using does not support alteration of the RPC password. Altering RPC passwords is supported by Natural RPC Server only. EntireX RPC servers do not support alteration of RPC passwords.

Contact Software AG support to check whether a newer version of the Natural RPC Server may support the feature.

The RPC Runtime uses the iconv interface for converting Unicode encodings under UNIX. The iconv interface returned an error (-1) during open of the conversion descriptor. Either the source or target Unicode encoding are not supported.

The Unicode encoding UTF-16BE is always needed. Depending on the used Unicode encoding of your environment, one of the following additional encodings are required: UTF-32BE UTF-32LE or UTF-16LE. See your UNIX documentation for more information on the iconv interface, especially the iconv open call. Check if the above encodings are available in your UNIX environment.

The RPC Runtime uses the iconv interface for converting Unicode encodings under UNIX. The iconv interface returned errno E2BIG. This error is an internal error of the RPC Runtime.

See your UNIX documentation for more information on the iconv interface and error E2BIG. Contact Software AG support.

The RPC Runtime uses the iconv interface for converting Unicode encodings under UNIX. The iconv interface returned errno EBADF. This error is an internal error of the RPC Runtime.

See your UNIX documentation for more information on the iconv interface and error EBADF. Contact Software AG support.

The RPC Runtime uses the iconv interface for converting Unicode encodings under UNIX. The iconv interface returned errno EILSEQ. This is a user error.

Check your data if valid Unicode characters being sent/received. See your UNIX documentation for more information on the iconv interface and error EILSEQ.

The RPC Runtime uses the iconv interface for converting Unicode encodings under UNIX. The iconv interface returned errno EINVAL. This is a user error.

Check your data to see whether valid Unicode characters are being sent/received. See your UNIX documentation for more information on the iconv interface and error EINVAL.

The RPC Runtime uses the iconv interface for converting Unicode encodings under UNIX. The iconv interface returned an undefined error.

See your UNIX documentation for more information on the iconv interface. Contact Software AG support.

Reliable RPC allows only IN parameters.

Remove any other OUT and INOUT parameters from this message.

The packet type shipped with the RPC protocol is not valid for the use of Reliable RPC.

Contact Software AG support.

The string buffer item "REL" is missing or invalid.

Contact Software AG support.

An application parameter cannot be processed because its content does not match the expected format unsigned numeric (NU). See IDL Data Types.

The message provides additional information such as <direction>, <parameter-name>, <type-length> and <location>, where

• <direction> is either 'Request' if the error was detected before the RPC server was executed, or 'Reply' for the answer, i.e. if the RPC server was already executed.

• <parameter-name> is available for target programming language C only

• <type-length> matches the IDL data type; see IDL Data Types

• <location> contains the hierarchy of IDL nodes, separated by a colon. If an IDL node is an array, its indexes are given in parentheses.

Example: Reply of IDL field (NU14.0), location=3.2(I=5).1.

The IDL below was used for the RPC call. The location is interpreted as follows: Third field on level 1 is 'G-parameter-3-on-level-1'; then second parameter on level 2 is the array 'G-parameter-32-on-level-2'and (I=5) means the fifth occurrence; then the first field on level 3 which is 'G-parameter-322-on-level-3' produced the error.

. . .
define data parameter
1 G-parameter-1-on-level-1       (A10) In
1 G-parameter-2-on-level-1                 In
1 G-parameter-3-on-level-1                 Out
   2 G-parameter-31-on-level-2
      3 G-parameter-311-on-level-3 (A5)
      3 G-parameter-312-on-level-3 (N8)
      3 G-parameter-313-on-level-3 (NU4)
   2 G-parameter-32-on-level-2    (/25)
      3 G-parameter-322-on-level-3 (NU14)
      3 G-parameter-321-on-level-3 (A5)
1 G-parameter-4-on-level-1      (A64)
. . .
end-define

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An application parameter cannot be processed because its content does not match the expected format signed numeric (N). See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An application parameter cannot be processed because its content does not match the expected format unsigned numeric (NU) or signed numeric (N). See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An application parameter cannot be processed because its content does not match the expected format unsigned packed (PU). See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An application parameter cannot be processed because its content does not match the expected format signed packed (P). See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An application parameter cannot be processed because its content does not match the expected format unsigned packed (PU) or signed packed (P). See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An application parameter of IDL type I1 cannot be processed because its content is less than the allowed minimum (-128) for I1. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An application parameter of IDL type I1 cannot be processed because its content is greater than the allowed maximum (+127) for I1. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An application parameter of IDL type I2 cannot be processed because its content is less than the allowed minimum (-32768) for I2. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An application parameter of IDL type I2 cannot be processed because its content is greater than the allowed maximum (+32767) for I2. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An application parameter of IDL type I4 cannot be processed because its content is less than the allowed minimum (-2147483648) for I4. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An application parameter of IDL type I2 cannot be processed because its content is greater than the allowed maximum (+2147483647) for I2. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An application parameter of IDL type F4 cannot be processed because its content is less than the allowed minimum (1.175494351e-38F) for F4. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An application parameter of IDL type F4 cannot be processed because its content is greater than the allowed maximum (3.402823466e+38F) for F4. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An application parameter of IDL type F4 cannot be processed because of conversation error HUGE_VAL. See C library strtod() for more information.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An application parameter of IDL type F8 cannot be processed because its content is less than the allowed minimum (2.2250738585072014e-308) for F8. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An application parameter of IDL type F8 cannot be processed because its content is greater than the allowed maximum (1.7976931348623158e+308) for F8. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An application parameter of IDL type F4 or F8 cannot be processed because of exponent over- or underflow. See IDL Data Types.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An application parameter of IDL type AV, BV, KV or UV cannot be processed because incorrect data was applied, see Using Variable-length Data Types AV, BV, KV and UV.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.

An index of an application parameter for an IDL unbounded array (see array-definition under Software AG IDL Grammar in the IDL Editor documentation) cannot be processed because its value exceeds the maximum for upper bound.

The additional information <direction>, <parameter-name>, <type-length> and <location> is explained under error message 00010200.

Make sure the IDL file, generated client interface objects and your client application are consistent. Check your client application for parameter integrity.