Hi,
I am trying to track down an error I am experiencing with large data sets being passed back to my Silverlight ReportViewer. I can't really tell what exception I am receiving, because the message that gets displayed in the ReportViewer says to look at the InnerException, which I have no access to.
I think this may be related to my binding setup (message size, timeout, etc.). I have already gone through the steps listed on the forum for creating a custom ClientFactory, and configured these binding properties following that documentation. I have also configured the ReportService binding server-side to have increased timeouts and message sizes.
In addition, I have even tried setting breakpoints in the async completed events to check the Error property (LoadPage, Render, RenderAndCache, etc.) When my error occurs, it doesn't fire the async completed event.
Currently, I have a WCF trace set up to see if I can hunt down the exception, but I'm having trouble interpreting the data in the trace. Is there anything else I can be doing to trap the error in the ReportService, so I can know exactly what is going wrong?
Thanks,
Rob
I am trying to track down an error I am experiencing with large data sets being passed back to my Silverlight ReportViewer. I can't really tell what exception I am receiving, because the message that gets displayed in the ReportViewer says to look at the InnerException, which I have no access to.
I think this may be related to my binding setup (message size, timeout, etc.). I have already gone through the steps listed on the forum for creating a custom ClientFactory, and configured these binding properties following that documentation. I have also configured the ReportService binding server-side to have increased timeouts and message sizes.
In addition, I have even tried setting breakpoints in the async completed events to check the Error property (LoadPage, Render, RenderAndCache, etc.) When my error occurs, it doesn't fire the async completed event.
Currently, I have a WCF trace set up to see if I can hunt down the exception, but I'm having trouble interpreting the data in the trace. Is there anything else I can be doing to trap the error in the ReportService, so I can know exactly what is going wrong?
Thanks,
Rob