NickCowley Posted February 2, 2005 Posted February 2, 2005 Hi All I am having issues getting the folowing to work: ASP.NET C# Build Word doc on server from template assign an active printer and print out. Printers are setup as local printers with port as remote server i.e: \\10.10.10.25\\myprinter and friendly name used as ActivePrinter. Issue the PrintOut() command and spools to the printer, but, then get errors and will not pass document to remote print queue. system event raised as follows: Win32 error code returned by the print processor: 3003. A StartDocPrinter call was not issued. This seems to indicate that the document has was not completly written or the spooler lost the reference to the document. Has anyone come cross this? If yes, has anyone solved it, or is their a work around? By the way, get the same issue with printing from Excel. Prints ok when print setup as local printer on LPT1. Many thanks for any help. Kind Regards Nick Quote
Mike_R Posted February 2, 2005 Posted February 2, 2005 I'm not too good with this printer stuff, but This Thread, esp. from Post #7 onward, would seem to be on-topic? The basic idea is to make use of the ActivePrinter parameter in the .PrintOut() command. The key is to use the correct String input; either using a Macro Recorder or a PrintDialog Control can get you the correct String to use. Hope this helps..! Quote Posting Guidelines Avatar by Lebb
NickCowley Posted February 2, 2005 Author Posted February 2, 2005 Hi Mike Manyhanks forhe quick reply. I don't have an issue in getting the doument into the queue. It seems as he document is only resident in memory the print spooler cannot seem to pass on to the remoe port/queue. Cheers Nick Quote
Mike_R Posted February 2, 2005 Posted February 2, 2005 Odd... Sounds more like a Networking issue than an actual Programming problem, yeah? What happens if you print a Word document "manually" to this Network Printer? Quote Posting Guidelines Avatar by Lebb
NickCowley Posted February 2, 2005 Author Posted February 2, 2005 If you print from Word all works fine. I think it's to do with the way the Component passes the document to the printer. Oh well... Quote
Recommended Posts