.NET Configuration Error & headache

by Erik Lane 2. November 2004 01:02

On a current project we're building some sites using the Plumtree portal framework.  To make it all work we need to reference the Plumtree dll's.  In building my projects I would from time to time get a .NET configuration error when building the project.  The error would say:

"access denied" "An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately".

This happened for one of the Plumtree assemblies and show the line in the machine.config "ADD assembly="*".  This didn't happen all the time but was getting to be a headache since I would need to reboot my machine to get my project to compile.


After googling a few times I believe I've found the fix (man I hope so).

CAUSE:
If you run Index Server (Cisvc.exe), then Index Server may rescan the Temporary ASP.NET Files directory while it requests a Microsoft ASP.NET page. Cisvc.exe then holds a lock on the Temporary ASP.NET Files directory for one to five minutes. The length of time of the lock depends on the size of the directory that causes the Aspnet_wp.exeprocess (or W3wp.exe process for applications that run on Microsoft Internet Information Services [IIS] 6.0) to not load the particular DLL.

RESOLUTION:
If you do not use Index Server on the server, you can disable it.  Or if you use Index Server, you can exclude the Temporary ASP.NET Files directory from the folders that the Index Server scans.

Here is the MSDN KB article.

Tags:

Comments

The Wife
The Wife United States on 11/1/2004 7:14:00 PM

Oh cool - did you get it worked out?  I've been praying you would!

eriklane
eriklane United States on 11/1/2004 7:21:00 PM

Looks like I did.  It's not been an issue today.  woohoo!!

Vidya
Vidya on 1/4/2005 2:32:00 AM

Thank you very much for the fix to this configuration error. It certainly was giving me a big headache. Now the application works just fine.

Paolo
Paolo on 4/28/2005 10:20:00 AM

I still have this darn problem, despite Index Server shutdown and SP1 intalled. DevEnv.exe still locks my DLL...

Bryan
Bryan on 8/9/2005 4:45:00 PM

I think I have this issue worse than anyone I've read about. No indexing running, and I get the lock error even after rebooting, and before I can even open a source (.cs) file! It won't even let me open the files to edit them, let alone compile them!

Strangly enough, only VS.net complains about opening the file. Any other program (notepad) will open it! WTF?! Anyone else have this problem?

eriklane
eriklane United States on 8/9/2005 4:49:00 PM

Bryan, That does sound like a serious issue.  I've not seen it that bad.  I hope you do find the answer.

Benjamin
Benjamin on 5/12/2008 12:30:00 AM

Thanks a lot man, this sure gave us a lot of headache...

Comments are closed