edutech4schools Posted July 11, 2012 Posted July 11, 2012 Hi, We have always had issues with jobs getting stuck while spooling on the server. Recently we got a new server and all the printers changed from HP to DELL. I thought this would fix the problem but at least 3 times a day I am having to stop the spooler service, delete all jobs from the spool drive and start the spool service. This seems to be completely random and not a particular computer / software issue. A computer that has been printing all day can all of a sudden be the one that has caused the above issue. Does anyone have any idea what might be causing this? Also, I was thinking it might be a good idea to move the spooler (for testing) away from the server and have all jobs spooled at the client machines. Is this possible. Our setup 2008r2 server DELL 1355cn printers GP printer deployment. Thanks.
gds64 Posted July 12, 2012 Posted July 12, 2012 Have you tried excluding the spool directory from your anti virus application? Or maybe set the driver to run in isolation mode (if it supports it). Either one can have an impact on the print spooler service.
edutech4schools Posted July 12, 2012 Author Posted July 12, 2012 Have you tried excluding the spool directory from your anti virus application LA controlled virus software and they do not like to make changes to the scanning. Or maybe set the driver to run in isolation mode (if it supports it) No joy, could not find isolation mode.
gds64 Posted July 12, 2012 Posted July 12, 2012 You need to have the Print Server Role added to the server, then look in Print Management for the drivers section under your server name. Right click on the driver and then set the isolation mode. 2
edutech4schools Posted July 12, 2012 Author Posted July 12, 2012 Will adding the printer role have any knock on issues with GPP (Policy printing) that we use?
gds64 Posted July 12, 2012 Posted July 12, 2012 I shouldn't have thought so, but you will be able to use it to deploy printers via Group Policy.
psydii Posted July 12, 2012 Posted July 12, 2012 Isolation mode, if 'it does what it says on the tin' should reduce the impact of a dodgy driver/document. Never used it but would love to hear if it worked and how you got on with it. You may also want to try installing Description of an update rollup for the printing core components in Windows 7 and in Windows Server 2008 R2
edutech4schools Posted July 12, 2012 Author Posted July 12, 2012 You may also want to try installing Description of an update rollup for the printing core components in Windows 7 and in Windows Server 2008 R2 Do they come out with standard windows updates?
psydii Posted July 13, 2012 Posted July 13, 2012 (edited) Do they come out with standard windows updates? No. We install them using powershell script on a schedule that contains lots of lines that look like this: if (!(get-hotfix -id KB2647753)) {start-process -wait -FilePath "c:\windows\system32\wusa.exe" -Argumentlist "Windows6.1-KB2647753-x64.msu /quiet /norestart"} There are probably better ways of doing it if you've got System Centre or CC4 etc, but this way when ever we need to push a new hotfix, we just add it to the end of the script and know that it will get deloyed later on that day. If you run it at startup it can add minutes to your boot time - but assuming you've got Dual Core machines the impact of a background install while a user is working is minimal. Edited July 13, 2012 by psydii
ricki Posted July 13, 2012 Posted July 13, 2012 Hi Have you checkdisked the server. If the hard drive has problems this can cause this. Have you checked that there is enough space on the drive with the spooler. I had to move mine to another drive due to space. Have you changed the driver. I have had this with various printers in the past and have had to use say a pcl 5 instead of a pcl 6. You get the idea. I have also had bidirectional printing problems and had to enable or disable this. Are you using vista machines because we have had this if the wrong driver was being used. Say it was a 64 bit pc and only the 32 bit drivers installed. Try a sfc /scan on the print server you might have a corrupt file. Unsigned or drivers that are not certified by micrsoft dont always load and a admin has to log on and allow the driver to install completely. These are just ideas. Richard
ricki Posted July 13, 2012 Posted July 13, 2012 Hi Sorry I forgot we had a hp p2055dn and another one that the printer had to have a firmware update as it crashed the spooler and printed random junk. Richard
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now