EntireX Communicator - Setting for ERXRegister

[David_J_Mather]

HI,

Have a problem with version mismatch.

If i compile me C code and the version set in the ERXRegister is x.1.0 and the EntireX Communicator version I actually have is x.1.1 will this cause the mismatch error message?

According to the documentation, the versions are backward compatible.

Thanks…DaveM

[Douglas_Kelly]

You need to post this question to the EntireX Communicator forum rather than the Natural Forum (go to the “crossvision community” link, EntireX, Discussions).

In any case, the closest error I can find to what you describe is 0010038, which reads:

00010038 Version not supported
Explanation The EntireX RPC Runtime API ERXRegister call was issued with an invalid version.

Action 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. Regenerate 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:

Regenerate the DCOM Server using the correct template files.

If this isn’t relevant or helpful, please re-post your question (along with any error codes or similar info!) to the EntireX forum