SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSRS report deadlock


SSRS report deadlock

Author
Message
Rob Taylor
Rob Taylor
Hall of Fame
Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)

Group: General Forum Members
Points: 3928 Visits: 1616
This only seems to happen when the server is busy; I run an SSRS report and it returns:

• An error has occurred during report processing. (rsProcessingAborted)
o Cannot read the next data row for the dataset dsCustomerList. (rsErrorReadingNextDataRow)
 For more information about this error navigate to the report server on the local server machine, or enable remote errors



So I talk with IT, they enable remote errors and when I run the SSRS report again, I get the error:

An error has occurred during report processing. (rsProcessingAborted)
Cannot read the next data row for the dataset dsCustomerList. (rsErrorReadingNextDataRow)
Transaction (Process ID 283) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.




I can run the exact same SQL query the report uses in SSMS and the query comes back in 20-45 seconds. Am I wrong in thinking that this is a SSRS problem and not in the query?

Is this a SSRS problem? or a DB problem? Do I need to look into DB deadlocks?

Any help appreciated.

Thanks,
Rob
Rob Taylor
Rob Taylor
Hall of Fame
Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)

Group: General Forum Members
Points: 3928 Visits: 1616
Turns out the problem was in the db and I was able to recreate the blocking/deadlock with the query in SSMS (though it happened far less than when run through SSRS). A little tuning seems to fixed the issue.

Rob
jswanson08
jswanson08
SSC Rookie
SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)

Group: General Forum Members
Points: 27 Visits: 124
Wow, I must be the only one with this problem. With in-line T-SQL the SSRS report runs in 30 seconds but the report with same SQL in a Stored Proc has deadlocks which max out the processors and run in more than 5 minutes.

Why does SSRS have deadlocks with no other reports running?
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search