• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2115
  • Last Modified:

Windows 2008 R2 issue with Print Spooler

We have a WIndows 2008 R2 server set for us as a terminal server.  From time to time, the few people that are currently testing the system will report not seeing any printers or report that Word/Excel has an issue (unable to save files, unable to import txt, etc).

If I restart the print spooler service, the issue at the time is resolved.

The problem is that the print spooler rarely if ever shows any unusual usage of memory.  Also the service is always found in a status of Running (it starts automatically) not in a status of Stopped.

Found this article:  http://support.microsoft.com/kb/2388142  but the hotfix is not applicable for us, there's been those files that have been updated since.
Anyone else experiencing this behavior?
1 Solution
Glen KnightCommented:
This is caused bu a printer driver, i h ad it a few months back and the driver was incompatible with Windows 2008R2.  I had to go through and up ate all the drivers and ensure that the clients were using the correct version.

It was a pain but it seemed to resolve the issue,
regosnellAuthor Commented:
Thanks, we might be stuck getting new printers that are 64-bit compatible native without the use of the universal driver.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Tackle projects and never again get stuck behind a technical roadblock.
Join Now