-
Notifications
You must be signed in to change notification settings - Fork 641
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
Edge fails on machines without msvcr110.dll on the DLL path #85
Comments
The log from Process Monitor used to diagnose this indicates lack of success in looking up msvcr110.dll:
|
This issue was reproed on Windows Azure Worker Role machines. |
I have a similar issue with msvcr120.dll when using Edge.JS from some ASP.NET Web API code. I've included msvcr120.dll from C:\windows\system32 on my dev machine in the bin\edge\x64 (or x86) directory alongside node.dll to workaround. Event Viewer shows Windows Activation Service (WAS) errors. Process Monitor shows same "NAME NOT FOUND" errors as above. |
Current mechanism of co-locating msvcr110.dll with edge.node does not work - the dll search sequence does not include this location. As a result edge apps on machines that do not otherwise have msvcr110.dll on the dll search path fail with
One workaround is to copy the appropriate version of msvcr110.dll next to the node.exe used to run the application, e.g.:
Complete and correct workaround TBD.
The text was updated successfully, but these errors were encountered: