Skip to Content
author's profile photo Former Member
Former Member

librfc32.dll not found on Windows Server 2003


I am using the SAP.NET Connector and everything is working fine on my local workstation. When I moved it to our development servers that are running Windows Server 2003 x64, it fails which I believe is due to the 64bit version not liking librfc32.dll.

I created a Windows Server 2003 32-bit VM and deployed my application to that. I have the SAP DLLs in my bin directory, and I copied the librfc32.dll to the Windows\System32 directory, but everytime I run the application I get the error:

Unable to load DLL 'librfc32.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)

Any ideas why I would be getting this? The Windows\System32 is in the PATH, plus even if I copy it to the applications BIN directory I still get the same error.


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jan 22, 2008 at 03:49 PM


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Ok, since nobody else had any ideas, I'll let everyone know how I solved this in the interim. I've read posts to not use the "runtime" install package (which I actually don't have) and simply put the two SAP dll's in the GAC, and the LIBRFC32.DLL in the System32 directory since that's all the runtime install does. I find this as a wrong answer.

      Since I don't have the runtime install package, I actually installed Visual Studio 2003 on the web server and then installed the SAP.NET connector (full install) on the machine. Guess What......IT WORKED.

      As soon as I installed the SAP.NET connector on the machine, no more missing DLL message. Everything worked as planned.

      I'm hoping to acquire the runtime install today to try on another Server and see how that goes.


  • author's profile photo Former Member
    Former Member
    Posted on Apr 29, 2009 at 02:13 PM


    I just had the same error and was looking for a solution, finding this post.

    the real reason was not that librfc32.dll was not found, but librfc32.dll could not be loaded.

    Because the c-runtime library librfc32.dll was referencing was not installed on the system.

    In this case .net connector comes along as 32 Bit DLLs, librfc32.dll needs in addition msvcr71.dll and msvcp71.dll. Because you are on a 64 Bit operating system you have to copy these two DLLs to %windir%\syswow64.

    Very helpfull in this case is filemon / procmon from



    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 15, 2010 at 03:14 PM

    Para que funcione SAP Connector en un ambiente de 64 bits seguir los siguientes pasos:

    1.- Dirigirse a las propiedades del proyecto que esten desarrollando (usumimos que ya hemos generado la conexión a SAP con .NET 2003 con Framework 1.1)

    2.- Luego en la sección "Build" de nuestro proyecto ubicamos la opción "Platform target" y escogemos "x86"

    3.- Asumimos que contamos con las siguientes dll traidas desde la carpeta c:WindowsSystem32 de nuestro ambiente de 32bits: librfc32.dll, msvcp71.dll, msvcr71.dll, SAP.Connector.dll y SAP.Conector.Rfc.dll

    4.- Copiar el archivo librfc32.dll hacia la siguiente ruta C:WINDOWSsystem

    5.- Copiar el archivo msvcp71.dll hacia la siguiente ruta C:WINDOWSsystem32

    6.- Copiar los archivos msvcp71.dll y msvcr71.dll hacia la siguiente ruta C:WINDOWSSysWOW64

    7.- Arrastrar los archivos SAP.Connector.dll y SAP.Conector.Rfc.dll hacia la siguiente ruta C:WINDOWSassembly

    Si fuera necesario descarguense antes el "Microsoft Visual C++ 2008 SP1 Redistributable Package (x64)" desde la pagina de microsoft, este archivo contiene dlls necesarias para un ambiente donde no se tiene instalado VS 2008.

    Con eso me funcionó sin ningun problema.


    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.