I installed Sql Server MDS on a brand new sql server. When I try to bring up the website I am getting 503 Service Unavailable, and when I check the app pool MDS creates (MDS Application Pool) it is stopped. I look in iis logs (503 doesnt show up) and event viewer and do not see any errors. Makes me think iis isnt even getting past the app pool.
I create a very simple website, with just index.html, and it runs fine from the browser. I change the app pool for the site to MDS Application Pool, and when i hit it from the browser I get a 503 error and the app pool stops.
I create a new app pool and set its identity to a service account login (valid because the credentials window when you set the identity will not close if the login fails) - I set the simple site to this app pool and it gives a 503.
I compare MDS Application Pool advanced settings to the default app pool advanced settings and everything is the same.
I tried disabling Rapid-Fail Protection to see if maybe I would see errors in the logs or event viewer, but no luck.
I have searched on SO and found a suggestion to run aspnet_regiis, but I'm hesitant to try it.
Any suggestions?
Two things fixed this:
Devops used the standard Windows Features to install IIS, but they didn't know that the dba group had an Ansible script that installs and configures IIS on their sql boxes.
Second, and more important, they needed to add the service account to two AD groups - one for Sql Server Service accounts and one for Sql Server NonProxy Service accounts - I assume these are specific to my company and not standard groups.