---
title: "Blueprint Tracker causes jobs to remain in queue on Great Plains Server or Terminal Server"
slug: "blueprint-tracker-causes-jobs-to-remain-in-queue-on-great-plains-server-or-terminal-server"
updated: 2024-03-04T13:57:22Z
published: 2024-03-04T13:57:22Z
canonical: "kb.pharos.com/blueprint-tracker-causes-jobs-to-remain-in-queue-on-great-plains-server-or-terminal-server"
---

> ## 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.

# Blueprint Tracker causes jobs to remain in queue on Great Plains Server or Terminal Server

After installing the Blueprint 3.5 Tracker on a Great Plains Terminal Server or Windows Terminal Server print jobs remain in the print queue and the Blueprint Tracker fails.

---

On some Great Plains and Windows Terminal servers it is possible that permissions restrict rights to the PharosSystems folder under All Users. Give "Everyone" full rights to the PharosSystems folder under All Users to resolve this problem. Setting these permissions will resolved the issue and the Tracker should operate normally.

## Related

- [If I change the print driver on the server will the Automatic Updater also update the driver on the desktops?](/if-i-change-the-print-driver-on-the-server-will-the-automatic-updater-also-update-the-driver-on-the-desktops.md)