Showing posts with label exporting. Show all posts
Showing posts with label exporting. Show all posts

Wednesday, March 21, 2012

Error when exporting to PDF

I am having an issue exporting reports to PDF.

I am connecting to the report server via https and all of the reports I'm using are working fine, but when I try and export the reports to PDF I run into problems.

On one machine running XP when I try and export a report to PDF; it will let me open the PDF, but if I try and 'save' the PDF it gives me an error that the site cannot be found.

On another machine running Windows 2000, I cannot save or open the report when trying to export to PDF with the same site cannot be found popup from Internet Explorer.

Anyone know of anything special that I need to setup to get this working? Could this be a mime type issue on the server?

Any help is greatly appreciated!

Just to add to this..

I am able to export to PDF and open on a machine running Acrobat reader 5.0,and a machine running Acrobat reader 6.0 but not from any computer running Acrobat reader 7.0!

Any ideas?

Error when exporting to pdf

I get the following message when I try to export a report to pdf. It works
for other instances of data. Not sure if there is to much data, a character
that is messing up the export or what. Any ideas?
Server Error in '/Reports' Application.
----
An internal error occurred on the report server. See the error log for more
details.
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.Exception: An internal error occurred on the
report server. See the error log for more details.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[Exception: An internal error occurred on the report server. See the error
log for more details.]
Microsoft.Reporting.WebForms.ServerReport.ServerUrlRequest(Boolean
isAbortable, String url, Stream outputStream, String& mimeType, String&
fileNameExtension) +489
Microsoft.Reporting.WebForms.ServerReport.InternalRender(Boolean
isAbortable, String format, String deviceInfo, NameValueCollection
urlAccessParameters, Stream reportStream, String& mimeType, String&
fileNameExtension) +925
Microsoft.Reporting.WebForms.ServerReportControlSource.RenderReport(String
format, String deviceInfo, NameValueCollection additionalParams, String&
mimeType, String& fileExtension) +84
Microsoft.Reporting.WebForms.ExportOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response) +153
Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext
context) +75
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +154
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously) +64
----
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET
Version:2.0.50727.42
--
Thanks,
Danny BaderHello Danny,
> I get the following message when I try to export a report to pdf. It works
> for other instances of data. Not sure if there is to much data, a character
> that is messing up the export or what. Any ideas?
> Server Error in '/Reports' Application.
try to do simple report (no extra features, just simple table, text,
etc), and try to export it to PDF. If it will work, you have error in
this report, which gives you this error.
I had error too (some custom assembly...), and I get similar errors
like you. After fix in CS, everything works...
--
Best regards,
Brano mailto:2ge@.2NOgeSPAM.us

Error when Exporting to Excel using SSRS 2003

Hi,

I have encountered an error when attempt to open a report which is exported to Excel using SSRS2003. It looks like this:

Microsoft Office Excel File Repair Log

Errors were detected in file 'C:\Documents and Settings\TocsonEI\My Documents\Rigid\Reports\rptRigidTransactionSummaryReport3.xls'
The following is a list of repairs:

Damage to the file was so extensive that repairs were not possible. Excel attempted to recover your formulas and values, but some data may have been lost or corrupted.

At first I thought it was because of the sheer bulk of the report since when I break down a month's report to every 5 days, it would export without error. So I thought that if I can break a whole report into several worksheets using page break, it might work. Unfortunately, although I did succeed in exporting the whole report into several worksheets, I still encounter the same error. Now I have no idea on what the root of the error is. Note that the same report can be exported in other formats and can be opened without error. Except for a case when I tried opening the same report exported in XML using Excel, an error which might be related to the error above occurs which says that there's an invalid unicode character in the xml file.

Any help in determining the root of the problem and a solution to it?

Hope I can help again.

It sounds like you're hitting some of the barriers of Excel 2003. I'm trying to figure out why you have 65k + rows in a spreadsheet but I probably should not ask.

Here is a kb article that references a hotfix from ms. Are you using RS 2000? Try this or grab the latest service pack.

http://support.microsoft.com/kb/905121

also see this post if you're exporting using code.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=893165&SiteID=1

cheers,

Andrew

Error when exporting to excel only

I get an error when I export my report to excel. But I do not get this error if I export the report to any other format. The error is:

An error occurred during local report processing.
An error occurred during rendering of the report.
An error occurred during rendering of the report.
Object reference not set to an instance of an object.

Any ideas what could be causing this error?

This report does contain a couple of sub-reports.

This may help you:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=790946&SiteID=1

error when exporting to excel

Hi,
When I export my resport to excel in reprot manager.
It always results in an error: index is out of bounds.
How can I do that?A few questions:
Are you using SQL Server 2000 Reporting Services 2000 SP1?
What is the exact error you are receiving?
Are you using an image in a page header?
Can you reproduce the problem using a sample database? If so could you post
an RDL the demonstrates the problem?
If you cannot not reproduce the problem with sample data is it possible for
you to send, directly to me, your RDL and RDL.Data file? RDL.Data are part
of SP1
--
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"ad" <ad@.wfes.tcc.edu.tw> wrote in message
news:usFscHKlEHA.324@.TK2MSFTNGP11.phx.gbl...
> Hi,
> When I export my resport to excel in reprot manager.
> It always results in an error: index is out of bounds.
> How can I do that?
>|||Thank Sir,
1. Yes, I have upgrade to SP1.
2. I am using Trandition Chinese version. The error is about index out of
bound or below zero.
3. Yes, I have two images in the page header.
4. I use Office xp. Is the problem is related to the version of Excel?
"Bruce Johnson [MSFT]" <brucejoh@.online.microsoft.com> ¼¶¼g©ó¶l¥ó·s»D
:OaAljVTlEHA.324@.TK2MSFTNGP11.phx.gbl...
> A few questions:
> Are you using SQL Server 2000 Reporting Services 2000 SP1?
> What is the exact error you are receiving?
> Are you using an image in a page header?
> Can you reproduce the problem using a sample database? If so could you
post
> an RDL the demonstrates the problem?
> If you cannot not reproduce the problem with sample data is it possible
for
> you to send, directly to me, your RDL and RDL.Data file? RDL.Data are part
> of SP1
> --
> Bruce Johnson [MSFT]
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "ad" <ad@.wfes.tcc.edu.tw> wrote in message
> news:usFscHKlEHA.324@.TK2MSFTNGP11.phx.gbl...
> > Hi,
> > When I export my resport to excel in reprot manager.
> > It always results in an error: index is out of bounds.
> > How can I do that?
> >
> >
>|||An "index was out of range" error will occur under the following conditions:
* SP1 is being used
* A page header contains an image
* The report is exported to excel.
The full error is "Index was out of range. Must be non-negative and less
than the size of the collection. Parameter name: index".
There are two workarounds for this issue:
* Increase the size of the page header so it is greater than the image
height.
* Set the image sizing property to "Fit"
--
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"ad" <ad@.wfes.tcc.edu.tw> wrote in message
news:%23hThRKWlEHA.1936@.TK2MSFTNGP12.phx.gbl...
> Thank Sir,
> 1. Yes, I have upgrade to SP1.
> 2. I am using Trandition Chinese version. The error is about index out of
> bound or below zero.
> 3. Yes, I have two images in the page header.
> 4. I use Office xp. Is the problem is related to the version of Excel?
>
>
> "Bruce Johnson [MSFT]" <brucejoh@.online.microsoft.com> ¼¶¼g©ó¶l¥ó·s»D
> :OaAljVTlEHA.324@.TK2MSFTNGP11.phx.gbl...
> > A few questions:
> >
> > Are you using SQL Server 2000 Reporting Services 2000 SP1?
> > What is the exact error you are receiving?
> > Are you using an image in a page header?
> > Can you reproduce the problem using a sample database? If so could you
> post
> > an RDL the demonstrates the problem?
> > If you cannot not reproduce the problem with sample data is it possible
> for
> > you to send, directly to me, your RDL and RDL.Data file? RDL.Data are
part
> > of SP1
> >
> > --
> > Bruce Johnson [MSFT]
> > Microsoft SQL Server Reporting Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> > "ad" <ad@.wfes.tcc.edu.tw> wrote in message
> > news:usFscHKlEHA.324@.TK2MSFTNGP11.phx.gbl...
> > > Hi,
> > > When I export my resport to excel in reprot manager.
> > > It always results in an error: index is out of bounds.
> > > How can I do that?
> > >
> > >
> >
> >
>|||Thank's Sir
Your answer is excellent!
After I increased the size of the page header, it's OK
Thank a lot
"Bruce Johnson [MSFT]" <brucejoh@.online.microsoft.com> ¼¶¼g©ó¶l¥ó·s»D
:e8oJ3PclEHA.3988@.tk2msftngp13.phx.gbl...
> An "index was out of range" error will occur under the following
conditions:
> * SP1 is being used
> * A page header contains an image
> * The report is exported to excel.
> The full error is "Index was out of range. Must be non-negative and less
> than the size of the collection. Parameter name: index".
> There are two workarounds for this issue:
> * Increase the size of the page header so it is greater than the image
> height.
> * Set the image sizing property to "Fit"
> --
> Bruce Johnson [MSFT]
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "ad" <ad@.wfes.tcc.edu.tw> wrote in message
> news:%23hThRKWlEHA.1936@.TK2MSFTNGP12.phx.gbl...
> > Thank Sir,
> > 1. Yes, I have upgrade to SP1.
> > 2. I am using Trandition Chinese version. The error is about index out
of
> > bound or below zero.
> > 3. Yes, I have two images in the page header.
> > 4. I use Office xp. Is the problem is related to the version of Excel?
> >
> >
> >
> >
> >
> > "Bruce Johnson [MSFT]" <brucejoh@.online.microsoft.com> ¼¶¼g©ó¶l¥ó·s»D
> > :OaAljVTlEHA.324@.TK2MSFTNGP11.phx.gbl...
> > > A few questions:
> > >
> > > Are you using SQL Server 2000 Reporting Services 2000 SP1?
> > > What is the exact error you are receiving?
> > > Are you using an image in a page header?
> > > Can you reproduce the problem using a sample database? If so could you
> > post
> > > an RDL the demonstrates the problem?
> > > If you cannot not reproduce the problem with sample data is it
possible
> > for
> > > you to send, directly to me, your RDL and RDL.Data file? RDL.Data are
> part
> > > of SP1
> > >
> > > --
> > > Bruce Johnson [MSFT]
> > > Microsoft SQL Server Reporting Services
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > >
> > >
> > > "ad" <ad@.wfes.tcc.edu.tw> wrote in message
> > > news:usFscHKlEHA.324@.TK2MSFTNGP11.phx.gbl...
> > > > Hi,
> > > > When I export my resport to excel in reprot manager.
> > > > It always results in an error: index is out of bounds.
> > > > How can I do that?
> > > >
> > > >
> > >
> > >
> >
> >
>sql

Error when Exporting to Excel

For the last couple of weeks we've been experiencing problems when try to
export reports to Excel either from the VS IDE or the Report Manager Web.
After some tinkering and investigation (maybe more luck than judgement) we
found it to be an issue relating to Page Breaks on tables. If we unchecked
the 'Insert Page Break before this table' checkbox the report would function
correctly and export to Excel without any hassles.Hi - Any idea why the page break would cause a probem ? In my situation, it
is only a problem in a Matrix report ? it works fine for me in table reports.
"Dave Peake" wrote:
> For the last couple of weeks we've been experiencing problems when try to
> export reports to Excel either from the VS IDE or the Report Manager Web.
> After some tinkering and investigation (maybe more luck than judgement) we
> found it to be an issue relating to Page Breaks on tables. If we unchecked
> the 'Insert Page Break before this table' checkbox the report would function
> correctly and export to Excel without any hassles.

error when exporting my report to excel

hi there,
i've a question about exporting reports to excel.
when i do this , i don't get the subreports to my excel !
i only get the mainreport.
what could i do ?
thanks patrick

Well, with all due respect maybe you answered your own question "Sub_Reports".

Within your primary report do you "call or navigate" to another report - if you do, these are "Sub Reports' and they will never get exported with your primary report..
I do not know for sure - I am just rying to help and not be rude within the process... Is there more information you may be able to provide?
Best Regards,
Joe