Error 2888 after building r-code using Progress 32-BIT but running on 64-BIT

Error 2888 after building r-code using Progress 32-BIT but running on 64-BIT
 

For OpenEdge versions 10.1A through 10.2B, code compiled with Progress 32-BIT cannot be run on Progress 64-BIT or vice-versa.  This has been a necessary change that was made to enhance performance and features of 64-BIT versions.

Source code must be compiled using the same Progress product bit version.

For Application Providers that do not have the same Progress product bit version that the End User has, a Progress development license can be used for creating Encrypted Source Code using the XCODE utility, that can then be taken to the End User site and recompiled using the End User's client license.

For Application Providers that have a PSDN license, the OpenEdge Development Server 64-bits can be used to compile the code.

This restriction was lifted starting with OpenEdge 11.0. Please see knowledgebase article,  OpenEdge 10.x and 11.x R-CODE bit compatibility rules for more information about the lifting of this restriction.

To help determine what bit-level an r-code file is:

32-bit r-code will have a version number below 16384
64-bit r-code will have a version number above 16384
References to Written Documentation:

References to other Documentation:
OpenEdge Getting Started: New and Revised Features, Chapter 1 "64-bit r-code: Performance versus portability"
OpenEdge Deployment: Managing 4GL Applications, Chapter 11 "Deployment Topics and Tasks"  (XCODE utility)
OpenEdge 10.1A Release Notes, RN#: 101A-00355 "Incompatibility issue between 32 bit r code and 64-bit r-code"

Progress Solutions:
P113045, How to compile 64-bit r-code ?
 OpenEdge 10.x and 11.x R-CODE bit compatibility rules