-
Notifications
You must be signed in to change notification settings - Fork 586
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
HTTP Error 500.1013 #405
Comments
Hi John, any solution so far? I am having the same messages. I used to fetch WordPress data prior to this yet unobserved bug Here the error message iisnode encountered an error when processing the request. HRESULT: 0x6d 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'. I solved this custom development issue by setting up the Azure SDK on my local pc, then using the 'command azure site log download' to fetch the error logs and continue with these's content's information. |
500.1013 usually means your node.exe is crashing due to some exception |
+1
It doesn't specify to which folder we should change the persmissions. I did it on iisnode within my express app in (C:\Program Files\iisnode\www\express\bin), and just in case, over the whole express app folder (C:\Program Files\iisnode\www\express). Nothing changed. I also tried it over logging folder of ISS (%SystemDrive%\inetpub\logs\LogFiles). No success either. |
More info about the problem here: http://stackoverflow.com/questions/33781455/500-1013-error-when-using-iisnode-and-express |
Have you tried running iisnode sample hello world on that machine? This will help rule out iis/iisnode/node installation issues. Beyond that, can you capture ETW logs as described at http://tomasz.janczuk.org/2011/09/using-event-tracing-for-windows-to.html. |
I did, I run all the examples included the Express one. But I still having the same problem. I found out that changing I just don't understand why, and why it works perfectly with the |
@tjanczuk When using |
I even tried with a simpler application extracted from the express documents (hello world), same problem. It works on node, it doesn't in iisnode. Now I'm getting the error: |
Maybe related with this topic:#160 ? |
I am running into the same error. In my case, the error is intermittent, and seems to occur only when the request needs a significant amount of processing. I suspect that IIS is timing out, as the node function completes successfully AFTER IIS has returned a 500 error. Is there a timeout setting that can be adjusted? I might need as long as five or ten minutes to deal with the request in some cases. |
From multiple forums you can increase timeout using: <system.web>
<httpRuntime executionTimeout="3600" />
</system.web> But it didn't work, so the problem must be in something else :( |
Any updates on this issue? From what I can tell, it is happening when there are concurrent requests being made and node.js closes the pipe for some reason, causing iisnode to immediately send an HTTP500. |
@johnwp did you fix this issue? this error occures when I download file that takes more than 2 minute. I have tried increasing timeout in iis advanced settings but didn't work. |
Hi, any updates on this issue. |
I have the same error (HTTP Error 500.1013 - Internal Server Error) while sending more than 240 MB files in the Request body. we have used IIS node in Azure App service |
I have the same issue , it has also been found that a detailed page is working , but not the absolute domain |
Why is this closed when the issue still persists? I am running into the same issue. |
+1 |
Same issue here. In my case it's happening in a just HelloWorld simple app I'm trying to run |
I found out this error is not related to iis but in my nodejs. There is a default timeout in nodejs that you need to configure. |
i have encountered the same issue has anyone resolved this ? |
I'm running into the following error after deploying my node app to a local instance of IIS 7.5.7600.16385 on 64-bit Windows 7. The Node.js sample apps run without any problems in the same app pool. I have 32-bit applications disallowed. The application runs as expected in debug mode. The helloworld sample app says I'm running IISNode 0.2.16 x64 and Node.js version 0.10.33 x64.
HTTP Error
Web.config
app.js
Stdout
�[0mGET /app.js �[32m- �[0m- ms - -�[0m
ETW Trace log
The text was updated successfully, but these errors were encountered: