Let’s see some code now. Start by importing the System.Diagnostics namespace.
Server.GetLastError() is accessible only at two places – 1. Page_Error event handler of a page . 2. Application_Error event handler in the global.asax

In this article, we’ll trap the unhandled errors in Application_Error event.

Note in the above code, Server.ClearError() is commented. This brings the customErrors section of the web.config into play. Once the error occurs, the error is logged into the event log and then redirected to a custom error page. Therefore make sure the customErrors section of the web.config file has an entry like this

Continuing with the creation of Eventlog, create a sample page on your site to generate application error and then follow the below steps.

1.Open Regedt32.

2.Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\EventLog.

3.Add FULL permissions to ASPNET and Network services account.

4.Browse to the sample page and create application error.

5.This error should be logged in Eventlog as a new log - MyAppLog.

6.Once the log is created remove permissions to NetworkServices account in Event log. Network services account is needed only to create the log.

7.Repeat error again on the sample page. A new error should be logged in the event log.

8.Repeat from remote system(to test as non- admin user).

9.Check event log.

The only drawback to create to an application specific event log is that you need admin rights on the web server. If that’s not possible, you can send out an email or write to a log file on the server. Code to send email -

Having an application specific event log helps you to view all the errors in one shot and saves you the time of browsing the regular event log and searching errors for your site.

Reporting Services web service is the simplest way to meet the above requirements. The web service resides on your reporting server. The Web Service includes a ton of methods that enable you to read and manage the report server and its contents. Let me dive right into the implementation part.
1. Open Visual Studio, create a new website.
2. Add the web service reference to your application using Add Web Reference. The path of the web service would be http://reportservername/ReportServer/ReportService.asmx
Change the web reference name say ReportingService and click Add Web Reference. This name will become the namespace for the web service proxy.

Once the reference is added,open the web.config file. You’ll notice a new section has been added the web.config

3. Next, we need add reference to the Microsoft.ReportViewer.WebForms inorder to use the Report Viewer.Go to Website. Add Reference. Select
Microsoft.ReportViewer.WebForms. Click Add. This would add the Report Viewer to the toolbox and new sections to the web.config.

4. Now we move on to creating a new page and designing the layout of the page. Typically the design would be given by user group but in my case I had to create a layout and present it for approval. As I browsed the report manager, I realized that we had several folders and each folder had reports related to a department or task. I had to organize the reports in such a way it would be easy for novice users to use it without any help. I cannot list all the reports as that would show too many reports to the user (depending on their access level of course) and that can be overwhelming!! Therefore I decided to use 2 combo boxes, one to list the folders and the second to list the reports in each folder. I also have a Run Report button the page. User can select a report in the combo box and click Run Report. This would display the in a new window.

5. We start by including the Reporting Services namespace to the code behind file. Then create an instance of the ReportingService proxy class on the page load event. Pass the client login credentials.

ListChildren method requires 2 parameters. The first parameter is the path of the folder to look in and the second parameter is a flag to indicate if the method should recurse through subdirectories.
The method returns an array of catalogitem objects based on the user permissions. The catalog items can be reports,data sources,folders Once we get the array of catalog items, we loop through the array and read the properties of each catalogitem. A catalogitem properties give us information about the item like Name,Created By, Description, Path, Type etc. Here we mainly make use of the type and Name. If an item is of type “Folder” we add the item to combo box. Since we don’t want to show data sources folder to users, we check for the name “Data Sources” and ignore it.

6.The next method ListReports is written for SelectedIndexChanged event of the folders combobox which means when an item in the folders combobox is selected this event is fired. As the name suggests this method lists all the reports in the selected folder item. We pass the path of the selected folder as a parameter to the List Children method. This time we check if the Item.type is Report.

7. Now to run the report. This is a simple javascript function to open the report in a new window. Pass the path of the report the new window.

8. Our next task is to display the report on a web page. Start by creating a new page. Drag and drop the report viewer control from the toolbox. In the code behind file get the path of the selected report from the query string and set the path of the report viewer.

Deployment -Where to host?

The simplest way to deploy the application on your intranet is by hosting the site on the reporting server. When the application and the reporting server are on the same machine, enable impersonation in web config file. Doing so will pass the user credentials directly to the report server.

When the reporting server and web server are on different machines, Kerberos authenication protocol is required to pass the user credentails from web server to reporting server.

That’s about it. Creating a repository of reports is pretty straighforward using Reporting Services web service. I hope you’ll find this example useful.