I keep getting the following error error everyday or so. I don't have cache
turned on and I can't really find any descriptions of this error so I have no
idea how to fix it. Anyone have any ideas?
Running IIS 6 on win2003.
Error: System.Web.UI.ParserCacheItem GetParserCacheItem()
Stack Trace:System.Web.UI.TemplateParser.GetParserCacheItem() at
System.Web.UI.TemplateControlParser.CompileAndGetParserCacheItem(String
virtualPath, String inputFile, HttpContext context) at
System.Web.UI.TemplateControlParser.GetCompiledInstance(String virtualPath,
String inputFile, HttpContext context) at
System.Web.UI.PageParser.GetCompiledPageInstanceInternal(String virtualPath,
String inputFile, HttpContext context) at
System.Web.UI.PageHandlerFactory.GetHandler(HttpContext context, String
requestType, String url, String path) at
System.Web.HttpApplication.MapHttpHandler(HttpContext context, String
requestType, String path, String pathTranslated, Boolean useAppConfig)
Thanks,
Chip
Alvin Bruney [MVP] - 31 Jan 2005 16:19 GMT
I believe an application restart is the culprit for generating this error.
You will need to look up your event logs for process restarts and try to tie
them to the time of the error first before looking for a fix.

Signature
Regards,
Alvin Bruney [MVP ASP.NET]
[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ http://tinyurl.com/27cok
----------------------------------------------------------
>I keep getting the following error error everyday or so. I don't have
>cache
[quoted text clipped - 21 lines]
> Thanks,
> Chip
csockwell - 31 Jan 2005 17:11 GMT
I found my mistake. While looking at the error log times I noticed that the
webpages that genetate this error do not exist in that particular directory.
It threw me off because it was an aspx error not a 401 page not found. This
is a simple broken link; is it normal to have aspx report an error for a
missing page?
> I believe an application restart is the culprit for generating this error.
> You will need to look up your event logs for process restarts and try to tie
[quoted text clipped - 25 lines]
> > Thanks,
> > Chip
csockwell - 31 Jan 2005 17:11 GMT
I found my mistake. While looking at the error log times I noticed that the
webpages that genetate this error do not exist in that particular directory.
It threw me off because it was an aspx error not a 401 page not found. This
is a simple broken link; is it normal to have aspx report an error for a
missing page?
> I believe an application restart is the culprit for generating this error.
> You will need to look up your event logs for process restarts and try to tie
[quoted text clipped - 25 lines]
> > Thanks,
> > Chip
Alvin Bruney [MVP] - 31 Jan 2005 22:48 GMT

Signature
Regards,
Alvin Bruney [MVP ASP.NET]
[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ http://tinyurl.com/27cok
----------------------------------------------------------
>I found my mistake. While looking at the error log times I noticed that the
> webpages that genetate this error do not exist in that particular
[quoted text clipped - 36 lines]
>> > Thanks,
>> > Chip