spoolss.exe generates Dr Watson log

Part 1-2

Marty,
Yes, I've had experience with Q199915! After several attempts with this problem, and calling M$ several times when the fix didn't work...

I can share this advice with you, I had to completely remove entire key:
HKEY_LocalMachine\System\CurrentControlSet\Control\Print\Monitors

Downloading the latest version of JetAdmin didn't fix anything! M$ won't help you with the Citrix Metaframe installed, because it adds entries into that "Monitor" key. I found out the hardway, that after M$ had me delete the entire key, local Citrix clients couldn't map their "Local" printers in WTS any longer. I had to manually "add" back the "Monitor" key I saved before deleting it, then write down the values in the "Client Printer Port". Then magically the Citrix clients "locally" mapped printers reappeared when then logged into WTS!

So my advice would be to save the "Registry" key before removing it in case you have to recover some of the subkeys to get Citrix to work! Also, in reading your note above concerning the HP Printers (4050n), those HP [Print] drivers aren't "Kernel Mode" compatiable with "Terminal Server"! I've had way to many instances where using HP (non-certified WTS) drivers corrupted the Spooler (stopping the service). I defined my 4000/4500 printers to use the HP/5 & Color Laserjet printer drivers. I won't load a driver on WTS that wasn't tested and verified by MS on the WTS CD.

As a matter of fact, I have a compatibility script configured so when a Citrix client maps their localled attached Network (or Lpt:) printers to WTS it uses a the driver matching the Printer from the compatibility script. I know some people don't believe in this... but my spooler use to die daily, now maybe just once a month!

Part 2-2

Also, in regards to Jetdirect cards... I found it easiet to define WTS printer ports was as "Local Ports" and point the queue back to an NT Server (running TCP/Print Services) and let the NT Server send the print files over to the network attached HP/Jetdirect cards. Having both WTS & NT Servers with print queues defined on it for the same printer, results in having to check two different queues to find out what job hung (or is spooling, etc.). By using the "Local Ports" even Print Operators can control all the files in queue from a single source (queue).

Sorry for the rambling, but I have shared your pain, and I know M$ support for WTS stinks to begin with, and when you mention you have Citrix/Metaframe installed... the support you get for that $200.00 phone call is worthless. It's a shame M$ treats TS as a "Step-Child"!

Sorry for the "split" but my reply exceeded the 1930 character length allowed per reply.

Good Luck,
Matt