Using the Log Viewer in .NET

Generation QR Code in .NET Using the Log Viewer

The Log Viewer is configured by default to record whenever a particular event happens in your Web site When you go to the Log Viewer, you will see a list of ten events most recently recorded Lots of events get recorded by the

Log Viewer and you can look through them by clicking the page number buttons on the bottom right of the screen (refer to Figure 10-9) As a regular maintenance task, you should delete unneeded events to keep the log size down You can delete selected items by clicking the Delete Selected Exceptions button or you can delete them all by clicking Clear Log Another way to look quickly through the Log Viewer is to change the number in the Records Per Page text box to a higher value If you select 100, you will see 100 records per page If you do this, be aware that the page will take longer to load depending on your Internet connection speed If you are logged in as a superuser, you will also see a drop-down list called Portal Superusers are allowed to see the events created by any of the Web sites that have been set up by any user, and the Portal drop-down list allows you to select the events from a specific Web site The default selection is All, which shows you the exceptions from all the Web sites at once Simply select the name of the site from the drop-down list to narrow down the list of events

Whereas the Site Log lets you see who is on your Web site and where they went and when they went there, the Log Viewer gives you even more details With the Log Viewer, you can see when a user logged in successfully and also when they tried to log in but failed This is useful for spotting when users are trying to hack into your Web site because it records the IP address of the computer making the attempt, which you can later use to track the offender if need be To easily see the failed login attempts, simply select Login Failure from the Type drop-down list One of the great things about DotNetNuke is that it enables you to do many tasks that would normally require a system Administrator In the Dark Ages before DotNetNuke, if something went wrong with your site, your users would get a nasty error page with some cryptic message that was of no use to you They would ring you up to tell you your site was broken, but when you asked them what was wrong, they could only repeat a cryptic message that told you nothing With DotNetNuke, on the other hand, your site is still displayed, and only the one module that has a problem shows an error message saying that the module is not available Now for the extra-cool part: Not only did DotNetNuke fail gracefully, but it also recorded everything about the failure that the technical support person will need to fix it If the failure is from a module, DNN creates a Module Load Exception in the Log Viewer You don t need to write anything down when your user rings you up and says that one of the modules on your site is showing an error: Simply say Thanks, and go to the Log Viewer to look for any Module Load Exceptions After you ve found the list of exceptions (or errors), you can send them to your technical support person In Figure 10-10, you can see the message window that makes it very easy for you to get help with technical problems To see this window, click the plus sign next to Send Exceptions To send the exceptions to your technical support person, simply select the check box next to each of the items you want to send, enter the tech support e-mail address, and write a friendly message about the problems you are experiencing Click Send Selected Exceptions and you re done Your support team will now have all the information they need to solve the problem and get your site running perfectly again