Extra Pages with Landscape

I have a report that is landscape (11w x 8.5h). The left margin is .2 and the
right margin is .2 and the body is 10.149w. The total (10.549) is under the
11 inches of the width but when I go to print preview, the report is 15 pages
with only 10 containing data. The last five pages are blank.
I then go to print it and the printer still sees the report a portrait
document instead of landscape so I have to manually adjust for this each
time.
Any ideas or suggestions?
I thought that this would be a good challenge for Peter Blackburn...In Visual Studio report designer make sure that the white canvas page is at
minimum size.
If the canvas (The white page you start with when designing a report) is
greater than the width of your paper then the print out will strech more
pagers...
"Kipp C" wrote:
> I have a report that is landscape (11w x 8.5h). The left margin is .2 and the
> right margin is .2 and the body is 10.149w. The total (10.549) is under the
> 11 inches of the width but when I go to print preview, the report is 15 pages
> with only 10 containing data. The last five pages are blank.
> I then go to print it and the printer still sees the report a portrait
> document instead of landscape so I have to manually adjust for this each
> time.
> Any ideas or suggestions?
> I thought that this would be a good challenge for Peter Blackburn...

Extra empty pages in PDF report

Report looks great in Visual studio and in a Browser, but when I convert it
to pdf for printing, I am getting extra pages after every good page with just
a header printed on those pages.
I tried decrease the size of the report and make sure that it fits into 8
1/2 x 11 inches, but it did not help.
I still have those annoying empty pages in the printed report.
Any other suggestions on how can I fix it?
Thank you.Simon if are you having problem with client side printing then you will want
to try the following.
Try setting body width to 8.46 if you are using letter/portrait. If you are
using letter/landscape then set the width to 10.96.
I hope that helps.
This is an issue Microsorft is now aware of.
"Simon Gold" wrote:
> Report looks great in Visual studio and in a Browser, but when I convert it
> to pdf for printing, I am getting extra pages after every good page with just
> a header printed on those pages.
> I tried decrease the size of the report and make sure that it fits into 8
> 1/2 x 11 inches, but it did not help.
> I still have those annoying empty pages in the printed report.
> Any other suggestions on how can I fix it?
> Thank you.
>|||Thanks Kevin. I figured it out about one hour before I got your e-mail. :-)
"Kevin Weir" wrote:
> Simon if are you having problem with client side printing then you will want
> to try the following.
> Try setting body width to 8.46 if you are using letter/portrait. If you are
> using letter/landscape then set the width to 10.96.
> I hope that helps.
> This is an issue Microsorft is now aware of.
> "Simon Gold" wrote:
> > Report looks great in Visual studio and in a Browser, but when I convert it
> > to pdf for printing, I am getting extra pages after every good page with just
> > a header printed on those pages.
> > I tried decrease the size of the report and make sure that it fits into 8
> > 1/2 x 11 inches, but it did not help.
> > I still have those annoying empty pages in the printed report.
> > Any other suggestions on how can I fix it?
> > Thank you.
> >

extra blank pages when exported to pdf

anyone know why I'm getting an extra blank page after every page when I
export to PDF?I did notice something weird ... I click on the body of the report and try
to change the width 11(w) x 8.5 (h) (landscape report) and it always changes
back to 11.125. I can't get it to change. any ideas?
btw, thank you for the quick reply. I am in a rush for this.
"Mike Collins" <MikeCollins@.discussions.microsoft.com> wrote in message
news:F73E92CC-0FBD-47CE-A284-554CE8FE5118@.microsoft.com...
> Course, I did not answer your question...directly. You are getting blank
> pages because something on your report (report width, a long field) is
> causing this and you are not seeing it by looking at the preview tab.
> "Emil" wrote:
> > anyone know why I'm getting an extra blank page after every page when I
> > export to PDF?
> >
> >
> >|||Please make sure that your report is setup as follows:
(Report.PageWidth - Report.LeftMargin - Report.Right Margin) >=Body.Width
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Emil" <laserview@.hotmail.com> wrote in message
news:e4r37RuhEHA.3016@.tk2msftngp13.phx.gbl...
> anyone know why I'm getting an extra blank page after every page when I
> export to PDF?
>|||I can't change my body width
(Report.PageWidth - Report.LeftMargin - Report.Right Margin) >= Body.Width
11-.25-.25 = 10.5
Body.width = 11.125
No mater what I do I can't change the body width. Always goes back to 11.125
Any ideas?
"Bruce Johnson [MSFT]" <brucejoh@.online.microsoft.com> wrote in message
news:%23XvlCquhEHA.2340@.TK2MSFTNGP11.phx.gbl...
> Please make sure that your report is setup as follows:
> (Report.PageWidth - Report.LeftMargin - Report.Right Margin) >=> Body.Width
>
> --
> Bruce Johnson [MSFT]
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Emil" <laserview@.hotmail.com> wrote in message
> news:e4r37RuhEHA.3016@.tk2msftngp13.phx.gbl...
> > anyone know why I'm getting an extra blank page after every page when I
> > export to PDF?
> >
> >
>|||Make sure u have all the size of reportitems to the <= body width u want.If u
are not able to change the body size means these is
something(textbox,rectangle table etc...)that has width larger that the width
of the body u are trying to set....
blank pages are usually when the following is not true....for the width
Report.PageWidth >= Report.LeftMargin + Report.Right Margin + Body.Width
I hope this helps...
"Emil" wrote:
> I can't change my body width
>
> (Report.PageWidth - Report.LeftMargin - Report.Right Margin) >= Body.Width
> 11-.25-.25 = 10.5
> Body.width = 11.125
> No mater what I do I can't change the body width. Always goes back to 11.125
> Any ideas?
>
>
> "Bruce Johnson [MSFT]" <brucejoh@.online.microsoft.com> wrote in message
> news:%23XvlCquhEHA.2340@.TK2MSFTNGP11.phx.gbl...
> > Please make sure that your report is setup as follows:
> >
> > (Report.PageWidth - Report.LeftMargin - Report.Right Margin) >=> > Body.Width
> >
> >
> > --
> > Bruce Johnson [MSFT]
> > Microsoft SQL Server Reporting Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> > "Emil" <laserview@.hotmail.com> wrote in message
> > news:e4r37RuhEHA.3016@.tk2msftngp13.phx.gbl...
> > > anyone know why I'm getting an extra blank page after every page when I
> > > export to PDF?
> > >
> > >
> >
> >
>
>|||I have a similiar problem - blank pages being generated when exporting
to PDF. However, I have checked my body(9.9in) vs report page width
(11in) with .25 inch left and rt margins. I think the problem is
related the way RS computes the vertical requirements of outputting a
report -- I have many conditionally hidden lines in a table group. If
I set the List height (4in) just large enough to contain the table, I
only get one page rendered when in fact two pages should be rendered to
PDF. However, if I increse the List height to (4.1in) I generate a
report of 4 pages for what should be a 2-page report with pages 2 and 4
blank.
Does anyone else have this same issue?
Dennis|||I am having the same problem - see below "DD" posting. Have you found
a solution to your problem?|||I was having the same problem (exports to PDF fine from VS IDE, but get extra
pages when I export to PDF from Report Manager). I was able to remedy the
problem by installing service pack 1 for sql reporting services.
"DD" wrote:
> I am having the same problem - see below "DD" posting. Have you found
> a solution to your problem?
>|||I was having the same problem, my fix was strange. In my report I have
detailed lines in which I wanted spaces to separate each row, to do this i
added an extra 2 detailed lines with no data fields on them, there height was
0.3cm, when I removed these emtpy lines or increased the height to 0.5cm the
problem went away.
"Jonathan Gordon" wrote:
> I was having the same problem (exports to PDF fine from VS IDE, but get extra
> pages when I export to PDF from Report Manager). I was able to remedy the
> problem by installing service pack 1 for sql reporting services.
>
>
> "DD" wrote:
> > I am having the same problem - see below "DD" posting. Have you found
> > a solution to your problem?
> >
> >sql

