none
Error when choosing sapBinding on "Consume Adapter Service" wizard RRS feed

  • Question

  • When I try to select the sapBinding on a 64bit windows 2003 r2 sp2 dev machine following error occurs (all other Bindings of the Adapter Pack work):

    System.Reflection.TargetInvocationException: Ein Aufrufziel hat einen Ausnahmefehler verursacht. ---> System.IO.FileLoadException: Die Datei oder Assembly "Microsoft.Adapters.SAP.SAPGInvoker, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" oder eine Abhängigkeit davon wurde nicht gefunden. This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem. (Ausnahme von HRESULT: 0x800736B1)

    Dateiname: "Microsoft.Adapters.SAP.SAPGInvoker, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" ---> System.Runtime.InteropServices.COMException (0x800736B1): This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem. (Ausnahme von HRESULT: 0x800736B1)

       bei Microsoft.Adapters.SAP.SAPConnectionUri.ParseUri(Uri uri)

       bei Microsoft.Adapters.SAP.SAPConnectionUri..ctor()

     

     

       --- Ende der internen Ausnahmestapelüberwachung ---

       bei System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)

       bei System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache)

       bei System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache)

       bei System.Activator.CreateInstance(Type type, Boolean nonPublic)

       bei Microsoft.ServiceModel.Channels.Tools.MetadataSearchBrowse.MetadataPanel.CreateConnectionURIFromBindingName(String bindingName)

       bei Microsoft.ServiceModel.Channels.Tools.MetadataSearchBrowse.MetadataUserControl.OnAdapterChangedEvent(Object sender, EventArgs e)

     

    In the System eventlog following three entries are written:

    1.
    Dependent Assembly Microsoft.VC80.CRT could not be found and Last Error was The referenced assembly is not installed on your system.


    2.
    Resolve Partial Assembly failed for Microsoft.VC80.CRT. Reference error message: The referenced assembly is not installed on your system.

    3.
    Generate Activation Context failed for C:\WINDOWS\system32\LIBRFC32U.dll. Reference error message: The referenced assembly is not installed on your system.

    It seems like the Visual C++ 2005 Redistributable Package is missing, but I installed the 32bit and 64bit version of both 2005 , 2005 SP1, 2008 and 2008 SP1. I also installed all the other necessarry components like:
     - RFCSDK in system32 and syswow64
     - R2DLLINS (ran exe file)
     - WCF LOB Adapter SDK SP2 64bit
     - BizTalk Adapter Pack 2.0 32bit and 64bit

    Does anybody have an idea what the problem is? The tool dependency walker (depends.exe) showed that the msvcr80.dll file in the sql server x86 binn folder was used. So I uninstalled SQL Server. Now depends.exe said that it couldn't find msvcr80.dll at all. Shouldn't the Visual C++ 2005 Redistributable Package Setup copy the DLL in the system32 folder?

    Regards

    Thursday, June 24, 2010 3:25 PM

Answers

  • Yes it seems so.

    Some suggestions:

    1. Install the latest patch of Sap RFC SDK libraries

    2. Or you can find the version that your client library is referencing by running in Vista/Win7/Win 2k8 machine. If you don't have adapter setup in any of the platforms, maybe you can use the tool here to check

     

     

    Wednesday, June 30, 2010 3:39 PM
  • I finally got it working with the help of a microsoft support technician. There was a specific security update for the vc++ runtime that was missing (I only had the vs 2008 version of the update installed). So after I installed following update (both x86 and x64) the binding loaded as expected:

    "Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update"

    http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en

    There is no SAP GUI installed on the machine.

    • Marked as answer by Elias Goetz Thursday, July 8, 2010 11:50 AM
    Thursday, July 8, 2010 11:42 AM

