Intersoft Community - WebGrid Enterprise - Unhandled Exception dialog

Unhandled Exception dialog

yudi — Wed, 10 Feb 2010 03:41:35 GMT

Per your instruction, I was able to repro the issue using CollectInput.aspx tutorial file in WebGridTutorial project. This minor issue has been forwarded to WebGrid development team. A work item, work item #601, has been submitted regarding this minor glitch.

We’re greatly appreciating this valuable feedback of error handling in WebGrid 7. I’ll let you know any news I heard from the team regarding this work item.

Thank you very much.

Unhandled Exception dialog

John.Bonin@dot.gov — Tue, 09 Feb 2010 08:43:00 GMT

Hi,

I found out what the problem is and you can see the problem with the samples that come with R2 and is not specific to my project.

The problem is the DocType. Using the sample called "CollectInput" in WebGridTutorials in the V3.5 directory, if you do the following you will see the problem:

1. In the code behind file change the SQL statement so that an error occurs (I changed the table name to customers2).

2. Change the DocType in the aspx file to:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >

Then open the page in a browser and click on the GetRecords button.  Notice that the Error Dialog has no buttons and no X to close the dialog.  There is no way to get back past the error dialog and returnr back to the main page.

I know in the past using the XHTML DocType was not supported but I thought it was with R2?

John

Unhandled Exception dialog

yudi — Tue, 09 Feb 2010 04:02:00 GMT

I have made a test page by using the settings applied in your attached page and was unable to repro the issue.
Could you please enclose ‘MedExDev.master’ master page file?

Please try to put the grid outside the ‘MedExDev.master’ master page file and let me know whether the issue still persists or not?

*Edited reason: add the last sentence asks to check whether the issue happen if not using the master page file

Unhandled Exception dialog

John.Bonin@dot.gov — Mon, 08 Feb 2010 13:48:18 GMT

I can't get a simple sample and it works fine using the samples, but with my project it doesn't. I did notice that all the text is centered, so wondering if maybe a style is in conflict. I am also using jQuery. I have attached the actual page with the webGrid attached.

Unhandled Exception dialog

yudi — Mon, 08 Feb 2010 02:39:12 GMT

I was unable to reproduce your issue on my end.

Could you please kindly send us a running simple sample that replicates the issue? If it is not possible to send a running simple sample, is it possible for you to send the structure of your page for further investigation?

Look forward for your response.

Unhandled Exception dialog

John.Bonin@dot.gov — Fri, 05 Feb 2010 07:27:17 GMT

Thanks.. but my windows don't have any buttons. The bottom of the page is blank, See attached. Is there a way to change the size of the error popup window?

Unhandled Exception dialog

yudi — Fri, 05 Feb 2010 01:22:53 GMT

Actually there is a button to close the “Unable to communicate with server” error GUI. I enclosed a screenshot of the error GUI in a smaller window size (so that the close button is visible). In your case, it seems that you need to scroll down the page in order to have the close button visible.

“Unable to communicate with server.” error will returns empty string in OnUnhandledError client side event. I suggest you to use following conditional statement in order to handle the error.

<script type="text/javascript">
    <!--
    function WebGrid1_OnUnhandledError(controlId, action, lastRequestObject, errorString) {
        var WebGrid1 = ISGetObject(controlId);

        if (errorString == "") {
            // Put your error handling script in here.
        }

        return true;
    }
    -->
</script>

About the tblName parameter in OnUnhandledError client side event that shows lastRequestObject instead of table name, the correct variable for this parameter should be ‘action’. I have discussed this with WebGrid development team and they agree to fix this. The fix should be available in the upcoming build of WebGrid 7.

Hope this helps.

Unhandled Exception dialog

John.Bonin@dot.gov — Thu, 04 Feb 2010 08:40:03 GMT

Hi,

I am aware of the OnUnhandledError event, but that is not what I was mentioning. The problem is if you don't use that event then the default dialog that is presented to the user from the webUI Grid has no way to close the modal dialog, this confuses users to no end. Attached is a screen shot of the dialog and no buttons.

Now since you did mention the OnUnhandledError event there is problems with it in that the errorString is an empty string so you have no idea what the error is? Also the tblName is not the table name but the FlyPostBackEvent, in my case Refresh and the lastRequestObject is always null. This makes using this event a little difficult.

Without the errorString, I have no idea if it a session timeout, expired login token or even an Oracle database error!

Unhandled Exception dialog

yudi — Wed, 03 Feb 2010 22:22:35 GMT

We already have an error handling for flypostback event in WebGrid during client side event.

If the flypostback event is triggered by WebGrid you could try implementing OnUnhandledError(controlId, tblName, lastRequestObject, errorString) to handle the timeout session exception.

<script type="text/javascript">
    <!--
    function WebGrid1_OnUnhandledError(controlId, tblName, lastRequestObject, errorString) {
        var WebGrid1 = ISGetObject(controlId);

        return true;
    }
    -->
</script>

This should help.

Unhandled Exception dialog

John.Bonin@dot.gov — Wed, 03 Feb 2010 07:56:34 GMT

Hi,

With webGrid 7 I noticed that when there is an unhandled exception the client side dialog that displays has no buttons to close the window. Since it's a modal window the user is stuck, yes they can use the back button but most users have no idea and they call the help desk!

Am I missing something?

John

NOTE: I am using a html button to get values from the user and using the client way to get the records as in your sample GetRecords (I think that the name). The error is Unable to Communicate with server, it occurs because the user session has expired.