locked
IIS 8.5 on Win Server 2012 R2 trouble RRS feed

  • Question

  • User-94285869 posted

    Hi,

    I'm trying to debug a web app (let's say named, "webapp1") on our production server (not yet live). I'm getting an error, "Unable to launch the IIS Express Web server".  However, I have another web app (say, "webapp2") installed on the same server and it runs fine when I'm debugging it.

    I noticed that the Logs folder inside my Documents/IISExpress folder does not create the "ex..." text file that's usually created for the other web app ("webapp2"). I don't know why it's not being created.  My IIS version for the Windows Server 2012 R2 Standard is 8.5.9600.16384.  The Visual Studio I'm using is VS 2015 Update 3.

    I have not yet published both web applications on the server since I'm still in debugging phase.  They both work okay on my dev machine but some errors are popping up on the production server so I'm trying to get rid of the bugs.

    Can anyone help me resolve why the IIS Server is not launching one app but launches the other?  Appreciate any help.

    Monday, November 6, 2017 5:54 PM

All replies

  • User753101303 posted

    Hi,

    What you are doing is unclear. Usually the production server uses IIS rather than IIS Express and Visual Studio is not installed on the server.

    Ah : try maybe "Project properties", "Web" and see which web server is selected : https://msdn.microsoft.com/en-us/library/aa983445.aspx

    For now my understanding is that your are using Visual Studio installed on your production server and your production server Visual Studio project could be configured to still use IIS Express? Check also https://blogs.technet.microsoft.com/chrad/2010/01/24/understanding-iis-bindings-websites-virtual-directories-and-lastly-application-pools/ ie IIS will need to find out from the IP, port or host header which site should process a particular query. If "bindings" for the new site are the same than for the current site, the site won't start (as IIS would be unable to know which site should process an incoming http request).

    IMHO having to debug directly on a server this way should be rare if even to be needed at all in your whole career.

    Monday, November 6, 2017 6:12 PM
  • User475983607 posted

    Configure IIS on the production server not IIS Express.  Only use IIS Express on your dev box.  If you need remote debugging, then install and configure remote debugging.  However, remote debugging in production is very rare.

    Can you explain the problem you are trying to solve? What errors are you experiencing?

    Monday, November 6, 2017 6:20 PM
  • User-94285869 posted

    Okay. I'm not clear on this.  I still don't have a URL assigned to the web applications.  Our IT says, he doesn't have the certificates yet. In order for me to publish the web apps to the production server, I need unique host addresses (which I don't have). So, for the time being, I'm using IIS Express to test the overall looks of the websites.

    I have multiple websites hosted on the production server (which is not yet live).  One of them I've already deployed using localhost on *.:80 (http).  I can't add another website in the IIS Server since it tells me localhost on *.:80 is already used.  Until I get the final URL from our IT dept., how am I to deploy and test the websites on the production server?

    I get it that I'm not supposed to install Visual Studio on production server.  I plan to un-install it when I'm ready to go live.

    Monday, November 6, 2017 7:28 PM
  • User-94285869 posted

    Thanks for the advice.

    Monday, November 6, 2017 7:28 PM
  • User475983607 posted

    mgambone

    I have multiple websites hosted on the production server (which is not yet live).  One of them I've already deployed using localhost on *.:80 (http).  I can't add another website in the IIS Server since it tells me localhost on *.:80 is already used.  Until I get the final URL from our IT dept., how am I to deploy and test the websites on the production server?

    Bind a new port to each site, 5000, 5001, 5002, etc.  Be sure to open the ports in the firewall otherwise the URLs will not work from a remote client.  When you have the domains and certs, just redo the bindings and you're done.  Using IIS Express means you still have to get IIS working and deal with any issue related to IIS configuration.

    Monday, November 6, 2017 7:32 PM