I"ve installed trang web on my local machine using IIS 7 successfully.But when I"ve deployed it on live server, I got the following error:

"The page cannot be displayed because an internal hệ thống error has occurred" Nothing else.

Bạn đang xem: The page cannot be displayed because an internal server error has occurred

Using the same IIS 7 on live và also set lớn have Detailed errors in Error Pages module, but still getting the same.What can be a reason?




Introducing: Trending sort You can now choose to lớn sort by Trending, which boosts votes that have happened recently, helping to surface more up-to-date answers.

Trending is based off of the highest score sort and falls back to it if no posts are trending.

Try it Dismiss
Highest score (default) Trending (recent votes count more) Date modified (newest first) Date created (oldest first)
I just got this error and it was caused by a duplicate static content MIME type in the web.config

This error was being returned only on static files - eg images, css, js files were all saying this error (text by itself, no other html or text in the response).

The way to lớn debug this is to lớn look in web config under static content. Here we have a json tệp tin extension loaded. This was required on IIS7 but will kill the ứng dụng if used on IIS8 because json is now pre-loaded at the hệ thống level.

So solution is to remove any of these mimeType entries one at a time lớn confirm which are needed và which kill your app!


Actually the best solution was provided by a commenter here. You can remove and then add, which will always work regardless of whether it is already defined or not. Like this:

nội dung
Improve this answer
edited Mar 1, 2020 at 6:24
answered Feb 13, năm nhâm thìn at 0:12


mike nelsonmike nelson
19.7k1313 gold badges6262 silver badges6969 bronze badges
địa chỉ a phản hồi |
I think the best first approach is to make sure lớn turn on detailed error messages via your web.config file, like this:

After doing this, you should get a more detailed error message from the server.

In my particular case, the more detailed error pointed out that my section of the web.config file was not allowed at the folder level where I"d placed my web.config. It said

This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false". "

cốt truyện
Improve this answer
edited Jan 21, 2021 at 21:49

145k2222 gold badges145145 silver badges175175 bronze badges
answered Jun 11, 2017 at 16:44

Eric BarrEric Barr
3,80433 gold badges2727 silver badges4141 bronze badges
địa chỉ a comment |
Modify your web.config khổng lồ display the server error details:

You may also need lớn remove/comment out the follow httpErrors section

From my experience if you directly have a vps error, this may be caused from an assembly version mismatch.

Check what is declared in the web.config & the actual ddl in the bin folder"s project.

nói qua
Improve this answer
edited Feb 14, 2017 at 1:32
Matthew Lock
12.7k1111 gold badges8888 silver badges125125 bronze badges
answered Jun 9, 2015 at 12:10
Mickael LYMickael LY
17455 bronze badges
địa chỉ a comment |
I"ve fixed it.I had the following section in web.config :

httpErrors existingResponse="PassThrough"When I remove it, I got a real error

Improve this answer
edited Nov 6, 2016 at 4:06
Divyang Desai
7,0951313 gold badges4545 silver badges6969 bronze badges
answered Jun 9, năm ngoái at 12:35
92822 gold badges1010 silver badges2020 bronze badges
add a bình luận |
In my case, setting httpErrors & the lượt thích in Web.config did not help lớn identify the issue.

Instead I did:

Activate "Failed Request Tracing" for the website with the error.Configured a trace for HTTP errors 350-999 (just in case), although I suspected 500.Called the erroneous URL again.Watched in the log folder ("%SystemDrive%inetpublogsFailedReqLogFiles" in my case).Opened one of the XML files in internet Explorer.

I then saw an entry with a detailed exception information. In my case it was

?C:Websitesexample.comwwwweb.config ( 592) :Cannot showroom duplicate collection entry of type "mimeMap" with quality key attribute "fileExtension" set to lớn ".json"

I now was able to lớn resolve it and fix the error. After that I deactivated "Failed Request Tracing" again.

giới thiệu
Improve this answer
answered Aug 12, 2018 at 21:40
Uwe KeimUwe Keim
38.3k5656 gold badges171171 silver badges280280 bronze badges
địa chỉ cửa hàng a phản hồi |
it seems it works after I commented this line in web.config

