Search the Community

Morning all Im in the middle of setting up new staff laptops. They are samsungs 200B's. Im trying to install drivers for the printers and i cant get them to install. Is this because its a X64 os or have i not got the right drivers for on the 2003 Server for the computers. (Or do i need to have a 2008 RC2 print server for it to work right...) Thanks for the help in advance) Karl

Hi I am looking for a good print management solution for our organization. Can you please share whats used in your organization or any good suggestions would be highly appreciated thanks

Good morning, I have a print server running on server 2019. The print spooler is not stable. It keeps restarting, the only way i have gotten it working is to set Subsequent Failures to restart the service. The service will restart between 3-5 minutes. during this time one can print no issues. I think its a corrupted or outdated print driver. The drivers that are in use range from 2018 - 2006. So yea i would say their are some really old drivers on their. I know the print spooler is crashing but i cannot find what exactly the cause it. the event viewer has not been much help i have posted the errors i see below. Is their a process to track down the driver? Everything i read online just said to update all the drivers but nothing about tracking the down the exact one that is causing it. Aside from having Techs do a Clean up on the server, Update Currently used drivers, Remove unused/old Drivers and delete old queues. If that does not work the only other thing i can thing od is to build a new server and install everything fresh and manually move printers over. Their are 78 drivers Their are 81 Printers Thoughts?? I see the below but those files don't exist, which is why i says "The print spooler failed to delete the file" The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\x64\PCC\prnms003.inf_amd64_9bf7e0c26ba91f8b.cab, error code 0x2. See the event user data for context information. The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\x64\PCC\prnms002.inf_amd64_4d944e2fb3bcc43c.cab, error code 0x2. See the event user data for context information. The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\x64\PCC\ntprint.inf_amd64_18b0d38ddfaee729.cab, error code 0x2. See the event user data for context information. The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\W32X86\PCC\prnms003.inf_x86_dd2fd5b05c3d8604.cab, error code 0x2. See the event user data for context information. The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\W32X86\PCC\ntprint.inf_x86_18b0d38ddfaee729.cab, error code 0x2. See the event user data for context information. I see this from time to time but it does not tell what the print driver is.... Document failed to print and was deleted because of corruption in the spooled file. The associated driver is: . Try printing the document again. Not much i could find out but about the below The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key S-1-5-21-636618257-2613738635-33974680-1377919\Printers\Connections. The print spooler could not open the registry key. This can occur if the registry key is corrupt or missing, or if the registry recently became unavailable. I see this every 3-5 minutes... The Print Spooler service terminated unexpectedly. It has done this 12 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. And yes i know about Cleaning out C:\Windows\System32\spool\PRINTERS but this is the not the case as it will stop while that is empty/ no jobs coming in. Thanks

Hi, I am having a problem which has been ongoing for months and I just cannot sort it. I am using Print Management on my server (running Server2016). When a client prints, the job is sent to the Print Server and then passed out to the printer (Konica Minolta BizHub454). Occasionally (at least 2 or 3 times a week) I will be informed that the printer is not working. On inspection, there will be a long list of jobs in the print queue with the earliest job "stuck". None of the other jobs will even get to the printer so because of one job, the printer is unusable. The way i am fixing this is to stop the Print Spool service and delete the files in the Windows/system32/spool/printers folder. Then re-starting the print spooler clears the queue and all is working again. Trouble is, I work part time and so if the problem happens when I'm not here, it causes chaos. Anyone any ideas what may be causing this and how to cure it?

Hi all, Happy new Year! Has anybody had any luck getting Canon Pixma printers to work on print servers? In particular the Pro9000 Model? I have 2 of these at school and want to add them to my print server so I can do cost recovery via Papercut. I've been battling away with a TP-Link TL-PS110U print server but I can't get them to play nicely. After a day banging my head against the wall I think I'm going to look for an alternative print server that supports Canon printers (even though the TP-Link says it does, I can't get it to work). The job gets passed to the print server, and the print server says it's passed it to the printer succesfully, but it doesn't print. The lights on the printer blink, then nothing happens. I've come across a 'Pricom 6200-U' which lots of people seem to rave about, but can't seem to buy one anywhere here in NZ. If anyone has had any success, I'd love to know the model of print server you are using Cheers John Driver

We have a print server setup, with the printers installed locally to the server. They are then shared, listed in directory, and pushed out via group policy. This is fine - but we want to restrict our level 1 techs to only be able to clear printer queues for when things get backed up and printers go into error mode. I've gone into the properties of the print server and given 'manage documents' permission to these techs, but they still get an 'access denied' error when doing so. Is there a better way of doing this? They have started messing with our print setup before when they had full access, so we don't want them to have access to drivers/ports/etc - just clearing all jobs/queues. AD Environment Windows Server 2008 R2 Thanks

Hi all, Got a bit of an issue with adding a 32bit driver on a 64bit print server. The printer in question is a RISO comcolor 7150. The 64bit driver works fine, but when i go to install the 32bit driver, the server doesn't do anything. I have a compatible driver for the OS, and i can access the .inf file for the driver, but i click ok and nothing happens. This is really frustrating as i need to retire a very old 2003 print server ASAP, and until this driver installs, that cannot happen. Is there anything i am doing wrong? Regards Harry

Bit of a strange one here and not sure what's really happening. In terms of Hyper V - I'd say i know enough but wouldn't say i'm an expert! It's just seemed to work in the past...... Got 2 virtual servers and they are both running exceptionally slow, one more so than the other. The main concern is the Print Server which is a VM running papercut. For some reason it is also running at 100% CPU whenever you do anything on it. The server hosting HyperV is absolutely fine performance and spec wise. It is also performing exceptionally slow when transferring data to/from it. If i ping it the response times can be as high as 180ms. Rest of the network seems fine traffic wise and pings all fine even the Hypervisor pings fine. Any ideas? Am i missing something straight forward? Thanks

Last week two of our HP Business Inkjet 1000s started playing up. Admin users can print OK, but anyone else can't. They're both connected to external Jetdirect servers, and another that is shared via the machine it is attached to seems to be unaffected - leading me to suspect that the problem lies somewhere in the Jetdirect. The users don't get any error messages, nor do the jobs appear to be stuck in the print queue. Both machines were fine the week before, and nothing has been changed to the best of my knowledge. I've tried resetting the Jetdirects to no avail, as well as restarting the print spooler. Bizarrely, the affected users can still ping and log on to the print server. Anybody got any ideas?