hexagon logo

PDF printing pop up even with printing turned off

I'm not sure if someone on another shift has possible turned something on but when I came in today, everytime I execute a feature using ctrl U/Q at the end I get the printing prompt below. Printing is turned off under File>Printing>Report Window Print Setup. We typically just produce .rtf and .dmo and rarely use pdf. Any idea how I can turn this off? 2022R1 is what we're using if that matters.

Attached Files
  • sounds like the "AMYUNI" issue

    open settings editor

    FIND "amyuni"

    Entry Name: DoNotUseAmyuniRTF
    Entry Type: Whole Number to specify RTF output option. Default value is 0.
    amyuni set value to 0

    DoNotUseAmyuniRTF is used to let pcdmis output RTF output in a more plain text output which allows 3rd party RTF parsers to work.
    This is mostly used when dimensions are being output in plain text mode. Not all reporting objects (such as the CAD reporting object,
    nor Text object for page number) do not output in this format.

    Output Option Key:
    0 - use Amyuni to generate the RTF. To do so, they generate a PDF and convert to RTF. Mostly images which result in a large file.
    RTF output uses Amyuni RTF output.

    1 - use the output setting at start of execution to determine what RTF out to use. People who do not use a PRINT command can use this.
    RTF output uses the old style RTF if you have selected the RTF output option via the Report Print Options dialog box before the program was executed.
    Setting the PRINT/REPORT command to RTF will not work correctly for this value.

    2 - force pcdmis to use MS RTF control to generate RTF output. People who use the PRINT command to output plaintext RTF use this.
    RTF output uses the old style RTF even if you have not set the option to “Print to RTF” in the Report Print Setup dialog box before the program was executed.
    This is useful for the Blade program where the wrong control would be used for reporting resulting in nothing being output if the flag was set to 1.
    Under all conditions the correct text object is used to display text in the report window.​
  • {"data-align":"none","data-size":"full","title":"2023-03-27_14-43-01.jpg","data-attachmentid":528675}

    its seeing it to print to this last location. thats why.


    It's not checked so it's not going any where...if it was checked it would print to that printer.
  • KatmandudaMeow No. That is not it. See my response to you below. This is now sounding like a Amyuni printer driver issue.
  • The Concatenate on the dialog indicates it is an Amyuni dialog being displayed. There is a registry setting that needs permissions.
    Search for Amyuni to find it as I can’t remember it.



    For future reference the registry setting is H_KEY_CURRENT_CONFIG/SOFTWARE/PCDMIS 50 CONVERTER the logged in PC user needs to have full access rights to this registry setting to allow print commands to work in Windows10​
  • So to update, I went into settings editor and Amyuni is set to 0. Also under save/print report its now set to PC-DMIS 50 Converter. With printing turned off, I'm still getting the PCDLRN pop up every time it executes a feature/features using CTRL U/Q or I cancel.

    Attached Files
  • So to update, I went into settings editor and Amyuni is set to 0. Also under save/print report its now set to PC-DMIS 50 Converter. With printing turned off, I'm still getting the PCDLRN pop up every time it executes a feature/features using CTRL U/Q or I cancel.


    Uninstall and reinstall the PDF drivers.

    Located in: C:\Program Files\Hexagon\PC-DMIS {Your Version}\PDFDriverInstallFiles

    PCDMIS should not be loaded when performing the next 2 steps.
    BatFileInstallPDF50.zip: contains the needed files

    1) Removing the previous drivers
    BatFileInstallPDF50.zip contains InstallPDF50.exe and UnInstallPDF.bat.

    Unzip these files to a temporary location. Double click on the UnInstallPDF.bat file.
    A dialog should be displayed saying the pdf driver is removed. This will remove other instances of the driver if they are present.
    Close the dialog.
    Close the COMMAND screen by pressing ENTER.
    (added instruction) Reboot the Computer.

    2) Installing the PDF Suite drivers
    Unzip the BatFileInstallPDF50.zip files to the pcdmis directory.
    There is also an UnInstallPDF.bat file which may be used in Step 1 above.
    Double click on the InstallPDF50.BAT.
    A dialog should be displayed saying the driver is being installed.
    Close the dialog.
    Close the COMMAND screen by pressing ENTER.
    (added instruction) Reboot the Computer.​
  • Did you check the registry setting mentioned above for permissions?

    The Concatenate on the dialog indicates it is an Amyuni dialog being displayed. There is a registry setting that needs permissions.
    Search for Amyuni to find it as I can’t remember it.


    For future reference the registry setting is H_KEY_CURRENT_CONFIG/SOFTWARE/PCDMIS 50 CONVERTER the logged in PC user needs to have full access rights to this registry setting to allow print commands to work in Windows10​

    1. you cannot (or should not try to print directly to the PCDMIS Converter or Amyuni as a printer. Amyuni is for PDF/RTF output and pcdmis must provide a license to print to it.
    2. The Report Output dialog above is used to manually print the report to an output type. Again, pcdmis will internally use Amyuni for file PDF/RTF output.
    3. The output is generated at end of execution based on either a PRINT command or File/Printing/Report Window Print Setup. Selecting Report output for file output (upper portion of the dialog) controls what file type is generated. I'm assuming you have NOT selected Printer.
    4. Once execution is complete pcdmis looks at the output type selected and tries to output to your selected type using the Amyuni Print Driver. The driver is attempting to change the above mentioned registry setting but is unable to and displays the Amyuni dialog which you have attached in your first comment (the one which contains Concatenate).
    5. If you correct the registry setting permissions is there still an issue?
  • Did someone add a print command to the routine itself? Like the Insert>>Report Command>>Print Command?

    It's also possible that you can trigger printing from a script. Are you calling any scripts at the end of your routine?