---
title: "Print jobs are deleted when queue names do not match Windows printer names exactly."
slug: "print-jobs-are-deleted-when-queue-names-do-not-match-windows-printer-names-exactly"
updated: 2024-03-28T12:20:51Z
published: 2024-03-28T12:20:51Z
canonical: "kb.pharos.com/print-jobs-are-deleted-when-queue-names-do-not-match-windows-printer-names-exactly"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.pharos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Print jobs are deleted when queue names do not match Windows printer names exactly.

All print jobs sent to a queue are being deleted, and an alert is created for each job with the following message:

`Print job arrive error on job '[jobname]': CJobCostMethodsLoaderBase::GetDefaultPerJobCost Couldn't find Method ''`

How can this be resolved?

---

This can happen if the queue name in Pharos does not match the printer name in Windows exactly (matching case as well). The simple way to address this is:

1. Select the queue in Pharos Administrator.
2. Append an 'x' to the queue name, and click another field to ensure the change is saved.
3. Remove the 'x', and then issue a Change Control.

The queue name should now match exactly, and the error should be resolved.

## Related

- [Pharos Beacon Update: October 2020 Release Notes](/pharos-beacon-update-october-2020-release-notes.md)
- [Printing from a Chromebook to a Uniprint system](/printing-from-a-chromebook-to-a-uniprint-system.md)