iisnode encountered an error when processing the request

Question

I'm trying to check angularjs app with a server side written in node js and this is an error i get when i run in by webmatrix

iisnode encountered an error when processing the request.

HRESULT: 0x2 
HTTP status: 500 
HTTP reason: Internal Server Error 

You are receiving this HTTP 200 response because system.webServer/iisnode/@devErrorsEnabled configuration setting is 'true'.

In addition to the log of stdout and stderr of the node.exe process, consider using debugging and ETW traces to further diagnose the problem.

The node.exe process has not written any information to stderr or iisnode was unable to capture this information. Frequent reason is that the iisnode module is unable to create a log file to capture stdout and stderr output from node.exe. Please check that the identity of the IIS application pool running the node.js application has read and write access permissions to the directory on the server where the node.js application is located. Alternatively you can disable logging by setting system.webServer/iisnode/@loggingEnabled element of web.config to 'false'.

Does somebody know how to fix it?

Answer 1

Your application pool doesn't seem to have enough permissions to write to the current folder.

1. You can either edit the permissions to give the IIS_IUSRS group write permissions to that folder

2. Go into the advanced settings menu and under Process Model -> Identity change the user account to a user that already has write permissions.

Answer 2

It looks like your iisnode cannot write its log file, perhaps because it does not have write permissions. If you have access to to the server then you can check inside the app's folder for an iisnode folder, that is where iisnode tries to write its logs by default.

Until you get this log info you are stuck because the 500 error you are seeing only tells you that the error has occurred on the server somewhere. You need the logs to give you the info you need to proceed.

The only other alternative is to run the whole thing locally and use something like node-inspector (I use grunt-node-inspector) to debug into the nodeJS code to see what is happening.