Prev: Subscription Ax data method provider
Next: SQL Reporting Services 2005 Report Parameters
From: sheckyd on 11 Nov 2009 17:48
Hi,
Server specs: Windows Server 2003 SP2, R2; SSRS 2005 SP 3

I have a ssrs report that has one parameter, Company, presented as a drop
down box. User selects a company, and runs the report, it works great!


Now, there are 235 companies in the drop down box.....
So instead of the users running it manually for each Company, I wrote a .NET
app that once a month, loops through each company that would be in the drop
down box and calls the SSRS report and saves the PDF output to a folder.
The .NET app uses SSRS's web services feature.

So, essentially .NET calls the report 235 times, each time passing in a
different Company ID as a parameter.

It works, sometimes, sort of.

The issue is, it gets through more than half of Companies, spitting out PDF
files, then it starts failing. But it doesn't always start failing at the
same row # in the loop, it fails at random row #'s.

Once I see it start failing, if I use IE to go to ssrs, I get general
errors, or I sometimes get:
"An unexpected error occurred in Report Processing. (rsInternalError) Get
Online Help The server failed to resume the transaction. Desc:47000003dd. The
transaction active in this session has been committed or aborted by another
session."

Has anyone experience any performance limitations with SSRS in calling it
programatically very quickly over and over? I put a 5 second delay in
between each call to space out the load on the server but it didn't help.
I think calling it in rapid succession is hosing SSRS.

If anyone else has tried something like this, let me know if you have
experienced the same or have any suggestions.
I can post code sample if needed.
Thanks,
Sean
 | 
Pages: 1
Prev: Subscription Ax data method provider
Next: SQL Reporting Services 2005 Report Parameters