A co-worker set up about 5 schedules for a compound document composer report that I created. The compound report consists of a report at the top and two graphs at the bottom of the report. The graphs are being saved using ON GRAPH PCHOLD FORMAT PDF. The report runs fine interactively and also in our self-serve application from a launch page. When the report is run from a batch schedule each month in ReportCaster for multiple customers and saved to the Report Library, from time to time when a particular customer tries to open up the report it displays a message that says "An error exists on this page. Acrobat may not display the page correctly" and no report displays. The hold file names for each customer are unique hold file names that contain the &FOCCPU number in the name. We don't know if there is a problem when trying to run multiple schedules for multiple customers at the same time even when the hold file names are unique. The fex is doing a PAGE-BREAK REPAGE for each customer.

Has anyone experienced a similar situation?Thanks.



Windows 7
WF 8009

This message has been edited. Last edited by: <Emily McAllister>,

quote:

Acrobat may not display the page correctly

Michele,

This is a friendly follow-up regarding your Report Library PDF issue.

Are you finding it is the same customer that has this issue? Do they have issues with other PDF reports not in the Report Caster Library?

You could try sending the PDF report via an email to the customer and see if it can be opened.

If all the above is working properly then you may need to open a case for further assistance.

To open a case click on - TechSupport Center

Thank you for participating in the Focal Point Forum.

Kindest regards,
Tamra Colangelo
Focal Point Moderator
Information Builders Inc.
* Summit 2016 – June 13-17 in Reno, Nevada  - http://www.informationbuilders.com/events/summit

Michelle,

I've found that the error handling for the document composer is very poor. There are a lot of things that the composer won't give you an error message for, but it won't be able to create a proper PDF, and Adobe will throw the error.

I would start by running the report from the MRE with the same variables as what RC would be using. I've found that sometimes the content outgrows the content area defined in the composer syntax. Check to see if your content is larger when you get that error as opposed to when you don't. And then adjust for overflow or the content area of your different reports.

Tamara, I am referring to reports that get saved in our internal Report Library. The behavior is what I see when I view the reports in the Report Library.

Eric, thanks for the feedback. Unfortunately, MRE is not set up at the present. I'll keep your observations in mind when the reports run in production next month. Will follow-up with feedback then. Thanks again.