Hello,
We recently upgraded the reports to the Q2 2013 release in a project that was previously using Q1 2011. We carried out this update in our local and development environments without issue. However, in the production environment, we experienced some issues that did not come up in our other environments. The reports render fine if they are generated from code and sent to the browser, but, if they are generated using the report viewer control, the report structure renders (fields on the form show up in the correct place, and default values for fields, set in the designer.cs file, render, see screenshot here: http://screencast.com/t/CJKr3kWBntgk) but there is no data being loaded into the form. This persists when we export the report from the report viewer, exporting a report that has no data. This behavior occurs for every report in the system.
I introduced some logging into one of the reports, and reviewed the differences between one that is generated in the report viewer versus one that is generated in the code and output to the browser. There are about 3 times as many entries in the working report as the non working report. At first, I thought the NeedsDataSource event for the report may not be firing, but, it seems to be called in both cases. I've noticed that the detail_itemDataBound event is not getting called, nor are the NeedsDataSource events for my tables in my report.
I would expect the report to fail in both places, if it was something with the report. It seems like this is environment dependent. There is nothing in the Event Viewer which suggests there is an issue here. Could this be related to our .NET version on our production server (we only have 4.0 on production, while in development we have 4.5.)? Has anyone run into similar issues? Any suggestions?
Thanks,
Travis
We recently upgraded the reports to the Q2 2013 release in a project that was previously using Q1 2011. We carried out this update in our local and development environments without issue. However, in the production environment, we experienced some issues that did not come up in our other environments. The reports render fine if they are generated from code and sent to the browser, but, if they are generated using the report viewer control, the report structure renders (fields on the form show up in the correct place, and default values for fields, set in the designer.cs file, render, see screenshot here: http://screencast.com/t/CJKr3kWBntgk) but there is no data being loaded into the form. This persists when we export the report from the report viewer, exporting a report that has no data. This behavior occurs for every report in the system.
I introduced some logging into one of the reports, and reviewed the differences between one that is generated in the report viewer versus one that is generated in the code and output to the browser. There are about 3 times as many entries in the working report as the non working report. At first, I thought the NeedsDataSource event for the report may not be firing, but, it seems to be called in both cases. I've noticed that the detail_itemDataBound event is not getting called, nor are the NeedsDataSource events for my tables in my report.
I would expect the report to fail in both places, if it was something with the report. It seems like this is environment dependent. There is nothing in the Event Viewer which suggests there is an issue here. Could this be related to our .NET version on our production server (we only have 4.0 on production, while in development we have 4.5.)? Has anyone run into similar issues? Any suggestions?
Thanks,
Travis