Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Feb 27, 2010 02:32 PM by efess
Sep 11, 2006 10:26 AM|LINK
Sep 12, 2006 01:49 AM|LINK
I too am struggling with this issue. I rarerly eveer saw this problem, but a few weeks ago I started using the Atlas framework in my site and now the problem occurs several times a week. In fact, it happened about 5 times today. I have my site "armed" to
email me whenever the problem happens so that I can manually fix it. This has been painful and I am running out of ideas. I am considering removing all of the cool Atlas enhancements in hopes that I reduce the frequency of this problem.
Sep 13, 2006 07:40 PM|LINK
Sep 17, 2006 03:17 PM|LINK
I installed the hotfix, and it works fine at beginning. I haven't seen the same error for the past 3 weeks, but UNFORTUNATELY, the problem showed up again today. I then decided to come here to see if there is any new development on this issue, and I foudn
[quote user="ICGopher"]Has anyone else noticed that disabling the debug in web.config seems to avoid this error? We have an application we are pushing out, and have experienced this problem. I disabled debug in the web.config in our test environment, I'll
report if we do not see the problem persist (although it seems like a hard bug to recreate).
I tried the same thing. I simply turned off debug WITHOUT manually modifying the page, and the error message disappeared.
I will keep an eye on this, and I hope this way works. If so, at least we can have a problem-free production server.
Sep 18, 2006 05:55 PM|LINK
Sep 20, 2006 02:43 PM|LINK
Sep 20, 2006 06:40 PM|LINK
Sep 20, 2006 08:48 PM|LINK
Sep 26, 2006 04:21 PM|LINK
I've the same problem, too.
My debug option in web.config file is always false... but I've the problem anyway.
I'm thinking about installing the hotfix... but I'm scared [:)]. I don't want to install something that is not completely tested.
When I've this problem I simply edit/save my main master page file (I use nested master pages)... this will require a recompile... and so web application starts to serve requests again.
When will MS release the official/supported/tested FIX for this problem?
Oct 17, 2006 01:50 PM|LINK
I concur that is a problem with nested user controls. Debug is set to
false in production.
Yes, clearing Temporary ASP.NET Files solves the problem but that is not the ideal solution. The solution would be to figure out the cause and fix it.
I contacted Microsoft and received a "hotfix patch" regarding KB915782
but that did not work.