The following outlines how to use the Management Pack to resolve common ASP.NET application and web service exception and performance problems.
Application exception alerts result from unhandled and top-level ASP.NET exceptions that prevent the application from completing a task. The alert details display the type of exception thrown and the resulting call stack. Some exceptions, such as System.DllNotFoundException, System.OutOfMemoryException, or System.IO.DirectoryNotFoundException are due to problems with system resources, and can be resolved without having to make any changes to the web application. Other exceptions, such as System.IndexOutOfRangeException, System.ArithmeticException or System.ArrayTypeMismatchException are due to actual errors in the application code, and require analyzing the stack trace and data values used in functions.
Critical ASP.NET application exception alerts arise from unhandled exceptions. To resolve these exceptions, check the exception type and the function that the exception was thrown from. The following is a list of typical exception types and suggested resolutions:
Common Connectivity Exceptions
| Exception Type | Resolution |
| System.Configuration | Check the property settings in the web.config file. |
| System.Data.Odbc.OdbcException, System.Data.SqlClient.SqlException, System.NET.WebException | Verify the validity of connection string in web.config. the remote port settings in IIS, server timeout settings and the remote server status. |
| System.IO.FileNotFoundException | If the file name is not visible in the exception details, enable the AVIcode Management Pack. |
Common Security Exceptions
| Exception Type | Resolution |
| System.Security, System.UnauthorizedAccessException | Check the Windows Security event log for other errors, access rights on the application pool identity account, and the access control list (ACL) file authorizations. |
| System.Data.Odbc.OdbcException, System.Data.SqlClient.SqlException, System.NET.WebException | Verify the validity of connection string in web.config. the remote port settings in IIS, server timeout settings and the remote server status. |
| System.IO.FileNotFoundException | If the file name is not visible in the exception details, enable the AVIcode Management Pack. |
Exceptions Returned from Externally Hosted Web Services
| Exception Type | Resolution |
| Error from external web service | Contact the remote vendor for assistance; for local Web Services, enable .NET monitoring for the service to capture exception information. To get runtime information about Web Service calls and to correlate events between multiple tiers, enable the AVIcode Management Pack. |
Miscellaneous Exceptions
| Exception Type | Resolution |
| System.EntryPointNotFoundException, System.MissingMemberException, System.Data.DataException | Investigate the call stack for information that identifies the problem. If additional information is needed (values for parameters, or member variables and source code information), then enable the AVIcode Management Pack. |
Critical application exception alerts result from unhandled and top-level ASP.NET exceptions, and for ASP.NET exceptions result in the user seeing the standard error page. Alert details for critical exceptions display the exception chain, exception details, and the resulting call stack.
Application performance alerts are generated when the execution time for the ProcessRequest() function in a page exceeds the configured alerting threshold. The alert details break down the execution time by percentage spent in various types of resource call and for internal code execution. Excessively long SQL, Oracle, Sybase, ODBC, or OLEDB calls may be due to either a problem with the database server or the structure and complexity of the database query. Long file I/O times may be due to problems with the file server. Web Services performance issues may occur because the web service or the server it resides on is down, or there is a problem in the Web Service code. Long internal execution times for applications may result from complex code or Remoting calls to other slow processes.
ASP.NET application performance alerts are generated when the execution time for the ProcessRequest() function in a page exceeds the configured threshold. The following is a list of typical application performance degradations and suggested resolutions:
Common Performance Degradations
| Exception Type | Resolution |
| Long Database Calls | Check the database server for issues affecting response times (memory, disk space). If the problem is not server related, the AVIcode Management Pack can be used to identify the exact query associated with the slowdown. |
| Long File I/O Times | Check the event log on the file server for errors affecting response time. |
| Long-running Web Services calls | For externally hosted services, contact the remote vendor for assistance; for local Web Services, check the server for issues affecting response times, and enable the .NET monitoring for the service. To get runtime information about Web Service calls and to correlate events between multiple tiers, enable the AVIcode Management Pack. |
| Long Internal Execution times | Use the AVIcode Management Pack to pinpoint the slow functions and monitor .NET Remoting calls. |
ASP.NET Application performance alerts are generated when the execution time for the ProcessRequest() function in a page exceeds the configured threshold. The alert details break down the execution time into percentages spent in various resource calls (e.g. calls to SQL, Oracle, Sybase, ODBC, OLEDB, or Web Services, file I/O) and for internal code execution. The alert details aid in determining the cause of the slow down. Additional details may be collected by installing the AVIcode .NET MP.
Web Service exception alerts result from unhandled exceptions that prevent the web service from completing a task. The alert details display the type of exception thrown and the resulting call stack. Some exceptions, such as System.DllNotFoundException, System.OutOfMemoryException, or System.IO. DirectoryNotFoundException are due to problems with system resources, and can be resolved without having to make any changes to the web application. Other exceptions, such as System.IndexOutOfRangeException, System.ArithmeticException or System.ArrayTypeMismatchException are due to actual errors in the application code, and require analyzing the stack trace and data values used in functions.
Critical web service exception alerts arise from unhandled exceptions. To resolve these exceptions, check the exception type and the function that the exception was thrown from. A list of typical exception types and resolutions is listed below:
Common Connectivity Exceptions
| Exception Type | Resolution |
| System.Configuration | Check the property settings in the web.config file. |
| System.Data.Odbc.OdbcException, System.Data.SqlClient.SqlException, System.NET.WebException | Verify the validity of connection string in web.config. the remote port settings in IIS, server timeout settings and the remote server status. |
| System.IO.FileNotFoundException | If the file name is not visible in the exception details, enable the AVIcode Management Pack |
Common Security Exceptions
| Exception Type | Resolution |
| System.Security, System.UnauthorizedAccessException | Check the Windows Security event log for other errors, access rights on the application pool identity account, and the access control list (ACL) file authorizations. |
Exceptions Returned from Externally Hosted Web Services
| Exception Type | Resolution |
| Error from external web service | Contact the remote vendor for assistance; for local Web Services, enable .NET monitoring for the service to capture exception information. To get runtime information about Web Service calls and to correlate events between multiple tiers, enable the AVIcode Management Pack. |
Miscellaneous Exceptions
| Exception Type | Resolution |
| System.EntryPointNotFoundException, System.MissingMemberException, System.Data.DataException | Investigate the call stack for information that identifies the problem. If additional information is needed (values for parameters or member variables and source code information), then enable the AVIcode Management Pack. |
Critical web service exception alerts result from unhandled exceptions. Alert details for critical exceptions display the exception chain, exception details, and the resulting call stack.
Web Service performance alerts are generated when the execution time for the web service method exceeds the configured alerting threshold. The alert details break down the execution time by percentage spent in various types of resource call and for internal code execution. Excessively long SQL, Oracle, Sybase, ODBC, or OLEDB calls may be due to either a problem with the database server or the structure and complexity of the database query. Long file I/O times may be due to problems with the file server. Long internal execution times for web services may result from complex code or Remoting calls to other slow processes.
Web Service performance alerts are generated when the execution time for the ProcessRequest() function exceeds the configured threshold. The following is a list of typical performance degradations and suggestions for their resolution:
Common Performance Degradations
| Exception Type | Resolution |
| Long Database Calls | Check the database server for issues affecting response times (memory, disk space). If the problem is not server related, the AVIcode Management Pack can be used to identify the exact query associated with the slowdown. |
| Long File I/O Times | Check the event log on the file server for errors affecting response time. |
| Long-running Web Services calls | For externally hosted services, contact the remote vendor for assistance; for local Web Services, check the server for issues affecting response times, and enable the .NET monitoring for the service. To get runtime information about Web Service calls and to correlate events between multiple tiers, enable the AVIcode Management Pack. |
| Long Internal Execution times | Use the AVIcode Management Pack to pinpoint the slow functions and monitor .NET Remoting calls. |
Web Service performance alerts are generated when the execution time for the web service method exceeds the configured alerting threshold. The alert details break down the execution time by percentage spent in various types of resource call (e.g. calls to SQL, Oracle, Sybase, ODBC, or OLEDB, file I/O) and for internal code execution. The alert details aid in determining the cause of the slow down. Additional details may be collected by installing the AVIcode .NET MP.
Last update: Monday, November 29, 2010 05:45:53 PM