Discussion Locked

WIN2K Pro Spooler Grabs Memory?

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I use a W2K Pro machine that has access to both an Active Directory network and a Novell Network. I have the Novell 4.8 client on this machine and never had any problems until the Active Directory network was added to this machine. Now, I have to keep the spooler stopped all of the time. If I do not keep the spooler stopped, it starts grabbing memory and will not stop until all memory (RAM and Virtual)is gone at which time the machine locks up. When I stop the spooler, memory usage is normal.

As soon as I start the spooler again, it starts grabbing memory again until the memory is gone.

What can I do about this?

5 replies

by dallen

I also encountered the same problem. I was running a Novell 4.71 client on WIN2k Pro. I upgraded to the 4.8 client and still had problems. The problem lies in NDPS. If you use NDPS on your network, it causes the spooler to hang. I have uninstalled NDPS since, and have had no problems and it has been 4 months. In my opinion NDPS, has way too many bugs in it. We have since gone to windows based print servers.

by curlie

I tried this and have had no problems with the Print Spooler since I deleted the NDPS from the Novell Client 4.8.

by bhostmeyer

This is a known issue with microsoft and has been fixed with sp1 for win2k

This will accure when you pause, stop or restart a print job.

Don't know the article number of the top of my head.

Thanks

Brooke Hostmeyer

This discussion is closed to new replies.