All replies

  • Do you use an 32bit enabled host for this? 64bit is not supported for SAP.

    In addition you should install SAPGUI instead of RFC SDK. Had some trouble with it in the past.


    If you like my post or consider it as a valid answer, please use the buttons to show me - Oliver

    http://biztalk.hauth.me

    Thursday, June 24, 2010 3:56 PM
  • 64 bit IS supported for SAP. What Oliver suggested applies to the old SAP adapter. You need 32 bit version to work with VS as VS is a 32 bit process.

    1. Is 32 bit VC++ redist installed on your system?

    2. Is the SAP RFC SDK installed correctly? Are you missing any DLL?

    Friday, June 25, 2010 4:35 AM
  • Is it really supported? I never got SAP Adapter running on x64 instances of BizTalk. Of course in a x64 environment, but always on a 32bit enabled host? And yes, I'm talking of the new adapter.
    If you like my post or consider it as a valid answer, please use the buttons to show me - Oliver

    http://biztalk.hauth.me

    Friday, June 25, 2010 5:13 AM
  • Thanks for the replies.

    VC++ redist: I installed both 32-bit and 64-bit versions of 2005, 2005 sp1, 2008, 2008 sp1 to make sure I'm not missing any of those dlls.
    What I was wondering was that the msvcr80.dll isn't in the system32 or syswow64 directory. Shouldn't it be there? There are several folders in the windows\winsxs folder (one folder for each version and plattform).

    SAP RFC SDK: I copied the 32-bit dlls to syswow64 and the 64-bit dlls to system32:
    icudt34.dll
    icuin34.dll
    icuuc34.dll
    librfc32u.dll
    libsapu16vc80.dll
    libsapucum.dll

    I didn't copy the .lib files. But just to make sure they aren't needed I copied them also temporarly, but it didn't make any difference.
    Rebooting the machine after each of the installation steps also didn't help.

    Regarding the host: It's running as 32-bit host, because of the standard edition limitation.

    Friday, June 25, 2010 6:28 AM
  • Hi,

    I suggest to use process monitor and reproduce the error and see what is missing where (file or registry).

    HTH

    Regards,

    Steef-Jan Wiggers    
    MCTS BizTalk Server
    http://soa-thoughts.blogspot.com/
    If this answers your question please mark it accordingly


    BizTalk
    Friday, June 25, 2010 2:57 PM
    Moderator
  •  

    Thanks for the hint Steef-Jan,

    Here some of the output (filtered for not "SUCCESS" and just PID of devenv.exe):

    15:18:28,6978002 devenv.exe 2664 QueryDirectory C:\WINDOWS\assembly\GAC_32\Microsoft.Adapters.SAP.SAPGInvoker\3.5.0.0__31bf3856ad364e35\Microsoft.Adapters.SAP.SAPGInvoker.INI NO SUCH FILE Filter: Microsoft.Adapters.SAP.SAPGInvoker.INI
    15:18:28,7009288 devenv.exe 2664 QueryAllInformationFile C:\WINDOWS\assembly\GAC_32\Microsoft.Adapters.SAP.SAPGInvoker\3.5.0.0__31bf3856ad364e35\Microsoft.Adapters.SAP.SAPGInvoker.dll BUFFER OVERFLOW CreationTime: 24.06.2010 10:42:03, LastAccessTime: 25.06.2010 15:17:43, LastWriteTime: 24.06.2010 10:42:03, ChangeTime: 24.06.2010 10:42:03, FileAttributes: A, AllocationSize: 143.360, EndOfFile: 141.688, NumberOfLinks: 1, DeletePending: False, Directory: False, IndexNumber: 0x1a000000013789, EaSize: 0, Access: Generic Read, Position: 0, Mode: Synchronous IO Non-Alert, AlignmentRequirement: Word
    15:18:28,7009841 devenv.exe 2664 QueryAllInformationFile C:\WINDOWS\assembly\GAC_32\Microsoft.Adapters.SAP.SAPGInvoker\3.5.0.0__31bf3856ad364e35\Microsoft.Adapters.SAP.SAPGInvoker.dll BUFFER OVERFLOW CreationTime: 24.06.2010 10:42:03, LastAccessTime: 25.06.2010 15:17:43, LastWriteTime: 24.06.2010 10:42:03, ChangeTime: 24.06.2010 10:42:03, FileAttributes: A, AllocationSize: 143.360, EndOfFile: 141.688, NumberOfLinks: 1, DeletePending: False, Directory: False, IndexNumber: 0x1a000000013789, EaSize: 0, Access: Generic Read, Position: 0, Mode: Synchronous IO Non-Alert, AlignmentRequirement: Word
    15:18:28,7025824 devenv.exe 2664 RegOpenKey HKCU\Software\Policies\Microsoft\Control Panel\Desktop NAME NOT FOUND 
    15:18:28,7028187 devenv.exe 2664 RegOpenKey HKLM\System\CurrentControlSet\Control\Nls\MUILanguages REPARSE 
    15:18:28,7028609 devenv.exe 2664 RegQueryValue HKLM\System\CurrentControlSet\Control\Nls\MUILanguages\0409 NAME NOT FOUND Length: 256
    15:18:28,7029662 devenv.exe 2664 RegQueryValue HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide\PreferExternalManifest NAME NOT FOUND Length: 20
    15:18:28,7031051 devenv.exe 2664 CreateFile C:\WINDOWS\assembly\GAC_32\Microsoft.Adapters.SAP.SAPGInvoker\3.5.0.0__31bf3856ad364e35\Microsoft.Adapters.SAP.SAPGInvoker.dll.2.Config NAME NOT FOUND Desired Access: Generic Read/Execute, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, AllocationSize: n/a
    15:18:28,7084669 devenv.exe 2664 RegOpenKey HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide\AssemblyStorageRoots NAME NOT FOUND 
    15:18:28,7087368 devenv.exe 2664 QueryOpen E:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe.Local NAME NOT FOUND 
    15:18:28,7106186 devenv.exe 2664 QueryOpen C:\WINDOWS\assembly\GAC_32\Microsoft.Adapters.SAP.SAPGInvoker\3.5.0.0__31bf3856ad364e35\LIBRFC32U.dll NAME NOT FOUND 
    15:18:28,7152952 devenv.exe 2664 RegOpenKey HKCU\Software\Policies\Microsoft\Control Panel\Desktop NAME NOT FOUND 
    15:18:28,7157120 devenv.exe 2664 RegOpenKey HKLM\System\CurrentControlSet\Control\Nls\MUILanguages REPARSE 
    15:18:28,7159232 devenv.exe 2664 RegQueryValue HKLM\System\CurrentControlSet\Control\Nls\MUILanguages\0409 NAME NOT FOUND Length: 256
    15:18:28,7162405 devenv.exe 2664 RegQueryValue HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide\PreferExternalManifest NAME NOT FOUND Length: 20
    15:18:28,7163858 devenv.exe 2664 CreateFile C:\WINDOWS\SysWOW64\LIBRFC32U.dll.2.Config NAME NOT FOUND Desired Access: Generic Read/Execute, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, AllocationSize: n/a

    There are "buffer overflow", "name not found" and "no such file" values, but I can't figure out the actual source of the issue.

    Regards

    Monday, June 28, 2010 6:53 AM
  • 1. Do you have the same version of VC++ assemblies for which you are getting the error under %WINDIR%\winsxs\x86_microsoft.vc90.crt_<version>

    2. Does your machine has the proper manifest file under %WINDIR%\winsxs\Manifests\x86_microsoft.vc90.crt_<version>.manifest

    Help link - http://msdn.microsoft.com/en-us/library/ms235342.aspx

    Thanks,

    Jeevitha

    Monday, June 28, 2010 8:27 PM
  • There are errors regarding librfc32u.dll and SAPGInvoker. Are you sure you installed the adapter pack and sap gui correctly? Check if these files are available.
    If you like my post or consider it as a valid answer, please use the buttons to show me - Oliver

    http://biztalk.hauth.me

    Tuesday, June 29, 2010 4:26 AM
  • Jeevitha,

    I'm not sure which exact version is expected by the LIBRFC32U.dll. The eventlog entry just says the Microsoft.VC80.CRT is missing. The installation guide for the BizTalk Adapter Pack has a link the "Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)". Like mentioned in my initial post I installed all combinations of the redist package (2005, 2008, 32-bit, 64-bit, with and without sp1).

    Here a list list of CRT dlls in the winsxs directory:

    amd64_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.1833_x-ww_90fa68b6
    amd64_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.3053_x-ww_ea198eaa
    amd64_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_3fea50ad
    amd64_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_9d1c6ce0
    amd64_Microsoft.VC80.DebugCRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_2968974c
    amd64_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.21009.1_x-ww_a8fbb457
    amd64_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_0296e955
    amd64_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_a17e7c1e
    amd64_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.4148_x-ww_069f922e
    amd64_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_2a6dacff

    ia64_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_9ecf7cde
    ia64_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_27beadbf

    x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.1833_x-ww_5ef082d6
    x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.3053_x-ww_b80fa8ca
    x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd
    x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700
    x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_d08d0375
    x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_6f74963e
    x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.4148_x-ww_d495ac4e
    x86_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_597c3456
    x86_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_f863c71f

    And the manifests directory:

    amd64_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.1833_x-ww_90fa68b6.cat
    amd64_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.1833_x-ww_90fa68b6.manifest
    amd64_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.3053_x-ww_ea198eaa.cat
    amd64_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.3053_x-ww_ea198eaa.manifest
    amd64_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_3fea50ad.cat
    amd64_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_3fea50ad.manifest
    amd64_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_9d1c6ce0.cat
    amd64_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_9d1c6ce0.manifest
    amd64_Microsoft.VC80.DebugCRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_2968974c.cat
    amd64_Microsoft.VC80.DebugCRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_2968974c.manifest
    amd64_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.21009.1_x-ww_a8fbb457.cat
    amd64_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.21009.1_x-ww_a8fbb457.manifest
    amd64_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_0296e955.cat
    amd64_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_0296e955.manifest
    amd64_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_a17e7c1e.cat
    amd64_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_a17e7c1e.manifest
    amd64_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.4148_x-ww_069f922e.cat
    amd64_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.4148_x-ww_069f922e.manifest
    amd64_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_2a6dacff.cat
    amd64_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_2a6dacff.manifest

    ia64_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_9ecf7cde.cat
    ia64_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_9ecf7cde.manifest
    ia64_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_27beadbf.cat
    ia64_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_27beadbf.manifest

    x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.1833_x-ww_5ef082d6.cat
    x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.1833_x-ww_5ef082d6.manifest
    x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.3053_x-ww_b80fa8ca.cat
    x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.3053_x-ww_b80fa8ca.manifest
    x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd.cat
    x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd.manifest
    x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700.cat
    x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700.manifest
    x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_d08d0375.cat
    x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_d08d0375.manifest
    x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_6f74963e.cat
    x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_6f74963e.manifest
    x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.4148_x-ww_d495ac4e.cat
    x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.4148_x-ww_d495ac4e.manifest
    x86_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_597c3456.cat
    x86_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_597c3456.manifest
    x86_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_f863c71f.cat
    x86_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_f863c71f.manifest

    Is it correct that the msvcr80.dll file only exists in the winsxs directory and not in the system32 or syswow64 directory?
    Something that you might find interesting: as long as sql server express edition was installed on the lokal machine depends.exe used the msvcr80.dll file in the binn folder of the sql server installation. When I uninstalled sql server completly on that machine depends.exe couldn't find the msvcr80.dll at all even though it's located in the winsxs folder in several versions.

    Tuesday, June 29, 2010 6:52 AM
  • Enabling sxstrace will let you find which version of VC80 CRT does the LIBRFC32U.dll is looking for.

    Help link: http://blogs.msdn.com/b/junfeng/archive/2006/04/14/576314.aspx

    Once you know the version, check if the exact same version is present in the winsxs directories. Both the dlls and the manifest.

    Even I am not an expert in how winsxs dlls are loaded. I faced this problem once, and it worked after installing the dlls and adding the manifest in the winsxs directories as mentioned in the above link.

    Thanks,

    Jeevitha

    Tuesday, June 29, 2010 9:30 AM
  • Jeevitha,
    do you know a way to use sxstrace on windows server 2003? I read about this tool before but I couldn't find the version I needed. Just copying the sxstrace.exe from my local machine didn't work.

    Tuesday, June 29, 2010 10:23 AM
  • I dont understand what you mean by copying the sxstrace to local machine. I believe it comes with Windows itself and is present in system32.

    You can refer to the help link I provided above to find more details on it.

     

    Tuesday, June 29, 2010 12:09 PM
  • There is no sxstrace.exe on the server (system32 or syswow64). Seems like it only comes with Vista or Win7.
    Tuesday, June 29, 2010 1:14 PM
  • Yes it seems so.

    Some suggestions:

    1. Install the latest patch of Sap RFC SDK libraries

    2. Or you can find the version that your client library is referencing by running in Vista/Win7/Win 2k8 machine. If you don't have adapter setup in any of the platforms, maybe you can use the tool here to check

     

     

    Wednesday, June 30, 2010 3:39 PM
  • I ran into the exact same issue on Windows 2003 SP2 64 bit platform. As Elias mentioned, I followed the steps in installation guide (installing 64-bit WCF SDK, 32 and 64-bit versions of Adapter SDK and then the SAP RFC SDKs with VS 2005 & VS 2008 SP1, all in 32-bit and 64-bit versions). No luck after multiple combinations. Looks like that the problem is caused by incompatible versions of SAP dlls and VC++ runtime.

    I solved the problem by uninstalling all versions of VC++ runtimes and deleting the RFC SDK and R3DLLINS that are copied to system32 and syswow64 folders. Once everything is cleaned up (except the WCF and Adapter SDK installs), I installed SAPGUI 7.10 which fixed the problem.

    Though, SAPGUI only installs in 32-bit mode; so need to figure out how to get the host instance run in 64-bit mode.

    Wednesday, July 7, 2010 8:16 PM
  • I finally got it working with the help of a microsoft support technician. There was a specific security update for the vc++ runtime that was missing (I only had the vs 2008 version of the update installed). So after I installed following update (both x86 and x64) the binding loaded as expected:

    "Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update"

    http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en

    There is no SAP GUI installed on the machine.

    • Marked as answer by Elias Goetz Thursday, July 8, 2010 11:50 AM
    Thursday, July 8, 2010 11:42 AM