spoolss.exe is hogging CPU!!! 2

[Pinkman]

I am running a Citrix over NT terminal server.&nbsp;&nbsp;Every so often the citrix server slows down.&nbsp;&nbsp;I have found that when this happens the spoolss.exe is consuming 90-95% of the processor and does not let go of the processor!<br><br>This is obviously a problem!<br><br>Is there a hotfix for this or anything I can do besides stopping and restarting the spooler service (which fixes it everytime) ????<br><br>Thanks for any responses,<br>Jeff

 

[MikeLacey]

I think you're right. This sounds like there will be a fix for it. I would look for the answer in ts and metaframe service packs.<br><br>Mike<br> <p>Mike Lacey<br><a href=mailto:Mike_Lacey@Cargill.Com>Mike_Lacey@Cargill.Com</a><br><a href=

http://www.cargill.com/>

Cargill's Corporate Web Site</a><br>

 

[Pinkman]

MikeLacey - <br><br>Is it safe to say you are having the same problems?<br><br>If you find out about any hotfixes let me know.<br><br>Thanks for the response,<br>Pinkman<br><br><A HREF="mailtoinkman@texas.net">Pinkman@texas.net</A>

 

[CodeEsan]

This is an interesting problem has anyone came up with a solution... I haven't found any as of yet.

if anyone has any help please contact me

 

[CitrixEngineer]

The recommended level of service packs for NT4 Terminal Server Edition servers running Citrix MetaFrame is:

NT4 TSE Service Pack 5 - or 6, with Microsoft Hotfix Q269214.

Citrix MetaFrame shold be at version 1.8, with Service Pack 2 (feature release 1).

The spoolss.exe problem reported is commonly caused by Hewlet Packard's Print Monitors. The printer drivers only should be installed, any additional software should not be used. To avoid additional software being installed, never run the setup utility provided on maufacturer's CDs, just add the printer through the Add Printers utility.

 

[Whitemtntn]

citrixengineer hit it right on the ole schnazole.....this problem is caused by HP DeskJet printer installations. I installed the DRIVERS for an HP Deskjet 820 (not even the software, just the driver---using the .inf files) and I had the same Spooler became a babbling fool situation.... incidently, i believe that in my situation the problem was in installing the Windows 95 additional driver (to support a home user).
-WhiteMtntn

 

[Whitemtntn]

If you want to GET RID of this problem, this is what you do. Verify which DeskJet printers you have installed. Run the NT installation(the Setup.exe) for each one, and choose the UNINSTALL option.
(You can get the software from HP.com if you don't have it)
This should wipe out any trace of that printer.....otherwise SPOOLSS.EXE will haunt you forever.
-WhiteMtntn

 

[CitrixEngineer]

It has yet to be absolutely proven, but I have yet to find anyone who has had success running the DeskJet 800 series printers in a Metaframe environment using the manufacturer's drivers.

Try using one of the default terminal server colour DeskJet drivers instead. Of course, this means that you will lose some functionality.

The choice really is this or use a different printer. I have heard good reports of newer Epson models, but not confirmed them.

The bottom line is, if you don't KNOW it works in a MetaFrame environment, either test it fully off-line, or don't use it.

Unfortunately, too many sysadmins are put into a position where management give little choice in the matter, but I would have thought that most will listen to hard facts.

This is now particularly true with Windows 2000 : If it's not on the Hardware Compatibility List, it probably won't work the way you want it to.

 

[cyjae]

I have found that the HP660c driver works well and does not cause spooler.exe problems. But maybe I am just lucky. I use the same HP660c driver for my 800 series printers as well as some other printers (Apollo for one).

 

[rasbiggy]

I am running a Citrix metaframe (1.8 sp3) over NT terminal server(sp5). Every time dr watson reports an error with spoolss.exe all remote users connected to this server are thrown out but they can work again once i restart the spooler service.

When i check the event viewer, the following error is registered;
Event ID: 1000, Source CLTMGR &quot;the server was not able to initialize the client management virtual driver (error 13)&quot;

I really dont know how these two errors are related but beleive me i am in really hot soup. I have tried the solution on citrix.com (CTX395746) but it doesnt work.

please help !!!

Is there a hotfix for this or anything I can do besides stopping and restarting the spooler service (which fixes it everytime) ????

Thanks for any responses,
Jeff

 

[DevilDog]

rasbiggy... It is possible that your Event ID 1000 condition is a symptom of your 1st problem: Dr. Watson. When you said that &quot;all remote users connected to this server are thrown&quot; do you mean that they loose their ICA connection? If yes than this might cause your 2nd error condition. Dr. Watson is your primary issue. Can you pinpoint when your problem started? Did you just install a new client printer or simply pickup a new client? See if you can find any client ID's in the Dr Watson log. -- Devil Dog --

 

[CitrixEngineer]

A couple of other things;

Try upgrading to SP6 (but remember the Q269214 hotfix!).

Try running Filemon

http://www.sysinternals.com

(out of hours ;-)) and reproduce the issue. Filemon should pinpoint exactly what is causing it.

