I have exactly the same error! I cannot print at all. I also installed Service Pack 2 beta... When I try to do anything with the printer it uses so much memory my PC crashes with a "Write Delay Failed" message. If you solve this problem please let me know! If I find any more info I'll tell you.

See if this helps . http://support.microsoft.com/default.aspx?scid=kb;en-us;330174&Product=winxp If not , get the latest printer drivers from epson & if they don't work , get them from MS Updates .

Also , try changing the settings for the printer to print directly to the printer rather than spool jobs. To do this, select the Properties for the printer in question, select the Advanced tab, and then choose "Print directly to the printer."

I just installed XP sp beta 2, and noticed that it would freeze a lot. Looking in the process list, spoolsv is eating all the memory and CPU. I dont even have a printer attached to my PC, its on a different, networked, computer. I just click 'end process tree' on spoolsv.exe in task manager. After this everything works fine. Havnt tried printing yet though :s

To all, Hey I had the same problem with XP Pro SP2. Here is what I did to fix the problem. Get the spoolsv.exe from longhorn and copy it to your XP in the system32 folder and the servicepackfiles i386 folder. I did this in safe mode with the spool service off just to make sure there was no problems. reboot and then reset the service to automatic and start it...... You should have no problems with that.

THIS is my problem also!!!!! I tried to get spoolsv.exe from longhorn(I do not know wht that is, but Google put me to MSDN)without success. The suggestion and plan was to copy it to XP in the system32 folder and the servicepackfiles i386 folder. I am a NOVICE (intermidiate wanna-be) so explicit instructions are really helpfull. HOW do I get spoolsv.exe tks Johnathan

Well, I have seen posts of other people having the same symptoms. A MS document says that the client is connecting to the server and opening up too many named pipes, although somewhat cryptic, if you can log onto the print server, open up a cmd prompt and type " net files " For me that produced a couple thousand connections. From what the article said, something went haywire and the client keeps sending requests but to no avail. I have a epson C64, but as I said there have been other people with different brand printers, so this is probably a nasty bug for everybody using WinXP with SP2. Since MS doesn't "technically" support this yet since it only went out to certain people, I hope that they have tested and reported this error. Does anyone know if there is going to be another release of SP2 before final release? Thanks Jamie Oh, and for the solution, I am uninstalling SP2 right now. I can wait... for awhile anyway :-) I'll post back if I'm still having the problem after killing SP2

Yes, it worked!!! I killed SP2 and wala! spoolsv is sulking at a low 3-4 MB as it should. Anybody else who has this problem and finds this post, UNINSTALL SP2!!!! There is no point in using SP2 if you can't print, right? Jamie