4 Replies Latest reply on Nov 17, 2017 12:36 PM by Scott Olswold

    PharosSystems.SecureRelease 100% CPU

    Rhys Gottwald Wayfarer

      Hi all,


        I have a Windows 2008 R2 server that has been running Pharaohs Uniprint for 4 Years.  Now the PharosSystems.SecureRelease process has started beating the CPU.


      Any idea where to start looking for causes, eg logs events and so on?



        • Re: PharosSystems.SecureRelease 100% CPU
          Nic Meadows Ranger

          Use the Pharos log setter tool and make sure that logging is on. The default location for the logs is c:\ProgramData\Pharos\Logs

          • Re: PharosSystems.SecureRelease 100% CPU
            Ricky Johnson Tracker



            Do you have everything all on one server?  And if so, have you experienced more printing for your area?


            I ask because we were experiencing similar issues and our SQL instance (memory usage) was very high.  When the SecureRelease service would run to release the job, it would use memory and CPU resources.  If enough users were trying to release jobs at the same time (and if any of the jobs were bloated in size due to the Universal Print driver from HP), it would spike the process.




            1 of 1 people found this helpful
              • Re: PharosSystems.SecureRelease 100% CPU
                Scott Olswold Guide


                Your "bloat" using the UPD is most likely due to the Resolution setting in the driver. If you have never connected your queue instance to a physical device (by specifying, for example, a Standard TCP/IP connection to a printer), you will only have a handful of "Print Quality" options in the Printing Preferences > Paper/Quality tab: 300 dpi, 600 dpi, and maybe FastRes 1200. If anything is printed that contains images, those images end up being upsampled to whatever DPI setting is specified, and you can get bloat really quick.


                However, if you connect to a device, you will get one or more ImageREt options that can significantly reduce image file size:




                This has helped in other implementations.



              • Re: PharosSystems.SecureRelease 100% CPU
                Rhys Gottwald Wayfarer

                It looks like this may have been associated to the size of DB and its Log file.  I will continue to monitor and confirm.


                Thank you for the feedback.