Cannot load onedal_thread.1.dll

BenOchoa · ‎07-29-2023

Under Windows 10 Pro 10.0.19045 using DAL 2023.2.0.49579, when linking to onedal_core_dll.lib (release) or onedal_cored_dll.lib (debug), at runtime onedal_core.1.dll loads fine but the following error occurs.

Intel oneDAL FATAL ERROR: Cannot load onedal_thread.1.dll.

The application also (and primarily) uses IPP 2021.9.0.49457 and MKL 2023.2.0.49500, and is linking to the following:

mkl_intel_lp64_dll.lib
mkl_intel_thread_dll.lib
mkl_core_dll.lib
ippi.lib
ipps.lib
ippcv.lib
ippcc.lib
ippvm.lib
ippcore.lib
onedal_core_dll.lib
libiomp5md.lib

Please help to resolve this issue, as this same code worked fine with older (1-2 years ago; versions unknown) versions of IPP, MKL, and DAL.

Thanks,
Ben

Also, it may not be related but while trying to resolve this issue myself, Dependency Walker found a circular dependency when loading onedal_core.1.dll. The function GetLogicalProcessorInformationEx is being imported from API-MS-WIN-CORE-SYSINFO-L1-1-0.DLL, which is importing the function GetLogicalProcessorInformationEx from KERNEL32.DLL, which is importing the function GetLogicalProcessorInformationEx from API-MS-WIN-CORE-SYSINFO-L1-1-0.DLL, etc.

BenOchoa · ‎07-29-2023

I removed all use of IPP and MKL, and still receive the error:

Intel oneDAL FATAL ERROR: Cannot load onedal_thread.1.dll.

DiyaN_Intel · ‎07-31-2023

Hi,

Thank you for posting in Intel communities.

Please provide the following details so that we could reproduce the issue on our end :

1. Sample reproducer code

2. Exact steps and the commands used

Regards,

Diya

BenOchoa · ‎07-31-2023

Following is an example main.cpp illustrating this issue.

#if defined( _MSC_VER )
#pragma warning( push )
// this function or variable may be unsafe
#pragma warning( disable: 4996 )
#endif // _MSC_VER
#include <daal.h>
#if defined( _MSC_VER )
#pragma warning( pop )
#endif // _MSC_VER

int main( int argc, char *argv[] )
{
    const int width = 4;
    const int height = 3;
    const unsigned char image[width * height] = 
    {
        0, 1,  2,  3, 
        4, 5,  6,  7, 
        8, 9, 10, 11
    };
    daal::data_management::NumericTablePtr pData = 
        daal::data_management::HomogenNumericTable<unsigned char>::create( 
            daal::data_management::DictionaryIface::equal, 
            const_cast<unsigned char*>( image ), 1, width * height );

    const float radius = 0;
    const int minObservations = 1;
    daal::algorithms::dbscan::Batch<float> dbscan( radius, minObservations );
    dbscan.input.set( daal::algorithms::dbscan::data, pData );
    dbscan.compute();
    const int numClusters = dbscan.getResult()->get( 
        daal::algorithms::dbscan::nClusters )->getValue<int>( 0, 0 );

    return 0;
}

Built using Microsoft Visual Studio Professional 2019 version 16.10.2.

Compiler arguments:

/JMC /external:env:"EXTERNAL_INCLUDE" /permissive- /ifcOutput "x64\Debug\" /GS /W3 /Zc:wchar_t /I"C:\Program Files (x86)\Intel\oneAPI\dal\2023.2.0\include" /ZI /Gm- /Od /sdl /Fd"x64\Debug\vc142.pdb" /Zc:inline /fp:precise /D "_DEBUG" /D "_CONSOLE" /D "_UNICODE" /D "UNICODE" /errorReport:prompt /WX- /Zc:forScope /RTC1 /Gd /MDd /FC /Fa"x64\Debug\" /EHsc /nologo /Fo"x64\Debug\" /Fp"x64\Debug\testdaal.pch" /diagnostics:column

Linker arguments:

/OUT:"C:\Projects\testdaal\x64\Debug\testdaal.exe" /MANIFEST /NXCOMPAT /PDB:"C:\Projects\testdaal\x64\Debug\testdaal.pdb" /DYNAMICBASE "onedal_cored_dll.lib" "kernel32.lib" "user32.lib" "gdi32.lib" "winspool.lib" "comdlg32.lib" "advapi32.lib" "shell32.lib" "ole32.lib" "oleaut32.lib" "uuid.lib" "odbc32.lib" "odbccp32.lib" /DEBUG /MACHINE:X64 /INCREMENTAL /PGD:"C:\Projects\testdaal\x64\Debug\testdaal.pgd" /SUBSYSTEM:CONSOLE /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /ManifestFile:"x64\Debug\testdaal.exe.intermediate.manifest" /LTCGOUT:"x64\Debug\testdaal.iobj" /ERRORREPORT:PROMPT /ILK:"x64\Debug\testdaal.ilk" /NOLOGO /LIBPATH:"C:\Program Files (x86)\Intel\oneAPI\dal\2023.2.0\lib\intel64" /TLBID:1

