February 10, 2012  
   Login  
Forum  
 
ForumForumEnesys RS Data ...Enesys RS Data ...Support - RS Da...Support - RS Da...Problem with Problem with 'big' reports and pdf rendering
Previous Previous
 
Next Next
New Post
 5/7/2009 11:43 AM
 

Hi,

I have been using the trial version and it looks very promissing. Small reports work just fine but I have one report with 3 sub reports which generates a 240 page report (or it should). Sometimes the report does not complete.either with a time out error or an unexpected error.

If I restrict the output (e.g. 39 pages), the web report shows up fine but an export to PDF returns an 'unexpected error has occurred' message. Export to Excel works (but is not very useful with subreports), so does CSV/XML.

Any help on this would be appreciated. This is a showstopper for us.

Regards,
Kees

New Post
 5/7/2009 12:24 PM
 

Hi,

Not sure if it is the cause of the issue you are facing but we are releasing version 3.1 in a couple of hours.

Amongst other things, this new version includes some changes for handling large lists.

I propose that you upgrade once the release is available.

If you still encounter any problem afterward, we could investigate your issue.

In the meantime, would you mind sending us (to our support address) the queries you are using for your reports?

Regards


Frederic LATOUR
ENESYS
New Post
 5/7/2009 6:23 PM
 

Hi,

Thanks for the quick response. I have downloaded the 3.1 version and installed it over the existing one. The improvements are marginally (in my particular case). I still get 'an unexpected error has occurred' when opening the big report. Using a subset (39 pages) works in SharePoint, the full set fails (106 pages). Rendering to PDF still fails, even for the subset. The CPU load goes to 50% (on a dual core system with 2GB).

Is there a way to check that the new version is used? I assume so but independent confirmation would be nice. Did you receive my email with the queries?

Regards,
Kees

New Post
 5/7/2009 6:50 PM
 


By running ERSDE Server Configuration tool on your server, you should know the exact version installed.

image

If your server is not updated (granting that you have run our 3.1 installation package on your server), you will be propose to do so.

I have indeed received your email. Thanks.

It doesn’t look like you are dealing with large lists (therefore, version 3.1 will not help in that respect). My assumption is that the problem has something to do with sub reports. To tell the truth, unless for aggregating unrelated reports together we generally avoid sub reports (they do not perform very well and have some bugs reported).

I’m wondering about your report architecture. Are you using sub-reports as a way to link related data together? Any specific reason why you would not use a single query?

Regards,


Frederic LATOUR
ENESYS
New Post
 5/8/2009 9:18 AM
 

Hi,

I ran the configuration tools (both client and server) and both report the new 3.1.229.2308 version. I can imagine that using subreports would be less efficient but I have 1 parent table with details in 3 child tables which have nothing in common with each other (but, of course, share the primary key of the parent table. Could you suggest a different approach to this problem?

Regards,
Kees

New Post
 5/8/2009 3:32 PM
 
 Modified By Marien Monnier  on 5/8/2009 2:35:28 PM

Hi Kees,

If they share the primary key of the parent table, you can use a sqlQuery statement to join the different tables.

For more information, you can look at these articles:
- http://www.enesyssoftware.com/Products/EnesysRSDataExtension/KBandSamples/tabid/93/EntryID/56/language/en-US/Default.aspx
- http://www.enesyssoftware.com/Products/EnesysRSDataExtension/Features/tabid/73/language/en-US/Default.aspx#Apply_operations_to_listsOverview

Don't hesitate if you need more information.

Regards,
Marien MONNIER
Enesys

New Post
 5/11/2009 4:51 PM
 

Hi Marien,

I looked at your references and I agree, if I had a single subreport, this would be a good solution. But I have 3 subreports, each linking to the same parent. Joining all 4 tables would result in Carthesian products and too much data:

heading: parent with unique ID
status: child with reference to parent (and other data)
issue: child with reference to parent
study: child with reference to parent

If I join the parent with its 3 sublists I would get 8 rows if each list contained only 2 items for a parent id (and going up fast from there).

Regards,
Kees

New Post
 5/11/2009 5:07 PM
 
 Modified By Marien Monnier  on 5/11/2009 4:31:39 PM

Hi Kees,

You can join those tables without Carthesian product.

Using a query similar to this one, you should be able to do what you want. Assuming that the unique ID in the heading list is "ID", and that each reference is named "HeadingID":

SELECT *
FROM heading h, status s, issue i, study sd
WHERE h.ID = s.HeadingID
AND h.ID = i.HeadingID
AND h.ID = sd.HeadingID

You can do this too (giving the same results):

SELECT *
FROM heading h
INNER JOIN status s ON h.ID = s.HeadingID
INNER JOIN issue i ON h.ID = i.HeadingID
INNER JOIN study sd ON h.ID = sd.HeadingID

For more information on SQL joins, please refer to this page: http://www.shokhirev.com/nikolai/abc/sql/joins.html

 

It looks like I replied too fast on this one. Please don't take care of my post.

I work on something and come back to you as soon as I can.

Regards,
Marien MONNIER
Enesys

New Post
 5/11/2009 5:49 PM
 

Hi Kees,

I edited my previous post. Sorry for that, I replied too fast.

In order to come with an appropriate solution, please send us your report file to our support address (you can find it in the documentation).

Regards,
Marien MONNIER
Enesys

New Post
 5/11/2009 11:43 PM
 

Hi,

To further comment this thread, you would not link all lists together in that case.

You can use multiple “dataset” into one report.

Having your report (.rdl file in your report’s project) will let us have a better understanding of your requirement.

Thanks,


Frederic LATOUR
ENESYS
New Post
 9/8/2009 5:47 PM
 

Hello,

I'm running into an issue with a report timing out when run against a large dataset.  It runs for 30 minutes and then times out.  Did you find a solution to this particular problem?

Thanks

New Post
 9/9/2009 11:18 PM
 

Hi,

The Report Execution Timeout (1800 sec by default) can be configured on a per report basis.

Manage Processing Options in SharePoint integrated mode.

Execution configuration in Standalone mode.

That said, 30 minutes is quite a lot. No way to optimize the query? If you send us the report file (.rdl) and some information about the volumes in each list, we can have a look.

Regards,


Frederic LATOUR
ENESYS
New Post
 9/11/2009 10:58 PM
 

Thanks for the help.  Where should I send the RDLs?

Do you just need a count of the number of items in each list?

Previous Previous
 
Next Next
ForumForumEnesys RS Data ...Enesys RS Data ...Support - RS Da...Support - RS Da...Problem with Problem with 'big' reports and pdf rendering

 
You need to login for posting to the forums.
If you don't have a login, click here to register.
 
Copyright 2010 Enesys - All rights reserved Terms Of UsePrivacy Statement