cancel
Showing results for 
Search instead for 
Did you mean: 
4 Replies
Michael325861-xrx
FreeFlow Production Workflow Moderator
FreeFlow Production Workflow Moderator

Re: "The document could not be printed because invalid job ticket attributes were encountered.&

Please contact Xerox Customer Support at (888) 550-6336 and they will assist with troubleshooting, and generate a bug report (SPAR) for tracking purposes, if necessary.

0 Kudos
DavidU54339-XRX
FreeFlow Production Workflow Moderator
FreeFlow Production Workflow Moderator

Re: "The document could not be printed because invalid job ticket attributes were encountered.&

Contact Xerox support and explain the issue. They should be able to guide you through the submission process. If this does not work post another message and I will obtain more details.

0 Kudos
jkraft
New Member
New Member

Re: "The document could not be printed because invalid job ticket attributes were encountered.&

I'm not familiar with the process to author a SPAR.  Could you explain how this is done?  Thanks.

0 Kudos
DavidU54339-XRX
FreeFlow Production Workflow Moderator
FreeFlow Production Workflow Moderator

Re: "The document could not be printed because invalid job ticket attributes were encountered.&

Could you author a SPAR? From your description the problem could reside within FFCore or the DFE. In-depth analysis of the job ticketing provided by FFCore to the DFE is necessary to determine the source of the problem.

0 Kudos
jkraft
New Member
New Member

"The document could not be printed because invalid job ticket attributes were encountered."

We recently upgraded to FFC 5.4.0 and added two Xerox Iridesse printers.  For each printer, one Printer Destination for a certain type of printing always fails with the error "The document could not be printed because invalid job ticket attributes were encountered."  Note that we have many other Printer Destinations, to different Virtual Printers, configured and working perfeclty.

Through trial and error, I discovered that I could get past this error by setting Define Job Ticket Default > Main Stock > (some actual stock) on the Printer Destination.  We don't use Job Ticket Defaults for any other Printer Destinations; only for this workaround.

I'd like to report this as a bug.

0 Kudos