Last post Nov 10, 2017 03:48 PM by cbassett
Nov 10, 2017 07:14 AM|cbassett|LINK
I am having a strange problem where I cannot run a VS ASP.NET app (specifically, an MVC 5 app) that was developed on another machine with the same version of VS (2015, Update 3). However, I can create a new ASP.NET MVC 5 app on the machine and that runs
fine. But when I try to run the app developed on the other machine, all I get is a Page cannot be displayed error, like IIS isn't running, but I don't get any error messages from IIS or VS. Both machines are configured the same way with the same version
of VS (2015 Community) and the same update (Update 3). Both run Windows 10 as well.
I'm wondering if there is a configuration settings that configures the local express version of IIS in the project that perhaps is creating the conflict, and that maybe by chance, IIS Express on both machines is not configured the same way for some reason
(although I never changed the configuration of IIS on either machine from their defaults.)
NOTE: I also know if you have IIS installed (from the Control panel -> Programs & Features -> Add Windows Features) in addition to the version of IIS 10.0 Express that VS installs, that can create a problems when testing in VS, but I don't have that version
of IIS enabled/installed; only the Express version 10.0 version that was installed with Visual Studio. I also don't have any other web services installed (ie. Apache, WAMP, etc).
Suggestions? I've tried running VS as an Administrator as well, with the same result so Windows permissions does not seem to be the problem. I've also deleted the "IISExpress" folder in the Documents folder to clear out any possibility of that being an
Nov 10, 2017 08:23 AM|Deepak Panchal|LINK
I have several suggestions that you can try.
-> first of all you can try to delete the browsing history from web browser and try again.
check that you can open the default page or not.
check that you set some redirection in global.asax. which work on that machine but can not work on any other machine.
if you find anything like that then try to modify it.
try to check for any dependency available on source machine and which is not available in new machine.
try to clean the solution and rebuild it.
at last you can try to repair the IIS and try to reinstall it.
Nov 10, 2017 08:38 AM|PatriceSc|LINK
You should likely find a more detailed error in the Windows log or maybe IIS Express logs. The http status code could also help. The first step might be to understand if the query can reach IIS Express or not. The address looks fine with a port number ?
You could also perhaps have a look at "project properties", "web" to see which web server is selected.
My approach would be to try to get some more information about the exact error that happens.
Nov 10, 2017 02:47 PM|cbassett|LINK
I've gone through and cleared the browser history (even tried different browsers too, both Firefox and Edge as well as Internet Explorer). As far as logs, there aren't any in the IISExpress folder. I guess I could look into the Windows Event Viewer too.
Now I'm getting an error saying that IIS Express can't even be started... even after a reboot and also tried running VS as an administrator. I've also removed IIS Express 10 and did a repair on VS, which reinstalled it, without any luck.
I'm at the point where I'm going to uninstall and re-install VS. My computer did install the Windows 10 Creator's Update so I sort of wonder if that broke something (my other computer at work has Windows 10, but doesn't have the Creator's update installed
yet so I'm wondering). Although, it doesn't explain why I would able to run an out-of-the-box MVC app, but not one that only has minimal customization (added some views and an E-F diagram, along with a single controller). Nothing odd in the other program
files (Program.cs, Global.cs.asdx, etc).
Nov 10, 2017 03:48 PM|cbassett|LINK
I never did find the reason for this, but after fully removing VS 2015 (and IIS 10 Express) and then installing VS 2017 Community, I can now open my projects and run them so I'm thinking that either I had a corrupted IIS install, and/or a corrupted VS install
(possibly related to the Creator's update). either way, it seems to work fine with VS 2017 now (and for me, the version of VS doesn't matter as this is an individual project for a small company, so it's not a large Enterprise application).