[Expand]General Information
[Expand]WinForms Controls
[Collapse]ASP.NET Controls and MVC Extensions
 [Expand]What's Installed
 [Collapse]Common Concepts
  [Expand]Web.config Modifications
  [Collapse]Callback Exception Handling
    Displaying Message Texts for Callback Errors
    Handling Callback Exceptions on Server
    Response Redirection on Callback Exceptions
    Handling Callback Exceptions on Client
  [Expand]Client-Side Functionality
  [Expand]Cookies Support
  [Expand]Appearance Customization - Theming
   Icon Collection
  [Expand]Performance Optimization
  [Expand]CSS Image Sprites
   Data Annotation Attributes
   Supported Document Types
  [Expand]Accessibility Support
   Right to Left Support
   HTML Encoding
  [Expand]SharePoint Support
   Mobile Support
  [Expand]Office Document Management
   Cloud Storage Account Management
  [Expand]Web Farm and Web Garden Support
 [Expand]ASP.NET WebForms Controls
 [Expand]ASP.NET MVC Extensions
 [Expand]Redistribution and Deployment
  Get More Help
 [Expand]API Reference
[Expand]ASP.NET Bootstrap Controls
[Expand]ASP.NET Core Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Office File API
[Expand]Report and Dashboard Server
[Expand]eXpressApp Framework
[Expand]eXpress Persistent Objects
[Expand]CodeRush Classic
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation
View this topic on docs.devexpress.com (Learn more)

Callback Exception Handling

Typically, when a callback sent by a web control is processed on the server side and an unhandled server error occurs, the web application becomes unresponsive to the end-user (i.e., it crashes or hangs in the client's browser). DevExpress ASP.NET controls implement a built-in callback error-handling mechanism, which enables a web application to remain responsive in this case.

The ASPxHttpHandlerModule provides this error-handling mechanism, which catches unhandled server exceptions that occur during callback processing. The module generates and sends a specific response that contains exception-related information, to prevent the application from remaining in an unresponsive state.

By default, error messages are displayed within a browser based on the callback initiator (a DevExpress web control or an external control). An AJAX-enabled DevExpress web control shows error information within its embedded UI element, whereas an external control displays error details within a popup message box.

The error message content to be sent to remote clients depends on the customErrors mode setting defined in web.config. Before the message is sent to a client, you can modify it with a DevExpress API. See the following topic to learn more:

The following common callback error handling-scenarios are allowed:

Is this topic helpful?​​​​​​​