.Net Open Client Error : Invalid version, 17391 (expected 1100) in object file. (2888) (7211) - Forum - OpenEdge General - Progress Community

.Net Open Client Error : Invalid version, 17391 (expected 1100) in object file. (2888) (7211)

 Forum

.Net Open Client Error : Invalid version, 17391 (expected 1100) in object file. (2888) (7211)

This question is not answered

My .r code is compiled in Progress 10.1B (64 bit), however my OpenEdge Appserver is running 11.5 (64 bit), it is running on Windows Server 2012.

In Visual Studio I'm getting the following error while trying to load the dll files generated through ProxyGen:

Message = "ERROR condition: Invalid version, 17391 (expected 1100) in object file customer.r. (2888) (7211) ".

Progress knowledgebase suggest that it is due to conflict of bitness between the systems progress code is compiled vs. where it is accessed. In my case both systems are 64 bit (although Progress versions are different).

I've already confirmed that the build platform in Visual Studio is 64 bits.

My questions are:

1. Does the difference of Progress version cause this error too?

2. Is there a way to use the ProxyGen in 64 bit/ 32 bit flavors? I'm thinking in terms of the custom compiler (CSC.exe) and XSD Generator (XSD.exe) I'm using to generate strongly typed proxy classes?

All Replies
  • Going from OpenEdge 10 to OpenEdge 11 you must recompile. R-Code is not compatible over major OpenEdge releases. Reality when using OO is, that it might not even be compatible between the point releases.

    Not sure why you care about 64 bit / 32 bit flavors with te XSD.exe and CSC.exe. IMHO that proxies are platform independent.

    Architect of the SmartComponent Library and WinKit

    Consultingwerk Ltd.

  • Thanks Mike for your response. If the code is compiled using Progress 10.1B, do you reckon OpenEdge 10.2B would make a difference? or an exact OpenEdge version is required for it to work?

    Also, I started looking into the bitness (32 vs. 64) for the proxies based on the Progress knowledgebase description of the error which talks about this difference.

    Thanks in advance again.

  • If you're not using OO (unlikely in 10.1B), I'd say the 64 bit 10.1B R-Code should be OK for 64 bit 10.2B.

    Some further rules here:

    knowledgebase.progress.com/.../P124103

    Architect of the SmartComponent Library and WinKit

    Consultingwerk Ltd.

  • Is 64bit OpenEdge 10.2B available? I was told by my IT person that OpenEdge 10.2B is available only in 32bit.

    When I ran my 64bit compiled r-code against 32bit OpenEdge 10.2B, I got the same error.

  • These are the platforms in my ESD account:
     

    Architect of the SmartComponent Library and WinKit

    Consultingwerk Ltd.

  • > Reality when using OO is, that it might not even be compatible between the point releases.

    I don't want to hijack but I'm intrigued by this, and a little concerned.  Mike, could you please elaborate on this?

  • All my attempts of using r-code compiled on one version of the classes provided by Progress (like the http client, JsonObject, …) will fail in another version of OpenEdge.
     
    Our most recent incident here was trying to execute Web Handlers compiled on OpenEdge 11.6 on OpenEdge 11.7. In OpenEdge 11.7.3, the IWebRequest Interface was extended – resulting in the fact, that the class in the 11.6 r-code does no longer meet the requirements of the Interface on OpenEdge 11.7. Sudden death of PASOE.
     
     
     

    Architect of the SmartComponent Library and WinKit

    Consultingwerk Ltd.

  • Thanks Mike.

  • Thanks for the screenshot Mike. Just curious, is OpenEdge 10.1B available in 64bit too?

  •  
    Not sure if on all platforms. Others might be better at history here. And if you feel like you need it, you’ll need to get in touch with Progress sales anyway.

    Architect of the SmartComponent Library and WinKit

    Consultingwerk Ltd.

  • Maybe the confusion is because the 64-bit OpenEdge Windows products included the 32-bit GUI client until 11.3. The 64-bit GUI client was introduced in 11.3 and the 32-bit client was removed from 64-bit products at the same time.