We've seen a similar behavior on some machines, so I'll have to try this as well if it pops up again. So far, it appears to be related to when we've updated HP Universal drivers on the Print server. The client tries to update the driver automatically, but something in the process fails silently--during investigation I can always see the driver is the old one, and can't update it manually to fix. Often times the machine will print one time after a reboot, then fails to print (even though it appears in the local queue and disappears) each subsequent time until the next reboot. We've only had a few, and have reimaged some machines, but finally made a custom process to rip them out, which has worked on some.
-B ________________________________ From: listsad...@lists.myitforum.com <listsad...@lists.myitforum.com> on behalf of Jimmy Tran <ji...@jt-solution.com> Sent: Wednesday, August 14, 2013 10:46 PM To: ntsysadm@lists.myitforum.com Subject: RE: [NTSysADM] interesting print issue I tried the W7 full repair. Although it never completes on the machine, I think it solved the problem. I rebooted after the “fix” never completed after about 2 hours. I added the printer back and the print job stayed in the queue for about 30 seconds before it said print. I believe this behavior is normal. Earlier, it would appear in the queue and disappear in less than a second. Lets see if the end user emails me in the morning seeing the test print out. Crossing my fingers. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Aakash Shah Sent: Wednesday, August 14, 2013 7:09 PM To: ntsysadm@lists.myitforum.com Subject: RE: [NTSysADM] interesting print issue You may want to try the Microsoft Fixit for Printing: http://blogs.technet.com/b/askperf/archive/2012/02/24/microsoft-fixit-for-printing.aspx I haven’t come across a scenario where I’ve needed to use this and hence don’t have any personal experience with these, but I’d be curious to hear whether it works for you. -Aakash Shah From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Jimmy Tran Sent: Wednesday, August 14, 2013 6:54 PM To: ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com> Subject: RE: [NTSysADM] interesting print issue I tired both options you have but same result… From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of J- P Sent: Wednesday, August 14, 2013 4:51 PM To: ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com> Subject: RE: [NTSysADM] interesting print issue opt 1 1. Go to Programs and Features in Control panel > click Turn Windows features on or off 2. click + sign of Print services 3. Select LPD and LPR. You should remove Internet Printing Client. > restart your PC to ensure there is no error of spooler service. 4. Add your printer driver again. opt 2 stop spooler svc goto %systemroot%\system32\spool\drivers\w32x86 or 64 bit C:\Windows\System32\spool\drivers\x64 delete everything , readd printer Jean-Paul Natola ________________________________ From: ji...@jt-solution.com<mailto:ji...@jt-solution.com> To: ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com> Subject: [NTSysADM] interesting print issue Date: Wed, 14 Aug 2013 23:32:56 +0000 So I have a desktop that no longer prints to a specific printer. It was working fine and dandy until I deployed that printer via GPO. No matter what I do or how I map the printer it doesn’t print. It shows it in the queue, it says its printed but the printer is non-responsive. I tried to remove the related print drivers via printui, same result. Installed printer via tcp/ip port same result Installed printer via tcp/ip port on a working machine and shared it, same result Installed original drivers and latest drivers, same result. Tried a new user profile, same result What can I do besides reimaging this bad boy because there is no image yet. Anyway to strip all the drivers and printing service out and then reinstall it? TIA Jimmy
