Hi Folks,

I've been getting the following error on and off in an asp.net project that uses my generated DAL:

Description: 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.

Parser Error Message: Access is denied: 'SD.LLBLGen.Pro.DQE.SqlServer.NET11'.

Source Error:

Line 196: <add assembly="System.EnterpriseServices, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/> Line 197: <add assembly="System.Web.Mobile, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/> Line 198: <add assembly="*"/> Line 199: </assemblies> Line 200: </compilation>

Source File: c:\windows\microsoft.net\framework\v1.1.4322\Config\machine.config Line: 198

Anyone have any idea what is causing this? It seems to happen sometimes after I rebuild the project and refresh the page I was working on.

Has anyone else experienced this behavior?

Cheers,

Padgett

I think the file is locked by the IDE. You are using VB.NET? THe VB.NET compiler has this weirdness, I'm positive about that, the C# compiler has it less often (almost never).

Very odd - I am just hoping it isn't going to happen on my live web server!!

I have four main projects: * DAL - C# * Main windows app - VB.NET * Main website - VB.NET * Report server website - C#

I get this behaviour when testing both websites - under both languages.

I will post an update if I can figure out whats going on here.

Cheers,

Padgett

If you are testing after a compile, it can be that the file is locked, I've seen reports about this error in newsgroups (not llblgen related). You shouldn't run into errors when the IDE is closed. If you DO in that situation, it's something else.

I get the same error using C# only - but only when using windows 2000 - with windows XP I'm yet to encounter this problem.

Anyone know of a quick way of having the file unlocked? Apart from a reboot :-) NB: Closing the IDE doesn't work.

http://www.systeminternals.com has a tool, process explorer, which allows you to find a resource and check which process contains a lock on that file. With that you can check which process locks the file and thus which process to kill/restart. (you can do that with process explorer as well )