I hope this helps

 

[rasbiggy]

Hi,
My problem still persists. I have upgraded to sp6 and deleted all HP printers from my server and havent since seen the spoolss.exe error. But i still have the event 1000 error only that this time a new event warning is registered just before the error.
ID : 1003
source : Winlogon
Description : monitor thread did not find any processes - logging off user [username].

Once this warning is registered, it triggers a disconnection of all active users with event ID 1000. the problem is solved if the citrix server is restarted.

Thanx
Rasbiggy

 

[DevilDog]

I know this may sound a bit abvious, but have you tried working with the client user identified by the 1003 event? Is the 'user' registered in 1003 always same or diff? Have you had this problem since 1st building this server or was ir problem free for some time? How soon after reboot does this event occur? -- Devil Dog --

 

[rasbiggy]

Thanx for the reply,

The users registered in event 1003 are always different. I have always experienced this problem since building the server, i even once went as far as reinstalling the server which is not possible now cauze its a live production server.

Regards

 

[DevilDog]

Let's try something new... You say that you have build this server at least twice and both times you have had the same problem of all users being thrown out of the system; can this be a hardware problem? . 1st - I say that both your 1000 & 1003 events are only symptoms. Do not get wrapped around those; waste of time. I assume you have looked at your system logs very closely. Do you really have to reboot the server after this condition? Is the server 'hung'? Can you access the network from the server? Can you shutdown/restart the ICA browser service and continue working? Do as much troubleshooting as possible after this occurs. Can you uncover any other problems? Have you tried using Filemon as CitrixEnginner suggested? -- Devil Dog --

 

[Hubris]

I see every1 talking about SP6, what about SP6a ??? is this Q269214 patch included in SP6a ???

and yes it's very frustrating we have 2 use 'special designed drivers' 4 TSE. here's a answer I got from HP:

Windows NT Terminal Server 4.0 uses a slightly different memory management
scheme than the Windows NT 4.0 Server. Consequently, the Windows NT Terminal
Server 4.0 tends to be less tolerant of certain drivers that were designed for
the Windows NT 4.0 Server. To download the LaserJet 4000 PCL6 driver that
will work with Windows NT Terminal Server and the LaserJet 4050, go to the
following URL:

http://www.hp.com/cposupport/printers/software/lj312en.exe.html

NOTE: It may be necessary to copy and paste this URL into your browser.

NOTE: Although the LaserJet 4050 is not listed, it is compatible with the
LaserJet 4000 NT 4.0/Win 2000 driver.

All Hewlett-Packard NT 4.0 drivers for both HP LaserJet and HP Color LaserJet
printers are compatible with the Terminal Server environment except for the
following drivers:

NOTE: The HP LaserJet 3150 is supported when the driver only installation is
performed.

HP LaserJet 8000/8100 Series PCL 5e driver--version 4.3.0.9
HP Mopier 240/320 Series PCL 5e driver--version 4.3.0.9
HP LaserJet 4050 Series PCL 5e driver--version 4.3.0.9
HP Color LaserJet 8500--PCL 5 driver--version 1.0
HP LaserJet 3100 Series Printers--all versions

You also may try the latest drivers off our web site for the 4050:

http://www.hp.com/cgi-bin/cposupport/swindex.pl?p=hplaserjet10810&l=en&c=Micro

softWindowsNT40

You can also use the Microsoft LJ4+ as an alternative.
If the HP LaserJet PCL5e fails, try installing an alternate driver provided by
Microsoft Windows. This driver may be more compatible with your printing
environment. The LaserJet 4050 is able to interpret the PCL language to the
PCL6 level. This means that the printer is able to utilize other
Hewlett-Packard LaserJet drivers that are provided by the Windows operating
system. This also provides backward compatibility with older Hewlett-Packard
LaserJet printers.

Just 4 some info !

 

[ChrisBurch]

We had the same spoolss problem on Citrux with terminal server, using DJ895 printers. Cpu would go to near 100%, and would would have to kill the spooler service to clear it, sometimes (at 100%) I'd have to re-boot. The problem turned out to be a licensing issue, where the install program, on client, wasn't getting the EULA acceptance. This is due to using the drivers from the CD supplied with the printer, which are home use only. If you go to the HP site you can get commercial versions which solve the problem (sorry, I can't remember exactly where).

I have gone from 3 to 4 episodes per month, to 1 in several months. I can live with that. In fact I suspect that one of my branch printers hasn't been re-configured. Chris

It worked yesterday.
It doesn't work today.
That's Windows!

 

[ChrisBurch]

In my previous post I should have said 'Corporate' drivers, rather than 'Commercial'.

Did anyone spot the deliberate spelling mistake? Chris

It worked yesterday.
It doesn't work today.
That's Windows!

 

[Hubris]

hehehe nope didn't see it, but felt what U meant !!!
Nice of U correcting ur self !!! ¶;-)--~