Ditto. Sometimes it takes removing all the drivers manually (to be sure to get any uninstall remnants) to properly fix a printer driver issue.
-- ME2 On Fri, Apr 16, 2010 at 7:41 AM, Miller Bonnie L. < [email protected]> wrote: > I'd agree with Ben about drivers, and this kind of problem can be a pain to > troubleshoot. > > I'd start by looking at all of the drivers you've updated recently (back to > when the problem started). On the WS03 print server, look for the files > associated with each driver. For some, you can see these names on the > "About" tab of the print driver, but you might have to go straight to > searching the registry. What can happen is if you have any files in common > between drivers they may have been updated when you installed the latest > printer, which can sometimes break an older driver. > > Then, look at your problem printers and do the same thing (get the file > names). Try to find if there are any files in common and narrow in on > those. The files are usually stored under %systemroot%\system32\spool, but > you can usually find the path in the registry for specific printers. > > Then, you might need another WS03 test server that hasn't had any of these > printer drivers installed yet. Install just the older drivers, so you can > see what the files looked like before the latest drivers were updated to > figure out what changed. If you have a backup, that might also be an easier > way to find them--you need to be able to confirm the file is different. > > Then, you test by replacing the file back to the older version. In some > cases, I've found I can stop the spooler and replace the file with an older > version as "updating" the printer driver again with the older one does not > generally overwrite any newer files (and it doesn't warn you). But, I've > also found where that doesn't always work or the newer printer driver will > break after replacing the file with the old one. You'll have to test all > printers that share whatever file you had to replace. In one case, we had > such a bad conflict that we ended up using a different type of driver (PS vs > PCL) for one of them, but I don't know if you will have that kind of option > here. > > -Bonnie > > -----Original Message----- > From: Ben Scott [mailto:[email protected]] > Sent: Thursday, April 15, 2010 2:39 PM > To: NT System Admin Issues > Subject: Re: label printer > > On Thu, Apr 15, 2010 at 3:24 PM, paul d <[email protected]> wrote: > > We entered into a contract to have all our non-label printers to be > leased > > from a company (we used to just buy them) and have been replacing the > > current printers with these new printers. That, of course, means > changing > > the drivers on the print server. > > I'd start looking there, then. You changed printer drivers, and now > you have some new printer problems. I doubt that's coincidence. > > I've seen all manner of weird problems come about due to printer > drivers. A buggy printer driver can affect other printers using other > drivers on the same computer. (HP's drivers started doing this to us. > It's one of the main reasons we're not buying HP printers anymore.) > > -- Ben > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
