I have even money that says you are way over committed. Its not an R2 version.. Also why aren't you using esx? Why waste the ram on a large host os? Also adds a huge layer of complexity We installed the applications and then proceeded to add shared printers off the server..
I understand fully what you are saying digital blacksmith Thanks so much for all of the responses so far and I will be trying hockroot's utility soon. Any more suggestions in the meantime? Thanks again. Stop the Print Spooler. Turn off the printer. Turn printer back on and restart the service. Ya I am not trying to be callous, what I am getting at is I don't know if there is much you can do outside of moving to esx.
From what I get in your description, you are running a terminal server in a virtual box, and using it as a print server. I dont know what that would do to a box. Does each terminal session try to share out it's printers? Maybe that is causing the issue? Could it be that someone is trying to access the spool service such as the hokey 32 bit only app :. As mentioned above, stop the Print Spooler, set it to manual, reboot the server and see if it pops up again, if it does you have a virus.
If everything works smoothly, start the spool service manually and see if the usage spikes again. Then start looking to see what is accessing the spool service by looking in your process monitor. Are you using HP printers? I had this issue before - you have to delete a HP file and replace it with a blank text file with the same name.
I had this a while back, on vmware 1. Brian Smallwood. I had problems with the spooler taking all the CPU when printing to a network resource with a virtual drivers. The printers we had only supported a windows type driver GDI, I think is called. This type of driver did not work thru Citrix and most likely thru TS it would not either.
Beside installing the PCL board there was nothing else to do, but not use those printers when connecting to the remote servers. Another problem that I saw after converting a server was that a program was using the LPT port to create file reports in crystal report format. So far I have not observed what happens in the windows spool directory when a lock occurs. But I have ensured that all printers are on the latest drivers.
The vast majority of the printers are various Kyocera models, and they all have both x64 and x86 drivers installed. I don't know if this relates Right clicking on the print would show a message that the driver was not installed. After several weeks of periodic reinstalling of printers and drivers, I finally determined that if every has "Manage Printer" permissions, the problem goes away. I never knew why , but that was an acceptable solution. It has been ever since then that this new problem has been occuring.
There is nothing in the event logs to coincide with this problem. Had any new printer been added or any printer driver been upgraded before this issue occurred? This method will help us determine if this issue is caused by a loading program or service.
Please perform the following steps: 1. Click "Start", go to "Run", and type "msconfig" without the quotation marks in the open box to start the System Configuration Utility.
Click "OK" to restart your computer to Selective Startup environment. Check whether or not the issue still appears in this environment. The materials may include technical inaccuracies or typographical errors and may be revised at any time without notice. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No.
0コメント