-
Notifications
You must be signed in to change notification settings - Fork 1.9k
lib_lightgbm.dll is not getting loaded while running benchmarks on .NetFramework #1945
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@TomFinley who is the owner of the lightgbm package who can look at this? |
Are you getting this error on other non windows platform? Based on very quick search seems like windows upgrade error. This dll comes from a nuget that is published by @guolinke |
I am getting this error in windows platform. I have not checked it for non-windows platform |
@Anipik - can you try adding |
@eerhardt I tried running it by specifying 64 bit its still not able to find the lighgbm dll |
TL.TR - another way to fix this issue is to install Microsoft Visual C++ Redistributable x64 This is how it happened.
Tried various combinations of publishing, including Self-Contained deployment with configuration targeting Any CPU, x86, x64, but it didn't run on server #3. Only comparing list of installed programs I noticed that the only missing part on server #3 is MS Visual C++ Redistributable x64. I think I have this update on local computer because I have VS 2019 installed, server #2 is a Server Edition, so probably has this update by default, but server #3 was a custom installation of Windows Pro and it was missing it. |
when we try to run this https://github.com/dotnet/machinelearning/blob/master/test/Microsoft.ML.Benchmarks/Numeric/Ranking.cs#L50
and
https://github.com/dotnet/machinelearning/blob/master/test/Microsoft.ML.Benchmarks/Text/MultiClassClassification.cs#L47
on .netFramework, the benchmark is not able to load the lib_lightgbm.dll
The benchmarks run properly on .NetCore
cc @danmosemsft @eerhardt @adamsitnik
The text was updated successfully, but these errors were encountered: