I have come across a very unusual problem relating to printing. I'm not really sure whether it is Windows 2000, the printer, Excel or something else, but never mind. Here goes:
There are a group of 3 people who use a networked printer, an ordinary HP Laserjet 4, with an inbuilt JetDirect card, which is used to connect it to the network. Workstations are connecting to it using IP, rather than shares off a server.
The 3 workstations run the standard build: Windows 2000 Pro SP4 with IE6 and Office XP. However, they are all different models of PC, and other PC's of the same model print fine without exhibiting this problem elsewhere in the organisation. This, to my mind, rules out something in the RIS build that disagrees with their printer, which is why I haven't yet tried reinstalling the PC's.
Here's the problem: Very occasionally, while printing something from Excel (and it is only Excel, it doesn't happen with any other application), the print just doesn't come out.
Restarting the print spooler service in control panel fixes the problem, but it doesn't explain why this happens in the first place. It isn't anything in a spreadsheet either, because it could print it fine once, but then fail if printed again at a later date.
This problem started when they were upgraded to Excel XP, it didn't happen with Excel 97 (also on windows 2000).
Here's the weird bit: Setting the Print Spooler service to automatically restart after a failed attempt (on the Recovery tab of the Properties box in the Services MMC snapin) doesn't restart the service, it must be done manually.
I have checked and these three people all have local administrator rights on their PC's, so the service should have no problems restarting even if it was run as them rather than local administrator. The event logs also show nothing unusual around the time they try to print something, whether it works or not.
Nobody else uses this printer, so we can't easily find out if it is the printer, PC's, Excel or something else. Additionally, everybody keeps to their own PC, so we can't easily find out if it relates to their profile on their PC (no roaming profiles).
Here's what has been tried so far:
* Uninstall, reboot and reinstall office XP (rather than a repair install)
* Install office XP SP3
* Set the Remote Procedure Call service to restart on failure (Print Spooler is listed as being dependent on the RPC service), although this doesn't seem to stop.
This issue has been around in the helpdesk now for several months, and has baffled everybody here. If anybody has any ideas as to the cause of this, or what I can do to fix it, I am open to suggestions.
John
There are a group of 3 people who use a networked printer, an ordinary HP Laserjet 4, with an inbuilt JetDirect card, which is used to connect it to the network. Workstations are connecting to it using IP, rather than shares off a server.
The 3 workstations run the standard build: Windows 2000 Pro SP4 with IE6 and Office XP. However, they are all different models of PC, and other PC's of the same model print fine without exhibiting this problem elsewhere in the organisation. This, to my mind, rules out something in the RIS build that disagrees with their printer, which is why I haven't yet tried reinstalling the PC's.
Here's the problem: Very occasionally, while printing something from Excel (and it is only Excel, it doesn't happen with any other application), the print just doesn't come out.
Restarting the print spooler service in control panel fixes the problem, but it doesn't explain why this happens in the first place. It isn't anything in a spreadsheet either, because it could print it fine once, but then fail if printed again at a later date.
This problem started when they were upgraded to Excel XP, it didn't happen with Excel 97 (also on windows 2000).
Here's the weird bit: Setting the Print Spooler service to automatically restart after a failed attempt (on the Recovery tab of the Properties box in the Services MMC snapin) doesn't restart the service, it must be done manually.
I have checked and these three people all have local administrator rights on their PC's, so the service should have no problems restarting even if it was run as them rather than local administrator. The event logs also show nothing unusual around the time they try to print something, whether it works or not.
Nobody else uses this printer, so we can't easily find out if it is the printer, PC's, Excel or something else. Additionally, everybody keeps to their own PC, so we can't easily find out if it relates to their profile on their PC (no roaming profiles).
Here's what has been tried so far:
* Uninstall, reboot and reinstall office XP (rather than a repair install)
* Install office XP SP3
* Set the Remote Procedure Call service to restart on failure (Print Spooler is listed as being dependent on the RPC service), although this doesn't seem to stop.
This issue has been around in the helpdesk now for several months, and has baffled everybody here. If anybody has any ideas as to the cause of this, or what I can do to fix it, I am open to suggestions.
John