Microsoft application error reporting how to enable

MICROSOFT APPLICATION ERROR REPORTING HOW TO ENABLE UPDATE
MICROSOFT APPLICATION ERROR REPORTING HOW TO ENABLE CODE

You can keep ReportServer unchanged if you use the default configurations. Then run the below command after you have replaced the ReportServerName with the actual name of the Reporting Services server you want to configure and the ReportServer instance name. Open the command promt window by running the 'cmd' command in the 'Run' box. I chosed C drive to keep it easy to run the below command promt statement. Of course you can select an other name for the script file name and an other folder to save your script.

MICROSOFT APPLICATION ERROR REPORTING HOW TO ENABLE CODE

And this method successfully worked for my case.Д¬onsole.WriteLine('Remote errors enabled.')Д¬opy the above script code in an empty text file and as the script file as EnableRemoteErrors.rss on the root folder of your C drive. I chosed this method for solution in my problem.

MICROSOFT APPLICATION ERROR REPORTING HOW TO ENABLE UPDATE

The codes of the script that will update configuration values for EnableRemoteErrors is given in the SQL Server 2005 Books Online. Second way to enable remote errors is using and running a script which updates the running configuration values of the Reporting Services. You can simply run an update sql statement to enable remote errors.Д«ut you may not be successfull to see the changes made on the ConfigurationInfo table on the Reporting Services application, if the application is being used intensely.Д®nable EnableRemoteErrors property though running a script The default value for EnableRemoteErrors property in the ConfigurationInfo database table is 'False'. Update ReportServer database Configuration table for EnableRemoteErrorsДЇirst way is updating the ConfigurationInfo table which is in the ReportServer database for configuration record named 'EnableRemoteErrors'. There are two ways to set the EnableRemoteErrors property to True for a Reporting Services instance. I decided to enable remote errors on the web server where the Reporting Services instance is running to see additional error information for troubleshooting the problem I experienced.Д®nabling remote errors for SQL Server Reporting Services means setting EnableRemoteErrors Reporting Services system property to True The only information about the error is displayed as 'For more information about this error, navigate to the report server on the local server machine, or enable remote errors.'Д«ecause I had to deploy the current version of the application I'm developing on the test server which was not possible at that time, I chosed the second way to see more detailed information about the reporting services error. Only if you are running the Reporting Services application on the IIS server which hosts the Reports or ReportServer virtual directories, you can then see the detailed error information on the page that the error has occured. Since the SQL Server 2005 Reporting Services application is not my local computer, I was not able to see the error or exception information thrown by the Reporting Services.Д«ecause for security reasons displayin errors to remote computers is disabled by default.

Recently, while working on a custom report viewer page which includes the ReportViewer web control, I had to run the application in debug mode and connect to a test Reporting Services server.

I'm developing a web application which is using Microsoft SQL Server Reporting Services and ASP.NET ReportViewer component in order to display reports on the web pages. How to Enable Remote Errors for SQL Server Reporting Services

Microsoft application error reporting how to enable