Hi Dave,

Since errors/exceptions within async postback which was triggered by CallBackManager (used for WARP and UltraWebTab) in most cases do not belong to a particular WARP or UltraWebTab, the error handling on server is static. The CallBackManager has public methods Add/RemoveErrorHandler.

Errors also can be processed on client using ClientSideEvents.Error property (javascript for that handler can be generated by WARP automatically at visual design).

Below is example for both those handlers.

aspx:

<script type="text/javascript">
function WebAsyncRefreshPanel1_Error(oPanel, oEvent, flags)
{
 alert('flag:' + flags + '\nserverError:' + ig_shared.getCBManager().serverError);
}
</script>
<igmisc:WebAsyncRefreshPanel ID="WebAsyncRefreshPanel1" runat="server" ClientError="WebAsyncRefreshPanel1_Error">
</igmisc:WebAsyncRefreshPanel>

vb:

Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
 Infragistics.WebUI.Shared.CallBackManager.AddErrorHandler(Me, AddressOf Me.OnWarpError)
End Sub

Protected Sub OnWarpError(ByVal sender As Object, ByVal e As UnhandledExceptionEventArgs)
  Dim ex As Object = e.ExceptionObject
  If (e.IsTerminating = True) Then
   ex = "Error will trigger full post back on client."
  End If
End Sub