Last post Nov 03, 2014 10:02 PM by Angie xu - MSFT
Oct 28, 2014 04:25 PM|Bob Hill|LINK
I'm deploying a site to a new server. The main sign-in page comes up but when I attempt to sign in I get a generic "This Page cannot be displayed" error.
I'm not sure if this is the correct forum to post this since it could be an IIS 8.5 config issue, but does anyone have tips on debugging this? I've tried viewing error and event logs but to no avail.
A nudge in the right direction would be helpful.
For some background, the app works fine within VS 2010 and is currently deployed on our production server running IIS 6.0 and works fine there. I have other ASP.NET apps deployed on this new server and they are running without issue. It's just this one site
that I'm having problems with.
Oct 28, 2014 04:31 PM|smirnov|LINK
Disabling HTTP Friendly Error Messages in Internet Explorer
Oct 29, 2014 09:30 AM|Bob Hill|LINK
I am disabling Friendly Error messages. That's one of the first things I tried.
I would think there would be something in the log files when this error appears. I have even tried turning on Developer Tools in Internet Explorer and it shows nothing.
Oct 29, 2014 09:52 AM|smirnov|LINK
the "page cannot be displayed" is the browser message, not a server response. Both server (IIS) or engine (ASP.NET) return detailed messages with server codes. E.g. 404 not found, 500 internal error, etc. So, make sure you disabled user friendly messages
or try to use another browser, e.g. Chrome.
If you will get 500 message, and it will say only about "Server Error in Application" then additionally you will need to check the web.config and set
Oct 29, 2014 11:59 AM|Bob Hill|LINK
I tried FireFox and instead get "Object moved to here" with here as a hyperlink. Clicking the hyperlink just returns me to the original page.
This is baffling!!
Oct 29, 2014 12:09 PM|smirnov|LINK
So do you redirect from the code-behind?
Nov 03, 2014 10:02 PM|Angie xu - MSFT|LINK
For this issue, here are some suggestions for you:
First you need enable the Failed Request Tracing in IIS, this will give me some hint on why a request has failed.
Secondly you need check your deployment procedure, here is the asp.net application deployment reference:
# ASP.NET Web Application Project Deployment Overview
Please let me know if there is anything that I can do to help.