Successfully deployed MVC 4 site runs but does not display - asp.net-mvc

I succesffuly deployed an MVC 4 application to IIS Express on my development machine and everything runs fine. I can also successfully deploy to my production server, but when trying to access the deployed application in the production envioronment it can't be displayed.
Development tool: Visual Studio 2012 Express for Web.
Production server (all updates installed):
- Windows Server 2008 R2 x64
- IIS 7.5
- MS .Net Framework 4.5
- ASP.Net MVC 4 with language pack
- Web Deploy 2.1 and Web Deploy 3.0
- Recommended configuration for IIS.
Furthermore, ASP.NET is registered with IIS for Framework\v4.0.30319 and Framwork64\v4.0.30319 and the application pool of the site is .Net Framework v4.0.30319. The IIS_IUSRS group has inherited permissions (Read & Execute, List Folder Contents and Read).
I have a production web server tied to the web via DynDNS, my site uses port 80.
What could be the cause for the site running but not displaying?
Any help would be appreciated.
Additional info: When I check the compatibility in WebMatrix of any site deployed to the production server I always get the result "Not available" for a Simple HTML-Page (the .Net-Framework-Version on the other hand always gives "Available").

It seems that everything is ok, I had a DNS-Server error (wrong external server address).

Related

How to deploy an asp.net mvc app to IIS 8 on azure virtual machine

Trying to deploy an asp.net mvc application with IIS 8 on azure virtual machine but Im getting the following error:
This is what ive done so far in azure Virtual machine:
Installed IIS
Installed Web deploy 3.6, web deploy for hosting server, web deploy tools 2.1, web deploy without sql bundled support
In IIS azure Virtual machine:
Created a website "Nextix" in IIS
Disabled Default Web site in IIS
In my Visual Studio 2013 (asp.net mvc project), selected publish -> web deploy package
Copied the deployed package to the virtual machine
In IIS, clicked website "Nextix" and selected import application
Followed all instructions in Import Application Package Wizard to install Web deploy package
I also installed ASP.net 4 in iis by following the instruction in the link
ASP.NET MVC on IIS 7.5
After the steps I did, this is how my IIS application pools looks like:
And how the advance settings of my nextix website looks like:
Is there something else I need to check or do? Im still getting the above error message screen.
Fixed by following the instruction in this link: http://www.iis.net/learn/get-started/whats-new-in-iis-8/iis-80-using-aspnet-35-and-aspnet-45

Running a .NET 4.6 MVC application on IIS 8.5 (Windows Server 2012)

I have an MVC Web API 2 application that I am running quite successfully locally within Visual Studio 2015 RC. I have also successfully published this application to an IIS 8.5 instance running on Windows Server 2012. I have installed .NET Framework 4.6 on this machine also.
The behaviour that I am getting when I try to navigate to the root of the site (http://localhost:81) is that I get a directory listing of the files in the root folder. Clearly I was expecting the routing config of the application to kick in an execute the home controller, but this is not happening.
I am a developer and it has been some time since I configured IIS, but I do remember that I had to do some fiddling with IIS (6?) to get the routing to work.
What am I missing?
Make sure your application pool is running in integrated mode and not classic.

Why do I need to switch off module inheritance to make my ASP.NET MVC site work on Windows Server 2008?

I am developing an ASP.NET MVC 5 site targeting .NET 4.5.1 and for some reason I am struggling to deploy it on a Windows Server 2008 Standard edition server.
To be clear the site runs fine on my Windows 7 development machine and my Windows Server 2012 test environment but when I deploy it to the Windows Server 2008 in question I get this error:
At this point I tried all the advice about reinstalling ASP.NET and enabling runAllManagedModulesForAllRequests that I found in threads like this one ASP.NET MVC on IIS 7.5 but nothing would make it work.
Eventually I found that I could fix the problem by switching off the "Invoke only requests to ASP.NET applications or managed handlers" option for all managed modules in the application. What this did in essence was to make the following changes to the web.config file:
So my question is two-fold. Firstly, why is this change necessary to get the site to work? Secondly, am I safe to change the web.config permanently given that it will be installed on other servers as well, not all of which will be Windows Server 2008?

ASP.NET app on IIS 8 Server not talking to SQL Server 2012 database server

I am working on an ASP.NET MVC application, recently we are given IIS 8 server (Windows Server 2012) and database server with SQL Server 2012. Now application sits on my local machine, talking to the SQL Server database works perfectly.
But when I deploy the application to IIS and run the app and try to let it talk to that database ... it does not and getting following warning
The remote host does not have the dbDacFx Web Deploy provider installed, which is required for database publishing. To learn more about this visit this link.

Application in ASP.NET MVC 2 Beta running on IIS 7.5

i have problems runnning an mvc2beta application in iis 7.5.
WebServer:
Windows Server 2008 R2 (x64)
Application:
MVC 2 Beta (developted in Visual Studio 2010 Beta)
On IIS i added a new application beneath the Default Web Site and the new application has Application Pool ASP.NET V4.0
If i runn application within Visual Studio everything is fine. but on IIS Server i became an error page:
Service Unavailable
HTTP Error 503. The service is unavailable
What is missing?
In Event Log got this Message:
Application pool 'DefPool' is being
automatically disabled due to a series
of failures in the process(es) serving
that application pool.
If you have upgraded to .NET v4 then delete any older versions from %windir%\Microsoft.Net\Framework and try again. Also, check again that the application pool isn't set to use v4.0, and not v2.0.
Without seeing your debug messages, it's hard to diagnose what these failures were.

Resources