Skip to main content
M
markw69566490
Known Participant
April 10, 2018
Answered

Frame 2017 cannot print to PDF or PS or Printer as of April 6, 2018

  • April 10, 2018
  • 17 replies
  • 27124 views

Since a major update to Windows 10, installed April 6 2018, I cannot generate a PDF. Nothing happens. When trying to output to PS of send to a printer, I get the error dialog - Cannot print because the selected default printer is not compatible with FrameMaker. (Cannot query escape 768.) I have Creative Cloud tools as well, in particular Acrobat DC. Running Windows 10, Version 1803, OS Build 17133.1

    This topic has been closed for replies.
    Correct answer Matt-Tech Comm Tools

    Hi Mark,

    It was nice to chat with you in our screen session.

    Glad we could solve your problem with Save as PDF by choosing the CMYK option instead of RGB in the PDF Setup options.

    I wish I could give you a solid reason why this option makes a difference, I just know from experience that it's the more reliable choice for producing PDF from FrameMaker, and why it's part of the post I referred to earlier.

    17 replies

    T
    thanh-liemh66980277
    Participant
    July 25, 2018

    Hi,

    Just updated Win10 with the latest fix (KB4340917) for this issue for FrameMaker 10. PDF printing is working fine on version 10 too.

    Regards,

    Kaalki2
    Kaalki2
    Known Participant
    July 23, 2018

    Hello,

    I have this same problem, but the Correct Answer posted at the top of this thread doesn't work for me . . . The PDF Setup dialog box doesn't have the RGB/CMYK selections. I'm using FM 12 on Windows 10 Pro Version 1803 Build 17134.165.

    Are there any workarounds for version 12 while we wait for the fix from Microsoft? Thanks.

    Dov Isaacs
    Dov Isaacs
    Legend
    July 23, 2018

    The fix from Microsoft is expected tomorrow, July 24 as part of a significant “Patch Tuesday” update to Windows 10 version 1803.

              - Dov

    - Dov Isaacs, former Adobe Principal Scientist (April 30, 1990 - May 30, 2021)
      Z
      zacksalfred
      Known Participant
      July 24, 2018

      Halleluja. Will Adobe be testing all know issues before giving the all-clear?

      A
      aprils44061206
      Participating Frequently
      July 17, 2018

      After having struggled with this issue for months, my colleague and I finally found a couple things that work.

      We can now generate PDFs with no problems at all!

      #1 We had IT remove Windows 1803 from her computer and install the previous Windows version. This was a more "drastic" solution.

      #2 I changed all the settings per the blog article "PDF Tips and Tricks." There is not rhymm or reason as to why this worked, but it did and it only took about 15 minutes to incorporate the suggestions. FrameMaker PDF Tips and Tricks - Tech Comm Tools

      PS I tried the "Windows Insider Program" suggestion per a previous post and it has been absolutely AWFUL. It has made my FrameMaker app run like pure crap. Worst suggestion ever. Thanks Microsoft for royally screwing things up AGAIN.

      kinabalu2
      kinabalu2
      Known Participant
      June 30, 2018

      I'm running FrameMaker 8.0p277 under Windows 10 Vsn 1803 (OS build 17134.137) and also can no longer create a pdf file even trying all the strategies outlined above. Distiller works with other programs and I have been creating pdf's from this setup for years now.

      I tried rolling back the Windows Update but this is no longer an option for me as the files for the previous update are only kept for 10 days and that has passed. This is very frustrating as I'm truly stuck now, unable to create a pdf, waiting for a fix from Microsoft or Adobe which as of today, hasn't arrived.

      Any idea when the fix will be released?

      David

      Dov Isaacs
      Dov Isaacs
      Legend
      July 1, 2018

      The problem was caused by Microsoft and the fix from Microsoft will likely be released at the end of July.

                - Dov

      - Dov Isaacs, former Adobe Principal Scientist (April 30, 1990 - May 30, 2021)
      alexanderb22010573
      alexanderb22010573
      Participant
      July 3, 2018

      Dear Mr. Isaacs,

      is there any workaround for FM12 on Win10?

      Thanks.

      Alex

      M
      markw69566490Author
      Known Participant
      June 19, 2018

      Amitoj,

      As the original poster of this thread, I say thinks for the the interim fix. I just swapped FrameMaker.exe files using the ZIP package you have provided and now I can produce a valid PDF file using save as PDF with the RGB option. Links are there, vector graphics are there, and math equations are not clipped, as was the case when using the CMYK option.

      Now that I have done this, do you recommend swapping back to the original FrameMaker.exe when the Win10 patch finally arrives? Perhaps you will update us when the time comes.

      Thanks

      Mark Wickert

      A
      Adobe Employee
      Amitoj
      Adobe Employee
      June 19, 2018

      Hi Mark

      Thanks for update. In the technote executable that has been shared, we have bypassed the same in such a fashion that as and when Microsoft releases another update with this fixed, same executable as the one in technote should start working with the printer escape function. You may not be required to uninstall and reinstall FrameMaker and then apply all updates to get it working again.

      Regards

      Amitoj Singh

      T
      TeraRecon
      Known Participant
      June 12, 2018

      This did not work for me - I suddenly starting getting this message on 6/11/2018. I'd last printed a book to PDF on 6/6/2018. So I don't think it is linked to a Windows update on 4/6/2018. I've tried to repair the Adobe DC installation but I still get the error message. So now what do I do?

      Thanks!

      A
      ADocs
      Known Participant
      June 12, 2018

      Sorry Adobe, but I'm a self-employed freelancer and I can't put up with any more of this time wasting and having to work-around all the time. I installed a trial version of Foxit PhantomPDF and it does everything I need at the moment, all my fonts and graphics print 100% as expected. The only real setback as far as I can see is the lack of automatic generation of bookmarks from headings etc. But for straightforward document publishing I'll quite happily use it until the 'big boys' sort themselves out. Microsoft are not making any friends over this.

      I have an old WIN7 machine sitting idle somewhere here that might just see the light of day again!

      Matt-Tech Comm Tools
      Community Expert
      Matt-Tech Comm ToolsCommunity Expert
      Community Expert
      June 12, 2018

      I've managed to stay away from the Win update problems thus far, but will look up PhantomPDF as a temp solution if I run into any problems before Microsoft gets their act together.

      -Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant
      S
      StreamFlow
      Known Participant
      May 23, 2018

      I tried your solution and I was able to save as a pdf one time.  After that It goes back to the same error message even with the CMYK box ticked.  Also, I now get the   "Cannot Print ..... escape 768"  error when i print to ANY of our physical printers as well.  When I click OK on the error message dialogue box, FM crashes.  I am now dead in the water with a project that is already late!

        T
        TeraRecon
        Known Participant
        June 12, 2018

        This is my experience as well.

        Jeff_Coatsworth
        Community Expert
        Jeff_CoatsworthCommunity Expert
        Community Expert
        June 12, 2018

        You probably just got the Win10 1803 update pushed out to you. The only solution until MS issues their fix is to roll back to 1709.

        Dov Isaacs
        Dov Isaacs
        Legend
        May 22, 2018

        On behalf of Adobe Systems Incorporated ...

        As of today, Tuesday, May 22, 2018, I have received information that Microsoft has indeed discovered the source of the problem in its own code that was modified immediately prior to the release of Windows 10 Version 1803. The code change was not made to any other version of Windows.

        Microsoft recognizes that this is a high severity bug that they are working on a fix for to appear in an upcoming Patch Tuesday update to Windows 10 Version 1803.

        Thanks to everyone who reported this problem and provided the information necessary to properly describe it to Microsoft.

                  - Dov

        - Dov Isaacs, former Adobe Principal Scientist (April 30, 1990 - May 30, 2021)
          M
          markw69566490Author
          Known Participant
          May 22, 2018

          Dov and Others,

          Wow! This is great news. I never really look forward to patch Tuesday, now I am excited.

          Mark

          Dov Isaacs
          Dov Isaacs
          Legend
          May 21, 2018

          On behalf of Adobe Systems Incorporated:

          There appears to be a number of “issues” with printing, especially if any OpenType CFF fonts are used, with the Windows 10 Spring 2018 version 1803. However, the issue described in this thread is not one that we understand yet.

          It would be most helpful if the OP could try printing to Adobe PDF making sure that the Rely on system fonts only option is not enabled. Please let us know whether the problem still occurs or not.

          Microsoft is already aware of this thread on the Adobe Forums!!!

                    - Dov

          - Dov Isaacs, former Adobe Principal Scientist (April 30, 1990 - May 30, 2021)
          krickstadt
          krickstadt
          Participant
          May 21, 2018

          Dear Dov,

          I'm not the OP, but I have tried to print with the environment you described. Here are some screenshots (sorry, that it is the German version, but you may get the point):

          Hope, that helps.

          Kind regards, Thomas Krickstadt

          Dov Isaacs
          Dov Isaacs
          Legend
          May 21, 2018

          It does, thank you. The font option doesn't seem to be the variable causing the problem!

                    - Dov

          - Dov Isaacs, former Adobe Principal Scientist (April 30, 1990 - May 30, 2021)
          L
          lenahanson
          Inspiring
          May 16, 2018

          We have the exact same problem, but with FrameMaker 7.2. Cannot print to any "real" printer or to any pdf printer. The problem is that the version of pdf-writer (or FM) we have doesn't have any settings for RGB or CMYK, like in the screen shots above. The problem is on my colleagues computer, I have not yet installed the Windows update. AND I WILL NOT as I print a lot every day. He only needs it sometimes.

          PS. I have tried all kinds of "PDF Job options" including the RGB and CMYK. Doesn't work.

          Matt-Tech Comm Tools
          Community Expert
          Matt-Tech Comm ToolsCommunity Expert
          Community Expert
          May 16, 2018

          Hi Lena,

          The screenshot with the RGB/CMYK option is from the Save as PDF route.

          Can you please visit and follow ALL the steps listed at http://techcommtools.com/framemaker-pdf-tips-and-tricks/

          http://techcommtools.com/framemaker-pdf-tips-and-tricks/

          They have worked for many folks, and should work for you as well.

          Specifically, the Rely on system fonts only; do not use document fonts option seems to be hanging up most folks after a recent Win update. This option should be deselected, as in the screen below.

          -Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant
          Show more replies
          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices