HTTP Error 500.1002 - Internal Server Error

I am trying to host prerender which is a node.js app inside IIS on my windows server 2008 Enterprise R2. Prerender runs fine via the command line. if I try to host it with IISNode. I keep getting the error below:

Application has thrown an uncaught exception and is terminated: Error: write ENOTSUP - cannot write to IPC channel. at errnoException (child_process.js:1001:11) at ChildProcess.target.send (child_process.js:465:16) at Worker.send (cluster.js:406:21) at sendInternalMessage (cluster.js:399:10) at handleResponse (cluster.js:177:5) at respond (cluster.js:192:5) at Object.messageHandler.queryServer (cluster.js:247:5) at handleMessage (cluster.js:197:32) at ChildProcess.emit (events.js:117:20) at handleMessage (child_process.js:322:10)

On the Windows Task Manager, I could see node.exe started then disappeared.

Any ideas would be greatly appreciated as I am out of clues now.

Thank you.

Bing

could you please paste your web.config and the main script file if possible?

Hi

Here is the config:

The main script I use is https://github.com/prerender/prerender/blob/master/server.js

Please let me know if you need anything else.

Cheers

Bing

I have same issue with Prerender and IIS 8.5. I tried with iisnode tag and without this in web.config. My web.config is similar to icyice80 but I have put "server.js" in path attribute,

Sample applications from Node.js runs flawlessly, chrome debug included.

Same issue on Azure websites, trying to run pencilblue cms

I'm having the same issue as @icyice80 trying to run prerender with iisnode. Apparently, iisnode doesn't support cluster which is what prerender uses internally.

any news on this issue??

iisnode does not support cluster which prerender uses internally as @tysonnero mentioned above. Cluster does not support named pipes on windows which is the main issue here.

add node to the application settings on Azure. this helps at least for the azure problem

Same issue on Azure websites, trying to run pencilblue [cms]

same issue here any news?

I had this same issue. The problem for me was that the account that the application pool was running under did not have write access to the filesystem where the IIS node logs were being written. I changed the identity to the System account and it worked.

I had the same problem. It was caused by not enough rights of the application pool user, when the package "win-ca" was used.

As a temporary solution, instead of using "win-ca" we disabled checking of the local certificates.

Hi, how did you do this exactly? @allens01

@EnderDev I did that in the Advanced Settings of the application pool, I set the identity to LocalSystem.

This is not necessary the best solution as some companies might raise this as a security concern as the app has higher rights than required. Alternatively, if you app pool is running under the context of a service account, you can try giving that account rights to the directory where the IIS node logs are written?