Thank you for helping keep Tek-Tips Forums free from inappropriate posts. The Tek-Tips staff will check this out and take appropriate action. Click Here to join Tek-Tips and talk with other members! Already a Member? Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free. Register now while it's still free! Already a member? Close this window and log in. Join Us Close. Join Tek-Tips Forums! Join Us! I'll see what we can do about the spooler update applied. That will have to go through our change control processes. As I don;t know the root cause as yet, and therefore cannot test if the patch fixes it or not, then that could be challenging.
Comparing checksums with a known good client does not reveal any issues and the ACL looks the same,. If an upgrade from prior UPD versions, this is the likely cause of your issues. AutoUpgradeUPD is the new official HP tool for upgrading existing print queues which is found in the printer admin pack. I've opened a call with our support provider, who in turn has escelated to thier resource.
I will keep the thread updated, and post the response back from the support provider. It's becoming more of a pain point for us with every passing day. After trying BSOD's suggestion, if this issue still occurs, please try to remove users' modify permission from the affected registry keys? This can be beneficial to other community members reading the thread. BSOD These drivers have not been upgraded, they are a fresh install. Thanks for your contribution though I'm very reluctant to do that without fully understanding the implications of it.
Alan: I've not been able to apply the print hotfix rollup as yet to the clients, I will struggle to get a speculative change of that nature through our change management process. I am running it on my PC, but the intermittent nature of the problem means that I can't be sure that its solved the issue. While I know it doesn't help for solving the problem, I haven't run into this problem yet our environment which appears to be the same as you.
Thought about installing them on a few test boxes? We have been working through what looks like the same issue and Surry44 mentioned this post to me. We will be aiming to apply the Print Spooler CU to our clients some time this week. I'm not desperate to turn off CSR on our print queues, we have a large number of them and pull printing solutions that we use elsewhere will cause us a non-trivial problem when it comes to that being implemented in the forest in question in the forthcoming weeks.
We have the same problem. The problem began after migrering to win7 32 bit and new servers, win One user can print out in the morning, later on the same day the print are corrupt. I can reinstall the print drivers or put back the missing keys in registry dependent files, monitor, help file. After that it can go weeks or months before the same users have the same issues again.
I had the same problem and reinstall the drivers in januari. So far my drivers are ok. If the user have more network printers and they uses different drivers, only printers with the same drivers are corrupt. We are getting phone calls every day from users who have this problem.
Depends on what drivers they are using, printing problems are little different. Hp driver looks like the print is going to the printer but nothing happens, Xerox and Minolta printers are missing functions like printing in A3. I wonder if file version and langue on win32spl. We had to different version of win32spl. Can anyone comment if you've been able to correlate that the affected printers only users' default printers? Can you please set up some data collection on a cross set of users in hopes that we can catch what is changing the registry settings in the act?
We can run Procmon in a way that uses very little memory, saves the events to a backing file rather than the paging file, and can be run remotely by an admin. Below are the steps for configuring Procmon to only grab events that access a reg key called Dependent Files:.
Set Procmon to drop filtered events under Filter. File - Export Configuration to save the configuration to a file ProcmonConfiguration. Save Procmon. To use PSExec to run remotely: 1. Run the following command from the remote computer:. This should get us the Procmon data for the stack information for anything touching the Dependent Files key of any printer.
Please reply to this post with the Procmon log attached or a link to it. We have been having the exact same issue and don't want to turn on SSR. We will update results in our thread:.
It looks like the real issue is when you redirect a print server Microsoft's spooler. We recently redirected our print server again and went through the exact same issue again with multiple print drivers being corrupted a day. Myself and a colleague put together a. If it finds it it will delete it and restart the print spooler service on that computer prompting it to re-download the driver. This will work regardless of the domain, printer brand or driver you are using.
We have seen corrupted drivers on and this has been tested with Xerox, Samsung and HP printers with multiple driver versions. I tried dragging a spoolsv. You folks are very smart Thanks ahead of time for any help that you can give.
You will normally find several copies of it on your drive. That may also replace any other files that got lost in the cleaning process. Try that and report back. Log in or Sign up to hide this advert. I have to run so when SFC finishes and fails to fix your problem, which is likely, since if isn't that handy, do a drive search for spoolsv.
Then run Services. That should restore the printers to functionability. If not report back and I or someone else will take you further on this.
0コメント