Blueprint Tracker causes jobs to remain in queue on Great Plains Server or Terminal Server
  • 04 Mar 2024
  • 1 Minute to read
  • Contributors
  • Dark
    Light
  • PDF

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

  • Dark
    Light
  • PDF

Article summary

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?


Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.