Hi All, People have been having sporatic problems with the ability to lay down a new version of an ASP.NET application. The following is an exception that is occurring and quite often the only way to get around this is to reboot...
Anyone else seen this...By the way some of the Components are using COM+ Services. Configuration Error 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: Can not access file 'FKInfo' because it is being used by another process. Source Error: Line 197: <add assembly="System.Drawing, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/> Line 198: <add assembly="System.EnterpriseServices, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/> Line 199: <add assembly="*"/> Line 200: </assemblies> Line 201: Source File: c:\winnt\microsoft.net\framework\v1.0.3705\Config\machine.config Line: 199 ------------------------------------------------------------------------ -------------------------------- This particular message is complaining about "FKInfo", but the error can occur on all sorts of different files, there doesn't seem to be any pattern. Sometimes restarting IIS works, most the time it doesn't though. Restarting IIS is better then a reboot, but it still kills everyone in production. I've tried cleaning all our objects out of COM+, but that doesn't seem to have an effect. Some posts from Microsoft on Google recommended shutting down the indexing service and virus checkers on the web server, which we did, but we still get the problem, and other posts on Google say it didn't work for them either. I think ATT may have other services scanning files, which may be the problem, but I'm not sure. I'm extremely suspicious this has something to do with caching. Check out the files in the directory: C:\WINNT\Microsoft.NET\Framework\v1.0.3705\Temporary ASP.NET Files. That directory is full of .dll's. I think that's were files are getting locked up by IIS and not released. If we can solve this problem for FK we'd be heroes. Its really driving them crazy, b/c xcopy deployment isn't really possible now. Its xcopy and then reboot. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
