| Groups | Blog | Home |
sql server reporting services : Corrupt PDF when using Subscription with file share
I am exporting report document to a file share every 1 hour using
Subscriptions. Sometimes the PDF document that the subscription created is corrupted. This happens at random. This is the error I get when I open the PDF either in 5.0 or 6.0: In 5.0: "There was an error processing a page. There was a problem reading this document (109)" In 6.0: "There was an error processing a page. There was a problem reading this
If you open the file in notepad, is there an HTML error at the bottom of the
PDF file? If so, what is the stack trace? You can also find it in the server log file in the LogFiles directory. -- This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Sanjay Gandhi" <SanjayGandhi@discussions.microsoft.com> wrote in message news:8957774A-E840-4A80-9B32-17A6D056F71B@microsoft.com... >I am exporting report document to a file share every 1 hour using > Subscriptions. Sometimes the PDF document that the subscription created is > corrupted. This happens at random. > > This is the error I get when I open the PDF either in 5.0 or 6.0: > > In 5.0: > "There was an error processing a page. There was a problem reading this > document (109)" > > In 6.0: > "There was an error processing a page. There was a problem reading this > document (117)"
Hi,
I had the same problem when rendering PDF reports to files thru the Web Service. The issue was that, when a file existed with the same name, my FileStream.Write overwrote bytes but, in the case the new report was smaller thant the previous one, extra bytes were left at the end of the PDF making it invalid for Acrobat Reader. The turnaround was to delete the file before rendering the new report. "Donovan Smith [MSFT]" <donovans@online.microsoft.com> a écrit dans le message de news: %235Q2FyhOFHA.2468@tk2msftngp13.phx.gbl... [quoted text, click to view] > If you open the file in notepad, is there an HTML error at the bottom of > the PDF file? If so, what is the stack trace? You can also find it in > the server log file in the LogFiles directory. > > -- > This posting is provided "AS IS" with no warranties, and confers no > rights. > > > "Sanjay Gandhi" <SanjayGandhi@discussions.microsoft.com> wrote in message > news:8957774A-E840-4A80-9B32-17A6D056F71B@microsoft.com... >>I am exporting report document to a file share every 1 hour using >> Subscriptions. Sometimes the PDF document that the subscription created >> is >> corrupted. This happens at random. >> >> This is the error I get when I open the PDF either in 5.0 or 6.0: >> >> In 5.0: >> "There was an error processing a page. There was a problem reading this >> document (109)" >> >> In 6.0: >> "There was an error processing a page. There was a problem reading this >> document (117)" > >
I completely forgot about my post.
No there is no http error in the PDF source. I can forward you the PDF document if needed. The errors just seem to occur at random. This time around when I opened a PDF document generated by Reportin Services, it just comes out blank. In viewer it says 24 pages, but it doesnt go beyond 1st page. I read the post by Philippe and I am in a similar scenario. I generate a PDF file daily every hour. So the next day around, Reporting Services overwrites the previous file that it created the day before. I guess I may have to use the method you have - create my own scheduler and delete the existing PDF and write the new PDF file everytime. [quoted text, click to view] "Donovan Smith [MSFT]" wrote:
> If you open the file in notepad, is there an HTML error at the bottom of the > PDF file? If so, what is the stack trace? You can also find it in the > server log file in the LogFiles directory. > > -- > This posting is provided "AS IS" with no warranties, and confers no rights. > > > "Sanjay Gandhi" <SanjayGandhi@discussions.microsoft.com> wrote in message > news:8957774A-E840-4A80-9B32-17A6D056F71B@microsoft.com... > >I am exporting report document to a file share every 1 hour using > > Subscriptions. Sometimes the PDF document that the subscription created is > > corrupted. This happens at random. > > > > This is the error I get when I open the PDF either in 5.0 or 6.0: > > > > In 5.0: > > "There was an error processing a page. There was a problem reading this > > document (109)" > > > > In 6.0: > > "There was an error processing a page. There was a problem reading this > > document (117)" > >
I thought we had fixed an issue like this in SP1. Are you sure you have SP1
applied? -- This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Sanjay Gandhi" <SanjayGandhi@discussions.microsoft.com> wrote in message news:8EF047FB-1E50-4524-BDAE-3B112E53693C@microsoft.com... >I completely forgot about my post. > > No there is no http error in the PDF source. I can forward you the PDF > document if needed. The errors just seem to occur at random. This time > around > when I opened a PDF document generated by Reportin Services, it just comes > out blank. In viewer it says 24 pages, but it doesnt go beyond 1st page. > > I read the post by Philippe and I am in a similar scenario. I generate a > file daily every hour. So the next day around, Reporting Services > overwrites > the previous file that it created the day before. I guess I may have to > use > the method you have - create my own scheduler and delete the existing PDF > and > write the new PDF file everytime. > > > "Donovan Smith [MSFT]" wrote: > >> If you open the file in notepad, is there an HTML error at the bottom of >> the >> PDF file? If so, what is the stack trace? You can also find it in the >> server log file in the LogFiles directory. >> >> -- >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> >> "Sanjay Gandhi" <SanjayGandhi@discussions.microsoft.com> wrote in message >> news:8957774A-E840-4A80-9B32-17A6D056F71B@microsoft.com... >> >I am exporting report document to a file share every 1 hour using >> > Subscriptions. Sometimes the PDF document that the subscription created >> > is >> > corrupted. This happens at random. >> > >> > This is the error I get when I open the PDF either in 5.0 or 6.0: >> > >> > In 5.0: >> > "There was an error processing a page. There was a problem reading this >> > document (109)" >> > >> > In 6.0: >> > "There was an error processing a page. There was a problem reading this >> > document (117)" >> >> >>
No I have not yet applied SP1. I will try that out and let you know.
Thanks [quoted text, click to view] "Donovan Smith [MSFT]" wrote:
> I thought we had fixed an issue like this in SP1. Are you sure you have SP1 > applied? > > -- > This posting is provided "AS IS" with no warranties, and confers no rights. > > > "Sanjay Gandhi" <SanjayGandhi@discussions.microsoft.com> wrote in message > news:8EF047FB-1E50-4524-BDAE-3B112E53693C@microsoft.com... > >I completely forgot about my post. > > > > No there is no http error in the PDF source. I can forward you the PDF > > document if needed. The errors just seem to occur at random. This time > > around > > when I opened a PDF document generated by Reportin Services, it just comes > > out blank. In viewer it says 24 pages, but it doesnt go beyond 1st page. > > > > I read the post by Philippe and I am in a similar scenario. I generate a > > file daily every hour. So the next day around, Reporting Services > > overwrites > > the previous file that it created the day before. I guess I may have to > > use > > the method you have - create my own scheduler and delete the existing PDF > > and > > write the new PDF file everytime. > > > > > > "Donovan Smith [MSFT]" wrote: > > > >> If you open the file in notepad, is there an HTML error at the bottom of > >> the > >> PDF file? If so, what is the stack trace? You can also find it in the > >> server log file in the LogFiles directory. > >> > >> -- > >> This posting is provided "AS IS" with no warranties, and confers no > >> rights. > >> > >> > >> "Sanjay Gandhi" <SanjayGandhi@discussions.microsoft.com> wrote in message > >> news:8957774A-E840-4A80-9B32-17A6D056F71B@microsoft.com... > >> >I am exporting report document to a file share every 1 hour using > >> > Subscriptions. Sometimes the PDF document that the subscription created > >> > is > >> > corrupted. This happens at random. > >> > > >> > This is the error I get when I open the PDF either in 5.0 or 6.0: > >> > > >> > In 5.0: > >> > "There was an error processing a page. There was a problem reading this > >> > document (109)" > >> > > >> > In 6.0: > >> > "There was an error processing a page. There was a problem reading this > >> > document (117)" > >> > >> > >> > >
Thanks Donovan,
I think applying SP1 fixed that problem. I will re-post if the problem occurs again. [quoted text, click to view] "Sanjay Gandhi" wrote:
> No I have not yet applied SP1. I will try that out and let you know. > Thanks > > "Donovan Smith [MSFT]" wrote: > > > I thought we had fixed an issue like this in SP1. Are you sure you have SP1 > > applied? > > > > -- > > This posting is provided "AS IS" with no warranties, and confers no rights. > > > > > > "Sanjay Gandhi" <SanjayGandhi@discussions.microsoft.com> wrote in message > > news:8EF047FB-1E50-4524-BDAE-3B112E53693C@microsoft.com... > > >I completely forgot about my post. > > > > > > No there is no http error in the PDF source. I can forward you the PDF > > > document if needed. The errors just seem to occur at random. This time > > > around > > > when I opened a PDF document generated by Reportin Services, it just comes > > > out blank. In viewer it says 24 pages, but it doesnt go beyond 1st page. > > > > > > I read the post by Philippe and I am in a similar scenario. I generate a > > > file daily every hour. So the next day around, Reporting Services > > > overwrites > > > the previous file that it created the day before. I guess I may have to > > > use > > > the method you have - create my own scheduler and delete the existing PDF > > > and > > > write the new PDF file everytime. > > > > > > > > > "Donovan Smith [MSFT]" wrote: > > > > > >> If you open the file in notepad, is there an HTML error at the bottom of > > >> the > > >> PDF file? If so, what is the stack trace? You can also find it in the > > >> server log file in the LogFiles directory. > > >> > > >> -- > > >> This posting is provided "AS IS" with no warranties, and confers no > > >> rights. > > >> > > >> > > >> "Sanjay Gandhi" <SanjayGandhi@discussions.microsoft.com> wrote in message > > >> news:8957774A-E840-4A80-9B32-17A6D056F71B@microsoft.com... > > >> >I am exporting report document to a file share every 1 hour using > > >> > Subscriptions. Sometimes the PDF document that the subscription created > > >> > is > > >> > corrupted. This happens at random. > > >> > > > >> > This is the error I get when I open the PDF either in 5.0 or 6.0: > > >> > > > >> > In 5.0: > > >> > "There was an error processing a page. There was a problem reading this > > >> > document (109)" > > >> > > > >> > In 6.0: > > >> > "There was an error processing a page. There was a problem reading this > > >> > document (117)" > > >> > > >> > > >> > > > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |