I’m working on an MVC Website. In development in Visual Studio, things are working perfectly. My app needs to run in IIS. Easy enough, right? Just set it up in IIS and you’re off and running.
Recently though, my IIS instance of the site stopped working. What?! I began to get the following error:
HTTP Error 503. The service is unavailable.
Wha wha wha?! I checked IIS and it’s running properly. What the heck? SQL Server is okay. The thing works perfectly in Visual Studio. ARG.
Well it turns out that I recently change my password. The application pool I have the site using is logging in as “me” but hadn’t been updated with the new password. Ah ha!
Go to the IIS Manager and select the Application Pools. You’ll find the application pool your app is using there. Right click on it and choose “Advanced Settings”.
Next, click the ellipses in the Process Model > Identity property. This will allow you to specify the identity the application pool should run as.
Finally, you can select a built in account or specify a custom account. Select the radio button and click the “Set” button. There, you’ll be able to specify the username (DOMAIN\UserName) and the password.