Skip to end of metadata
Go to start of metadata

If you're having trouble with the Print Anywhere client, you may find an answer to your question below.  If not, please submit a Helpdesk ticket for further assistance.


Unable to contact an LPD service on the Pharos Print Server

Some firewall/security applications, specifically BitDefender Total Security, will block the Print Anywhere client from communicating with the server.  Please see your application's documentation for how to add application exceptions.


Documents are printing double-sided instead of single-sided

Windows

When going to print, select the printer and click the Preferences button.  Make sure the following two options are set to "1-sided".

macOS

When going to print, click the "Show Details" button.

Screenshot of Print dialog

After that, select "Printer Features", then "Finishing Options", and make sure the Print Type is set to "1-Sided".

Screenshot of expanded Print dialog


Unable to find the port:PharosPopupPort

The Windows installer leaves a "ControllerLog.txt" file in the user's %temp% folder.  In addition to receiving an error message during installation, the following entry may appear in this log file.

Sample ControllerLog.txt Contents
[2018/09/17 18:07:10.121 P8DF0 T7E0C Controller] [CRunInstructions::DoStep] A PSException was caught: "Unable to find the port:PharosPopupPort"


To resolve this issue, you'll need to completely uninstall the client, following the Windows Client Cleanup process, and specifically delete the following registry key:

"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Pharos Systems Popup Port Monitor"


Print queues are not added on MacOS

If the macOS installer finishes successfully, but does not automatically add the CNU Print Anywhere queues, you may need to remove any old or existing drivers to prevent conflicts.  Follow the macOS Client Cleanup process, and be sure to delete the existing Konica Minolta driver files.


Windows Client Cleanup

In the event of a failed installation on Windows, the following steps should be taken prior to attempting a re-installation of the client.

  1. Start out by running the Pharos uninstaller.  Give the program a chance to clean up as much configuration as possible in a normal manner.
  2. Delete the program folders
    1. "C:\Program Files (x86)\Pharos\"
    2. "C:\Program Files (x86)\PharosSystems\"
  3. Launch the Windows Registry Editor (regedit.exe) and delete the following registry keys
    1. "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Pharos"
    2. "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\PharosSystems"
    3. "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Pharos Systems Popup Port Monitor"
  4. Restart the computer.
  5. Re-try the installation.


macOS Client Cleanup

In the event of a failed installation on macOS, the following steps should be taken prior to attempting a re-installation of the client.

  1. Start out by running the Pharos uninstaller, to give the program a chance to clean up as much configuration as possible in a normal manner.
    1. In Finder, use the "Go" menu, select "Computer", and then double-click the local hard drive.
    2. Under the “Library” folder, go to “Application Support,” and then “Pharos.”
    3. In the “Utilities” folder there, run the Uninstaller application.
    4. When prompted, tick the box next to “Pharos Popup” and press the Continue button twice, followed by the Done button to fully remove the application.
  2. Open System Preferences and check under Printers & Scanners to see that all of the "CNU_PrintAnywhere" queues have been removed.  If any remain, remove them manually.
  3. Delete all of the Konica Minolta drivers
    1. In Finder, use the "Go" menu, select "Computer", and then double-click the local hard drive.
    2. Browse to the Library > Printers folder and delete the "KONICAMINOLTA" folder there.
    3. Browse to the Library > Printers > PPDs > Contents > Resources folder and delete all "gz" and "ppd" files that start with "KONICAMINOLTA" or "Konica-Minolta".
  4. Restart the computer.
  5. Re-try the installation.


Installer Log File Locations

Windows

  • The Windows installer leaves a "ControllerLog.txt" file in the user's %temp% folder.  This file is available during and after installation.

macOS

While the installer is running (typically after the error occurs, but before the installer window is closed), go to the Window menu and select "Installer Log".

Screenshot of macOS menu


Change the Detail Level drop-down (top left) to "Show All Logs".

Screenshot of macOS Log Console


Use the Save button (top right) to save the log file to a viewable location.

If this didn't resolve your issue:

or call (757) 594-7079