1 of 1 people found this helpful
We experienced this a little after upgrading to Uniprint 8.3. My understanding is that there can be many different explanations, but in our case, we (with the help of Pharos Support) identified that it was caused by handful of devices (Xerox PSX devices) that did not have any copy station configured. Those copy stations were then repeatedly sending copy transactions to the DB Server. After identifying and correcting the devices, CPU usage went back to normal.
An error was logged in the Windows Application log and the Pharos application log helped us identify the problem.
Hope this helps!
Logging why within the DBServer helps tremendously. You use the Pharos LogSetter tool to enable logging. Once the DBServer log is in hand, it is very easy to pick out what is causing the issue. You may even find your target by engaging the SQL Profiler tool on the SQL Server hosting the Pharos database.
If you need more help, you can definitely open a ticket with Pharos Technical Support (email@example.com) and somebody will be able to help you make sense of it all.
Good Afternoon Scott,
We already have a ticket open [Incident: 131202-000020]. Jeff spent a good bit of time looking into things yesterday. The perplexing part is that the system has been operating normally (no noticeable/extended slowdowns) for a number of months before this popped up out of the blue.
We upgraded all of our Print servers to revision 423 last night and this morning the CPU usage issue seems to be resolved. I don’t know if the 423
installation corrected it or if rebooting all of our servers corrected it but the issue seems to be resolved. CPU usage is now in the 0 – 10% range
with momentary spikes in the 20-70% range. I will be watching CPU usage to see if the problem occurs again.