external image not rendering when generated from aspx page

I'm having problems displaying images generated by aspx pages from a report. It works fine if I point the external value to a static image on the web. I can paste the url to the page into IE and it generates the image with no issues. What am I doing wrong? I used a textbox to verify that the correct url is being generated (= Parameters!MYPROJECT_URL.Value & Parameters!MYPROJECT_NO.Value).

Are there any issues with generating external images with reporting services?

I have installed SP1 for MS 2005...shouldn't I see some sort of visual confirmation in Management studio when I click the Help Menu->about? saying the version is MS SQL Server 2005? how do I verify that the upgrade was successful?

You can check if the upgrade is successful from the error logs, they contain the build number on the top.

|||Check if ASPX pase generate the image have anonymouse accesssql

Extending the number of rows returned per page in RS

Is there a way to extend the number of rows that will be returned so that Reporting services doesn't display such a large number of pages for the users to page through? It would be easier for them to "wheel mouse" through a long page on the screen.

Anyone out there have any thoughts on how this might be accomplished?

Thanks!

Travis

Here are a couple of options:

- set PageBreakAtEnd and PageBreakAtStart to false on your tables/matrices/grouping panels

- make your row heights smaller, use a smaller font

- filter your data better, or group it into smaller groups and have each group rendered into its own table, turn off paging on those tables

But turning off paging looks okay when viewing the report in the browser, but can make the report look like *** when exported to PDF.

expose 1433 on net

I need to exposed 1433 on the net to enable a IIS6 pages to query remote SQL
servers.
Im looking for information on how to do this as securely as possible
(although im sure this is not ideal) ?
At the moment im using SQL authentication only.
Thanks for any information
ScottWhy not install SQLXML and take advantage of the easy stored procedure to
web services tool. Then you can apply an SSL certificate and have your web
site only talk to SQL Server over TCP 443. It's safer, it's encrypted, it's
extensible, and it's more portable. It's SOA!
hth,
Eric
scott wrote:
> I need to exposed 1433 on the net to enable a IIS6 pages to query
> remote SQL servers.
> Im looking for information on how to do this as securely as possible
> (although im sure this is not ideal) ?
> At the moment im using SQL authentication only.
> Thanks for any information
> Scott|||sounds excellent but how do you set it up ?
Currently my aspx app on IIS6 queries SQL on an IP addresson port 1433 and
pulls back XML.
How do i install SQLXML ?
Use the web service tool ?
Setup SSL ?
(guess I just forward port 443)
Sorry for all the questions
Scott|||you should start by reading about sqlxml at
http://www.microsoft.com/sql/techinfo/xml/default.asp
scott wrote:
> sounds excellent but how do you set it up ?
> Currently my aspx app on IIS6 queries SQL on an IP addresson port
> 1433 and pulls back XML.
> How do i install SQLXML ?
> Use the web service tool ?
> Setup SSL ?
> (guess I just forward port 443)
> Sorry for all the questions
> Scott

expose 1433 on net

