There is a problem with the resource you are looking for and it cannot be displayed. .net core

I just changed my .NET Framework Version of the Application Pools in IIS7 Manager, following Specify a .NET Framework Version for an Application Pool (IIS 7) instructions by Microsoft Technet. Now when I try to re-upload my ASP.NET page, it shows me a 500 - Internal server error. I have tried uploading it in .NET 2.0 (x86, x64, AnyCPU), and 4.0 (x86, x64, AnyCPU), and everything gives the same error. This is all the details the error gives me: "There is a problem with the resource you are looking for, and it cannot be displayed."

Show

When keeping the .NET version 2.0 on the server, it works just fine. Also, when uploading index.htm, it works fine as well, it just shows the HTML page.

This is on Windows Server 2008 R2, by the way.

EDIT:

I have finally found out how to get the error details. Here they are:
Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list. Most likely causes:

  • Managed handler is used; however, ASP.NET is not installed or is not installed completely.
  • There is a typographical error in the configuration for the handler module list. Things you can try:
  • Install ASP.NET if you are using managed handler.
  • Ensure that the handler module's name is specified correctly. Module names are case-sensitive and use the format modules="StaticFileModule,DefaultDocumentModule,DirectoryListingModule"

I am sure that I have installed ASP.NET completely.

hello all,
I have taken space on godaddy server.when i upload my website(asp.net with c#) and run its url(www.purplebayuk.com),it returns an error i.e.
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.what is this.I have also specified custom error mode=off in web.config file but the problem remains same.please help me


i have one question here

are you uploaded application from FTP (using ftp credentials) or From control panel file manager ?

Suggestions:
1) Check Default Folder settings from your godaddy admin control panel.
2) Check Redirect Path in Control Panel.
3) Try to chat with your host provider(godaddy) on this issue.(it might be server down sometimes.)

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900

Assignees

Labels

affected-few

This issue impacts only small number of customers

area-runtime

Includes: Azure, Caching, Hosting, Middleware, Websockets, Kestrel, IIS, ANCM, HttpAbstractions

Docs

This issue tracks updating documentation

Done

This issue has been fixed

External

This is an issue in a component not contained in this repository. It is open for tracking purposes.

✔️ Resolution: Fixed

The bug or enhancement requested in this issue has been checked-in!

servers-iis

Includes: IIS, ANCM

severity-minor task

asp.net core app deployed on iis meets 500 internal server error

Questions : asp.net core app deployed on iis meets 500 internal server error

2022-08-05T04:42:30+00:00 2022-08-05T04:42:30+00:00

722

