Good news.
Hi Dave! I reinstalled FreeFlow Core version 6 on a VM and it worked as expected. I believe that the problem of not returning information about spot colorants may have been caused during the update. I thank you for the tests you did and for our conversations. Best Regards.
My FFCore is also 6.0... Could you send me your files to test? I´m a Xerox support analyst of my country, my email is elvio.arruda@xerox.com
I was not able to download your files. I made my own. I am not seeing a problem with CMYK + Pantone Spot documents. I am using FFCore 6.0.0. I recommend contacting Xerox support to determine the issue.
Not even restarting the PC works at all, that is, it seems to be a bug. Thank you
Elvio,
I understand your frustration. The only "quick" solution may be a reboot of the system. From the log, I cannot ascertain a fix. Xerox support should be able to sort out the issue.
Thanks,
Dave
Hi David! XML was the format I had already chosen for the Preflight Report Format. As I said, the error only occurs only when I use the Colorant variable $FFwfDoc.ColorantNames$. The watermark works with any other variable or text that I tried. The workflow is so simple, just a preflight node (xml format report) and a watermark with the $FFwfDoc.ColorantNames$
Regards
Élvio
I am not able to recreate the problem. Note: xml format needs to be chosen for the Preflight Report Format to obtain $FFwfDoc.ColorantNames$ in the Watermak node.
Looking at the log, it appears that Callas xml report reader has the "wrong" version. This should not be happening. Please contact Xerox support to debug the issue.
I´m just did a simple workflow:
1) Simple Preflight just checking fonts not embedded;
2) Watermark using $FFwfDoc.ColorantNames$;
3) Save PDF;
My FFCore is version 6.0. I already read here the article PDF Colorants about the use of th variable $FFwfDoc.ColorantNames$ but a message "internal error" still appears and tells me to look at the FreeFlow log. There is a lot of information in the log, indicating errors but I can't know how to solve it. Bellow, a link to image that shows part of the log:
https://photos.app.goo.gl/V39UTzo7erghUigJA
Any tips???
Solved! Go to Solution.