Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Upgrade PREPARE: errors ocurred during the registration of LIBRFC32.DLL

Hi All,

This is our infrastructure:

Windows 2000



Kernel Release 46D

We want to upgrade to SAP R/3 4.7 x 200 SR1, in this moment we are running the PREPARE.EXE but the General Checks Module Finished in status <b>FAILED</b>. When you open the <b>CHECKS.LOG</b> file it gives this error:

Errors occurred during the registration of LIBRFC32.DLL

Change to directory C:\WINNT\system32 and try to execute

the following command manually:

<b> regsvr32.exe LIBRFC32.DLL</b>

I ran this command but it gives this message.

LIBRFC32.DLL was loaded, but the DllRegisterServer entry point was not found.

DllRegisterServer may no bet exported, or a corrupt version of LIBFRC32.DLL may be in memory. Consider using pview to detect and remove it.

I google the error and found an IBM link that say you this:


How to resolve missing file: LIBRFC32.DLL


To solve this problem, install the SAPGUI on your machine. The missing DLL will then be copied to your system.

In fact before the ran of the PREPARE <b>we installed SAP GUI 7.10</b>

as a UPGRADE request.

After that, I searched in my computer for the LIBRFC32.DLL file and it is located here: <b>C:\WINNT\SYSTEM32\LIBRFC32.DLL</b>

Then I searched in the CDs. That I received from SAP.

In the SAP CD where the SAP Gui is located (SAP Presentation 2004s) I found the same file LIBRFC32.DLL file with 3,57 MB that is located in the C:\WINNT\SYSTEM32 probably it was isntalled when i installed the SAP GUI.

But in the actual SAP Kernel there is another version of the LIBRFC32.DLL file version 2,26 MB. So I had two version if the file, the old one of the Kernel and the new one of the SAP Gui 7.1. Does anybody have an idea about how to resolved this version conflict?

Please Some tips!

Best Regards,

Desiree Cardenas

Former Member

As far as I remember my courses, one should<b> NOT install a SAPGUI </b>on the same system, the server is running on.

The requirement mentioned in the installation is pointing to the <b>client </b>systems accessing the system - if necessary - during some upgrade phases when the new kernel runs. A SAPGUI is not necessary for an upgrade on the SERVER.

I'd go for the following:

- unregister the DLL (regsvr32 /u librfc32.dll)

- rename the DLL

- copy a librfc32.dll/librfc32u.dll from a SAPGUI 6.40

- copy that one to %SYSTEMROOT%\system32

- register it (regsvr32 librfc32.dll)



0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question