1st Solution, Try BOTH SOLUTIONS PART 1 & 2. Please Find other part link on end of this video or on Upper Right Corner.
Server Error in '/' Application. The resource cannot be found. Description: HTTP 404. Your URL is fine, Several times it run successfully but when you alter something and run again it shows above error, this really sucks… this is the issue, I put the solution for. It worked for me
There may be several reasons for this Error but I am trying to explaining here a few solutions which worked for me. I am explaining this solution for the problem when we neviagte between pages on UI then above said error can occure while the neviagte URL is tested several times and Fine. Hello Friends, I know this is a really common error, and you must be bored of troubleshooting it by now! But here's the situation I have: I created an "Asp.Net Web application" for .Net 2.0 using visual studio 2008. I then set up IIS on my local machine (XP SP2), and it runs the website fine. But when neviagte to other pages you find this error.
More info on this error. It seems to only happen on page nested within page groups. Interestingly, we get the error continually when we are trying to add or edit pages, but if we navigate in the sitemap to the the first nested page in the page group, then we can view the other nested pages within that group fine until i make another edit.
The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the URL and make sure that it is spelled correctly.
\Server Error in '/' Application.
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
You are welcome! An internal server error could occur for numerous reasons like - incorrect database server, incorrect username / password etc etc. The best way to approach this would be to find out what's the actual error. You have said that you could see the 1st page, but the error happens after you enter the user name/ password. What type of authentication does your web application / site use ? See if it's setup correctly in IIS under the "Authentication" module. Also, go to the server and visit your page there, instead of from a machine that just acts as a client. If you use the server itself, it will give you much more information than a useless "500 internal server" error. If you could do that and see the actual error, it might be helpful If you have qns. post it here and one of us will help! Its difficult to help w/ just the general 500 error...