Page Break at End throws unwanted additional blank page in PDF

Hi,
Originally posted as "Extra Page Break thrown in Export to PDF" - however I
thought this might be misinterpreted as a page size issue.
We have a report which has a group. The "Page Break at End" option is
checked for the group. The report renders correctly in the report manager
with totals immediately under the last group.
Unfortunately, when exporting to PDF, an additional blank page is added.
Can this be avoided?
Note, the report has three tables which are directly on top of each other -
the tables are all sitting within a rectangle.
many thanks
MattJust a thought - Could I edit the RDL file directly and put a condition in
the PageBreak at End element - is this an possibility?
"Matt" <NoSpam:Matthew.Moran@.Computercorp.com.au> wrote in message
news:ex8fbmIGFHA.3732@.tk2msftngp13.phx.gbl...
> Hi,
> Originally posted as "Extra Page Break thrown in Export to PDF" - however
I
> thought this might be misinterpreted as a page size issue.
> We have a report which has a group. The "Page Break at End" option is
> checked for the group. The report renders correctly in the report manager
> with totals immediately under the last group.
> Unfortunately, when exporting to PDF, an additional blank page is added.
> Can this be avoided?
> Note, the report has three tables which are directly on top of each
other -
> the tables are all sitting within a rectangle.
> many thanks
> Matt
>|||In answer to editing the RDL - unfortunately, no.
"Matt" <NoSpam:Matthew.Moran@.Computercorp.com.au> wrote in message
news:eWdstsIGFHA.2824@.tk2msftngp13.phx.gbl...
> Just a thought - Could I edit the RDL file directly and put a condition in
> the PageBreak at End element - is this an possibility?
>
> "Matt" <NoSpam:Matthew.Moran@.Computercorp.com.au> wrote in message
> news:ex8fbmIGFHA.3732@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> > Originally posted as "Extra Page Break thrown in Export to PDF" -
however
> I
> > thought this might be misinterpreted as a page size issue.
> >
> > We have a report which has a group. The "Page Break at End" option is
> > checked for the group. The report renders correctly in the report
manager
> > with totals immediately under the last group.
> >
> > Unfortunately, when exporting to PDF, an additional blank page is added.
> > Can this be avoided?
> >
> > Note, the report has three tables which are directly on top of each
> other -
> > the tables are all sitting within a rectangle.
> >
> > many thanks
> >
> > Matt
> >
> >
>|||Actually, the additional page only seems to occur when the table has rows
after the last group - in my case, it's a grand total field
"Matt" <NoSpam:Matthew.Moran@.Computercorp.com.au> wrote in message
news:eWdstsIGFHA.2824@.tk2msftngp13.phx.gbl...
> Just a thought - Could I edit the RDL file directly and put a condition in
> the PageBreak at End element - is this an possibility?
>
> "Matt" <NoSpam:Matthew.Moran@.Computercorp.com.au> wrote in message
> news:ex8fbmIGFHA.3732@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> > Originally posted as "Extra Page Break thrown in Export to PDF" -
however
> I
> > thought this might be misinterpreted as a page size issue.
> >
> > We have a report which has a group. The "Page Break at End" option is
> > checked for the group. The report renders correctly in the report
manager
> > with totals immediately under the last group.
> >
> > Unfortunately, when exporting to PDF, an additional blank page is added.
> > Can this be avoided?
> >
> > Note, the report has three tables which are directly on top of each
> other -
> > the tables are all sitting within a rectangle.
> >
> > many thanks
> >
> > Matt
> >
> >
>|||I believe there are some issues with page breaks while exporting to PDFs..
Hopefully some of these kinds of things will be fixed as time goes forward,
I have yet to be able to eliminate all of the extra pages as well...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Matt" <NoSpam:Matthew.Moran@.Computercorp.com.au> wrote in message
news:ex8fbmIGFHA.3732@.tk2msftngp13.phx.gbl...
> Hi,
> Originally posted as "Extra Page Break thrown in Export to PDF" - however
> I
> thought this might be misinterpreted as a page size issue.
> We have a report which has a group. The "Page Break at End" option is
> checked for the group. The report renders correctly in the report manager
> with totals immediately under the last group.
> Unfortunately, when exporting to PDF, an additional blank page is added.
> Can this be avoided?
> Note, the report has three tables which are directly on top of each
> other -
> the tables are all sitting within a rectangle.
> many thanks
> Matt
>|||I have found a work around - although it's a bit clunky.
The issue seems to be where you have something appearing after the last
group. If there is nothing after the last group, the report exports to PDF
correctly. But because I want grand totals I have not been able to simply
put a summation in the table footer.
Firstly, I am using a stored procedure as my report data source.
I added two additional fields to my stored procedure result set a) a grand
total field and b) a last group flag.
I then put the grand total field into a footer row of the outermost group
and set the hidden property to an expression including the Last Group flag
which evaluates to false when at the last group.
This is not a particularly complex thing to work around - but was quite
painful as I resist having to use unintuitive solutions such as this because
they make maintenance more difficult :)
Note: I would have used pagenumbering to determine the last page but
unfortunately, the Global values for Pagenumber and TotalPages are not
accessible within the body of the report.
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:OLxJc%23NGFHA.2932@.TK2MSFTNGP15.phx.gbl...
> I believe there are some issues with page breaks while exporting to PDFs..
> Hopefully some of these kinds of things will be fixed as time goes
forward,
> I have yet to be able to eliminate all of the extra pages as well...
>
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Matt" <NoSpam:Matthew.Moran@.Computercorp.com.au> wrote in message
> news:ex8fbmIGFHA.3732@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> > Originally posted as "Extra Page Break thrown in Export to PDF" -
however
> > I
> > thought this might be misinterpreted as a page size issue.
> >
> > We have a report which has a group. The "Page Break at End" option is
> > checked for the group. The report renders correctly in the report
manager
> > with totals immediately under the last group.
> >
> > Unfortunately, when exporting to PDF, an additional blank page is added.
> > Can this be avoided?
> >
> > Note, the report has three tables which are directly on top of each
> > other -
> > the tables are all sitting within a rectangle.
> >
> > many thanks
> >
> > Matt
> >
> >
>sql

