This message was discovered on microsoft.public.dotnet.framework.aspnet.
| DelC |
In the latest version of our Web Application we have started seeing the following error message - "External component has thrown an exception", Stack Trace is shown below.
Only minor bug fixes in the .vb codebehind files have been done between a previous version that was fine and this one.
I have googled on this but not found any answer or suggestions as to where to start looking. Is this error in my code (.vb or .aspx) or a build option or deployment issue ?
The application is built and deployed to .Net Framework 1.0 and runs on Win2k SP4.
External component has thrown an exception. in System.Web
at System.Web.Compilation.BaseCompiler.ThrowIfCompilerErrors(CompilerResults
results, CodeDomProvider codeProvider, CodeCompileUnit sourceData, String
sourceFile, String sourceString)
at System.Web.Compilation.SourceCompiler.CompileAndCache()
at System.Web.Compilation.SourceCompiler.CompileSourceStringIntoType(String
sourceString, String typeName, CodeLinePragma linePragma, IDictionary
assemblies, Type compilerType, CompilerParameters compilParams)
at SWU.SimpleWebHandlerParser.CompileSourceCode()
at SWU.SimpleWebHandlerParser.GetCompiledTypeInternal()
at SWU.SimpleWebHandlerParser.GetCompiledType()
at SWU.SimpleWebHandlerParser.GetCompiledTypeFromCache()
at SWU.WebHandlerParser.GetCompiledType(String virtualPath, String
physicalPath, HttpContext context)
at SWU.SimpleHandlerFactory.GetHandler(HttpContext context, String
requestType, String virtualPath, String path)
at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String
requestType, String path, String pathTranslated, Boolean useAppConfig)
at
System.Web.MapHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep
..Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously)
SWU = System.Web.UI
|
|
| |
| |
| Natty Gur |
Hi,
It's hard to know but your Stack Trace implies that something goes wrong
in the dynamic process of creating assembly that represent the page HTML
definition. What I suggest:
1) Delete the cache of your application from asp.net temporary files
directory located under C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322.
2) Double check with source safe for changes between the last deployed
version and the current one in the pages HTML.
HTH
Natty Gur[MVP]
blog : http://weblogs.asp.net/ngur
Mobile: +972-(0)58-888377
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
|
|
| |
|
|
|
|
|
