At my current place of employment I administer a medium size windows 2003 domain. Most of my work is done remotely and I'm not really involved with the day to day client problems that occur. I generally just help out with domain wide problems and installing new hardware or software. I got a system down for setting up new printers remotely and it was working exceedingly well until about a month ago.
Let the Problems Begin
It was a normal day and got a call saying there was a new printer plugged in in the server room and it needed to be setup and deployed across the domain. I proceeded to remote in and create a reservation in DHCP, create a TCP/IP port and then add the printer to the print server. All went well until the last step. The print spooler would crash and burn and the printer would not be working. This particular printer was an HP LJ 2035n. We currently had three of these printers on the domain working flawlessly. Adding a forth printer really caused problems.
The Solution ?
I cleaned the spooler on the printer server using a program from M$ called cleanspl.exe and proceeded to reinstall all the drivers and printers. The intention was to clean out the corrupted driver and then everything would be okay. Well I successfully got the spooler to stop crashing on the server and was able to add the printer to the network and all was good?
Problem 2
I got a call saying the printer problem was not fixed and the spooler was crashing on the clients now.
Solution 2
So I suggested running cleanspl.exe on all the computers and they asked that I do that so I did. I thought I got the problem completely fixed at this point. I wasn't able to get around to all the computer and someone were not at the school so I left instruction with a capable person on how to run cleanspl.exe.
Problem 3
I get a call a couple days later saying that some people still can't print and are getting the spooler crashed error.
Solution 3
I seeked help from the professionals and they suggested cleaning the spooler manually because M$ program doesn't work that great. My thought was big surprise. I proceeded to clean out the spooler manually on the server. Then I wrote a script that manually would clean the spooler on startup for all the other computers. I added a run once feature by checking for a file to indicate that the spooler had already been clean the script creates when it cleans the spooler. I tested the script on handful of computers and they were able to print just fine.
Problem 4??? Really???
I got a call saying that some of the teachers were still unable to print and that this is getting frustrating and they want it fixed now. At this point I was out of things to try. I was watching an error log of one of the computer they were getting the spooler error on and noticed a small difference in the error. Forgive me but I hadn't been reading the actual error message every time I just saw in the log and knew what it was. This time I noticed it said requed. I posed the question have you been clicking "Ok" on the error messages? The answer I got was "no". Click "Ok" on the error messages and reboot. The error messages didn't come up again. At this point I had told them at least five times that the errors saying the spooler crashed are from the previous time the computer was on and they have the time actually indicating when the spooler crashed. They proceded to tell me that they saw the time and it from Thursday of last week.
Solution 4
[conversation form]
Me: Try printing something real quick
Them: Okay.....
Them: It worked!!!
Me: Have you actually tried printing anything ever or just the saw the error and assumed that it wouldn't print?
Them: We just saw the error.
Me: (Not in to the phone) WHAT THE CRAP!!!!
Them: Well I'll give you a call if we have any more problems, Thanks!!! , Bye.
A Message to ALL
Before you say you printer is messed up, won't print, and contact someone to help you fix it......Actually try printing.
Lessons Learned
Regardless of what someone tells you when troubleshooting a problem never ever assume they know what they are talking about. I've had this problem before there but kinda of assumed that when they said there printers won't print that they actually tried printing.





