SSRS 2016 SP1 CU3 List View Report Bug - by Nick Colebourn

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


29
0
Sign in
to vote
ID 3134731 Comments
Status Resolved Workarounds
Type Bug Repros 15
Opened 5/24/2017 3:32:00 AM
Access Restriction Public

Description

After applying SQL Server 2016 SP1 CU3 to a reporting services native mode instance, selecting any paginated report in "List View" results in the error message "Could not load folder contents" "The folder "report/reportpath" does not exist. IT could have been renamed, moved, or deleted." (where reportpath is the full report path).

Selecting the same report whilst in "Tile View" works fine and does not raise the error.

Removing SQL 2016 SP1 CU3 and reverting to SQL 2016 SP1 CU2 fixes the problem and the report loads correctly in both "Tile View" and "List View"

Sign in to post a comment.
Posted by neonite on 8/7/2017 at 4:32 PM
Moot point with the CU4 approaching, but if you change your browser emulation to IE 10, anything not edge or IE11, and the error goes away.
Posted by Microsoft on 7/17/2017 at 6:43 PM
Thanks for reporting this bug. We've fixed it in SQL Server 2016 SP1 CU4, which should be available by mid-August.
Posted by Dan English on 7/17/2017 at 8:34 AM
Wow, that is a pretty major bug. I always run my reports in Chrome, so never noticed this. I just tested in IE and definitely a bug when trying to run reports in List View compared to Tile View. Very odd...

So this means all of our users must be running this in Tile View still because they all use IE... haha, lucky.
Posted by RodVE on 7/12/2017 at 11:26 PM
Approaching two months since this bug was reported, its significant and I have 50+ users complaining about it. Lets see some action here Microsoft!
Posted by laureategroup-JM on 7/11/2017 at 10:32 PM
This is a pretty significant bug. When can we expect to see a fix??
Posted by DE.NY on 7/5/2017 at 8:38 AM
Is there any fix for this yet? It's been over 1 month and rather significant bug affecting basic functionality.
Posted by Justin Bird TGT on 6/9/2017 at 5:52 AM
This does occur in IE11, but doesn't happen in Chrome!