System.Web.Compilation.BaseCompiler.ThrowIfCompilerErrors

[Guest]

We are getting the following exception in our IIS6/ASP.NET 1.1 application
and it stops if we copy our DLLs back into the local BIN directory. But will
start happening again in several hours?

What could be causing something like this and why would recopying our DLLs
back into the directory fix the problem temporarily?

The application was working fine for over a year and this started happening
about a week ago. Could an update to the ASP.NET 1.1 be causing this?

This is a high traffic web application that receives over 1million page
views a year.

Here is the stack trace:
<LogEntries><log LogGUID="cf9f9a1a-dd0f-4994-b208-1a5bbbbfbb9b"
LogTypeKey="MODULE_LOAD_EXCEPTION" LogUserID="-1" LogUserName="mikead"
LogPortalID="0" LogPortalName=""
LogCreateDate="2006-05-30T17:31:34.9070000-05:00" LogCreateDateNum="0"
BypassBuffering="false" LogServerName="216-55-168-180"
LogConfigID="3"><properties><property><name>ModuleId</name><value>-1</value></property><property><name>ModuleDefId</name><value>-1</value></property><property><name>FriendlyName</name><value
/></property><property><name>ModuleControlSource</name><value
/></property><property><name>AssemblyVersion</name><value>03.02.02</value></property><property><name>Method</name><value>System.Web.Compilation.BaseCompiler.ThrowIfCompilerErrors</value></property><property><name>FileName</name><value
/></property><property><name>FileLineNumber</name><value>0</value></property><property><name>FileColumnNumber</name><value>0</value></property><property><name>PortalID</name><value>0</value></property><property><name>PortalName</name><value>South
Padre Island Real Estate - Alice
Donahue</value></property><property><name>UserID</name><value>224</value></property><property><name>UserName</name><value>mikead</value></property><property><name>ActiveTabID</name><value>79</value></property><property><name>ActiveTabName</name><value>My
Properties</value></property><property><name>AbsoluteURL</name><value>/Default.aspx</value></property><property><name>AbsoluteURLReferrer</name><value>http://www.alicedonahue.com/MyProperties.aspx</value></property><property><name>ExceptionGUID</name><value>b08adab4-789a-4a81-ba45-a5eb93709d9e</value></property><property><name>DefaultDataProvider</name><value>DotNetNuke.Data.SqlDataProvider,
DotNetNuke.SqlDataProvider</value></property><property><name>InnerException</name><value>External
component has thrown an
exception.</value></property><property><name>Message</name><value>DotNetNuke.Services.Exceptions.ModuleLoadException:
External component has thrown an exception. ---> System.Web.HttpException:
External component has thrown an exception. --->
System.Web.HttpCompileException: External component has thrown an exception.
at System.Web.Compilation.BaseCompiler.ThrowIfCompilerErrors(CompilerResults
results, CodeDomProvider codeProvider, CodeCompileUnit sourceData, String
sourceFile, String sourceString) at
System.Web.Compilation.BaseCompiler.GetCompiledType() at
System.Web.UI.UserControlParser.CompileIntoType() at
System.Web.UI.TemplateParser.GetParserCacheItemThroughCompilation() --- End
of inner exception stack trace --- at
System.Web.UI.TemplateParser.GetParserCacheItemInternal(Boolean
fCreateIfNotFound) at System.Web.UI.TemplateParser.GetParserCacheItem() at
System.Web.UI.TemplateControlParser.CompileAndGetParserCacheItem(String
virtualPath, String inputFile, HttpContext context) at
System.Web.UI.TemplateControlParser.GetCompiledType(String virtualPath,
String inputFile, HttpContext context) at
System.Web.UI.UserControlParser.GetCompiledUserControlType(String
virtualPath, String inputFile, HttpContext context) at
System.Web.UI.TemplateControl.LoadControl(String virtualPath) at
DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule,
PortalSettings PortalSettings) --- End of inner exception stack trace
---</value></property><property><name>StackTrace</name><value
/></property><property><name>Source</name><value
/></property></properties></log></LogEntries>

 

[Guest]

We disabled the application directory from anti-virus scanning and the issue
went away.

 

[Guest]

The issue has resurfaced, it does not happen as often with virus scan diabled.