Blueprint Tracker causes jobs to remain in queue on Great Plains Server or Terminal Server
- 04 Mar 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Blueprint Tracker causes jobs to remain in queue on Great Plains Server or Terminal Server
- Updated on 04 Mar 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
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.
Was this article helpful?