Skip to Content

Sap Logon Control

Hi, experts.

Can I still using Sap Logon Control activex component on my Windows 10 applications to execute functions on SAP via RFC (Remote Function Call)?

I'm using Sap Logon Control importing the activex component wdtlog.ocx to my non-sap delphi application. This activex comes with SAP GUI installation and my application is working fine. But I read this ocx was classic rfc library (librfc32.dll) dependent and this library is obsolete now. I also read that since SAP GUI version 7.50 this ocx is no longer classic rfc library dependent. Is this activex (wdtlog.ocx) SapLogonCtrl.dll dependent? Is wdtlog.ocx becomming obsolete? Or does wdtlog.ocx is totally independent now and I can use it for long?

I didn't find the answers anywhere and I really appreciate any tip that can guide me to the right path!

Add a comment
10|10000 characters needed characters exceeded

  • Thank you, Luis and Sandra.

    These workarounds will help me if I have to compile my application using 64 bits.

    I have now received the information from SAP that ActiveX controls such as SAP Logon Control (wdtlog.ocx), SAP Remote Function Call Control (wdtfuncs.ocx) and SAP BAPI Control (wdobapi.ocx) and their unicode versions which used the classical RFC library has been moved to the new SAPNWRFC. Technically from librfc32.dll to sapnwrfc.dll. SAP GUI for Windows 7.70 includes 64bit versions of these controls. Since these need sapnwrfc.dll, the delivery also includes a 64bit version of this dll.

    Regards!

  • Hi and welcome to the SAP Community!

    Thank you for visiting SAP Community to get answers to your questions. Since you're asking a question here for the first time, I recommend that you familiarize yourself with https://community.sap.com/resources/questions-and-answers (if you haven't already), as it provides tips for preparing questions that draw responses from our members. For example, you can outline what steps you took to find answers (and why they weren't helpful) and share screenshots of what you've seen/done. The more details you provide, the more likely it is that members will be able to assist you.
    Should you wish, you can revise your question by selecting Actions, then Edit (although once someone answers your question, you'll lose the ability to edit the question -- but if that happens, you can leave more details in a comment).

    Finally, if you're hoping to connect with readers, please consider adding a picture to your profile as it encourages readers to respond to you. Here's how you do it: https://www.youtube.com/watch?v=F5JdUbyjfMA&list=PLpQebylHrdh5s3gwy-h6RtymfDpoz3vDS.

    Best,
    Lena
    SAP Community Moderator

Related questions

1 Answer

  • Posted on Sep 28, 2020 at 10:30 PM

    Hi Alexandre Dantas,

    I am also interested in the topic, hence the reason I replying to help and also learn.

    From an app perspective, you will start having trouble with SAPGUI because of it is a 32bit program , which is also true for its Active libraries like LogonControl.

    There are workaounds via DLL surrogates, but they require changes to the registry and might not be stable longterm

    You can also use SAP Function instead of LogonControl, and fix the registry entries below

    [HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{5B076C03-2F26-11CF-9AE5-0800096E19F4}]
    @="SAP Remote Function Call"
    "AppID"="{5B076C03-2F26-11CF-9AE5-0800096E19F4}"
    
    [HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{5B076C03-2F26-11CF-9AE5-0800096E19F4}\Control]
    @=""
    
    [HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{5B076C03-2F26-11CF-9AE5-0800096E19F4}\InprocServer32]
    @="c:\\program files (x86)\\sap\\frontend\\sapgui\\wdtfuncs.ocx"
    "ThreadingModel"="Apartment"
    
    [HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{5B076C03-2F26-11CF-9AE5-0800096E19F4}\MiscStatus]
    @="0"
    
    [HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{5B076C03-2F26-11CF-9AE5-0800096E19F4}\MiscStatus\1]
    @="132241"
    
    [HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{5B076C03-2F26-11CF-9AE5-0800096E19F4}\ProgID]
    @="SAP.Functions"
    
    [HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{5B076C03-2F26-11CF-9AE5-0800096E19F4}\ToolboxBitmap32]
    @="c:\\program files (x86)\\sap\\frontend\\sapgui\\wdtfuncs.ocx, 1"
    
    [HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{5B076C03-2F26-11CF-9AE5-0800096E19F4}\TypeLib]
    @="{5B076C00-2F26-11CF-9AE5-0800096E19F4}"
    
    [HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{5B076C03-2F26-11CF-9AE5-0800096E19F4}\Version]
    @="5.0"
    
    [HKEY_CLASSES_ROOT\WOW6432Node\AppID\{5B076C03-2F26-11CF-9AE5-0800096E19F4}]
    "DllSurrogate"=""

    Operating system will continue to evolve, and 64 is kind of standard in everything. I would start into looking how you can migrate your code to SCP.

    Hope it sheds a light,

    Luis

    Add a comment
    10|10000 characters needed characters exceeded

    • Since SAP GUI <= 7.60 has many 32bits controls, they can't work if they are run from 64 bits applications, like maybe MS Office application (e.g. run from VBA in Excel 64 bits).

      In that case, you may make it work with DLLSurrogate, which will be supported long enough until SAP GUI 7.70 is officially released, as it will offer 64 bits controls -> You may save the following lines to a MakeSAPGUIRFC64bits.reg file and execute it as an administrator from Windows File Explorer to automatically update the registry values:

      Windows Registry Editor Version 5.00
      
      ; ====================================================================================
      ; SAP Logon Unicode Control %ProgramFiles(x86)%\SAP\FrontEnd\SAPgui\wdtlogU.ocx {0AAF5A11-8C04-4385-A925-0B62F6632BEC}
      ; ====================================================================================
      
      [HKEY_CLASSES_ROOT\WOW6432Node\AppID\{0AAF5A11-8C04-4385-A925-0B62F6632BEC}]
      "DllSurrogate"=""
      
      [HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{0AAF5A11-8C04-4385-A925-0B62F6632BEC}]
      "AppID"="{0AAF5A11-8C04-4385-A925-0B62F6632BEC}"
      
      [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{0AAF5A11-8C04-4385-A925-0B62F6632BEC}]
      
      ; ====================================================================================
      ; SAP Remote Function Call Unicode Control %ProgramFiles(x86)%\SAP\FrontEnd\SAPgui\wdtfuncu.ocx {0AF427E7-03B9-4673-8F21-F33A683BCE28}
      ; ====================================================================================
      
      [HKEY_CLASSES_ROOT\WOW6432Node\AppID\{0AF427E7-03B9-4673-8F21-F33A683BCE28}]
      "DllSurrogate"=""
      
      [HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{0AF427E7-03B9-4673-8F21-F33A683BCE28}]
      "AppID"="{0AF427E7-03B9-4673-8F21-F33A683BCE28}"
      
      [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{0AF427E7-03B9-4673-8F21-F33A683BCE28}]
      
      ; ====================================================================================
      ; SAP Logon Control (not Unicode) %ProgramFiles(x86)%\SAP\FrontEnd\SAPgui\wdtlog.ocx {B24944D6-1501-11CF-8981-0000E8A49FA0}
      ; ====================================================================================
      
      [HKEY_CLASSES_ROOT\WOW6432Node\AppID\{B24944D6-1501-11CF-8981-0000E8A49FA0}]
      "DllSurrogate"=""
      
      [HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{B24944D6-1501-11CF-8981-0000E8A49FA0}]
      "AppID"="{B24944D6-1501-11CF-8981-0000E8A49FA0}"
      
      [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{B24944D6-1501-11CF-8981-0000E8A49FA0}]
      
      ; ====================================================================================
      ; SAP Remote Function Call Control (not Unicode) %ProgramFiles(x86)%\SAP\FrontEnd\SAPgui\wdtfuncs.ocx {5B076C03-2F26-11CF-9AE5-0800096E19F4}
      ; ====================================================================================
      
      [HKEY_CLASSES_ROOT\WOW6432Node\AppID\{5B076C03-2F26-11CF-9AE5-0800096E19F4}]
      "DllSurrogate"=""
      
      [HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{5B076C03-2F26-11CF-9AE5-0800096E19F4}]
      "AppID"="{5B076C03-2F26-11CF-9AE5-0800096E19F4}"
      
      [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{5B076C03-2F26-11CF-9AE5-0800096E19F4}]

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.