Discussion Locked

Spool32 error epidemic in mixed environm

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Users reporting epidemic of spool32 errors, mostly "invalid page fault at kernel32.dll" -- increased dramatically after we were infected by the Lovebug. Checked for corrupted dll files -- all clean. Tried workaround of making call to spooler from 32 bit apps first; not working reliably for all users. Users locking up, can't print, can't work, can't stand IT right now. Suggestions?

9 replies

by igp

Try to reinstall drivers (phisicaly deletion + installation)
If unhelpfull there is only one way: reinstall Windows (try fix mode)

by lylea42

Had similar problem in same environment when we were attacked by the love bug and the only solution I could find was to reinstall. You cannot find every file that has been deleted or infected. It picks them all at random unless you try to isolate to virus first with your anti virus software them purge your system and manually reinstall the dll's. This make take some time and I found it much easier just to reinstall the operating system.

run your vrus scan first with any new updates, delete any infected files then turn your virus scan off and reinstall.

by wayne

Try replacing the MFC42.DLL with version 7.2. This is a common shared dll between MS Office/Outlook applications and Novell.

If that doesn't help, get ahold of the client unistaller and run it. After, do not reboot but manually search your registry with keywords NETWARE and NOVELL. Get rid of any reference, then reboot and reinstall the client. You may also want to reinstall the 3.1 client instead of 3.2.

Good luck!

by m_a_singer

Really wanted to try this but couldn't find 7.2 version of MFC42.dll. Did reinstall the Netware client and it helps for a while.

by todd o.

To the extent that it was your NT Server that was nailed by the virus, you probably should restore from backup all of your files with the extensions .EXE, .COM, .DLL, and .SYS from a backup made shortly before May 4. Unless you have added or updated some applications, that should be safe to do (obviously, you will want to do a backup right before restoring so you can get back to square one if something goes sideways). If the virus clobbered some of those files, it probably also took out some .TXT files, which you might also want to restore from backup if you can identify them.

You did not say whether the users can print from some applications but not others. That might be worth looking into. At a couple of my client's sites, they got hit with a couple of other worm viruses at the same time they got hit with the Love Letter virus and that caused some printing crashes when they tried to print from MS Office apps. Repairing the damage caused by other viruses got them back in action.

I agree with t

This discussion is closed to new replies.