Web Viewer NOT consistently loading in ASP.net 4.0 Site

marsh76 · Post by **marsh76** » Fri Jun 04, 2010 6:50 am

My company develops an ASP.net based business web portal that until recently ran on .net 3.5 SP1. Within the last month we upgraded the portal to run under .net 4.0.

Since cutting over to version 4.0 of the .net framework the web viewer does not consistently load medium to larger reports into IE browsers (that would be IE6, IE7, or IE8). In IE8 sometimes I'll have more luck than with IE6 or IE7, but frequently the Flash loader still is not loading into the browser. The only way I can get the flash based report viewer to load up in IE6 or IE7 is to load a near empty report (i.e. one or two page long report). Anything longer than a couple page report results in the entire flash component not loading. I'm trapping for all JS and code behind C# errors, and nothing is being captured into the logs, indicating the code loading all the elements onto the page continues to function properly. In fact, everything else expected on the page does load on these browsers (i.e. HTML header/footer/menu/etc.).

Furthermore, I've inspected the Event viewer on the Windows 2008 servers, where we've tested for this issue (we tested for this problem on four different Windows 2008 servers now, and all produced the same issue), and no IIS or other errors, warnings, or info messages are being logged at the time of the problem occurring.

An important point to note is that NOTHING has changed w/ the syntax of the ASP.net page hosting the web viewer or the C# code behind syntax loading the web viewer for our reports. Literally the only thing that has changed here is our use of the 4.0 version of the .net framework in place of the 3.5 SP1 version of the .net framework.

The file version for our Stimulsoft dll's in the bin folder of this portal is "2009.3.511.0". Are there known issues w/ the version we are using when used under ASP.net 4.0? Is anyone else having this problem? It is very perplexing as I'm getting nothing in our app logs or Window's event logs, and sometimes it works and other times it does not work.

Any help will be greatly appreciated.

(This was edited to clarify that the problem has been narrowed down to IE browsers only.)

Post by **Vladimir** » Mon Jun 07, 2010 1:43 am

Hello,

We need some time to check this problem.

Thank you.

marsh76 · Post by **marsh76** » Wed Jun 09, 2010 3:40 pm

Vladimir,

As this is a relatively urgent issue, I appreciate any help you can provide. Please let me know if there is more I could provide for you on this situation.

Matt

Post by **Vladimir** » Thu Jun 10, 2010 5:09 am

Hello,

We tested the Web Viewer in several modes under .NET 4.0, and found no errors. We tested versions 2009.3.500 and 2010.2.730. We recommend you upgrade to the latest prerelease build, because there were some changes to improve work with .NET 4.0

If it does not help, please send us your Web project for the analysis (or its part) to support[at]stimulsoft.com

Thank you.

marsh76 · Post by **marsh76** » Thu Jun 10, 2010 6:06 am

Vladimir,

Thank you for your feedback. We'll try the 2010.2.730 build and report back if it resolves our problem. We rolled back one of our test environments to .net 3.5 SP1 (our last used version) just as a sanity check, and sure enough it works right out of the box for us there. Maybe there will be something environmental, either w/ our development environment or implementation, but so far it is not clear.

As necessary we'll follow up with code blocks reflecting our implementation.

Thanks again for your time.
Matt

Post by **Vladimir** » Thu Jun 10, 2010 7:03 am

We will wait for the results of your tests.

Thank you.

marsh76 · Post by **marsh76** » Fri Jun 11, 2010 7:23 am

Vladimir,

We compiled a new build of our platform, integrating the latest release of the report writer from your end and it DID resolve our problem. In an effort to be comprehensive in our approach to testing this solution to our problem, we simply integrated the latest pre-release build from your site into the exact same code base that was experiencing the problem under the 2009.3.511.0 build we've been using up until now. And, as just indicated above, the problem is now resolved, and reports are displaying consistently in IE6, IE7, and IE8.

Thank you for your direction on this matter. You can consider the issue closed.

Regards,
Matt

Post by **Andrew** » Fri Jun 11, 2010 8:13 am

Thanks for letting us know!