I need to exposed 1433 on the net to enable a IIS6 pages to query remote SQL
servers.
Im looking for information on how to do this as securely as possible
(although im sure this is not ideal) ?
At the moment im using SQL authentication only.
Thanks for any information
Scott
Why not install SQLXML and take advantage of the easy stored procedure to
web services tool. Then you can apply an SSL certificate and have your web
site only talk to SQL Server over TCP 443. It's safer, it's encrypted, it's
extensible, and it's more portable. It's SOA!
hth,
Eric
scott wrote:
> I need to exposed 1433 on the net to enable a IIS6 pages to query
> remote SQL servers.
> Im looking for information on how to do this as securely as possible
> (although im sure this is not ideal) ?
> At the moment im using SQL authentication only.
> Thanks for any information
> Scott
|||sounds excellent but how do you set it up ?
Currently my aspx app on IIS6 queries SQL on an IP addresson port 1433 and
pulls back XML.
How do i install SQLXML ?
Use the web service tool ?
Setup SSL ?
(guess I just forward port 443)
Sorry for all the questions
Scott
|||you should start by reading about sqlxml at
http://www.microsoft.com/sql/techinfo/xml/default.asp
scott wrote:
> sounds excellent but how do you set it up ?
> Currently my aspx app on IIS6 queries SQL on an IP addresson port
> 1433 and pulls back XML.
> How do i install SQLXML ?
> Use the web service tool ?
> Setup SSL ?
> (guess I just forward port 443)
> Sorry for all the questions
> Scott

Exporting to PDF through web service produses blank pages

Hi all,
I am exporting to PDF through web service a report that contains matrix.
I get almost every second page a blank page.
The same report when exported to PDF by the report manager does not contain
blank pages.
Is it a bug, Is there any work around
Thanks,
YuvalNobody is going to answer your question. I've been asking it for days. I
emailed all those Microsoft bloggers. I posted here. Nothing. I did
enough research that I am conviced Microsoft knows about the issue.
Note they claim you can find known bugs here:
http://msdn.microsoft.com/bugs/
But you can only find bugs they want you to find (ie ones they know how to
fix). If you seach for reporting services, you will find 0 known bugs.
The problem is that the List containing the matrix is growing so much that
the report won't fit on one page. So it prints two pages. You can see this
by changing the background colour of the List that contains the matrix.
When you run it, you will find the coloured list extends onto the 'blank'
page.
I haven't seen a fix yet. You can shrink your matrix so that the list won't
grow onto the next page. But that's not usually an acceptable fix, because
it means leaving about a third of the page blank.
Seems to me there's no acceptable way to print a matrix report. This issue
affects the tiff, and I found a different issue in Excel.
Scott
"Yuval Rabinovitz" <yvlrb@.netvision.net.il> wrote in message
news:e66FusBkEHA.3848@.tk2msftngp13.phx.gbl...
> Hi all,
> I am exporting to PDF through web service a report that contains matrix.
> I get almost every second page a blank page.
> The same report when exported to PDF by the report manager does not
contain
> blank pages.
> Is it a bug, Is there any work around
> Thanks,
> Yuval
>|||I did eventaully get a reponse from Microsoft. Everyone was quite friendly,
but it took a while to find the person who knew the answer.
If you are not using subtotals in your matrix, you might try "KB article
875518 is FIX: Width of the list that contains a matrix grows unexpectedly
when exported to PDF." This hotfix (only available by calling support)
didn't solve my problem.
If you are using subtotals in your matrix (like I was), this is the answer.
This response was from Sarah Parra:
"
The problem is that the list always extends a certain amount to the right
and bottom of the matrix, and the amount that it extends is based directly
on how wide (for column totals) or tall (for row totals) the total textbox
is. If you look at your report in the designer, in the bottom right corner,
under the totals boxes, there is a gray/brown empty space. That space is
effectively how much extra list you will see in the final output. We take
the size of the matrix to be the actual size that you see, minus the totals
boxes. That means that the list effectively looks like it is that much
bigger than the matrix (instead of being the exact same size). When the
rendering happens, it then adds that much padding to the right and below the
actual matrix.
This is a bug as well, it's just a different bug from the one described in
the article/hotfix. :) This one does have a fairly simple workaround. You
need to resize the list to be the size of the matrix, minus the size of the
totals columns/rows. The designer will not allow you to size the list
smaller than the matrix (which includes the totals), but you can do this
manually in the rdl. The following are the instructions I sent to another
customer on a sample report he had provided, so the sizes and line number
will not match up for you:
(1) Find the size of the column total box. You can just click on it and look
at the Width property. It's 0.875in.
(2) In the Solution Explorer, right click the .rdl file and select View
Code. In the code, find the Width definition for the List itself. You'll see
it on line 78, and it looks like this : <Width>5.875in</Width>. Change that
to that value, minus the size of the total column, .875. So just make it
5.0in, or you can make it a little bigger if you want some extra space
displayed to the right of the matrix itself. In the designer at this point,
it will look like the Total box is gone, but it's still there. You can do
the same thing for the row totals if you want. You will probably want to do
this, because if you have a situation where the matrix should end at the
very bottom of the page, you may still get an extra page if the extended
list height would force it.
(3) Preview and render the report. You should no longer see any blank pages.
"
"Scott Stonehouse" <scott@.mphec.ca> wrote in message
news:%23N3MVjFkEHA.2812@.tk2msftngp13.phx.gbl...
> Nobody is going to answer your question. I've been asking it for days. I
> emailed all those Microsoft bloggers. I posted here. Nothing. I did
> enough research that I am conviced Microsoft knows about the issue.
> Note they claim you can find known bugs here:
> http://msdn.microsoft.com/bugs/
> But you can only find bugs they want you to find (ie ones they know how to
> fix). If you seach for reporting services, you will find 0 known bugs.
> The problem is that the List containing the matrix is growing so much that
> the report won't fit on one page. So it prints two pages. You can see
this
> by changing the background colour of the List that contains the matrix.
> When you run it, you will find the coloured list extends onto the 'blank'
> page.
> I haven't seen a fix yet. You can shrink your matrix so that the list
won't
> grow onto the next page. But that's not usually an acceptable fix,
because
> it means leaving about a third of the page blank.
> Seems to me there's no acceptable way to print a matrix report. This
issue
> affects the tiff, and I found a different issue in Excel.
> Scott
>
> "Yuval Rabinovitz" <yvlrb@.netvision.net.il> wrote in message
> news:e66FusBkEHA.3848@.tk2msftngp13.phx.gbl...
> > Hi all,
> >
> > I am exporting to PDF through web service a report that contains matrix.
> > I get almost every second page a blank page.
> > The same report when exported to PDF by the report manager does not
> contain
> > blank pages.
> >
> > Is it a bug, Is there any work around
> >
> > Thanks,
> > Yuval
> >
> >
>

