This is the scenario:
NT Server, service pack 6a applied. No exchange or sql running.
Problem is with the network printing. Started with one printer (an epson reciept printer running off a Lexmark MarkNet adapter) not receiving print jobs, orcorrupted job. Tried reinstalling driver, recreateing printer at client, same results, tried printing from server – worked. Once. Then got same results from server as from client. Then was informed that all network printing had ceased with “unknown system error”. This appeared to be an access denied error going thru the server, as printing to any network printer from the server recieved an access denied error. Researched Technet, applied hotfix from Microsoft for this error (the one containing the rpctr4.dll file), this did not fix the problem. (I had already stopped/started the spooler). Then created a new spool file location , this fixed the problem. I thought. Lasted for about 2 hours, then the network printing went down again with the same errors. On a hunch, checked the new spool folder, was full of files (about 85 or so), deleted *.*, and fixed problem. However, the folder keeps filling up with files, (anywhere from 60 up to 250 before printing stops), deleting everything there starts things going again, but I can’t figure out why it is happening.
One thing I noticed was that the jobs filling up the folders were the job files themselves, the header files were not there at all.
Anyone have any ideas on this? Ever see the like before?
