Runtime Server Error in '/' Application and a 'create root file to fix' dunno how to do this.
For several weeks Firefox crashes when I close it down for the day. Firefox error message box sends crash report. Today I got I think from Firefox: please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off". <configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration> Then there's a second file it says to add. Umm, where/how? The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL. <configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration> Okay, but under ProgramFiles>Firefox there are several folders and none of them say "root" so where am I to create said file and how do I get it there? And then what? I sure don't want to crash Firefox any more than it does as it at least still works.
Giải pháp được chọn
Is/was the page background a pale yellow color? That message is not for you. It's the instructions of Microsoft's IIS web server to the web developer or webmaster on how to make error pages more intelligible so they can fix a glitch in their web application.
Occasionally that kind of glitch is caused by mismatched files or cookies, so you might be able to work around it by doing "the usual":
When you have a problem with one particular site, a good "first thing to try" is clearing your Firefox cache and deleting your saved cookies for the site.
(1) Bypass Firefox's Cache
Use Ctrl+Shift+r to reload the page fresh from the server.
Alternately, you also can clear Firefox's cache completely using:
"3-bar" menu button (or Tools menu) > Options > Advanced
On the Network mini-tab > Cached Web Content : "Clear Now"
If you have a large hard drive, this might take a few minutes.
(2) Remove the site's cookies (save any pending work first). While viewing a page on the site, try either:
- right-click and choose View Page Info > Security > "View Cookies"
- (menu bar) Tools > Page Info > Security > "View Cookies"
In the dialog that opens, you can remove the site's cookies individually.
Then try reloading the page. Does that help?
Regarding crashes, when Firefox crashes, it usually records information about what was happening at that moment. You can submit that data to Mozilla and share it with forum volunteers to see whether it points to the solution. Please check the support article "Firefox Crashes" (especially the last section) for steps to get those crash report IDs, and then post some of the recent ones here.
Đọc câu trả lời này trong ngữ cảnh 👍 18Tất cả các câu trả lời (2)
Giải pháp được chọn
Is/was the page background a pale yellow color? That message is not for you. It's the instructions of Microsoft's IIS web server to the web developer or webmaster on how to make error pages more intelligible so they can fix a glitch in their web application.
Occasionally that kind of glitch is caused by mismatched files or cookies, so you might be able to work around it by doing "the usual":
When you have a problem with one particular site, a good "first thing to try" is clearing your Firefox cache and deleting your saved cookies for the site.
(1) Bypass Firefox's Cache
Use Ctrl+Shift+r to reload the page fresh from the server.
Alternately, you also can clear Firefox's cache completely using:
"3-bar" menu button (or Tools menu) > Options > Advanced
On the Network mini-tab > Cached Web Content : "Clear Now"
If you have a large hard drive, this might take a few minutes.
(2) Remove the site's cookies (save any pending work first). While viewing a page on the site, try either:
- right-click and choose View Page Info > Security > "View Cookies"
- (menu bar) Tools > Page Info > Security > "View Cookies"
In the dialog that opens, you can remove the site's cookies individually.
Then try reloading the page. Does that help?
Regarding crashes, when Firefox crashes, it usually records information about what was happening at that moment. You can submit that data to Mozilla and share it with forum volunteers to see whether it points to the solution. Please check the support article "Firefox Crashes" (especially the last section) for steps to get those crash report IDs, and then post some of the recent ones here.
jscher - wow. THANK YOU!!! Yes, pale yellow, have emptied cache. Perhaps now everything will again work glitchless. By the way, I completed about half of what all that the post on Firefox crashing said to do. I was a bit intimidated on the memtest86+ tool. But now I am again encouraged. Wouldn't you like to move to Idaho and be my close neighbor. Blessings! Thanks!