Exporting the Report into Excel : Timeout Problem

Hi,

I have installed the SSRS 2005 beta version, when I am exporting the report into excel format it is working if my report has 1 to 3 pages. But the same report contains more than 10 pages then I will be getting the TimeOut error.

The operation has timed out

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Net.WebException: The operation has timed out

Any suggestions are welcome.

Thanks in Advance

Hello,

Can you export to other formats (HTML, PDF) without problems? How much information do you actually have on a page ? How many columns and rows in your excel spreadsheet?

Thank you,

Nico

|||

Hi,

I made the same experience, when exporting to XLS I got a timeout error message. This also happens when exporting to pdf, but not when exporting to csv, html. This only happens with larger reports (In our case approx. 700 pages). We would need some help here, too.

Thx

Michael

Exporting the Report into Excel : Timeout Problem

Hi,

I have installed the SSRS 2005 beta version, when I am exporting the report into excel format it is working if my report has 1 to 3 pages. But the same report contains more than 10 pages then I will be getting the TimeOut error.

The operation has timed out

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Net.WebException: The operation has timed out

Any suggestions are welcome.

Thanks in Advance

Hello,

Can you export to other formats (HTML, PDF) without problems? How much information do you actually have on a page ? How many columns and rows in your excel spreadsheet?

Thank you,

Nico

|||

Hi,

I made the same experience, when exporting to XLS I got a timeout error message. This also happens when exporting to pdf, but not when exporting to csv, html. This only happens with larger reports (In our case approx. 700 pages). We would need some help here, too.

Thx

Michael

|||Is this answered already?I almost have te same problem.I am using a custom code.When i am exporting my report to PDF, the operation time out.But why not when exporting to Excel or HTML.