Thanks Chris --
I got a few details including that w3wp.exe the network path was not found
and The current configuration only supports loading images built for a AMD64 processor architecture.
I seemed to get the sites working, no thanks to 3essentials. I don't know how this changed... or if these are the "wrong fix"
Here's what I did.
1. in IIS Manager, I put "Enable 32-Bit Applications" to True under "Set Application Pool Defaults"
2. I put Start Mode to "AlwaysRunning"
3. Then, for each of my sites... I changed from DefaultAppPool to the mysite.com(domain)(4.0)(pool) under Sites.. Mysite.com.. "Set Application Defaults" and also under "Advanced Settings" for mysite.com
4. I also made sure each IPWG user had FULL CONTROL permissions... which I don't think should have changed, but just to add to what I did.
-Is there a disadvantage/problem with Enabling 32-bit applications?
-Is there a disadvantage to AlwaysRunning as StartMode? (other than performance, maybe... my sites are not high traffic so that shouldn't be a concern).
-Is there a disadvantage to having each site use it's own App Pool instead of the DefaultAppPool? (Or is it even possible for all sites to run on DefaultAppPool). I have 7 DNN installs... so now running on 7 App Pools.