Hi All, When we try running a report for 10 concurrent users, we are facing blocking. i.e. till the execution for 1st user is complete, 2nd user's execution doesn't work. We ran profiler to get some insight. How do we handle such thing to avoid blocking. Thanks. -Nitin Pawar

Please refer below link http://www.bigresource.com/Tracker/Track-ms_sql-aLv7Dkl4/Nanda

This doen't help my cause. My reprot runs fast when tested on 1 user. However when 10 concurrent users are accessign the same report, it gets blocked by the user who first executed it. Once his execution is complete, then 2nd person's execution starts. So, instead of rendering in few seconds, it takes 15 mins.-Nitin Pawar

I believe, I have found the answer after a day's research. This seems to be a bug in SSRS, which has been registered at following link. https://connect.microsoft.com/SQLServer/feedback/details/635140/ssrs-creating-lock-timeouts-in-reportservertempdb-when-using-mdx-with-parameters?wa=wsignin1.0 Excerpt from the link: Some interesting facts: 1. This only occurs if there is a SSAS connection and one or more Parms. Even with one parm that does not select MDX (it gets SQL Server data) a lock timeout still occurs. 2. If run thru BIDS (which does not use Report Server) the report runs very fast and there is no locking 3. If a report only has SQL Server connections no matter the number of parameters it is very fast and there is no locking (I can run a similar report against the underlying data warehouse). 4. If a report is run with a SSAS connection with NO parameters it runs very fast and no locking occurs. -Nitin Pawar