We have an ASP.NET application that was written by a former employee that I have thus far been holding together with duct tape. The app was written with MVC, NHibernate and
This may not apply if you're not trying to get the site to run locally, but, this may help someone...
I had brought over my production server's web.config to my local workstation. I had forgotten that the production config uses impersonation. That turned out to be my problem. That user has nearly no permissions on my local workstation.
If you add the impersonation user to your local machine's IIS_WPG you can keep from having to do weird things to your Temporary ASP.NET Files permissions, etc.
Hats off to this post that led me to this truth.
My solution was to delete the impersonation line from my local web.config
Could you check permissions for IIS user in your wwwroot folder and “Temporary ASP.NET Files” C:\WINDOWS\Microsoft.NET\Framework\version\Temporary ASP.NET? If permissions alright try clear asp.net temp folder and run your application again(and check permissions on this folder again).
Just fixed this one. A new reason:
The ACLs on the deployment folder had become messed up (eg. bin
folder showing, in Explorer's security advanced view, inheriting permissions not from its parent, but its parent's parent).
A quick reset permissions from the site's root and all started working again.
For me the issue was with the config file.
<identity impersonate="true" userName="abc" password="xyz"/>
Here the credential given was not correct either correct that or comment out if not required.