- Posted by justin on July 15, 2005
Saw this on Janine’s personal blog @ http://jiwhite.ebloggy.com/ . I have been having this problem ever since I re-install everything on my laptop. Thanx for the fix.
Excerpt from Janine’s Blog:
I finally found a solution to a programming problem that has been wasting my time for months. Approximately every other time (sometimes more) that I compiled an ASP .NET application, then tried to test the site, I would get and Access is Denied error indicating that there was a problem with the machine.config or web.config file while trying to load the assemblies. The only reliable way I found to clear this issue was to reboot, which was wasting a lot of my time. It turns out that the issue has nothing to do with the config files. It is cause by the Indexing Service catching the files, even if the ASP .NET application doesn't use Indexing! The best solution is to turn off the Indexing if you're not using it. For example, on my Windows XP Pro machine, I went to Start>Administrative Tools>Services, right click on Indexing Service and select Stop. I also opened up the Properties for the Indexing Service and set it to start Manually, instead of Automatically.
An excellent article on this topic is Access is NOT Denied! Also, thanks to Eric Bowen's blog for pointing the way to it.