Package Validation Error in Custom PipelineComponent

Hi

I'm developing an PipelineComponent (ComponentType.Transform). When I try to execute this component, the following error is thrown:

Code Snippet

===================================

Package Validation Error (Package Validation Error)

===================================

Error at Data Flow Task [DTS.Pipeline]: Buffer Type 1 had a size of 0 bytes.

Error at Data Flow Task [DTS.Pipeline]: The buffer manager failed to create a new buffer type.

Error at Data Flow Task [DTS.Pipeline]: The Data Flow task cannot register a buffer type. The type had 50 columns and was for execution tree 0.

Error at Data Flow Task [DTS.Pipeline]: The layout failed validation.

Error at Data Flow Task: There were errors during task validation.

(Microsoft.DataTransformationServices.VsIntegration)

Program Location:

at Microsoft.DataTransformationServices.Project.DataTransformationsPackageDebugger.ValidateAndRunDebugger(Int32 flags, DataWarehouseProjectManager manager, IOutputWindow outputWindow, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchDtsPackage(Int32 launchOptions, ProjectItem startupProjItem, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchActivePackage(Int32 launchOptions)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchDtsPackage(Int32 launchOptions, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.Launch(Int32 launchOptions, DataTransformationsProjectConfigurationOptions options)

Can anyone help me, please? The "Integration Services Error and Message Reference" didn't help me much.

Thank you

Manuel Bauer

The error does not give me any clues other than it happens during a validation stage, so what is in your Validate method?

Have your tried debugging this, i.e. Visual Studio attached to the execution host?

|||

Hi

Thank you for your answer. My pipeline component's validate method runs without any problems, I debugged this in design time and in run time (before the exception occured). In my opinion, the problem is the early validation (http://sqljunkies.com/WebLog/knight_reign/archive/2005/04/20/12365.aspx) of the data flow task. As I expect, the data flow task does any validation itself.

I can't imagine what "The Data Flow task cannot register a buffer type. The type had 50 columns and was for execution tree 0." means, so I really don't know where the problem could be.

The exception is thrown immediately after running the package (also after running the validate method of my pipeline component).

|||

Does the package work if you take your component out of it?

The early validation vs late validation is the same Validate method calls, and since it generally works, I'd say it is clear that your transform has a problem, regardless of if it is the early or late call. Early and Late means normally Validate gets called twice, there is no difference between them. The Task will have a validate method, and a Data Flow will then call Validate for each child component.

How can the exception be thrown "after" running a package, Execute will never get called if a task fails validation. What is the return of your Validate method when you debug it?

Did you debug against dtsdebughost or just Visual Studio (designer)? For simplicity when trying to resolve run-time issues I set the code project debug option to use dtexec directly, just using /F and a package file. It is faster than attaching to a designer instance of VS.

|||

I found a solution for my problem. I was thinking wrong about this validation thing, I thought that the data flow task does some independant, general validation itself.

In my component, I "forgot" to call base.Validate(), which would no be a problem if the own validate method is implemented as id should. In my case, it was not.

Thank you for your competent analysis of my problem.

Manuel Bauer