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

Unable to load DLL 'libuv': The specified module could not be found - (kestrel) Windows IOT #1111

Closed
matizk144 opened this Issue Nov 22, 2015 · 8 comments

Comments

Projects
None yet
5 participants
@matizk144
Copy link

matizk144 commented Nov 22, 2015

Hi!
I just trying to run basic asp.net project (Hello world) on my RP2, but unfortunatelly always I received error:

.\web : System.DllNotFoundException: Unable to load DLL 'libuv': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
    + CategoryInfo          : NotSpecified: (System.DllNotFo...LT: 0x8007007E):String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

   at Microsoft.AspNet.Server.Kestrel.Networking.Libuv.NativeMethods.uv_loop_size()
   at Microsoft.AspNet.Server.Kestr
el.Networking.Libuv.loop_size()
   at Microsoft.AspNet.Server.Kestrel.Networking.UvLoopHandle.Init(Libuv uv)
   at Microsoft.AspNet.Server.Kestrel.KestrelThread.ThreadStart(Object parameter)

The problem not appear on my desktop computer for x86 & x64 architectures.
I checked packages and all looks fine, libuv.dll exists.
Btw, when I try run launch server in IOT using weblistener, server starts.

@moozzyk

This comment has been minimized.

Copy link
Contributor

moozzyk commented Nov 22, 2015

You need to publish for win10-arm runtime (--runtime option) - bug aspnet/KestrelHttpServer#340

@Eilon

This comment has been minimized.

Copy link
Member

Eilon commented Nov 22, 2015

@moozzyk close this?

@matizk144

This comment has been minimized.

Copy link

matizk144 commented Nov 22, 2015

Always I restore / publish with runtime option. I checked again and doesn't work. Btw. in published package "Microsoft.AspNet.Server.Kestrel" I have folder runtime:
To better understand I use path:
In location:
\10.0.1.61\c$\compiled\approot\packages\Microsoft.AspNet.Server.Kestrel\1.0.0-rc1-final\runtimes
I have folders: osx, win7-x64, win7-x86, win10-arm, which all include libuv.(in subfolder native)
Path example:
\10.0.1.61\c$\compiled\approot\packages\Microsoft.AspNet.Server.Kestrel\1.0.0-rc1-final\runtimes\win10-arm\native\libuv.dll

So, on first looks, that required dlls exists, but something is wrong to load dll. I tryied to rename folder win10-arm to win7-arm, but I have the same result.

@meriturva

This comment has been minimized.

Copy link

meriturva commented Nov 23, 2015

The same here.....i think is it related to: aspnet/KestrelHttpServer#216 and aspnet/KestrelHttpServer#106

@moozzyk

This comment has been minimized.

Copy link
Contributor

moozzyk commented Nov 24, 2015

This is a bug indeed. I am not sure if this is a regression or I tried a slightly different scenario (probably the latter) because I did run Kestrel on a R-Pi2 to verify aspnet/dnx#3095.
FWIW

  • publishing with --runtime does not include win10 specific arm dlls because the application is published for win7-arm. I opened a bug for this in the dnx repo: aspnet/dnx#3197
  • publishing with --framework is completely broken because the application is published for win7-x86 and win7-x64 even though my original app was only restored for win10-arm. For this I commented on a bug we already had

I think for now the problem could be worked around adding {APPFOLDER}\approot\packages\Microsoft.AspNet.Server.Kestrel\1.0.0-rc2-15950\runtimes\win10-arm\native to the %PATH%.

@matizk144

This comment has been minimized.

Copy link

matizk144 commented Nov 24, 2015

I resolved problem, copying libuv.dll to folder, where Microsoft.AspNet.Server.Kestrel exist. But unfortunatelly I observed, that in published package, published runtime (dnx) still use packages from C:\Users[user.dnx\packages.

@MelbourneDeveloper

This comment has been minimized.

Copy link

MelbourneDeveloper commented Nov 22, 2016

I'm getting this error as well. I have all the latest NuGet packages for ASP .NET Core as of right now

@moozzyk

This comment has been minimized.

Copy link
Contributor

moozzyk commented Nov 22, 2016

You cannot get this error since this applies to win10-arm and currently there is no arm runtime available. See also: aspnet/KestrelHttpServer#216 (comment)

ryanbrandenburg pushed a commit that referenced this issue Nov 20, 2018

Merge pull request #1111 from aspnet/rel/2.0.0
Complete the lstat patching for #1101
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment