Skip to main content

Resolution: SAP Connection Failures after recent SAP Kernel Patches

Steve Audey
  • Updated

HOTFIX Instructions –  SAP Kernel patch RFC Connectivity Issue.

Assembly can be downloaded here: https://files.syniti.com/f/sapnco3181  
 

Download the x64 (64bit) NCo 3.1 Compiled with .NET Framework 4.6.2 release hotfix version (currently 3.1.8.1 as of 01-Oct-2026).

  1. Before applying any changes to the server, we strongly recommend backing up the IIS server through your normal system backup processes.
  2. Unblock the ZIP file and extract them into a folder.
  3. Stop ALL CranSoft Services and IIS Services
  4. Go to the CranSoft installation folder and find the ExternalAssemblies\x64 folder, the default path is: C:\Program Files (x86)\BOA\DSP\Web\bin\ExternalAssemblies\x64
  5. If you want to be safe, you can copy out the sapnco.dll and sapnco_utils.dll files into a backup folder on your system.
  6. Delete the sapnco.dll and sapnco_utils.dll files in this folder
  7. Copy in the DLLs from the unzipped driver file we supplied (there should be 3 there, you should only need the sapnco.dll and sapnco_utils.dll files)
  8. Paste those DLLs into the ExternalAssemblies\x64 folder
  9. Make a backup copy and then modify the {CransoftInstallationFolder}\Web\web.config and \Web\bin\CranSoftService64.exe.config files to include the new runtime assembly components described below.
    1. You may need to enable the File Explorer option of “Show File Extensions” to see the .config in the file name.
  10. Restart IIS and your CranSoft services

 

In your web.config and CranSoftService64.exe.config files you may have a <runtime> section. That section could already include sets of <dependentAssembly> components. You will want to add in the following dependentAssembly components:  

    <dependentAssembly>
      <assemblyIdentity name="sapnco" publicKeyToken="50436dca5c7f7d23" culture="neutral" />
      <bindingRedirect oldVersion="0.0.0.0-3.1.0.42" newVersion="3.1.0.42" />
    </dependentAssembly>
    <dependentAssembly>
      <assemblyIdentity name="sapnco_utils" publicKeyToken="50436dca5c7f7d23" culture="neutral" />
      <bindingRedirect oldVersion="0.0.0.0-3.1.0.42" newVersion="3.1.0.42" />
    </dependentAssembly>

 

If you do not see existing <depenendentAssembly> sections in your web.config or CransoftServiceExe.config files, you will need to add the parent components of <assemblyBinding> or <runtime>.

<configuration> --This is the outermost tag of the .config files and will already be there. 

  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="sapnco" publicKeyToken="50436dca5c7f7d23" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-3.1.0.42" newVersion="3.1.0.42" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="sapnco_utils" publicKeyToken="50436dca5c7f7d23" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-3.1.0.42" newVersion="3.1.0.42" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>


</configuration> --this should be the last closing tag of the .config file.

Related articles