MobilePrint: Print Driver Error Releasing a Print Job from Print Center

Overview

When you release a print job uploaded or emailed through Print Center, MobilePrint may display an error stating that the render server does not have an available print queue using the selected driver. This usually means that the printer mapping references a driver or renderer queue that is missing, mismatched, or unavailable on the MobilePrint Worker Server.

Applies to

• MobilePrint for Uniprint

• MobilePrint for Blueprint

• MobilePrint 2.6.2 deployments using supported Pharos server versions:

• Uniprint 9.1 SP3 with Print Center 4.11.23 or later

• Uniprint 9.2 with Print Center 5.0.26 or later

• Blueprint 5.3 Update 7 or later with Print Center 5.4.2.1 or later

• Blueprint 5.4 Update 2 or later with Print Center 5.5.1.12

• Blueprint 5.5 or later

• For older MobilePrint releases, use the installation and configuration guide that matches the installed version.

Symptoms

You may see an error similar to:

Error releasing print job: Failed to render Job Id ... as the render server does not have an available print queue that uses the 'Microsoft PCL6 Class Driver' driver ...

The job may fail when released from Print Center even though it was uploaded or emailed successfully.

Cause

The MobilePrint printer mapping references a driver that is not assigned to a valid renderer queue on the Worker Server. The queue may be missing, the driver name may not match, or the driver may not be installed on every Worker Server.

Starting with MobilePrint 2.4.5, MobilePrint no longer installs a generic driver and queue automatically. You must create a MobilePrint queue and assign a suitable print driver.

Resolution

1. Sign in to Print Center with an administrator account.

2. Review the MobilePrint printer mapping for the affected manufacturer and model.

3. On every server hosting the MobilePrint Worker Service, install the driver recommended for the printer model.

4. Create or verify a MobilePrint renderer queue on each Worker Server.

5. Confirm that the same required drivers are installed on every Worker Server. Releasing jobs may fail if one Worker Server is missing a driver.

6. In the MobilePrint configuration, map each printer model to the correct renderer queue and driver.

7. Do not leave the mapping assigned to the Microsoft PCL6 Class Driver unless that driver is intentionally installed, assigned to a valid renderer queue, and supported on every Worker Server.

8. After installing or changing drivers, restart the Print Spooler and MobilePrint Worker Service when required by the applicable installation guide.

9. Submit a test job through Print Center and release it to the affected printer.

10. If the job releases successfully without the renderer error, repeat the validation for other affected printer models.

Validation

Confirm that:

• The affected printer model maps to the intended renderer queue.

• The mapped driver exists on every MobilePrint Worker Server.

• The driver name in the mapping matches the installed queue configuration.

• A test job releases successfully from Print Center.

• No new renderer or driver-mapping alert appears in Pharos Administrator.

Notes

• A 29062 timeout processing a PDF is not always a driver-mapping error. Complex PDFs, PDF rendering, Windows Print Spooler processing, and driver compatibility can also cause timeouts. Test the affected document with an appropriate current driver, including a PostScript driver when supported for the device.

• If mappings disappear after Windows patching or server reboots, collect MobilePrint, PharosAPI, and server event logs and escalate the issue. This may indicate a configuration synchronization problem rather than an incorrect manual mapping.

• When multiple Worker Servers are used, verify the driver installation and renderer queue configuration on every server before testing.