>I have written a windows service application that converts Word docs (.docs and .rtfs) to .tif files and moves them into a third party imaging system. The service runs on a Win2003 server. The documents are converted by creating an instance of Word, opening the doc and 'printing' (save as .tif) it using a third party print driver (ePrint by LeadTools). The code is fairly simple and I got it to work after tweaking some DCOM settings for the print driver, Word and the Office10 dll.
>My problem is that every day or two, the service stops working. There is no error, and the service continues to run and tries to process documents. What stops is the document conversion. The OS logs each print job and shows that the documents were 'printed', but shows 'pages printed = 0'. The cure is to stop the print spooler and restart it. After that, everything is fine for a few days. It seems like a memory leak? The ePrint people are looking into it, but I wondered if anyone had any other ideas?
>
>TIA
>
>John

This is a work-around.

Place is a DOS .BAT file the following:

NET STOP SPOOLER
NET START SPOOLER

then, create a Scheduled Task for the .BAT file. Set the interval to once or twice a day, reoccur every day.

Therefore the print spooler will automatically get reset every day. The down-side, I think, is the unpreformed, or failing, print jobs will have to be resent after the reset.

my 1 cent.