Happy Holidays team!
I have a issue that has been very difficult to track.
I have a asp page that contains a number of WebDialogWindow controls (like fourteen I think). There are several standard asp buttons on the page that open these dialogs. These dialog controls are also contained in a number of update panels on the page.
The problem I am having is that on my development system, there is no problem. Everything works fine. However, sometimes on other computers that have not accessed the page before, clicking one of the buttons that is supposed to unhide a dialog will fail and nothing happens. Then if you close the browser and open it again to the same page and click the button once more it works fine and will continue to work from then on.
Further, if I then click another button to open another WebDialogWindow it will silently fail again until the browser is closed and then the page reloaded. After that then that button will also work correctly 100% of the time.
Once you follow this process and go through all the buttons on the page then everything will work fine but I can't realistically offer that up to my 1600+ users as a viable solution.
The only information I have on the problem is the following error reported by the browser when the button is clicked:
Message: Sys.WebForms.PageRequestManagerParserErrorException:The message received from the server could not be parsed.Common causes for this error are when the response is modified by calls toResponse.Write(), response filters, HttpModules, or server trace is enabled.Details: Error parsing near '<!DOCTYPE html PUBLI'.
I am wondering if you have any insight into what might be happening or at least point me in a direction to look.
I am working with NetAdvantage 11.1 ASP.NET CLR3x
Thanks for any advice!
Hi stevenhunter411,
Thank you for your reply.
Please feel free to contact me with any updates.
Hi Petar,
From what I have been reading about this control I suspect you are correct and the issue has to do with the boxes being inside the update panels.
It is unfortunate because I really like how it is working now and I dread having to tear the form apart to fix the issue as it is fairly complex but if there is no alternative then I will just have to do so.
As to the browser, no it doesn't seem to be specific. I have tested it with IE, Firefox and Chrome and have seen the issue on all three platforms.
I am working on another hot project at the moment but later this week I will work on this and let you know what happens.
Thanks for your input!
Thank you for posting in the community.
In this scenario placing the WebDialogWindows inside update panels may be the cause of your issues. If at all possible I would suggest testing your page with the DialogWindows outside panels in order to see if that helps. Setting the update mode of the UpdatePanels to Conditional and using your respective buttons' click event as asyncPostbackTriggers may also prove helpful. Any additional information such as whether the issue is browser specific would be greatly appreciated and would allow me to investigate the matter further.