This compiles and links without error but at runtime results in

Intel oneDAL FATAL ERROR: Cannot load onedal_thread.1.dll.

though onedal_core.1.dll loads fine prior to this fatal error.

DiyaN_Intel · ‎08-07-2023

Hi,

Thank you for providing all the details.

We were able to reproduce the issue from our end.

Please make these necessary changes to make your program work in Microsoft Visual Studio

1. Please set the properties as Debug and x64 both in the Visual Studio editor as well as on the properties page of the project, while changing your Include and library directories.

2. In the properties of Visual Studio please make these changes :

a. In the configuration properties --->>C++ --->>General--->> Add the below path

C:\Program Files (x86)\Intel\oneAPI\dal\2023.2.0\include

b. In the configuration properties--- >> C++ --->> Linker -->> Input --->>> Add this library in the Additional Dependencies

onedal_cored_dll.lib

c. In configuration properties ---> vc++ directories--->In the library directories, Add the below path

C:\Program Files (x86)\Intel\oneAPI\dal\2023.2.0\lib\intel64

After making all the above changes, your program should work fine.

If this resolves your issue, make sure to accept this as a solution.

This would help others with similar issues. Thank you!

Regards,

Diya

BenOchoa · ‎08-07-2023

Please carefully look at the compiler and linker arguments in my previous post and you will see this is already configured correctly. Again, this is not a compile- or link-time error. This is a runtime error, where onedal_core.1.dll loads fine but onedal_thread.1.dll does not load.

DiyaN_Intel · ‎08-14-2023

Hi,

We are investigating your issue at our end and working on this internally. We will get back to you with an update soon.

Regards,

Diya

Alex_H_Sin · ‎09-01-2023

Hi Ben,

My name is Alex and I have picked up your case. I escalated this issue to the DAL team and they are working on reproducing your issue. I will update you along the way.

Best,

Alex

Alex_H_Sin · ‎09-05-2023

Hi Ben,

Our engineering team is not able to reproduce your issue on versions DAL 2023.2.0.49579 and 2023.2.0.49396 using the following cmake configs:

----------------------------------------------------------------------------------------------

# without cmake oneDAL module

cmake_minimum_required(VERSION 3.21)

project (Test)

add_executable(Test test.cpp)

target_include_directories(Test PRIVATE $ENV{DALROOT}/include)

target_link_directories(Test PRIVATE $ENV{DALROOT}/lib/intel64)

target_link_directories(Test PRIVATE $ENV{TBBROOT}/lib/intel64/vc14)

target_link_libraries(Test PUBLIC onedal_cored_dll.1.lib tbb12.lib tbbmalloc.lib)

----------------------------------------------------------------------------------------------

cmake_minimum_required(VERSION 3.21)

project (Test)

set(CMAKE_BUILD_TYPE Release)

set(ONEDAL_USE_DPCPP no)

set(ONEDAL_INTERFACE no)

set(LINK_TYPE "so")

find_package(oneDAL REQUIRED)

add_executable(Test test.cpp)

target_include_directories(Test PRIVATE ${oneDAL_INCLUDE_DIRS})

target_compile_options(Test PRIVATE ${ONEDAL_CUSTOM_COMPILE_OPTIONS})

target_link_libraries(Test PRIVATE ${oneDAL_IMPORTED_TARGETS})

target_link_options(Test PRIVATE ${ONEDAL_CUSTOM_LINK_OPTIONS})

set_target_properties(Test PROPERTIES RUNTIME_OUTPUT_DIRECTORY .)

----------------------------------------------------------------------------------------------

Can you try these and see if the error persists?

BenOchoa · ‎09-06-2023

Thanks, Alex, but I did not build DAL from source. I downloaded DAL 2023.2.0.49579 from https://www.intel.com/content/www/us/en/developer/tools/oneapi/onedal-download.html Can the engineering team reproduce the runtime error from this release build?

Alex_H_Sin · ‎09-11-2023

Hi Ben,

We are still working on reproducing the issue and I will give you an update soon.

Thanks,

Alex

Alex_H_Sin · ‎10-04-2023

Hi Ben,

Unfortunately, the engineering team is unable to reproduce your issue on DAL from oneAPI Base Kit 2023.2.0.49579 given the information you provided. Can you provide additional information?

Best,

Alex

Alex_H_Sin · ‎10-13-2023

Hi Ben,

I have not heard from you for some time, so this ticket will be closed. If you need further assistance, please create a new ticket.

Thank you,

Alex