Skip to Content

JCO Connectivity issue 32bit vs 64bit vs 32bit

Hi,

we are running IDM 8.0 with latest SPs. Now, trying to connect an ABAP system runs into connection error "Parameter message server host ('jco.client.mshost') is missing" although all parameters are correctly set. So after some investigation and checking some SAP notes I tried to check the installed JCo version (system was installed & updated using SWPM/SUM). The console showed Java VM version and JCo3 API. But library could not be found. Instead there was an error "Can't load AMD 64-bit .dll on a IA 32-bit platform".

Ok... so, following note 2313331 I replaced the JCo3 files with the 32 bit version, re-started everything and checked again the JCo console. Now, it's fine - no errors, library was loaded, initialization successfully.

Great, I thought, problem solved, I thought... Nope.. the connection test to ABAP repository still failed. I increased the trace level and checked the DSE.log file. Now, here comes the funny part... it says "Can't load IA 32-bit .dll on a AMD 64-bit platform" (>_<)

Anyone, knows this stupid behavior?

Regards, Richard

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Jul 26, 2020 at 11:23 AM

    In general, native libraries loaded by a Java VM must match the JVM's own word size, i.e. a 64 bit JVM will only ever load 64 bit native libraries successfully. Assuming you're using SAPJVM 8 for SAP IDM 8.0, it seems unlikely that the 32 bit version of the JCO DLL is the correct one, because -at least on the public download location at https://tools.hana.ondemand.com- SAPJVM 8 is only available for x64. Hence, my guess is that this can only work with 64bit JCO.

    Maybe the misleading results you received from the console in your initial analysis have been caused by a different environment of your own user (which may have a different path and other environment variables), compared to the OS user that is executing the SAP IDM runtime?

    Could it be that the real root cause is really more related to the connection parameters -which implicitly combine with data read from the SAP IDM runtime matchine's content of /etc/services- , and that there was initially no problem at all with the native library?

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.