General discussion

Locked

spoolsv.exe mem leak after SMS SP3 upg

By cordlapp ·
Problem: SMS (SP3) and Print Spooler ?SPOOLSV.EXE? developed a problem after upgrading our SMS 2.0 (SP2) system to (SP3) where the print spooler begins growing in memory after system starts up and continues to get bigger until all of the system resources are gone usually several hours to a day or so. it is growing in random increments 20+k, 200+k, 1034k, etc (it grew to almost 500MB on some machines). Actually crashes some systems if "print spooler" - spoolsv.exe is not stopped and restarted. Affected Systems: W2K Servers & Workstations connected to both Active Directory Domain and Novell 5.1 Servers with Novell 4.8 Client. This problem currently is not affecting any of our NT4 systems or W2K systems NOT connected to the Domain.

This conversation is currently closed to new comments.

17 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

spoolsv.exe mem leak after SMS SP3 upg

by sdraney In reply to spoolsv.exe mem leak afte ...

Check the event logs (application and system) for a possible error that the system is trying to "mail" or "print" out to some unknown device or resource that is not available. It's possible the event system is interacting with the spooler and randomly generating the memory leak.
Check also the service pack level and if the pack (or lack thereof) has affected the spooling system.

Collapse -

spoolsv.exe mem leak after SMS SP3 upg

by cordlapp In reply to spoolsv.exe mem leak afte ...

Poster rated this answer

Collapse -

spoolsv.exe mem leak after SMS SP3 upg

by cordlapp In reply to spoolsv.exe mem leak afte ...

Poster rated this answer

Collapse -

spoolsv.exe mem leak after SMS SP3 upg

by kgosnell In reply to spoolsv.exe mem leak afte ...

This is a low tech fix that may or may not help, active desktop leaks,and as really additive if coupled with another program that enhances this leakage, turn of the active desktop on all machines connected to the one causeing the problem, as well asthat one, and it will help, but there is a base problem in the setup and has to be resolved or you can't use active desktop while using that device.
Hope this helps

Collapse -

spoolsv.exe mem leak after SMS SP3 upg

by cordlapp In reply to spoolsv.exe mem leak afte ...

Poster rated this answer

Collapse -

spoolsv.exe mem leak after SMS SP3 upg

by cordlapp In reply to spoolsv.exe mem leak afte ...

Poster rated this answer

Collapse -

spoolsv.exe mem leak after SMS SP3 upg

by kgosnell In reply to spoolsv.exe mem leak afte ...

I thought I better explian my reasoning behind "Active Desktop" as many primary setups use a version of Active Desktop, you will habve to detemine what this is on your machine if not normal Windows, as it has been coppied with all it's faults

Collapse -

spoolsv.exe mem leak after SMS SP3 upg

by cordlapp In reply to spoolsv.exe mem leak afte ...

Poster rated this answer

Collapse -

spoolsv.exe mem leak after SMS SP3 upg

by cordlapp In reply to spoolsv.exe mem leak afte ...

Poster rated this answer

Collapse -

spoolsv.exe mem leak after SMS SP3 upg

by rkelly In reply to spoolsv.exe mem leak afte ...

The only thing I can think of for this is it must be to do with Updated Client Side components on your domain based machines.

I find it strange that it only happens on your Win2K SMS Clients. I assume that you have upgraded all your clients/servers to Win2K SP1? I've been trawling the WEB to solve this problem as I've not yet upgraded my systems to SMS SP3 and now won't be until I can find an answer.

I know that Win2K SP1 fixes lots of problems with the spooler service so that is worth ago.

Microsoft also pulled SMS 2 SP3 when it was first released as it caused more problems than it fixed - I assume that you have a very recent copy of the SP so that shouldn't be an issue.

There are currently no new hot fixes available from MSfor Win2K so unless the Win2K Service Pack fixes the problem (and it is always worth a reinstall) I'm afraid that it's that horrendous limbo period where we wait for MS to admit the problem and produce the fix.

Back to Windows Forum
17 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums