500 error when run the app in azure

[jimeilong]

Hi ,
when i try to open the url and it's show a server error.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 681e10a1-05d3-5761-2afd-42602a7efecf
• Version Independent ID: f72e21b1-3530-8554-f1f1-fc66b222a485
• Content: Real-time data visualization of sensor data from your Azure IoT hub – Web Apps
• Content Source: articles/iot-hub/iot-hub-live-data-visualization-in-web-apps.md
• Service: iot-hub
• GitHub Login: @rangv
• Microsoft Alias: rangv

[jimeilong]

[Mike-Ubezzi-MSFT]

@jimeilong Thanks for the feedback. We are actively investigating and will get back to you soon.

[Mike-Ubezzi-MSFT]

@jimeilong I am in the process of completing this tutorial but having issues unrelated to your specific issue. Are you still experiencing this issue? Thanks for updating this issue with any additional steps you have taken to resolve this. Otherwise, given me 24 hours to look into this. Thank you!

[Mike-Ubezzi-MSFT]

I am able to reproduce this:

Server 500 Error

Step 5 completed successfully: Download the web app from GitHub, and upload it to Azure for the web app to host. To do so, run the following commands:

I have assigned the issue to the content author to evaluate and update as appropriate.

[rubinstu]

I am getting the same error. Has this been resolved?

[paolo-tn]

HI, I'encountering the same error. Any fixes ?

[MBCO]

Same error still exist. Any fixes. Mij logfile show the following
D:\home\site\wwwroot\node_modules\azure-event-hubs\dist\lib\rhea-promise\connection.js:183

async createSender(options) {

      ^^^^^^^^^^^^

SyntaxError: Unexpected identifier

at Object.exports.runInThisContext (vm.js:76:16)

at Module._compile (module.js:542:28)

at Object.Module._extensions..js (module.js:579:10)

at Module.load (module.js:487:32)

at tryModuleLoad (module.js:446:12)

at Function.Module._load (module.js:438:3)

at Module.require (module.js:497:17)

at require (internal/module.js:20:19)

at Object.<anonymous> (D:\home\site\wwwroot\node_modules\azure-event-hubs\dist\lib\rhea-promise\index.js:16:20)

at Module._compile (module.js:570:32)

Application has thrown an uncaught exception and is terminated:

D:\home\site\wwwroot\node_modules\azure-event-hubs\dist\lib\rhea-promise\connection.js:183

async createSender(options) {

      ^^^^^^^^^^^^

SyntaxError: Unexpected identifier

at Object.exports.runInThisContext (vm.js:76:16)

at Module._compile (module.js:542:28)

at Object.Module._extensions..js (module.js:579:10)

at Module.load (module.js:487:32)

at tryModuleLoad (module.js:446:12)

at Function.Module._load (module.js:438:3)

at Module.require (module.js:497:17)

at require (internal/module.js:20:19)

at Object.<anonymous> (D:\home\site\wwwroot\node_modules\azure-event-hubs\dist\lib\rhea-promise\index.js:16:20)

at Module._compile (module.js:570:32)

<title>IIS Detailed Error - 500.1002 - Internal Server Error</title> <style type="text/css"> </style>

HTTP Error 500.1002 - Internal Server Error

The page cannot be displayed because an internal server error has occurred.

Most likely causes:

• IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
• IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
• IIS was not able to process configuration for the Web site or application.
• The authenticated user does not have permission to use this DLL.
• The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.

Things you can try:

• Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
• Check the event logs to see if any additional information was logged.
• Verify the permissions for the DLL.
• Install the .NET Extensibility feature if the request is mapped to a managed handler.
• Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.

Detailed Error Information:

Module	iisnode
Notification	ExecuteRequestHandler
Handler	iisnode
Error Code	0x00000002

Requested URL	https://MartijnDemoApp:80/server.js
Physical Path	D:\home\site\wwwroot\server.js
Logon Method	Anonymous
Logon User	Anonymous

More Information:

This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.

View more information »

Microsoft Knowledge Base Articles:

[Mike-Ubezzi-MSFT]

@robinsh @xinshiMSFT Any chance you can assist with fixing this tutorial, or know someone who can address this?

[Mike-Ubezzi-MSFT]

@jimeilong @rubinstu @MBCO Possible solution to this issue is: For running sample, you must modify node version in app settings. Change value for "WEBSITE_NODE_DEFAULT_VERSION" to "8.9.4".

Yes the sample doesn't run because by default the version of node is "6.9.1" and I had an error in library.

Can one of you test this out? Apologies for the delay on this. Regards, ~Mike

[Mike-Ubezzi-MSFT]

Fixed!

[Mike-Ubezzi-MSFT]

Please update the doc.

For running sample, you must modify node version in app settings. Change value for "WEBSITE_NODE_DEFAULT_VERSION" to "8.9.4".

[Asvaldrz]

@Mike-Ubezzi-MSFT I'm sorry i can't see where that option is on the
"AzureHub>MyWebApp>Application Settings" page.
Am i looking in the wrong place or do i need to add this as a new setting name?
Btw i selected a Windows WebApp

[Asvaldrz]

Yep that was it. I had to add the new setting and value to "AzureHub>MyWebApp>Application Settings>ApplicationSettings"

[Mike-Ubezzi-MSFT]

@Asvaldrz In this section of the instructions (Configure the web app to read data from your IoT hub), you add your Azure.IoT.IoTHub.ConnectionString and Azure.IoT.IoTHub.ConsumerGroup property values. You also have another value WEBSITE_NODE_DEFAULT_VERSION. Change the property value from 6.9.1 to 8.9.4.

[MBCO]

Works, THX

[Mike-Ubezzi-MSFT]

The documentation has been updated. Closing issue.