:( Oops. 500 Internal Server Error An anycodings_iis error occurred while starting the anycodings_iis application.

This message came out when I added database anycodings_iis functionality to my asp.net core app and anycodings_iis deployed it to iis. When I developed it in anycodings_iis Visual Studio, everything went well. But anycodings_iis after deploying, this error messages anycodings_iis appeared.

I tried to use dotnet myapp.dll to run my anycodings_iis app in the deploy folder, and found out it anycodings_iis worked well. It is likely that the problem anycodings_iis is relation to iis. I tried to add anycodings_iis <compilation anycodings_iis debug="true">..</compilation> to anycodings_iis web.config, but it seems useless. What is anycodings_iis problem are actually, or is there any other anycodings_iis way to see the detailed error info to help anycodings_iis find out what's happened?

Total Answers 13

28

Answers 1 : of asp.net core app deployed on iis meets 500 internal server error

  1. Change stdoutLogEnabled="false" to true anycodings_iis and then check the logs at anycodings_iis stdoutLogFile=".\logs\stdout". The anycodings_iis error(s) there might tell you something.

  2. Check that you set up right Environment anycodings_iis Name using ASPNETCORE_ENVIRONMENT anycodings_iis environment variable as so use correct anycodings_iis settings like connection string. On your anycodings_iis machine by default you have anycodings_iis "Development" environment.

  3. You may use Error Handling middlewares anycodings_iis for showing exceptions like

    app.UseDeveloperExceptionPage();

0

2022-08-05T04:42:30+00:00 2022-08-05T04:42:30+00:00Answer Link

mRahman

4

Answers 2 : of asp.net core app deployed on iis meets 500 internal server error

Had the same issue. Here is the guide anycodings_iis that helped me. Note, that I did not anycodings_iis want to install the "Runtime" on the web anycodings_iis server, but rather deploy all the anycodings_iis necessary files as a stand alone app. anycodings_iis Below are the steps in a more anycodings_iis abbreviated form:

  1. On your local PC, Determine which anycodings_iis version to publish based on your server. anycodings_iis I was targeting Windows Server 2008, R2 anycodings_iis which meant i needed to publish anycodings_iis win7-x64. Open a command prompt in your anycodings_iis project directory and run the command anycodings_iis below:

    dotnet publish -c release -r win7-x64

    This creates a publish folder containing anycodings_iis hundreds of dlls, an .exe, and anycodings_iis web.config located here: anycodings_iis bin\Release\netcoreapp2.0\publish

  2. On the web server with IIS, go to this anycodings_iis landing page. Click the link for your anycodings_iis desired version. Find the link for the anycodings_iis Runtime and Hosting Bundle. Click to anycodings_iis download and run.

  3. Restart IIS by running this from an anycodings_iis elevated command prompt:

    net stop was

    net start w3svc

  4. Copy all of the files in your local anycodings_iis publish folder to your desired anycodings_iis application folder on the IIS server.

  5. On the server, Open IIS, and create a anycodings_iis separate AppPool and Application like anycodings_iis normal. For the AppPool, under Basic anycodings_iis Settings, change the .NET Framework anycodings_iis version to No Managed Code. Make sure anycodings_iis your Application in IIS points to your anycodings_iis desired folder and the proper AppPool.

  6. Test your web application in a browser.

0

2022-08-05T04:42:30+00:00 2022-08-05T04:42:30+00:00Answer Link

miraj

6

Answers 3 : of asp.net core app deployed on iis meets 500 internal server error

In my case, I got this because I hadn't anycodings_iis actually installed the latest anycodings_iis 'DotNetCore.2.0.0-WindowsHosting.exe' on anycodings_iis the windows server I was running it anycodings_iis on... so it was working fine on my local anycodings_iis machine in debug and error five anycodings_iis hundy'ing on the server.

I had other non trivial to fix issues anycodings_iis with the upgrade also... I'd advise anycodings_iis avoiding it if you can.

0

2022-08-05T04:42:30+00:00 2022-08-05T04:42:30+00:00Answer Link

joy

3

Answers 4 : of asp.net core app deployed on iis meets 500 internal server error

Mark333's comment below solved my anycodings_iis problem.

Quoting for easy reading:

"I'm using the normal publish provided anycodings_iis by Visual Studio. And, I just found anycodings_iis out using the latest version of Hosting anycodings_iis Bundle will fix the issue. +1 on this anycodings_iis microsoft.com/net/download/dotnet-core/runtime-2.1.0-rc1"

I had to install for 1.1 since my app is anycodings_iis a little older, but Hosting Bundle fixed anycodings_iis it. In my case we deploy to a Docker anycodings_iis image for our official environment, but anycodings_iis when I want to do some testing locally I anycodings_iis publish it and let my local IIS serve it anycodings_iis up.

0

2022-08-05T04:42:30+00:00 2022-08-05T04:42:30+00:00Answer Link

joy

5

Answers 5 : of asp.net core app deployed on iis meets 500 internal server error

My problem was solved installing anycodings_iis .netcore latest: anycodings_iis https://dotnet.microsoft.com/download/thank-you/dotnet-runtime-2.2.2-windows-hosting-bundle-installer

https://docs.microsoft.com/pt-br/aspnet/core/host-and-deploy/iis/index?view=aspnetcore-2.2#install-the-net-core-hosting-bundle

Worked like a charm!

0

2022-08-05T04:42:30+00:00 2022-08-05T04:42:30+00:00Answer Link

miraj

5

Answers 6 : of asp.net core app deployed on iis meets 500 internal server error

I had installed anycodings_iis DotNetCore.2.0.5-WindowsHosting.exe on a anycodings_iis Windows 2008 R2 Standard machine and anycodings_iis encountered the same http 500 error. anycodings_iis Logging didn't help (blank logs were anycodings_iis generated - and Event Viewer logs were anycodings_iis the generic ErrorCode = 0x80070002)

I had to do two things to solve my anycodings_iis problem:

  1. Give Read rights to the ApplicationPoolIdentity user (EG: IIS APPPOOL\AppPoolIdentityName) to the website directory and the application directory
  2. I had to install IIS ASP Core under Server Manager (this felt weird, but it worked!)

0

2022-08-05T04:42:30+00:00 2022-08-05T04:42:30+00:00Answer Link

jidam

2

Answers 7 : of asp.net core app deployed on iis meets 500 internal server error

I had the same issue.

My problem was that my connection string anycodings_iis to db was not set in anycodings_iis appsettings.production.json

And the internal server error 500 was to anycodings_iis vague error message.

Changing the stdoutLogEnabled = true did anycodings_iis nothing to me so i was not seeing any anycodings_iis information about the error.

0

2022-08-05T04:42:30+00:00 2022-08-05T04:42:30+00:00Answer Link

jidam

4

Answers 8 : of asp.net core app deployed on iis meets 500 internal server error

I experienced this issue. The problem anycodings_iis was due to my local Sql Server instance. anycodings_iis Remote connection were not allowed. So I anycodings_iis manually restarted the SQL instance and anycodings_iis my App restarted working fine.

0

2022-08-05T04:42:30+00:00 2022-08-05T04:42:30+00:00Answer Link

joy

5

Answers 9 : of asp.net core app deployed on iis meets 500 internal server error

I had similar issue after istalling anycodings_iis dotnetcore-windowshosting using anycodings_iis chocolatey while doing AWS ec2 instance anycodings_iis bootstrapping.

When I checked my IIS modules anycodings_iis AspNetCoreModule was missing.

This solved my issue. anycodings_iis https://github.com/aspnet/IISIntegration/issues/434

I had to uninstall chocolatey package, anycodings_iis restart machine and install it again.

Hope this helps!

0

2022-08-05T04:42:30+00:00 2022-08-05T04:42:30+00:00Answer Link

raja

3

Answers 10 : of asp.net core app deployed on iis meets 500 internal server error

Make sure the App Pool has permissions anycodings_iis to the folder where your app resides.

0

2022-08-05T04:42:30+00:00 2022-08-05T04:42:30+00:00Answer Link

raja

2

Answers 11 : of asp.net core app deployed on iis meets 500 internal server error

In my case, I created a .NET 5 single anycodings_iis file output, and I was getting:

500 - Internal server error. There is a problem with the resource you are looking for, and it cannot be displayed.

The problem turned out to be that the anycodings_iis EXE file was for some strange reason anycodings_iis recognized as a virus by the protection anycodings_iis software (CrowdStrike Falcon). anycodings_iis Re-building without "single file output" anycodings_iis option solved that problem.

0

2022-08-05T04:42:30+00:00 2022-08-05T04:42:30+00:00Answer Link

raja

6

Answers 12 : of asp.net core app deployed on iis meets 500 internal server error

There is an article called "Configuring anycodings_iis IIS, ASP.NET, and SQL Server" which I anycodings_iis highly recommend. I followed the steps anycodings_iis described there and my asp.net core app anycodings_iis now communicates with my SQL database anycodings_iis (after being published to IIS):

https://www.codeproject.com/Articles/674930/Configuring-IIS-ASP-NET-and-SQL-Server

0

2022-08-05T04:42:30+00:00 2022-08-05T04:42:30+00:00Answer Link

miraj

2

Answers 13 : of asp.net core app deployed on iis meets 500 internal server error

It also happens when you install anycodings_iis dotnet-hosting-bundle/dotnet runtime anycodings_iis beofore IIS.

In this case re-install anycodings_iis dotnet-hosting-bundle/dotnet runtime.

0

2022-08-05T04:42:30+00:00 2022-08-05T04:42:30+00:00Answer Link

raja

How do you fix there is a problem with the resource you are looking for and it Cannot be displayed?

There is a problem with the resource you are looking for, and it cannot be displayed. To resolve this issue, set the Enable 32-bit Applications to "False": Open the Internet Information Services (IIS) Manager. Select Application Pools.

What does 500 Internal server error There is a problem with the resource you are looking for and it Cannot be displayed?

A 500 internal server error is, as the name implies, a general problem with the website's server. More than likely, this means there's an issue or temporary glitch with the website's programming. Some potential causes of a 500 internal server error include: Corrupted or broken .

How do I get rid of 500 internal server error?

Delete your browser's cookies. You can correct some 500 Internal Server Error issues by deleting the cookies associated with the site on which you're getting the error. After removing the cookie(s), restart the browser and try again. Troubleshoot as a 504 Gateway Timeout error instead.

Why do I keep getting 500 internal server error?

The 500 Internal Server error could be caused by an error during the execution of any policy within Edge or by an error on the target/backend server. The HTTP status code 500 is a generic error response. It means that the server encountered an unexpected condition that prevented it from fulfilling the request.