Hi everyone, I not going to make any philosophic reflexions, neither make a thought about the BI business problems and the user’s point of view. What I show you this time, it’s a terrible issue that unfortunately, some people who works with Reporting Services maybe has encountered with. I posted a reference to what I found in the Internet in MSDN forums too. Just because it was freaking out our minds in a recently Project, I gave it more importance that it seems out there; however people affected are worried about and still needs a solution. The problem is an exception executing some reports deployed in Sharepoint Reporting Services Site. Some people post their cases in the next links showing that the issues were from a heterogeneous origin, and not deploying to Sharepoint only: http://www.bidn.com/blogs/DustinRyan/ssis/125/ssrs-2008-index-was-out-of-range-error http://www.developmentnow.com/g/115_2005_6_0_0_552665/Index-was-out-of-range–depending-on-parameters-.htm http://www.sql-server-performance.com/forum/threads/index-was-out-of-range-must-be-non-negative-and-less-than-the-size-of-the-collection-parameter-name-index.28619/ http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/973e3546-3f52-4d1e-b370-6af79a4c3c53/ The message we received was: An error occurred during client rendering. Index was out...