tóm tắt
Improve this answer
answered Jan 23, 2018 at 14:59
40044 silver badges1414 bronze badges
add a comment |
I ended up on this page running web Apps on Azure.

Xem thêm: #1 Hướng Dẫn Cài Đặt Net Framework 4.5, Cách Cài Microsoft Net Framework 4

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

We ran into this problem because we applicationInitialization in the web.config

If running on Azure, have a look at site slots. You should warm up the pages on a staging slot before swapping it khổng lồ the production slot.

cốt truyện
Improve this answer
edited Dec 14, 2018 at 15:29
Uwe Keim
38.3k5656 gold badges171171 silver badges280280 bronze badges
answered Sep 25, 2018 at 9:27
56599 silver badges1212 bronze badges
địa chỉ cửa hàng a comment |
I got the same error when I added the applicationinitialization module with lots of initializationpages & deployed it on Azure app. The issue turned out khổng lồ be duplicate entries in my applicationinitialization module. I din"t see any errors in the logs so it was hard to troubleshoot. Below is an example of the error code:

Make sure there are no duplicate entries because those will be treated as duplicate keys which are not allowed and will result in "Cannot showroom duplicate collection entry" error for web.config.

nội dung
Improve this answer
answered Jan 16, 2020 at 16:41
4166 bronze badges
showroom a phản hồi |
I was hosting with Everleap và migrated khổng lồ Azure, where I was getting this error. Everleap deployments lớn their servers required the following in the web.config ` section:

When I commented out this code, the ứng dụng worked on Azure.

nói qua
Improve this answer
answered Apr 21, 2021 at 19:16
Matthew SidorickMatthew Sidorick
4133 bronze badges
showroom a bình luận |
For those of you who hit this entry because it ranks high for the phrase:

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

In my personal situation with this exact error message, I had turned on python 2.7 thinking I could use some python with my .NET API. I then had that exact error message when I attempted khổng lồ deploy a vanilla version of the API or MVC from visual studio pro 2013. I was deploying lớn an azure cloud webapp.

Hope this helps anyone with my same experience. I didn"t even think lớn turn off python until I found this suggestion.

chia sẻ
Improve this answer
edited Dec 14, 2018 at 15:29
Uwe Keim
38.3k5656 gold badges171171 silver badges280280 bronze badges
answered Mar 31, 2016 at 0:54
1,20299 silver badges88 bronze badges
địa chỉ a phản hồi |

Your Answer

Thanks for contributing an answer lớn Stack Overflow!

Please be sure to lớn answer the question. Provide details and share your research!

But avoid

Asking for help, clarification, or responding to lớn 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.

Draft saved
Draft discarded

Sign up or log in

Sign up using Google
Sign up using Facebook
Sign up using thư điện tử and Password

Post as a guest

email Required, but never shown

Post as a guest


Required, but never shown

Post Your Answer Discard

By clicking “Post Your Answer”, you agree lớn our terms of service, privacy policy & cookie policy

Not the answer you're looking for? Browse other questions tagged c# iis internal-server-error or ask your own question.

The Overflow Blog
Featured on Meta
An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode
IIS 500.19 with 0x80070005 The requested page cannot be accessed because the related configuration data for the page is invalid error
Config Error: This configuration section cannot be used at this path
ReSharper "Cannot resolve symbol" even when project builds
Unable to lớn launch the IIS Express Web vps
HTTP Error 500.19 và error code : 0x80070021
Why not inherit from List?
Hot Network Questions more hot questions

Question feed
Subscribe lớn RSS
Question feed to subscribe khổng lồ this RSS feed, copy và paste this URL into your RSS reader.

Stack Overflow
Stack Exchange Network
Site kiến thiết / hình ảnh © 2022 Stack Exchange Inc; user contributions licensed under cc by-sa. Rev2022.6.24.42450

Your privacy

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device và disclose information in accordance with our Cookie Policy.