Skip navigation
Currently Being Moderated

FrameMaker 10 not printing PDFs

Apr 14, 2011 2:59 PM

When I try to print to PDF on FrameMaker,  I get the "printing book" dialog box but nothing happens....the PDF is not created and no errors are reported. If I choose to print to poscript, open Acrobat Distiller, the PDF is generated there.

 

I recently upgraded to FrameMaker and Acrobat 10. I didn't have any issues on 9. I'm currently running both versions of FrameMaker on my PC for now.

Is this a Windows 7 issue? My co-worker has both versions of FrameMaker running with acrobat 10, but on an  XP system and everything seems fine on his end.

 

Thanks,

 
Replies 1 2 Previous Next
  • Currently Being Moderated
    Apr 14, 2011 6:20 PM   in reply to az_writer22

    I'm having the same problem. Windows 7 64-bit, 12 GB RAM and a fast processor.  TCS3 10.0.338. Updated Acrobat Pro X to 10.0.1, then 10.0.2.  I cannot print to PDF, but can print to a PostScript file, whiich distills successfully. I cannot save to PDF.

     

    I tried this on Server 2008 R2 just to see what would happen, and got the same results (I know FM 10 is not supported there). I have also uninstalled and re-installed TCS3 on Windows 7.

     

    I have a trial download of TCS3 on my work machine, a laptop with 4 MB of RAM running XP Pro SP3. It works fine there. I have used the same printer settings as this machine on my 64-bit system; no go. I have also tried updating the printer driver, adding a printer instance, changing ports, etc. I don't want to have to print to file, I just want it to work.

     

    Anyone?

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 14, 2011 10:55 PM   in reply to az_writer22

    This is a Win 7, 64-bit specific issue in "Print To PDF" route. We are actively looking at it.

     

    There are couple of ways to workaround the problem.

     

    • Use "File --> Save As PDF" option to directly create PDF from the source.
    • Use "Print to PS" followed by Distiller

    Regards,

    Rajat Bansal

    Sr Engineering Manager,

    Adobe FrameMaker

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 15, 2011 12:24 AM   in reply to az_writer22

    I think the issue is with "Print to PDF" route not with "Save as PDF" route.

     

     

    -Harsh

     

    Message was edited by: Harsh@FrameMaker

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 15, 2011 3:44 AM   in reply to Rajat Bansal

    Thanks, Rajat.  I wish you success.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 15, 2011 6:47 AM   in reply to az_writer22

    I get the "printing book" dialog box but nothing happens....the PDF is not created and no errors are reported.

     

    Is there any chance that the filename, or any of the directory names above it, contain a comma?

     

    If so, change the commas to underscores and try again.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 15, 2011 7:01 AM   in reply to Error7103

    Sounds like this is a now-known Win7 64bit issue that Adobe is working on.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 15, 2011 7:30 AM   in reply to Jeff_Coatsworth

    Sounds like this is a now-known Win7 64bit issue that Adobe is working on.

     

    Quite likely. But until the comma-in-the-Windows-filepath problem is fixed (and it doesn't appear to be fixed in FM9), it's going to continue to pop up, and can easily be mistaken for some other problem, and cause substantial time wasting. It can also prevent you from confirming that some other problem IS fixed or worked around.

     

    As I recall from years ago, it took me quite a while to figure out that what had changed between "can print" and "can't" was a trivial change of a single otherwise legal filename character. There are complaints on the old newsgroup comp.text.frame about this, dated 2003, and claiming that the problem was at least 2 years old then. So this probably has been there since FM6 if not earlier.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 15, 2011 7:55 AM   in reply to Error7103

    I've never used a comma in a file name or path in my life; I'm curious as to why anyone would do so.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 15, 2011 8:40 AM   in reply to Jack DeLand

    I've never used a comma in a file name or path in my life; I'm curious as to why anyone would do so.

     

    Multiple versions and archival copies of the same document.

     

    We routinely generate two versions of the .ps output:

    12345M_web.ps

    and

    12345M_print.ps (visible navs in doc suppressed)

     

    Because the platform is Solaris, we'd gotten into the habit of using:

    12345M,web.ps

    We'll eventually have to migrate to Windows, and unless the comma bug is fixed by then, we'll have problems doing this.

     

    When we release a new version of a manual, we make a second copy with a time-stamped filename, for archival purposes.

     

    "12345M.pdf" is always the current version (of the web version).

    The document source directory might also contain:

    12345M_1999-03-17_jfk.pdf

    12345M_2002-04-03_gwb.pdf

    12345M_2010-07-23_ati.pdf

    where "ati" are the Author's Three Initials.

     

    Memorializing the vintage in the file name matters because we have multiple versions of the same document, and the directory timestamp isn't necessarily preserved in network copying. The author info is for knowing who to blame.

     

    There are well-known characters [e.g. /\:;] that need to be avoided because they are legal on some OS'es and not on others. But I'd expect commas to work [now] because they apparently haven't been "illegal" since NetWare on DOS.

    _______

    Frame does work fine with spaces in filepath. Personally, I consider spaces in filepath to be extremely unwise.

     
    |
    Mark as:
  • Currently Being Moderated
    May 6, 2011 4:15 AM   in reply to az_writer22

    Hi there,

     

    it is possible to create PDFs with FrameMaker 10 and an Extended Script named PDF Tools. Actually this script allows you to combine several FM Documents with different paper sizes and/or formats (landscape or portrait) and the printing in PDF works perfectly fine.

    System requirements are Win XP, Win7 (x86) and Win7 (x64).

     

    - Maike

     
    |
    Mark as:
  • Currently Being Moderated
    May 18, 2011 11:08 AM   in reply to Rajat Bansal

    I am having these issues too, and more.  I am migrating a large FrameMaker 8 legacy to FM10 on new 64-bit Mobile Workstations running Windows 7.  FM10 displays files OK but when I "Save as PDF", Console complains Tahoma font family is possibly corrupt.  The resulting PDF diplays in Acrobat with square symbols in place of Tahoma text.  I tried replacing Tahoma with old WinXP-Tahoma.  No luck.  I replace Tahoma with another font; same problem wi the other font.  In Acrobat, you cannot scroll past the square-symbol areas without crashing the NVIDIA display driver, which eventually recovers itself.

     

    On top of that, FM10 frequently does not refresh when performing an operation (as above), rendering it inaccessible.  Using Windows Task Manager to alternately minimize, then mazimize restores the screen and functionality.

     

    What is happening at Adobe?  Was FM10 not tested against Windows 7 in both 32/64-bit modes?  How can Adobe leave paying customers hanging?  The thread elsewhere in this forum is mostly dated in April; it is now past mid-May and I cannot find any signs of life at Adobe as to a quick and immediate resolution.

     

    This is a show stopper!  Does FM10 support Windows 7?  Does FM10 support 64-bit O/S?

     
    |
    Mark as:
  • Currently Being Moderated
    May 18, 2011 11:45 PM   in reply to TekCom

    Hi,

     

    indeed it's a small challenge to generate a PDF with FM 10.

     

    On XP, you will need a Microsoft Patch. FM 10 works fine on Windows 7 (x86/x64), but the CMYK/RGB switch is also a challenge if you work with some imported PDF, EPS or font combinations. Also, it's not so easy if you want to print a pdf, and select some files in a book.

     

    From what FrameMaker release does your input come, really from FM 8 or from an older release like 5.1? Did you choose Print CMYK as RGB at PDF-Joboptions? Try Refresh: CTRL-L

     

    - Maike

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2011 12:46 PM   in reply to Rajat Bansal

    We're seeing this behavior in FM10 on Vista 64 bit also.

    Rajat Bansal wrote:

     

    This is a Win 7, 64-bit specific issue in "Print To PDF" route. We are actively looking at it.

     

    There are couple of ways to workaround the problem.

     

    • Use "File --> Save As PDF" option to directly create PDF from the source.
    • Use "Print to PS" followed by Distiller

    Regards,

    Rajat Bansal

    Sr Engineering Manager,

    Adobe FrameMaker

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2011 5:53 PM   in reply to lllearner

    The latest FM10 patch fixed my Win 7 64-bit problem; maybe it will help Vista.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 21, 2011 3:58 AM   in reply to az_writer22

    With 10.0.1 update, this issue has been resolved for all 64-bit versions (Vista / Win7 / XP).

     

    Regards,

    Rajat Bansal

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 21, 2011 5:41 AM   in reply to lllearner

    I wonder what "actively looking at it" means in real Adobe time.  Further to my post, we discovered with 2 identical laptops running FM10 on 64-bit CPU, Win7 ... one has the Print to PDF problem, the other does not.  Go figure.

     

    Also, both FM10 instances crash regularly.  Multiple suspects.  Sometimes, it seems a particular anchored PNG or PDF is the culprit; sometimes, it seems a PNG on the master page is the villain.  The PNGs are 'flat' and there is nothing complicated about them.  Other times, the book file converted from FM8 is the problem, requiring it to be scrapped and rebuilt from scratch in FM10; on the other laptop, FM8 books convert to FM10 without a hitch.  It must be gremlins.

     

    Print to postscript, then Distill, works flawlessly.

     

    Save As PDF still produces output with gibberish text/symbols substituted for certain font families.  Change the offending font family to another in the FM source and you get another font suddenly not liked by Adobe.

     

    There may be all sorts of neat DITA/XML improvements and other frills, but this FM10 seems poorly done.

     

    Any other horror stories out there?

     

    Cheers,

    Mike

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 21, 2011 5:56 AM   in reply to TekCom

    > There may be all sorts of neat DITA/XML improvements and other frills, but this FM10 seems poorly done.

     

    > Any other horror stories out there?

     

    I have to agree with Mike on this one. I have had more crashes with FM10 in the two weeks since installing it than I have had in several years of using FM8.

     

    Right now, I have two books that have been consistently crashing when I save after an update. I "think" I may have solved the problem by saving the books as FM10 MIF and then back into book format. I've had other crashes that seem to be related to inserting a cross-reference. And a couple of other crashes that just seem based on general ornerieness.

     

    This does not inspire confidence in a product, that up until this release, was almost bulletproof.

     

    Regards

    Keith

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 21, 2011 6:25 AM   in reply to TekCom

    It means they've already fixed it - see Rajat's post on the 10.0.1 patch. I suggest you install it on all your machines and report back.

     

    FWIW - I've been running FM10 (within TCS3) since it came out & haven't crashed once. I started authoring in FM9, so none of my books/docs were pre-9. I'm running XP SP3.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 21, 2011 7:37 AM   in reply to Jeff_Coatsworth

    I'm running the 10.0.1 update.

     

    I just had several crashes this morning. They all seem to be related to updating a book and then saving. I've been working with track text edits on. I may try disabling that feature to see if it makes any difference.

     

    Regards

    Keith

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 21, 2011 7:53 AM   in reply to ksoltys

    Great - I assume you have no problems printing to PDF then, right?

     

    With regard to your crashing - maybe you need to start a new thread on that issue. Then you can give us all the details about your O/S, memory, what you're doing in FM, and if you're getting hard errors.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 21, 2011 7:54 AM   in reply to Jeff_Coatsworth

    Thanks for the fix interpretation.  However, the Adobe updater installed 10.0.1 when it was available a few weeks ago and a recent patch too (10.0.1.402).  So, I am still getting the Save As PDF problem, along with crashing.

     

    Regards,

    Mike

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 21, 2011 8:10 AM   in reply to TekCom

    FWIW, the patch numbers and point release values (pXXX numbers) have all been rolled into one starting with FM10. So  the 10.0.1 patch = 10.0.1.402 from the Help > About screen. The patch number will now always be shown in the FM release number found on the Help screen.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 21, 2011 8:31 AM   in reply to TekCom

    Ok, leave the crashing aside - spin that off into a new thread as I advised Keith to do. So in an earlier post you said that you've got 2 laptops with 1 working when doing Print to PDF and 1 not? There's got to be some difference going on. When you do the Print to PDF, what's happening?

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 21, 2011 8:43 AM   in reply to Jeff_Coatsworth

    Will do (new crashing thread). The crashes are random.  It may take a few days to post again with details.

     

    Hands full right now and cannot regenerate book and attempt Save As PDF.  I did not keep previous wonky PDF; basically, the PDF results seemed better recently than before the patch (before-patch, there were many paragraph/character tags showing gibberish/symbols substituted; after-patch, there was only one character tag (font family) affected).  I'll post again soon to this thread.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 21, 2011 9:36 AM   in reply to TekCom

    Mike,

     

    I would like to work with you to investigate the issues that you are facing. I will need some more information on the same to debug it. Please see if you can share some test files on which you are facing issues at rabansal@adobe.com.

     

    Also please check ON "Convert CMYK Colors to RGB". FrameMaker has some issues related to fonts (fonts getting dropped / replaced) when this setting is turned off.

     

    Regards,

    Rajat Bansal

    Adobe FrameMaker Team

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 21, 2011 10:29 AM   in reply to Rajat Bansal

    Rajat,

     

    Thanks for the reply and offer.  Regrettably, I cannot share company source files.  I am in the midst of some testing: I am finding some text tagged with certain character tags show up as gibberish in files but seem to work OK in other cases; it is affecting different char-tags, different fonts.  I'll try the CMYK/RGB suggestion and get back to you.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 21, 2011 10:39 AM   in reply to TekCom

    Rajat,

     

    It works!  Select the Convert CMYK Colors to RGB check box in Settings, and the output is fine.  The connection with the various affected char-tags is that each has a custom (CMYK) color definition (as per corporate branding specifications).

     

    Thanks for the help.  Thanks to Jeff Coatsworth too.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 26, 2012 6:12 PM   in reply to az_writer22

    I am using FM 10, experiencing problems in creating a pdf of a  book. I use Adobe PDF as my print driver. The error said that a font,

    HelveticaNeueCond, was not available, and could not be embedded. I had never heard of this font as being in my book, but I downloaded it and installed it on my C drive in my WINDOWS/Fonts folder. Still got the same error!

     

    Also a pdf was made up to a certain page and then it failed. When I tried pdf ing that failed page, it worked. Then I tried to pdf the pages in between and it failed in a different spot.

     

    This failure makes no sense.

     

    I need help!

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 6:07 AM   in reply to H_Label_D

    I too have been having issues with Frame 10 and getting an internal error when I tried to create a PDF using the “print” method. After trying to resolve, the thing that appeared to work was removing some of the multitude of fonts in my fonts directory. We use a font named Knowledge Light and that was the font that wasn’t embedding and one of the last ones loaded. Using XP and I believe there may be a font limitation. Helvetica Neue Cond may be a font used in the ini substitution table (Found in your FrameMaker folder as Maker.ini). Hope this helps. Linda Hume

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 8:56 AM   in reply to H_Label_D

    It's not clear if you're creating the PDF by using FM's SaveAsPDF or printing directly to the AdobePDF printer instance or creating a postscript file and then manually distilling. Also, is this error being reported by Distiller or FM?

     

    Have you patched your version to FM10.0.2? This addressed many PDF issues especially if you are using the SaveAsPDF route with the default setting for "Convert CMYK Colors to RGB" (i.e. unchecked).

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 9:08 AM   in reply to Arnis Gubins

    I’m no long having the problem since I cleaned out my fonts list. Another lady was the one having a problem. I was responding to her query.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 19, 2012 3:31 PM   in reply to az_writer22

    I have exactly the same problem. "Save As" works for individual files, but large books with multiple files take FOREVER. With Frame10 on WinXP a 100 page book took less than a minute, now I can't make a PDF at all. If I print to the PDF printer nothing happens. If I print to PS it also takes forever.

     

    Adobe has to fix this!!!!!

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2012 4:27 AM   in reply to Clint Owen

    @Clint Owen - first off, are you all patched up in FM10? What o/s are you using? If WinXP, have you applied the MS Hotfix? The fact that when you print to the Adobe PDF printer instance, nothing happens, leads me to believe that something may have damaged your install of Acrobat. Are you running the standalone version of FM with the "headless" Distiller or do you have FM and Acrobat as part of the TCS or separate point products?

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2012 9:39 AM   in reply to Jeff_Coatsworth

    Thanks for the feedback. I am on Windows 7, 64 bit, with FrameMaker 10 and Acrobat X Standard. I just installed the FM 10.0.2 patch. Now when I start to print a book, it seems to start normally, but takes an interminable amount of time, on the order of 5 minutes per page, even for simple text pages. This is a major hindrance to my work. Thanks

     

     

     

     

     

    Clint Owen | Sr. Technical Writer | Crane Aerospace & Electronics | +1 425 743 8674 | Fax: +1 425 743 8113

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2012 9:44 AM   in reply to Clint Owen

    Something's still wrong - it shouldn't be taking that long. Remind me - are you printing to the Adobe PDF "printer" or Save As PDF?

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2012 9:55 AM   in reply to Jeff_Coatsworth

    I have tried it both ways and every combination that I can think of. I am printing the book, to end up with one PDF that combines all of the component files, as I have been doing for 11 years. For a small book with two files “Save As” seems to work OK, but for a large manual with 20 files it just crawls, whether I “Print To” or “Save As”.

     

     

     

     

     

    Clint Owen | Sr. Technical Writer | Crane Aerospace & Electronics | +1 425 743 8674 | Fax: +1 425 743 8113

     
    |
    Mark as:
1 2 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points