We have a few files that are in the PPI error directory due to network not being available at time of processing -

ERROR: I1012 : Error moving archive to \\dokcfile1pd\dept\MK\MKReports\MK305_LIVE_OCSR: Error code 64: The specified network name is no longer available.
ERROR: I1005 : Error while processing job; moving file to error folder: 40CE390B.ps

In V3 we were able to drop these files right back into the PPI IN directory when network was restored and they would process successfully.

Now in V7 this is the results when we drop them back into the PPI IN directory

DEBUG: Watch Process Name : Create_PDF_from_MK305
INFO: Starting conversion...
WARN: I1031 : The PS job does not contain the filename anchor; assuming it is a resubmit
INFO: Initializing PlanetPress Alambic...
INFO: Distilling file to 346297_A03LTRS.pdf...
DEBUG: %%[ Error: invalidfileaccess; OffendingCommand: file ]%%
DEBUG:
DEBUG: Stack:
DEBUG: (w)
DEBUG:
DEBUG: (C:\\Documents and Settings\\All Users\\Application Data\\Objectif Lune\\PlanetPress Suite 7\\PlanetPress Image\\Spool\\40CE390B\\346297_A03LTRS.pdi)
DEBUG: /FO
DEBUG:
DEBUG:
DEBUG: %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
DEBUG: %%[ Warning: PostScript error. No PDF file produced. ] %%
ERROR: I1007 : Error while converting to PDF : Error converting file: PostScript distillation did not produce any page.
ERROR: I1005 : Error while processing job; moving file to error folder: 41F0A57E.ps
TIME: 2009/08/24 10:00:35

I would like to be able to just drop these already processed postscript files back in to process without having to use the resubmit function on the original file since they only were in error because of network connectivity.

Any ideas are appreciated.

Any updates on this as I have a similar problem.

Hi Chris,

I guess the 'on error' properties of PlanetPress Image really don't work. I had to send the Image output to a folder on the local box (MOVE_PDF is what we named it) then run a separate process to move the files from the MOVE_PDF directory on the local box to the network directory and use the 'on error' properties of the Send To Folder output in this process. We created an 'on error' process called 'Failed_PDFs' and new directory FAILED_PDF for this. If any files fail the on error process drops them in the FAILED_PDF directory. Once network connection has been restored they can be moved back into the MOVE_PDF local directory and will process like normal. A few more processes to support but it has worked very well for us.

Hope that helps!

Indeed, the On Error process of an Image output doesn't do anything. This is due to the fact that Image is a separate service from Watch, and Watch doesn't monitor errors that are happening on the Image side.

If you want to use On Error on pdf creation, try using Digital Action, or Create PDF if you have Office or Production, since these actions occurs on the Watch side and aren't part of a separate service.

Regards,
Rapha