Skip to main content
krickstadt
krickstadt
New Participant
May 10, 2018
Answered

Strange error message from FrameMaker 2017 printing to Adobe PDF Printer

  • May 10, 2018
  • 3 replies
  • 1886 views

Hi,

I'm working with FrameMaker 2017 Release (German edition) on Windows 10 Version 1803 and Acrobat DC Pro. When printing to Adobe PDF Printer, FrameMaker shows up with an error message

"The chosen standard printer is not compatible with FrameMaker. (Can not ask for Escape 768.)"

This is my translation of the German error message "Der gewählte Standarddrucker ist nicht kompatibel mit FrameMaker. (Escape 768 kann nicht abgefragt werden.)"

As standard printer Adobe PDF Printer is configured. What could be the cause of that error message? I've already done two "Repair Acrobat DC Pro Installation", which didn't help.

Thanks, Thomas

    This topic has been closed for replies.
    Correct answer Test Screen Name

    Seems to be an error in the new version of Windows 10. Discussion and possible workarounds: Frame 2017 cannot print to PDF or PS or Printer as of April 6, 2018

    3 replies

    Dov Isaacs
    Dov Isaacs
    Brainiac
    June 14, 2018

    Moved to the FrameMaker forum. This discussion has absolutely nothing to do with Acrobat PDF creation.

              - Dov

    - Dov Isaacs, former Adobe Principal Scientist (April 30, 1990 - May 30, 2021)
    Dov Isaacs
    Dov Isaacs
    Brainiac
    May 23, 2018

    On behalf of Adobe Systems Incorporated:

    The problem is a known bug in Microsoft's Windows 10 Version 1803 and has nothing to do with FrameMaker.

    Microsoft is aware of the bug as well as the source of the bug and is working to provide a fix in a forthcoming “Patch Tuesday” update.

              - Dov

    - Dov Isaacs, former Adobe Principal Scientist (April 30, 1990 - May 30, 2021)
    S
    StreamFlow
    Known Participant
    June 13, 2018

    I noticed that you closed out the other thread addressing this topic, telling everyone to chill out and maybe it will be fixed next month.  We can't wait a month to have the program working.  We have 6 reports in progress that are several hundred pages each, representing over a half million in contracts with deadlines that we have to meet.  This is not just a little utility program or game that we can set aside and wait several months for a fix to be issued. 

    I am totally amazed at your cavalier attitude to an issue that can cost your users thousands in lost revenue and customer dissatisfaction when deadlines are not met!

    Dov Isaacs
    Dov Isaacs
    Brainiac
    June 14, 2018

    We are not being cavalier about this at all. At Adobe, we are not at all happy about this and other bugs that have been found in the v1803 update to Windows 10. And we do understand the impact on our users because it also has an impact on our own use of the software (we don't have a secret workaround, believe me!).

    We contacted Microsoft immediately after this issue was reported to us and have been working with them and applying appropriate pressure to get a fix ASAP. They have a fix that we have tested and we are awaiting their decision as to when to include that fix in a Patch Tuesday release.

    Adobe doesn't have source code to Windows and we can't issue a fix on our side. What do you expect us to do further?

              - Dov

    - Dov Isaacs, former Adobe Principal Scientist (April 30, 1990 - May 30, 2021)
    T
    Test Screen NameCorrect answer
    Brainiac
    May 10, 2018

    Seems to be an error in the new version of Windows 10. Discussion and possible workarounds: Frame 2017 cannot print to PDF or PS or Printer as of April 6, 2018

    krickstadt
    krickstadtAuthor
    New Participant
    May 10, 2018

    Thanks a lot. This points me in the right direction. Unfortunately I have removed "C:\Windows.old" after updating Windows 10, so rollback is no alternative for me. Hopefully Microsoft solves that problem asap. In the meantime, a workaround for me is to use the printer driver "Microsoft Print to PDF" (Extension to Windows). I know, that this driver is a poor one, but for my needs, it's sufficient.

    S
    StreamFlow
    Known Participant
    May 23, 2018

    I have the same Escape 768 problem, but it just started today.  I have had the 1803 update for several weeks without any problems.  I tried the CMYK fix and it worked for one print job and now I get the error with RGB or CMYK on all print jobs, for pdf's and all physical printers in the office.  I uninstalled TCS  2017 and reinstalled it.  With the new install, the Adobe DC application will not even install.  The installation program does not give me any errors, it just does not install.  With the new install, when I try to print to a physical printer, I get the same error and then the program crashes.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices