Could not load file or assembly 'BusinessObjects.Enterprise.Sdk' with 64 bit SDK

Question

I am running across an error that I do not fully understand when trying to get the SDK to work for 4.1 SP04. I have been trying to get this solution for a while now. I am able to run the SDK functionality with the 32 bit version without an issues however, my client would like to run the 64 bit version to align with their architecture. I have added the x64 DLLs to my project in VS2013, and compiled and built the project as a 64 bit project. I am receiving the following error message:
Could not load file or assembly 'BusinessObjects.Enterprise.Sdk' or one of its dependencies. An attempt was made to load a program with an incorrect format.
When building the project to build on "Any CPU" instead of x64 or x86, I am seeing the following messages:
Warning    1    There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "BusinessObjects.Enterprise.Sdk, Version=14.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304, processorArchitecture=AMD64", "AMD64". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.    DemoWeb2
Warning    2    There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "CrystalDecisions.Enterprise.Framework, Version=14.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304, processorArchitecture=x86", "AMD64". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.    DemoWeb2
Warning    3    There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "CrystalDecisions.Enterprise.InfoStore, Version=14.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304, processorArchitecture=x86", "AMD64". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.    DemoWeb2
Warning    4    There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "CrystalDecisions.Enterprise.PluginManager, Version=14.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304, processorArchitecture=x86", "AMD64". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.    DemoWeb2
I have made sure that I am referencing the 64 bit sdk .dlls from C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\. I only have 64 bit installed as well. Are InfoStore, Framework, and PluginManager only x86?
Thanks!

Answer 1

Hi Dustin
You do  not need to be concerned if your app references 32 or 64 bit assemblies. VS being 32 bit, needs to reference 32 bit assemblies in order to compile correctly. Thus running the app from the VS IDE, you wil be using 32 bit assemblies. Using a compiled exe or a DLL, the app will use 32 bit or 64 bit assemblies depending on how the app was compiled and "bitness" of the OS.
E.g;; an app compiled as 32 bit will require 32 bit assemblies
An app compiled as 64 bit will run 64 bit assemblies - on 64 bit OS only.
An app compiled as "Any CPU", will run 32 b it or 64 bit assemblies, depending on the OS. On a 64 bit OS, the app will by definition use 64 bit assemblies (but it is up to you to deploy the 64 bit runtime - not the 32 bit runtime). On a 32 bit OS the app will use 32 bit assemblies.
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow us on Twitter