Hi all -
I am new to these forums and pretty desperate! I have a custom built (but not by me!) application that runs under IIS. I have deployed it numerous times in various ways, with little to no trouble ever. This time, however, it's got me stumped.
The application runs under a specific, limited domain user and connects to a back-end SQL database. In this particular instance, setting the ApplicationPool to run as that user seems to work, but upon accessing the site I get a 503 and then the application pool stops. As a troubleshooting step, I changed the identity to NetworkService - this results in the site working, although it fails to connect to the database (as one would expect). So, the answer seems to be a permissions issue - something the service account lacks that the NetworkService account has.
The error returned in Event Log (WAS error) suggests the problem is the service account needs the "log on as a batch job" right, but I don't really understand why, nor why this has never been a concern in the past. I have very few deployments on 2012 - everything else is 2008/2008R2 or 2016. Maybe a quirk there? In any case, I'm hesitant to add rights to this user... all it should be able to do is run an app pool and connect to a specific database.
Can anyone think of something I have overlooked? Any help is appreciated.
Edit: I will add I am as close to certain as I can be it's not a credentials issue - changing the password to random characters (ie, an incorrect password) changes the logged error to reference invalid credentials.