Mixing
How to troubleshoot 500 error on Azure with .NET Core 2.1 app?
I've deployed a reasonably simple .NET Core 2.1 app to Azure (directly from Visual Studio 2017). When I hit the website, it only returns error 500.
I dug into it looking at /LogFiles/DetailedErrors/ErrorPagexxxx.htm and among other things it says:
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.
I am not sure where to go from here. The application worked fine when it was .NET Core 1.x. Once I upgraded it from .NET Core 2, this happened.
What can I try to fix this issue? And how do I get to the actual error that has occurred?
.net
azure .net-core asked Nov 19 '18 at 19:23
AngryHackerAngryHacker
27.3k76237444
add a comment |
I've deployed a reasonably simple .NET Core 2.1 app to Azure (directly from Visual Studio 2017). When I hit the website, it only returns error 500.
I dug into it looking at /LogFiles/DetailedErrors/ErrorPagexxxx.htm and among other things it says:
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.
I am not sure where to go from here. The application worked fine when it was .NET Core 1.x. Once I upgraded it from .NET Core 2, this happened.
What can I try to fix this issue? And how do I get to the actual error that has occurred?
.net
azure .net-core asked Nov 19 '18 at 19:23
AngryHackerAngryHacker
27.3k76237444
Does .NET Core 2.1 require the extension to be installed? Ref: docs.microsoft.com/en-us/aspnet/core/host-and-deploy/azure-apps/…
– Brendan Green
Nov 19 '18 at 22:18
@BrendanGreen I have it marked as installing in the publish profile, but the problem is still happening. The issue for me is how to get to the actual error that's occuring. I did go through the troubleshooting steps, but nothing helped.
– AngryHacker
Nov 20 '18 at 1:18
@BrendanGreen ...and the extension is installed.
– AngryHacker
Nov 20 '18 at 5:13
1
Try deleting the site in azure and recreating the site in azure. Also, try running the application that you are deploying by running dotnet MyApp.dll and making sure that works. You need more details as to why it’s having an application issue. This might help. Also consider testing using a self contained application. Also try installing the asp.net core extension on the azure app service
– joey
Nov 20 '18 at 19:46
@joey I ended doing what you suggested - just getting rid of the entire site and recreating it. It worked! Unfortunately I have no idea what went wrong or how to prevent it in the future.
– AngryHacker
Dec 18 '18 at 1:47
add a comment |
I've deployed a reasonably simple .NET Core 2.1 app to Azure (directly from Visual Studio 2017). When I hit the website, it only returns error 500.
I dug into it looking at /LogFiles/DetailedErrors/ErrorPagexxxx.htm and among other things it says:
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.
I am not sure where to go from here. The application worked fine when it was .NET Core 1.x. Once I upgraded it from .NET Core 2, this happened.
What can I try to fix this issue? And how do I get to the actual error that has occurred?
.net
azure .net-core asked Nov 19 '18 at 19:23
AngryHackerAngryHacker
27.3k76237444
I've deployed a reasonably simple .NET Core 2.1 app to Azure (directly from Visual Studio 2017). When I hit the website, it only returns error 500.
I dug into it looking at /LogFiles/DetailedErrors/ErrorPagexxxx.htm and among other things it says:
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.
I am not sure where to go from here. The application worked fine when it was .NET Core 1.x. Once I upgraded it from .NET Core 2, this happened.
What can I try to fix this issue? And how do I get to the actual error that has occurred?
.net
azure .net-core .net
azure .net-core asked Nov 19 '18 at 19:23
AngryHackerAngryHacker
27.3k76237444
asked Nov 19 '18 at 19:23
AngryHackerAngryHacker
27.3k76237444
edited Nov 19 '18 at 22:14
AngryHacker
asked Nov 19 '18 at 19:23
AngryHackerAngryHacker
27.3k76237444
asked Nov 19 '18 at 19:23
AngryHackerAngryHacker
27.3k76237444
asked Nov 19 '18 at 19:23
AngryHackerAngryHacker
27.3k76237444
27.3k76237444
Does .NET Core 2.1 require the extension to be installed? Ref: docs.microsoft.com/en-us/aspnet/core/host-and-deploy/azure-apps/…
– Brendan Green
Nov 19 '18 at 22:18
@BrendanGreen I have it marked as installing in the publish profile, but the problem is still happening. The issue for me is how to get to the actual error that's occuring. I did go through the troubleshooting steps, but nothing helped.
– AngryHacker
Nov 20 '18 at 1:18
@BrendanGreen ...and the extension is installed.
– AngryHacker
Nov 20 '18 at 5:13
1
Try deleting the site in azure and recreating the site in azure. Also, try running the application that you are deploying by running dotnet MyApp.dll and making sure that works. You need more details as to why it’s having an application issue. This might help. Also consider testing using a self contained application. Also try installing the asp.net core extension on the azure app service
– joey
Nov 20 '18 at 19:46
@joey I ended doing what you suggested - just getting rid of the entire site and recreating it. It worked! Unfortunately I have no idea what went wrong or how to prevent it in the future.
– AngryHacker
Dec 18 '18 at 1:47
add a comment |
Does .NET Core 2.1 require the extension to be installed? Ref: docs.microsoft.com/en-us/aspnet/core/host-and-deploy/azure-apps/…
– Brendan Green
Nov 19 '18 at 22:18
@BrendanGreen I have it marked as installing in the publish profile, but the problem is still happening. The issue for me is how to get to the actual error that's occuring. I did go through the troubleshooting steps, but nothing helped.
– AngryHacker
Nov 20 '18 at 1:18
@BrendanGreen ...and the extension is installed.
– AngryHacker
Nov 20 '18 at 5:13
1
Try deleting the site in azure and recreating the site in azure. Also, try running the application that you are deploying by running dotnet MyApp.dll and making sure that works. You need more details as to why it’s having an application issue. This might help. Also consider testing using a self contained application. Also try installing the asp.net core extension on the azure app service
– joey
Nov 20 '18 at 19:46
@joey I ended doing what you suggested - just getting rid of the entire site and recreating it. It worked! Unfortunately I have no idea what went wrong or how to prevent it in the future.
– AngryHacker
Dec 18 '18 at 1:47
Does .NET Core 2.1 require the extension to be installed? Ref: docs.microsoft.com/en-us/aspnet/core/host-and-deploy/azure-apps/…
– Brendan Green
Nov 19 '18 at 22:18
Does .NET Core 2.1 require the extension to be installed? Ref: docs.microsoft.com/en-us/aspnet/core/host-and-deploy/azure-apps/…
– Brendan Green
Nov 19 '18 at 22:18
@BrendanGreen I have it marked as installing in the publish profile, but the problem is still happening. The issue for me is how to get to the actual error that's occuring. I did go through the troubleshooting steps, but nothing helped.
– AngryHacker
Nov 20 '18 at 1:18
@BrendanGreen I have it marked as installing in the publish profile, but the problem is still happening. The issue for me is how to get to the actual error that's occuring. I did go through the troubleshooting steps, but nothing helped.
– AngryHacker
Nov 20 '18 at 1:18
@BrendanGreen ...and the extension is installed.
– AngryHacker
Nov 20 '18 at 5:13
@BrendanGreen ...and the extension is installed.
– AngryHacker
Nov 20 '18 at 5:13
1
1
Try deleting the site in azure and recreating the site in azure. Also, try running the application that you are deploying by running dotnet MyApp.dll and making sure that works. You need more details as to why it’s having an application issue. This might help. Also consider testing using a self contained application. Also try installing the asp.net core extension on the azure app service
– joey
Nov 20 '18 at 19:46
Try deleting the site in azure and recreating the site in azure. Also, try running the application that you are deploying by running dotnet MyApp.dll and making sure that works. You need more details as to why it’s having an application issue. This might help. Also consider testing using a self contained application. Also try installing the asp.net core extension on the azure app service
– joey
Nov 20 '18 at 19:46
@joey I ended doing what you suggested - just getting rid of the entire site and recreating it. It worked! Unfortunately I have no idea what went wrong or how to prevent it in the future.
– AngryHacker
Dec 18 '18 at 1:47
@joey I ended doing what you suggested - just getting rid of the entire site and recreating it. It worked! Unfortunately I have no idea what went wrong or how to prevent it in the future.
– AngryHacker
Dec 18 '18 at 1:47
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53381298%2fhow-to-troubleshoot-500-error-on-azure-with-net-core-2-1-app%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53381298%2fhow-to-troubleshoot-500-error-on-azure-with-net-core-2-1-app%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Does .NET Core 2.1 require the extension to be installed? Ref: docs.microsoft.com/en-us/aspnet/core/host-and-deploy/azure-apps/…
– Brendan Green
Nov 19 '18 at 22:18
@BrendanGreen I have it marked as installing in the publish profile, but the problem is still happening. The issue for me is how to get to the actual error that's occuring. I did go through the troubleshooting steps, but nothing helped.
– AngryHacker
Nov 20 '18 at 1:18
@BrendanGreen ...and the extension is installed.
– AngryHacker
Nov 20 '18 at 5:13
1
Try deleting the site in azure and recreating the site in azure. Also, try running the application that you are deploying by running dotnet MyApp.dll and making sure that works. You need more details as to why it’s having an application issue. This might help. Also consider testing using a self contained application. Also try installing the asp.net core extension on the azure app service
– joey
Nov 20 '18 at 19:46
@joey I ended doing what you suggested - just getting rid of the entire site and recreating it. It worked! Unfortunately I have no idea what went wrong or how to prevent it in the future.
– AngryHacker
Dec 18 '18 at 1:47