Thanks I made the change "Remove Unsupported Settings", the description made it look promising but I did not help.
Check the Job Ticket Verification settings by editing the printer. I would try setting it to "Remove Unsupported Settings".
1) Core 6.2.1
2) Not sure we have a number of Generic XPIFs we use becaue befor we moved to Core FF Required 1.
3) Error is in Core.
I have never had sucess in attaching anthing in this forum If you can email me at Jeffrey.email@example.com I could send an XOIF that fails that way. I had worked with Brendan Brown and John Czudak at Xerox when we ordered the Iridesse and sen't them a number of XPIFs for testing.
So a few questions: 1) what version of Core are you running? 2) what features are being used in the XPIF ticket? 3) is the error appearing in Core or at the Fiery?
So Core takes in XPIF tickets and converts the ticket under the hood when it communicates with the Fiery via IPP. Clearly the error message is stating an option was used that is not available.
Can you attach (for review) an XPIF here in the forum that is causing this issue? You may need to zip the file before attaching for it to work.
There are ways to use the Save preset to 'drop' the job ticket but it gets a little more complicated.
Lets get these initial answers and go from there.
I have been using Max for a few years not sending Jobs to several Xerox Printers with FreeFlow DFEs.
We recently got an Iridesse with a Fiery DFE.
My issue is we were told thet FreeFlow Core would be able to pass the XPIF information passed with MAX to the Fiery in a format Fiery can read. This appears to be false as all the Jobs fail. My question is can a single CSV passed through MAX drop the XPIF if the job is pointong to a Fiery Printer. If not this is going to be painful.
Failed Job Message:
"The document could not be printed because invalid job ticket attributes were encountered."