I'm hoping someone can help. We have started to have major printing issues on our x64 PS4.5 RUP 3 Terminal Server farm. The issue started with our accounts team who have three HP BL35p (x64) Terminal Servers and a HP DL 380 G3 (x32) Print Server.
In the office they use a mix of HP LJ4200, LJ4250, LJ8000, LJ4345, LJM4345 and CLJ5550 printers. The drivers for these were replicated across the farm. They are usually the relatively recent versions of the drivers (not necessarily the most up to date) and will be running across the farm.
We noticed that the spooler service on our terminal servers would start crashing with the following error message
Event Type: ErrorEvent Source: Application ErrorEvent Category: NoneEvent ID: 1000Date: 14/04/2009Time: 16:52:08User: N/AComputer: ##########Description:Faulting application spoolsv.exe, version 5.2.3790.3959, faulting module ntdll.dll, version 5.2.3790.3959, fault address 0x000000000003d2c7.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Data:0000: 41 70 70 6c 69 63 61 74 Applicat0008: 69 6f 6e 20 46 61 69 6c ion Fail0010: 75 72 65 20 20 73 70 6f ure spo0018: 6f 6c 73 76 2e 65 78 65 olsv.exe0020: 20 35 2e 32 2e 33 37 39 5.2.3790028: 30 2e 33 39 35 39 20 69 0.3959 i0030: 6e 20 6e 74 64 6c 6c 2e n ntdll.0038: 64 6c 6c 20 35 2e 32 2e dll 5.2.0040: 33 37 39 30 2e 33 39 35 3790.3950048: 39 20 61 74 20 6f 66 66 9 at off0050: 73 65 74 20 30 30 30 30 set 00000058: 30 30 30 30 30 30 30 33 000000030060: 64 32 63 37 0d 0a d2c7..
I have setup the Userdump tool to dump on the spooler when it fails but as I am no programmer I cannot make head nor tail of it.
The issue appeared worst when certain users were logging in. We seemed to have got over the issue by recreating some roaming TS profiles as it appeared that some users had a corrupt printer in their profiles. However it has since returned and is now affecting our operation Terminal server farm (50 Terminal Servers mix of HP BL35p, BL25p G2 and BL460c G1) to a lesser degree.
I'm not really sure where to go with this, one idea was to take one serverfr out of the farm, remove all of the print drivers from it then reinstall them using the latest versions.
I have noticed that there is a service "PML Driver HPZ12" running on the affected terminal servers, but from googleing appears to be a genuine HP services (though one, seemingly more associated with home printers rather than enterprise ones) Howerever this has not failed.
It's also worht commenting on the fact that it only ever seems to be the spoolsv crashing the CpSVC hardly ever seems to have any issues.
One final note is that this issu first occured after the snow day the UK experienced when we had about 100 people on our CAG. I don't know if somehow this has corrupted our printer driver store.
Any input greatly appreciated.
Have you tried setting a printer policy to use only the UPD Universal print driver?
I think the problem is a corrupt printer driver. How many drivers do you have installed on your servers? And are all of the installed (and auto installed) printer drivers x64?
You could implement Dan's suggestion with restricting the printer drivers available on the Servers. Also the Service PML Driver HPZ12 sounds like a no no and should be disabled.