nodejstools | Node.js Tools for Visual Studio | Runtime Evironment library

I have been trying to deploy a Meteor JS app on Google cloud but keeps getting this error. I followed this tutorial - https://cloud.google.com/community/tutorials/run-meteor-on-google-app-engine which is really good and understandable to follow. I don't know if the error I'm getting is as a result of error in my config but to the best of my knowledge I think I've followed the tutorial religiously.

this is my config. i am working in Windows 10 environment.

I have upgraded the Node.js version to 8.8.1, and updated this in the process environmental variables, iisnode.yml, Web.config and package.json.

Nonetheless, requests going to the app now get rejected with the following error:

The iisnode module is unable to start the node.exe process. Make sure the node.exe executable is available at the location specified in the https://github.com/tjanczuk/iisnode/blob/master/src/samples/configuration/web.config>system.webServer/iisnode/@nodeProcessCommandLine element of web.config. By default node.exe is expected in one of the directories listed in the PATH environment variable.

I tried to update the file path in Kudu to reflect the path to the node.exe I'm interested in ("D:\Program Files (x86)\nodejs\8.1.1\node.exe"), but got an error saying I was not authorized to do this.

The relevant files:

iisnode.yml:

I have a node js express app generated from Visual Studio 2017 Basic Azure Node.js Express Application. I assume all the configuration required for Azure deployment is set in the Web.config file that comes with the template, but i am getting this error after Azure publish:

iisnode encountered an error when processing the request. HRESULT: 0x2 HTTP status: 500 HTTP subStatus: 1002 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'.

If i publish the app without modifying anything, it works well, but the moment i add my static files, and add relevant modules, it starts giving me the error above. Below is my web.config file

I have a web application with continuous integration via visual studio team services and I want to add unit tests for my typescript code.

First try

At first I tried to create a Blank Node.js Console Application in my solution. I wrote some tests (with 'mocha',etc...) which worked fine locally. But as I commited the solution I noticed the build server not being able to...well...build:

I have an app that works locally but when I deploy it to azure POST requests receive a 404 response. Various answers suggest that I need to edit my web.config but I don't see what needs to be changed.

If it's relevant: My POSTs are to a path called /receive on the server, which should be handled by server.js