Hello,

From time to time it happens that specific print jobs from SAP are not printed. But in the SAP system the status is "finished" and the Windows Server 2008 R2 print server has a 307 event for this print job. So everything looks fine, just the printer didn't print the job and it doesn't show an error message.

So I think the print job got lost somewhere between print server an printer or was rejected from the printer - maybe because of corrupted data.

But I wonder why there is the event 307 in the print operational log. What's the precondition for Windows to write this event. Windows doesn't seem to communicate with the printer to receive a message which confirms the job really to be printed.
Is there any information about WHEN this event is written?

Regards,
Dirk

Hi,

Thanks for your post.

Did you receive any other event about this issue?

Meanwhile, for more test, we could use another application print job to check the result.

Regards.

Hi Vivian,

This is what is written to the print service operational log:

Information,25.06.2015 22:00:08,Microsoft-Windows-PrintService,307,Printing a document,"Document 8023, SAP Spool-ID: 0000269707-1 owned by SAPService on SAP-Server was printed on SAP-Printer through port SAP-Printer-Port.  Size in bytes: 17051. Pages printed: 0. No user action is required."
Information,25.06.2015 22:00:08,Microsoft-Windows-PrintService,805,Print job diagnostics,Rendering job 8023.
Information,25.06.2015 22:00:08,Microsoft-Windows-PrintService,842,Isolating printer drivers and other plug-ins,"The print job 8023 was sent through the print processor welpprint on printer SAP-Printer, driver Generic / Text Only, in the isolation mode 0 (0 - loaded in the spooler, 1 - loaded in shared sandbox, 2 - loaded in isolated sandbox). Win32 error code returned by the print processor: 0x0."

So everything looks fine for the print server and it wirites this log. All preconditions to write this 307 event seem to be fullfilled. But which are they and what is noch checked by the print server?

Regards,
Dirk

I'd start by setting the print processor to WINPRINT, unless welpprint is something SAP needs. The print processer of the "Generic / Text Only" is WINPRINT.

I have no idea if this will make any difference but you should start with a standard configuration and work from there.

Hi Alan,

The WELPPRINT print processor is in fact needed by SAP (for Unicode Font and Barcodes).
But my original post is not about finding out what happend to this print job. The topic is: What is the precondition for Windows to write event 307. No matter if the job was really printed or not. I just like to know what has happend (and what has not happend yet) when this event is written.

With this knowledge I could classify the value of the information of this event. Obviously it is not a reliable information if you want to be sure, that a job is REALLY printed.

Regards,
Dirk

• Edited by chaoshacker Thursday, July 02, 2015 2:03 PM

EndDoc has been processed when this event is fired off.  The device has not reported an error to the port monitor and the spooler will delete the print job as the next task.

The spooler did print the job and ran through all the steps to accomplish this.  Since there was not a component that reported any error to the spooler, 307 from the print service seems like the thing to do.

When the printer has a hard drive, the spooler will post event 307 prior to the job actually getting printed by the device because the print job is at the device, the spooler is finished with the data.

Print drivers and Language Monitors for specific printer models are around that can return True end of job but I'm not sure when the 307 event is posted when the print job goes from "Printing" to "Sent to printer" to "Printed"  to "Deleting", then "Deleted".

Thanks Alan! But do you also know if there still can things go wrong on the print server with the print job after event 307? Or can it only be that there is a kind of data corruption on the network transfer or something with the printer itself? In my case the printer didn't show an error as far as I know (it's connected by TCP/IP port and a few thousand kilometers away).

I would make sure that PS errors are enabled on the device if you are using a PostScript driver. I would also turn off Auto Continue on the device if this is HP.  Maybe with these two device configurations you can determine if a device error occurs.

Just so you know.  Disabling Auto Continue will place the device in an error where it will need to be power cycled so no printing would occur after the error .