B1DE (AddOn Installer) for 64 bit server

[Former Member]

Hi All,

I have a problem. One of my client has a 64 bit server. AddOn installation created with B1DE for SAP 2007 doesn't work on that server. After running SAP AddOn is trying to install, and then there is an error. Is there any way to create AddOn installation files that work on 64 bit server?

Regards

Hmg

[Former Member · Accepted solution]

Hi, here is an error text:

"Error: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)

[Former Member · Accepted solution]

I think you have two choices:

1. Change your project build options force 32-bit

This is done by changing the platform on the project properties to x86 on your .EXE and all projects that use the DI or UI COM objects (these are 32-bit).

2. Alter the .EXE using the process described below (this may upset the checks the add-on installer does)

http://blogs.intesoft.net/post/2007/12/Running-NET-Apps-in-32-bit-mode-on-64-bit-Windows.aspx

[Former Member · Accepted solution]

Thanks Robin for Your reply. I need to add that AddOn runs on that server if start from Shortcut (with argument that is connection string) on a pulpit. The problem is that the addon doesn't install. I think that B1DE doesn't create correct file that should work on 64 system.

[Former Member · Accepted solution]

I have the same problem. Can SAP please test this on SBO 2007 and 64 bit server?

[former_member201110 · Accepted solution]

Hi Arthur,

Point 1 from Robin's post above works fine for me. You'll need to make sure that the installer as well as the executable will be forced to build as 32bit. If you are using the B1DE, you'll need to let the project wizard complete the installer then change the project build properties, recompile the installer and then rerun the AddOnRegDataGen.bat file to rebuild your ard file.

Kind Regards,

Owen

[rasmuswulff_jensen · Accepted solution]

Both Robin and Owen are right... You need to run your code as forced 32 bit.

The reason is the following:

- A default project in Visual Studio is compiled as "Any CPU"

- Any CPU means that you code will be executed as 32bit on a 32bit machine, and 64bit on a 64bit machine.

- The Any CPU option is great for pure .NET (since all parts of it can run 32bit and 64bit)

- In case of the SAP SDK and the AddonInstaller.dll, these are COM-based unmanaged code

- If such unmanage code is not written to work with 64 bit, problems like yours can occur (this happens not only for SAP SDK... Tons of API out there have the same problems)

- If you change the Any CPU option to the x86 option, you will force 64 bit mashines to run your code in "simulated" 32bit (Don't worry.. it is quite fast and gives no problems)

We are you this with our 64 bit customers and without any problems...

Lastly, if you wish to know more about this please hear the following podcast that describes the issue in detail (A good listen): http://www.dotnetrocks.com/default.aspx?showNum=341

/Rasmus

[Former Member · Accepted solution]

Ok..I´ll try again. I did as you described on a 64 bit server and sbo 2005 couple of months ago and that worked fine. But with 2007 it doesn´t. I even took addons that worked on that 64 bit server with 2005 sbo and copied them over to the 64 bits server with sbo 2007 and I got the error message!! Thats why I wonder:) But I´ll try a bit more. Thanks!