Error: 'nextElement' is null or not an object when asyncrendering = false
I upgraded 2005 reports to 2008 and updated the corresponding report viewer control in the Web site. Now some reports throw JavaScript errors when AsyncRendering=False. I can't set AsyncRndering to true since that introduces other problems. Does anyone know what the issues are with upgrading the Report Viewer control form 8 to 9 with this AsyncRendering attribute? The goal with that attribute is so the browser doesn't have two scrollbars. With that attribute set to true the result is a report with scrollbars inside of a Web page with scrollbars.
November 25th, 2009 12:16am

Hi usp,I have tried to reproduce the issue. However, everything works fine in SQL Server Reporting Services 2008 SP1.So, could you please update the SQL Server Reporting Services and the Report Viewer control to check if the issue is solved?SQL Server 2008 SP1: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=66ab3dbb-bf3e-4f46-9559-ccc6a4f9dc19Cumulative Update #5 for SQL Server 2008 Service Pack 1 Microsoft Report Viewer 2008 SP1 Redistributable: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=bb196d5d-76c2-4a0e-9458-267d22b6aac6Please feel free to ask, if you have any more questions.Thanks,Jin ChenJin Chen - MSFT
Free Windows Admin Tool Kit Click here and download it now
December 2nd, 2009 6:45am

I am using the most recent Report Viewer 2008 SP1 Redistributable and upgraded to Cumulative Update 5. Neither of those helped to fix the error. I am fairly certain this problem relates to a different feature of SSRS that does not work properly under 2008. That is the FixedColumnHeaders feature. I removed all the <FixedData>true</FixedData> and <FixedColumnHeaders>true</FixedColumnHeaders> in every report and the JavaScript errors went away. The fixed column feature does not work properly under SQL Server 2008 SP1 CU5 with Report Viewer 2008 SP1. I posted this problem in a separate thread since the error seemed to have more to do with that fixed header feature than with AsyncRendering.
December 6th, 2009 9:56pm

Same problem and also validated the problem with <FixedData> and/or <FixedColumnHeaders>. Once removed the 'nextElement' error dissappeared. Thanks for the post.
Free Windows Admin Tool Kit Click here and download it now
October 1st, 2010 6:29pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics