PDF Document Object Error on Save

28 posts, 0 answers
  1. Adam
    Adam avatar
    13 posts
    Member since:
    Jul 2008

    Posted 29 Oct 2010 Link to this post

    We have recently upgraded to the Q2 2010 release of Telerik Reporting and have identified an issue with this version relating to PDF documents rendered by the reporting system.  Users are able to view the documents in Adobe Acrobat, but unable to save them to their local disk -- upon clicking the Save As... and choosing a location, they receive an error that states: "The document could not be saved.  There was a problem reading this document (109)."  When I do a Ctrl-Click to get the details from Adobe, it tells me the following: "Object label badly formatted."

    We have tested this with a couple of different reports and they all behave identically.  One of our developers rolled back to the Q1 version and the issue disappears.

    Is this a bug in the system, perhaps something that we are doing causing this or any other suggestions? (Note, I have examples of the same report from both Q1 and Q2 but cannot upload a PDF here).

    Thanks,
    Adam
  2. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 03 Nov 2010 Link to this post

    Hello Adam,

    Actually this is the first time somebody reports this error and it is not directly related to our product. A quick search shows this error from articles dating back to Acrobat 6 and in most cases it proves to be related with printer drivers. So in this line of thoughts, the downgrade to Q1 which works fine is very strange.

    Anyway try upgrading the drivers on your printer and if the problem persists, prepare a sample runnable project that shows the problem. Once we review it, we would be able to provide more info.

    Kind regards,
    Steve
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. Lamin
    Lamin avatar
    1 posts
    Member since:
    Dec 2008

    Posted 09 Nov 2010 Link to this post

    Hello Steve,

    we also upgraded recently to the Q2 2010 release and we found the same problem. We tested with different version of Adobe, like Adobe 8.1 Prof. and 9.4 Prof extended, Adobe reader 9.4. We got the same error message everytime  we use the option "save as". The system shows Error 109. The regular button in the taskbar to just use "save" shows de-activated.

    I working on a new laptop that runs Windows 7 and it does not work on that machine. I tried it on my old laptop (WIN XP) where I never had problems with saving pdf's under different names. It also does not work on that machine anymore. I visted some other websites (without the telerik component installed) and tried to use the "save as..."functionality and that works fine.

    I asked someone to try it out on a Mac and they had the same problem.

    I downloaded Foxit reader and with this reader I can use  "save as.." and save the pdf under a different name. 

    You are talking about updating printer drivers but what printer drivers can/should you update regarding Adobe in order to fix this problem?

    I visited the Telerik website: http://demos.telerik.com/reporting/product-tags/demo.aspx
    I tried to create a pdf and use "save as..." I could not save the pdf and got the same error message again.

    Than i tried the same at the following link:http://demos.telerik.com/reporting/report-book/demo.aspx
    When I created the pdf and used "Save as..." I could save the pdf without any error.

    To us it looks like the problem comes from the Q2 2010 telerik reporting module since we only have this problem since we upgraded.We did not change anything else.

    Hopefully you can help out on short notice!

    Thanks!
    Lamin  
  4. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 12 Nov 2010 Link to this post

    Hello Lamin,

    As we are unable to reproduce this problem on our end and you and Adam are the only users reporting this issue, we would appreciate if you open a support ticket and attach a sample runnable project that exhibits the problem. Once you do, we would review it and get back to you with more info.

    Sincerely yours,
    Steve
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  5. Adam
    Adam avatar
    13 posts
    Member since:
    Jul 2008

    Posted 12 Nov 2010 Link to this post

    Steve:

    We have been able to duplicate this situation on a couple of reports, though they are in the same project; we will try to create a bare-bones demonstration application with one of the reports using some hard-coded data.  Assuming that still exhibits the same behavior we can open a support ticket using that.

    Thanks,
    Adam
  6. Mike Hobbs
    Mike Hobbs avatar
    20 posts
    Member since:
    Feb 2008

    Posted 17 Nov 2010 Link to this post

    I wanted to report that I too am seeing this error.  It seems that Adobe Reader (free) can save documents fine, but the Adobe Writer/Standard generates the error mentioned in this thread.  Has any cause/solution been found?
  7. Mike Hobbs
    Mike Hobbs avatar
    20 posts
    Member since:
    Feb 2008

    Posted 19 Nov 2010 Link to this post

    I found that rolling back to Q1 2010 of the Reporting component resolves the problem.  I haven't tried the latest version yet.  The version I was using was Q2 2010 which was causing the problem mentioned here.
  8. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 23 Nov 2010 Link to this post

    Hi guys,

    As stated in previous reply, we are not able to reproduce this problem on our end (see attached video) and we would appreciate if you provide us with a sample runnable application that shows the problem.

    Kind regards,
    Steve
    the Telerik team
    Get started with Telerik Reporting with numerous videos and detailed documentation.
  9. Jürg
    Jürg avatar
    1 posts
    Member since:
    Jun 2012

    Posted 24 Nov 2010 Link to this post

    Hello there,

    i also wanted to inform that i have the same issue.

    telerik version: 4.1.10.921

    "save a copy" works in the following dev environment:
    server: Windows Server 2003 R2, Service Pack 2
    Adobe Reader 9, Version 9.4.0

    "save as" does not work in the following test environment:
    server: Windows Server 2003 Service Pack 2
    Adobe Acrobat 8 Standard: Version 8.2.3

    similar to Lamin's case i create the report in a http handler to send it to the browser. If i save the file directly (in the browser dialog) it works fine, but if i open it in acrobat and try to save it there it got the error....

    thanks & kind regards
    Jürg



  10. Joshua Kent
    Joshua Kent avatar
    15 posts
    Member since:
    Nov 2009

    Posted 28 Dec 2010 Link to this post

    I have the same issue, I am generating the report from a Generic Handler (ashx) using the example code provided in your documentation.

    ReportProcessor reportProcessor = new ReportProcessor();
    RenderingResult result = reportProcessor.RenderReport("PDF", CredoOutput, null);
     
    string fileName = result.DocumentName + ".pdf";
     
    context.Response.Clear();
    context.Response.ContentType = result.MimeType;
    context.Response.Cache.SetCacheability(HttpCacheability.Private);
    context.Response.Expires = -1;
    context.Response.Buffer = true;
     
    context.Response.AddHeader("Content-Disposition",
                       string.Format("{0};FileName=\"{1}\"",
                                     "attachment",
                                     fileName));
     
    context.Response.BinaryWrite(result.DocumentBytes);
    context.Response.End();

    Is it possible something else is getting written out to the response stream that is "corrupting" the pdf?

    Thanks,
       Josh
  11. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 29 Dec 2010 Link to this post

    Hi Adam,

    We were able to reproduce the original error when trying to save an exported PDF file with Acrobat Pro 9. The problem does not occur with Acrobat Pro 8 or FoxIt reader, so we would have to investigate what is causing this problem. The issue is logged in our bug tracking system and once we find the culprit, we would address it accordingly.

    Kind regards,
    Steve
    the Telerik team
    Get started with Telerik Reporting with numerous videos and detailed documentation.
  12. Joel
    Joel avatar
    168 posts
    Member since:
    Oct 2006

    Posted 29 Dec 2010 Link to this post

    We recently rolled out an update and now our users with acrobat pro are reporting the same symptoms. Free reader is unaffected. Will this thread be updated when there is a fix, or is there another location to watch? We were researching the error Assuming it was not a telerik problem and ran across a few instances of it in acrobat forums. The error seems to come from the document template and the document being the same size and that is not allowed. Apparantly they have to differ by 2 charachters to prevent the error? Not sure what that means exactly, but thought it may help.
  13. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 30 Dec 2010 Link to this post

    Hi guys,

    Yes, this thread would be updated once we resolve the problem. Sorry for the inconvenience once again.

    Best wishes,
    Steve
    the Telerik team
    Get started with Telerik Reporting with numerous videos and detailed documentation.
  14. Joel
    Joel avatar
    168 posts
    Member since:
    Oct 2006

    Posted 30 Dec 2010 Link to this post

    Thank you.  Our users are experiencing it on Acrobat Pro 8.1.  Reverting to Q1 2010 release has stopped the error.
  15. Adam
    Adam avatar
    13 posts
    Member since:
    Jul 2008

    Posted 06 Jan 2011 Link to this post

    Steve:

    Thanks for your help and persistence in reproducing the problem; we had planned to try to work in time to create a bare-bones sample project this week but I saw that you were able to reproduce it on your end.  If you do still need a sample or wish us to test out any solutions then please let me know.

    Thanks again,
    Adam
  16. John Hughes
    John Hughes avatar
    15 posts
    Member since:
    Mar 2010

    Posted 06 Jan 2011 Link to this post

    I am running into this problem as well using the Q3 2010 version.

    Thanks,

    John
  17. Steve
    Steve avatar
    19 posts
    Member since:
    Nov 2010

    Posted 19 Jan 2011 Link to this post

    I too am running into this problem using Q3 2010 TR.    Web Application using VS 2010.

    Summary:

    - Print to PDF - works.

    - Export to PDF, then choose Save - works.

    - Export to PDF, then choose Open, then when PDF on screen try to save - you get:

        "Document could not be saved.  There was a problem reading this document (109)."

  18. christine
    christine avatar
    17 posts
    Member since:
    Jul 2010

    Posted 03 Feb 2011 Link to this post

    I am also experiencing this problem.
  19. Vasu
    Vasu avatar
    14 posts
    Member since:
    Jan 2006

    Posted 05 Feb 2011 Link to this post

    I am experiencing the same problem and client is also reporting the same issue.
  20. Robert
    Robert avatar
    1 posts
    Member since:
    Nov 2010

    Posted 01 Mar 2011 Link to this post

    I'm having the same issue .... With Acrobat 8 .....
  21. Michael Gois
    Michael Gois avatar
    17 posts
    Member since:
    Oct 2008

    Posted 22 Mar 2011 Link to this post

    Hi

    I am also receiving this error using Acrobat X 10.0.0. Any ideas when a solution for this is expected to be found?

    Thanks
  22. Aaron Bowman
    Aaron Bowman avatar
    3 posts
    Member since:
    Nov 2009

    Posted 04 Apr 2011 Link to this post

    Please add me to the list of people waiting for this issue to be fixed.
  23. Jill
    Jill avatar
    3 posts
    Member since:
    Sep 2010

    Posted 21 Apr 2011 Link to this post

    I too am experiencing this problem.  Is there a fix yet?
  24. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 21 Apr 2011 Link to this post

    Hi guys,

    We've pinpointed the cause for the problem and this issue would be fixed in the upcoming Q1 SP1 (beginning of May).

    Thank you all for the patience.

    Regards,
    Steve
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  25. Guangxi Wu
    Guangxi Wu avatar
    2 posts
    Member since:
    Nov 2009

    Posted 05 May 2011 Link to this post

    When will Q1 SP1 be released? We are having the same problem with Q1 2011. We are scheduled to release the report in the next week. Is it possible to have SP1 in the next a few days?

    Thanks,

    Guangxi
  26. Joel
    Joel avatar
    168 posts
    Member since:
    Oct 2006

    Posted 09 May 2011 Link to this post

    Is this fixed in internal build  Telerik_Reporting_5_0_11_328_DEV.msi by any chance?  There are a lot of features we would like to use that have been implemented over the last 16 months and if this release finally fixes it, I would like to start our new report leveraging those features rather than  sticking with Q1 2010 for yet another report?
  27. Peter
    Admin
    Peter avatar
    1615 posts

    Posted 10 May 2011 Link to this post

    Hello,

    Telerik Reporting Service Pack 1 should be already available for download in your accounts. Here is a link to the release notes.

    All the best,
    Peter
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  28. Joel
    Joel avatar
    168 posts
    Member since:
    Oct 2006

    Posted 12 May 2011 Link to this post

    It is working correctly now with Reader.  Thank you for the upgrade.
Back to Top