I've been developing with Visual Studio on a Windows 10 PC for the last year. I have a ASP.NET web application and a SQL Server 2014 database installed on the same computer.
I've got the site running in IIS while I'm working on it:
I also have a connection string with integrated security:
<add name="WebsiteEntities" connectionString="metadata=res://*/websiteModel.csdl|res://*/websiteModel.ssdl|res://*/websiteModel.msl;provider=System.Data.SqlClient;provider connection string="data source=.;initial catalog=website;integrated security=True;MultipleActiveResultSets=True;App=EntityFramework"" providerName="System.Data.EntityClient" />
I connect to the sql database using my regular windows account. There is no active directory or domain on the network or anything:
This all started to break yesterday afternoon. Suddenly I started getting a error 503 when attempting to access the website on IIS:
Inspecting the application pool in IIS, I noticed that it's not started:
Whenever I access any of the web applications attached to this application pool, the pool immediately crashes (I say crashes, but it just stops running).
I make sure it's running:
Then accessing the website gives me the 503 and the application pool is stopped.
Over the last hours, nothing I've tried enables the application pool to keep running. There is nothing to debug in the application in Visual Studio, because it never starts there. The crash does not generate any logs in inetpub. I've tried to change my windows account password and updating this in the application pool, but I still get the same issue.
How can I effectively debug the app pool in order to figure out why it keeps crashing?