Hi,
- Cccam Error Reading Web Page Example
- Cccam Error Reading Web Page Template
- Cccam Error Reading Web Page Examples
Thank you for posting in Microsoft community.
1.Have you made any recent changes prior to the issue?
2.Do you get the error message with one particular webpage or will all the pages?
3.What is the complete error message/code you receive?
I have provided methods to fix the object error issue. Please follow each method carefully. If one method doesn't work, proceed with the next methods to resolve the issue.
Method 1: Use the Internet Explorer (No Add-ons) modeHow to manage add-ons in Internet Explorer 9
Method 2: Try to open the page in Compatibility view and check
How to use Compatibility View in Internet Explorer 9
Method 3: I would suggest you to refer the instructions in the thread and the link mentioned below:
How to troubleshoot script errors in Internet Explorer
Method 4:
How to optimize Internet Explorer
Note: The Reset Internet Explorer Settings feature might reset security settings or privacy settings that you added to the list of Trusted Sites. The Reset Internet Explorer Settings feature might also reset parental control settings. We recommend that you note these sites before you use the Reset Internet Explorer Settings feature.
Please post back if you are still experiencing the issue. I will be glad to provide you with additional options.
-->by Scott Mitchell
Download Code or Download PDF
What does the user see when a runtime error occurs in an ASP.NET web application? The answer depends on how the website's <customErrors> configuration. By default, users are shown an unsightly yellow screen proclaiming that a runtime error has occurred. This tutorial shows how to customize these settings to display an aesthetically-pleasing custom error page that matches your site's look and feel.
Introduction
In a perfect world there would be no run-time errors. Programmers would write code with nary a bug and with robust user input validation, and external resources like database servers and email servers would never go offline. Of course, in reality errors are inevitable. The classes in the .NET Framework signal an error by throwing an exception. For example, calling a SqlConnection object's Open method establishes a connection to the database specified by a connection string. However, if the database is down or if the credentials in the connection string are invalid then the Open method throws a
SqlException
. Exceptions can be handled by the use of try/catch/finally
blocks. If code within a try
block throws an exception, control is transferred to the appropriate catch block where the developer can attempt to recover from the error. If there is no matching catch block, or if the code that threw the exception is not in a try block, the exception percolates up the call stack in search of try/catch/finally
blocks.If the exception bubbles all the way up to the ASP.NET runtime without being handled, the
HttpApplication
class's Error
event is raised and the configured error page is displayed. By default, ASP.NET displays an error page that is affectionately referred to as the Yellow Screen of Death (YSOD). There are two versions of the YSOD: one shows the exception details, a stack trace, and other information helpful to developers debugging the application (see Figure 1); the other simply states that there was a run-time error (see Figure 2).The exception details YSOD is quite helpful for developers debugging the application, but showing a YSOD to end users is tacky and unprofessional. Instead, end users should be taken to an error page that maintains the site's look and feel with more user-friendly prose describing the situation. The good news is that creating such a custom error page is quite easy. This tutorial starts with a look at ASP.NET's different error pages. It then shows how to configure the web application to show users a custom error page in the face of an error.
Examining the Three Types of Error Pages
When an unhandled exception arises in an ASP.NET application one of three types of error pages is displayed:
- The Exception Details Yellow Screen of Death error page,
- The Runtime Error Yellow Screen of Death error page, or
- A custom error page
The error page developers are most familiar with is the Exception Details YSOD. By default, this page is displayed to users who are visiting locally and therefore is the page that you see when an error occurs when testing the site in the development environment. As its name implies, the Exception Details YSOD provides details about the exception - the type, the message, and the stack trace. What's more, if the exception was raised by code in your ASP.NET page's code-behind class and if the application is configured for debugging then the Exception Details YSOD will also show this line of code (and a few lines of code above and below it).
Figure 1 shows the Exception Details YSOD page. Note the URL in the browser's address window:
http://localhost:62275/Genre.aspx?ID=foo
. Recall that the Genre.aspx
page lists the book reviews in a particular genre. It requires that GenreId
value (a uniqueidentifier
) be passed through the querystring; for example, the appropriate URL to view the fiction reviews is Genre.aspx?ID=7683ab5d-4589-4f03-a139-1c26044d0146
. If a non-uniqueidentifier
value is passed in through the querystring (such as 'foo') an exception is thrown.Note
To reproduce this error in the demo web application available for download you can either visit
Genre.aspx?ID=foo
directly or click the 'Generate a Runtime Error' link in Default.aspx
.Note the exception information presented in Figure 1. The exception message, 'Conversion failed when converting from a character string to uniqueidentifier' is present at the top of the page. The type of the exception,
System.Data.SqlClient.SqlException
, is listed, as well. There's also the stack trace.Figure 1: The Exception Details YSOD Includes Information About the Exception
(Click to view full-size image)
(Click to view full-size image)
The other type of YSOD is the Runtime Error YSOD, and is shown in Figure 2. The Runtime Error YSOD informs the visitor that a run-time error has occurred, but it does not include any information about the exception that was thrown. (It does, however, provide instructions on how to make the error details viewable by modifying the
Web.config
file, which is part of what makes such a YSOD look unprofessional.)By default, the Runtime Error YSOD is shown to users visiting remotely (through http://www.yoursite.com), as evidenced by the URL in the browser's Address bar in Figure 2:
http://httpruntime.web703.discountasp.net/Genre.aspx?ID=foo
. The two different YSOD screens exist because developers are interested in knowing the error details, but such information should not be shown on a live site as it may reveal potential security vulnerabilities or other sensitive information to anyone who visits your site.Note
If you are following along and are using DiscountASP.NET as your web host, you may notice that the Runtime Error YSOD does not display when visiting the live site. This is because DiscountASP.NET has their servers configured to show the Exception Details YSOD by default. The good news is that you can override this default behavior by adding a
<customErrors>
section to your Web.config
file. The 'Configuring Which Error Page is Displayed' section examines the <customErrors>
section in detail.Gta for windows 8 free. Figure 2: The Runtime Error YSOD Does Not Include Any Error Details
(Click to view full-size image)
(Click to view full-size image)
The third type of error page is the custom error page, which is a web page that you create. The benefit of a custom error page is that you have complete control over the information that is displayed to the user along with the page's look and feel; the custom error page can use the same master page and styles as your other pages. The 'Using a Custom Error Page' section walks through creating a custom error page and configuring it to display in the event of an unhandled exception. Figure 3 offers a sneak peak of this custom error page. As you can see, the look and feel of the error page is much more professional-looking than either of the Yellow Screens of Death shown in Figures 1 and 2.
Figure 3: A Custom Error Page Offers a More Tailored Look and Feel
(Click to view full-size image)
(Click to view full-size image)
Take a moment to inspect the browser's Address bar in Figure 3. Note that the Address bar shows the URL of the custom error page (
/ErrorPages/Oops.aspx
). In Figures 1 and 2 the Yellow Screens of Death are shown in the same page that the error originated from (Genre.aspx
). The custom error page is passed the URL of the page where the error occurred via the aspxerrorpath
querystring parameter.Configuring Which Error Page is Displayed
Which of the three possible error pages is displayed is based on two variables:
- The configuration information in the
<customErrors>
section, and - Whether the user is visiting the site locally or remotely.
The
<customErrors>
section in Web.config
has two attributes that affect what error page is shown: defaultRedirect
and mode
. The defaultRedirect
attribute is optional. If provided, it specifies the URL of the custom error page and indicates that the custom error page should be shown instead of the Runtime Error YSOD. The mode
attribute is required and accepts one of three values: On
, Off
, or RemoteOnly
. These values have the following behavior:On
- indicates that the custom error page or the Runtime Error YSOD is shown to all visitors, regardless of whether they are local or remote.Off
- specifies that the Exception Details YSOD is displayed to all visitors, regardless of whether they are local or remote.RemoteOnly
- indicates that the custom error page or the Runtime Error YSOD is shown to remote visitors, while the Exception Details YSOD is shown to local visitors.
Unless you specify otherwise, ASP.NET acts as if you had set the mode attribute to
RemoteOnly
and had not specified a defaultRedirect
value. In other words, the default behavior is that the Exception Details YSOD is displayed to local visitors while the Runtime Error YSOD is shown to remote visitors. You can override this default behavior by adding a <customErrors>
section to your web application's Web.config file.
Using a Custom Error Page
Every web application should have a custom error page. It provides a more professional-looking alternative to the Runtime Error YSOD, it is easy to create, and configuring the application to use the custom error page takes only a few moments. The first step is creating the custom error page. I've added a new folder to the Book Reviews application named
ErrorPages
and added to that a new ASP.NET page named Oops.aspx
. Have the page use the same master page as the rest of the pages on your site so that it automatically inherits the same look and feel.Figure 4: Create a Custom Error Page
Next, spend a few minutes creating the content for the error page. I've created a rather simple custom error page with a message indicating that there was an unexpected error and a link back to the site's homepage.
Figure 5: Design Your Custom Error Page
(Click to view full-size image)
(Click to view full-size image)
With the error page completed, configure the web application to use the custom error page in lieu of the Runtime Error YSOD. This is accomplished by specifying the URL of the error page in the
<customErrors>
section's defaultRedirect
attribute. Add the following markup to your application's Web.config
file:The above markup configures the application to show the Exception Details YSOD to users visiting locally, while using the custom error page Oops.aspx for those users visiting remotely. To see this in action, deploy your website to the production environment and then visit the Genre.aspx page on the live site with an invalid querystring value. You should see the custom error page (refer back to Figure 3).
To verify that the custom error page is only shown to remote users, visit the
Genre.aspx
page with an invalid querystring from the development environment. You should still see the Exception Details YSOD (refer back to Figure 1). The RemoteOnly
setting ensures that users visiting the site on the production environment see the custom error page while developers working locally continue to see the details of the exception.Notifying Developers and Logging Error Details
Errors that occur in the development environment were caused by the developer sitting at her computer. She is shown the exception's information in the Exception Details YSOD, and she knows what steps she was performing when the error occurred. But when an error occurs on production, the developer has no knowledge that an error occurred unless the end user visiting the site takes the time to report the error. And even if the user goes out of his way to alert the development team that an error occurred, without knowing the exception type, message, and stack trace it can be difficult to diagnose the cause of the error, let alone fix it.
For these reasons it is paramount that any error in the production environment is logged to some persistent store (such as a database) and that the developers are alerted of this error. The custom error page may seem like a good place to do this logging and notification. Unfortunately, the custom error page does not have access to the error details and therefore cannot be used to log this information. The good news is that there are a number of ways to intercept the error details and to log them, and the next three tutorials explore this topic in more detail.
Using Different Custom Error Pages for Different HTTP Error Statuses
When an exception is thrown by an ASP.NET page and is not handled, the exception percolates up to the ASP.NET runtime, which displays the configured error page. If a request comes into the ASP.NET engine but cannot be processed for some reason - perhaps the requested file is not found or Read permissions have been disabled for the file - then the ASP.NET engine raises an
HttpException
. This exception, like exceptions raised from ASP.NET pages, bubbles up to the runtime, causing the appropriate error page to be displayed.What this means for the web application in production is that if a user requests a page that is not found then they will see the custom error page. Figure 6 shows such an example. Because the request is for a non-existent page (
NoSuchPage.aspx
), an HttpException
is thrown and the custom error page is displayed (note the reference to NoSuchPage.aspx
in the aspxerrorpath
querystring parameter).Figure 6: The ASP.NET Runtime Displays the Configured Error Page In Response to an Invalid Request(Click to view full-size image)
By default, all types of errors cause the same custom error page to be displayed. However, you can specify a different custom error page for a specific HTTP status code using
<error>
children elements within the <customErrors>
section. For example, to have a different error page displayed in the event of a page not found error, which has an HTTP status code of 404, update the <customErrors>
section to include the following markup:With this change in place, whenever a user visiting remotely requests an ASP.NET resource that does not exist, they will be redirected to the
404.aspx
custom error page instead of Oops.aspx
. As Figure 7 illustrates, the 404.aspx
page can include a more specific message than the general custom error page.Note
Check out 404 Error Pages, One More Time for guidance on creating effective 404 error pages.
Figure 7: The Custom 404 Error Page Displays a More Targeted Message Than
(Click to view full-size image)
Oops.aspx
(Click to view full-size image)
Because you know that the
404.aspx
page is only reached when the user makes a request for a page that was not found, you can enhance this custom error page to include functionality to help the user address this specific type of error. For example, you could build a database table that maps known bad URLs to good URLs, and then have the 404.aspx
custom error page run a query against that table and suggest pages the user may be trying to reach.Note
The custom error page is only displayed when a request is made to a resource handled by the ASP.NET engine. As we discussed in the Core Differences Between IIS and the ASP.NET Development Server tutorial, the web server may handle certain requests itself. By default, the IIS web server processes requests for static content like images and HTML files without invoking the ASP.NET engine. Consequently, if the user requests a non-existent image file they will get back IIS's default 404 error message rather than ASP.NET's configured error page.
Summary
When an unhandled exception occurs in an ASP.NET application, the user is shown one of three error pages: the Exception Details Yellow Screen of Death; the Runtime Error Yellow Screen of Death; or a custom error page. Which error page is displayed depends on the application's
<customErrors>
configuration and whether the user is visiting locally or remotely. The default behavior is to show the Exception Details YSOD to local visitors and the Runtime Error YSOD to remote visitors.While the Runtime Error YSOD hides potentially sensitive error information from the user visiting the site, it breaks from your site's look and feel and makes your application look buggy. A better approach is to use a custom error page, which entails creating and designing the custom error page and specifying its URL in the
<customErrors>
section's defaultRedirect
attribute. You can even have multiple custom error pages for different HTTP error statuses.The custom error page is the first step in a comprehensive error handling strategy for a website in production. Alerting the developer of the error and logging its details are also important steps. The next three tutorials explore techniques for error notification and logging.
Happy Programming!
Further Reading
For more information on the topics discussed in this tutorial, refer to the following resources:
On Windows 10, Microsoft Edge has included a reading experience for PDF documents, EPUB ebooks, and web pages using Reading view for quite a while. But starting with the April 2018 Update (version 1803) the experience is getting updated with various improvements and a new interface.
In the updated version of Edge, which continues the work from previous versions, you'll find an interface that uses Fluent Design elements for a more consistent experience, whether you're reading an ebook or web page, or filling out a form online. Also, there are some new tools and features that will be available depending on the content you're viewing.
In this Windows 10 guide, we'll walk you through the steps to get started with Microsoft Edge to use the browser with PDF documents, EPUB ebooks, and Reading view to declutter web pages.
How to use Microsoft Edge as a PDF reader
On Windows 10, you don't need a third-party application to view and edit PDF documents locally stored on your computer or on the web, because Microsoft Edge has you covered with all the essential features you've come to expect on a PDF reader.
Navigating PDF tools
Starting with the April Update, Microsoft Edge includes a redesigned toolbar that ditches the edge-to-edge design with an experience that floats under the address bar. Also, it now uses the Acrylic effect part of Fluent Design that adapts to the color theme you're using on the browser.
On the left, the toolbar shows the total number of pages, and the page you're on, and you can click to specify the page you want to go.
The Table of contents button is located next to the page information, and the menu allows you to quickly skip to a specific chapter in the document.
If the table of contents isn't available, you can use the Search button (Ctrl + F) to query part of the text to find a specific section. Alternatively, you can use the page option to go to the page you want to read.
On the right side, you'll find several tools to adjust the view of the PDF document, including 'fit to page,' 'zoom out' and 'zoom in.' In addition, you get a Rotate button that comes in handy when you're working with scanned documents that don't have the proper orientation.
And the Layout button includes options to switch between one-page and two-page view and continuous scrolling for better navigation on long PDF documents.
Also, depending if you're editing a protected or unprotected PDF document, you'll see the options to Save and Save As, along with a button to view the document in full-screen mode (F11) for a distraction-free reading experience.
Filling out forms
Using the reading experience, you can also fill in PDF forms online (or forms stored on your computer) within the browser, and then save for printing.
The process to fill out a form is a straightforward process. Open the PDF document, edit the fields, and use the drop-down menus to select additional options as required. Then click the Save button in the top-right corner, or click the Save As button to keep a copy.
Annotating PDF documents
Microsoft Edge supports PDF annotation using highlighter, notes, and the ability to ask Cortana. Also, the experience includes options to copy and share content using the Windows 10 Share functionality.
On an unprotected PDF document, you can select some text to access the context menu with five options, including:
- Highlight – Allows you to highlight text using four different colors, and also remove the highlight.
- Add a note – Opens a Sticky Notes-like experience to add comments. After typing the note, click the check mark button in the top-right corner to save it, or the trash can button in the bottom-right to delete it.
- Copy – Copies selected text to the clipboard, which you can paste into another document.
- Share – Lets you share selected content through email, social media, or another app using the Windows 10's Share experience.
- Cortana – Opens the assistant flyout and researches the word or text you've selected.
Alongside the visual menu, you can also right-click the selected text to access the same options, but in a traditional menu style that includes the name of each option.
Printing PDF documents
Using the browser you can also print PDF documents and forms. Just click the Print button in the toolbar, select your preferences, and click the Print button.
How to use Microsoft Edge as a EPUB reader
Along with the ability to read books you purchase from the Microsoft Store, Edge can also read protected and unprotected EPUB ebooks.
Navigating EPUB tools
When viewing an EPUB file, similar to the PDF reading experience, you'll find a floating toolbar with specific tools for this type of file. However, unlike reading PDF documents, the experience uses Fluent Design elements, but it doesn't adapt to the browser color scheme. It only uses the light theme color.
On the left side, you'll find the EPUB table of contents that allows you to quickly jump between sections.
Then there's the Notes flyout that includes a list of comments, annotations, and highlights you added to the book. Clicking any of the items will take you to the page where you inserted the note.
On the right side of the toolbar, you'll find a Text flyout with a number of options to change the text size, text spacing, and page theme.
In addition, when reading ebooks, you can use the Grammar Tools button with options to help you better comprehend the text that you're reading.
Using these options, you can split words into syllables, and highlight all nouns, verbs, and adjectives. (If you're opening the Grammar Tools for the first time, you'll need to click the button to download and install the tools.)
The toolbar also includes a floppy disk button to save free EPUB books directly from the web and onto your device.
If you need to save a page for later viewing, you can conveniently click the Bookmarks button, and then click the Add to bookmark option. If you want to return to a page, click the button again, and select the bookmark you want.
Quick Tip: To remove a bookmark, hover over the item and click the X button, or right-click the item and select Delete. You can even change the name of the bookmark by selecting the Rename option.
Although you can just hit the F11 key to access the full-screen mode when reading a book, you can also click the Full screen button for a distraction-free reading experience.
Annotating EPUB books
You can annotate on EPUB books using highlighter, underline, and notes. In addition, you can copy and share fragments of text, and use Cortana to research content.
To get started with EPUB annotation, select some text to access the context menu with five options, including:
- Highlight – Allows you to highlight text using four different colors, and then remove the highlight.
- Underline – This is just another way to highlight content, but using a red underline.
- Add a note – Opens a Sticky Notes-like experience to add comments. After typing the note, click the check mark button in the top-right corner to save it, or the trash can button in the bottom-right to delete it.
- Copy – Copies selected text to the clipboard, which you can then paste into another document.
- Share – Lets you share selected content through email, social media, or another app using the Windows 10's Share experience.
- Cortana – Opens the assistant flyout and researches the word or text you've selected.
Alternatively, you can select and right-click the text to access the same options, but using a traditional menu that shows the name of each option.
Finally, at the bottom of the page, you'll find a seek bar that shows your reading progress, the number of pages, and an option to jump to a specific page number.
How to use Microsoft Edge Reading view experience
Usually, web pages are filled with all sorts of content, including ads and many other design elements, and while they serve their purposes, they also add clutter and distractions to your reading experience.
Microsoft Edge's Reading view is a feature that removes the clutter from web pages for a distraction-free web reading experience, similar to reading a book.
Navigating Reading view tools
You know when to use this experience because the book button in the address bar will light up when you're on a website that supports this feature. Clicking the button will convert the page into a PDF document-style experience without any distracting elements.
As you start the experience, you'll notice the floating toolbar with tools available for Reading view.
On the right side, the Text flyout includes a number of options to change the text size, text spacing, and page color scheme.
Also, when using Reading view, you can click the Grammar Tools button to access features to help you better comprehend the content.
Using the tools, similar to the EPUB files, you can split words into syllables, and highlight all nouns, verbs, and adjectives.
If you want to print a web page as you see it in Reading view without clutter, simply click the Print button in the toolbar, select your preferences, and click the Print button.
For a completely distraction-free web reading experience, you can click the Full screen (F11) button available in the toolbar.
How to use Microsoft Edge read-aloud experience
The Microsoft Edge reading experience also includes a feature that allows the browser to read aloud text from PDF documents and forms, EPUB ebooks, and web pages in Reading view.
To hear text aloud, select the text, right-click the selection and use the Read aloud option. Alternatively, you can choose the text and click the Read Aloud button in the toolbar, or use the Ctrl + Shift + G keyboard shortcut to start hearing the words aloud.
When using this feature, a number of controls will be available to play and pause, or skip to the next or previous paragraph, and you can also click the Voice settings button to change the reading speed and voice.
How to set Microsoft Edge as your default reader experience
Microsoft Edge is your default reader on Windows 10 for PDFs and EPUBs, but if you're using different apps, you can set the browser as your default using these steps:
- Open Settings.
- Click on Apps.
- Click on Default apps.
- Click the Choose default apps by file type link.
- Click the app button next to .epub and choose Microsoft Edge.
- Click the app button next to .pdf and choose Microsoft Edge.
Wrapping things up
This guide outlines the steps to get started with the most interesting reading features available on Microsoft Edge in the April 2018 Update. If you want to know the specific Edge improvements added to the Windows 10 April 2018 Update, check out this guide with everything you need to know about the updated version of Edge.
Also, it's worth noting that there's technically only one reading experience on Microsoft Edge, but it adapts with specific tools depending on the content you're reading.
More Windows 10 resources
For more helpful articles, coverage, and answers to common questions about Windows 10, visit the following resources:
Cccam Error Reading Web Page Example
I am using
<error-page>
element in web.xml to specify the friendly error page when user encounters a certain error such as error with code of 404:However, I want that if the user does not meet any error code specified in
<error-page>
, he or she should see a default error page. How can I do that using the element in the web.xml?Community♦
Cccam Error Reading Web Page Template
ipkissipkiss5,6182525 gold badges7474 silver badges115115 bronze badges
3 Answers
On Servlet 3.0 or newer you could just specify
But as you're still on Servlet 2.5, there's no other way than specifying every common HTTP error individually. You need to figure which HTTP errors the enduser could possibly face. On a barebones webapp with for example the usage of HTTP authentication, having a disabled directory listing, using custom servlets and code which can possibly throw unhandled exceptions or does not have all methods implemented, then you'd like to set it for HTTP errors 401, 403, 500 and 503 respectively.
That should cover the most common ones.
Benny Neugebauer29.6k1717 gold badges155155 silver badges157157 bronze badges
BalusCBalusC874k309309 gold badges32293229 silver badges32713271 bronze badges
You can also do something like that:
For error code 403 it will return the page 403.html, and for any other error code it will return the page error.html.
GuyGuy
You can also specify
<error-page>
for exceptions using <exception-type>
, eg below:Or map a error code using
Aniket Sahrawat<error-code>
:Cccam Error Reading Web Page Examples
Aniket Sahrawat7,05022 gold badges1414 silver badges4141 bronze badges