From what I recall we ran into a similar issue using CR XI R2 in a 64bit environment.
I found a work around that involved adding two additional registry keys for our 64bit process to use 32bit crystal:
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{0BC59388-6740-4D7E-B7D9-B5F20EEABDCD}]
"AppID"="{0BC59388-6740-4D7E-B7D9-B5F20EEABDCD}"
[HKEY_CLASSES_ROOT\Wow6432Node\AppID\{0BC59388-6740-4D7E-B7D9-B5F20EEABDCD}]
"DllSurrogate"=""
This allowed the OLE 64bit to 32bit dllhost surrogate to find the crystal runtime and bridge the 64bit to 32bit process gap.
I found the idea to create these entries from this very general article here: http://www.gfi.com/blog/32bit-object-64bit-environment/
The article was called "Using a 32bit COM object in a 64bit environment"
However you really need to move beyond RDC at this point.
Hope this helps!