-
Notifications
You must be signed in to change notification settings - Fork 582
iisnode faq
Please choose x86 flavors for installation on 32-bit Windows systems, and amd64 flavors for installation on 64-bit Windows systems.
iisnode is completely async and does not block threads per request or connection. It does allocate small amounts of memory for active requests.
Please verify if your issue is already known by searching https://github.com/tjanczuk/iisnode/issues. If you don't find it there, create a new issue report. Please include the following information with your bug report:
- Windows OS version and bitness (32/64)
- IIS version
- which version of iisnode you are using (changelist number if compiled, binary package name if downloaded)
- all interesting information from the IIS error page that displays (if any)
- all interesting information IIS logs into the Event Viewer (http://msdn.microsoft.com/en-us/library/ms524984(v=vs.90).aspx)
If you run into a 503 status code with IIS reporting error code 0x5 (ERROR_ACCESS_DENIED), make sure the identity of the application pool running the site that hosts your node.js application has read & execute rights to node.exe on disk. If you are using the default IIS configuration (DefaultAppPool running under ApplicationPoolIdentity), you can set appropriate ACLs on the node.exe by running:
icacls %systemdrive%\node\node.exe /grant IIS_IUSRS:rx