Sounds like you need to spar it then, call Xerox, supply the config sheets and they will send it to engineering to get it fixed
We have tried different queue's just to be on the safe side, including creating a new "legacy" que to see if the Adobe PDF Print Engine could have something to do with this (have seen strange things before in that area), and no, the problem is not in the file nor seem to be an issue with FFPS. The issue occurs on both of our 1000 presses and no where else. Also, not limited to a particular job, it's any jobs containg "mixplexing" . All jobs print successfully on our little C75 with FFPS.
As far as paper goes, we run roughly 8MM sheets of this stock annually accross our fleet of b/w and color. This is exclusively a Color Press 1000's headache.
I did try converting to CMYK from the native RGB color source, same result....Interestingly though i added a pipe symbol (|) to the blank pages in 12pt font (so pretty small) in the documents and the problem appears to go away. Of course it's no longer a mixplex job at this point but apparently anything will do as long as it's printing something and not blank.
This leads me to believe that somehow the press itself is logically not recognizing the 1 sided pages inside the two sided print job and is trying to utilize this perceived "open" spot to lay down the registration patch for it's intermitent systems checks or something. I believe that is controlled in the PCUI unit?
If you preview the job in rip is it still there? <because this would put the fault at the IOT>
How about if submitted to a different queue? <Queue based issue>
You have an odd one, I would typically think it was simply a thing in the file submission method, the fact it is only on simplex pages implies it is there intentionally. I don't know Freeflow Output manager at all, but if he happens Acrobat > FFPS with no intervention, we can eliminate that as the source, assuming it is not in the Acrobat file, and is there as soon as it hits the FFPS as verified via Previewing it, if it was a per page, and not just the ones specified as simplex, I would say it was something like Acrobats thing here
But again, that is an every page or no page thing, so that could only be the culprit if you were combining the single pages into the file later, not if it all left in one go (simplex and duplicate pages sourced in same submit) <Prove wrong via printing a different page as simplex>
And if it isn't in the pdf, and if imported direct to the FFPS and printed with no changes or settings (expected it won't), then it would have to be in the queue level, but only gets called into play with what you see in the Exception pages section, yet there is nothing there (At least not in my J75 with FFPS 9SP3) to print anything, let alone bars in the margins. <Prove false via print to another queue>
background form would also not apply unless the pages defined as single were preprocessed and then combined later. <Easily proven by making a different page print simplex and still get the color bar>
It might be interesting to see what would happen if you printed the simplex page in BW, would the bar show up in color or BW, if at all. <Honestly, I don't know where we would be going, but it would interest me at least>
Lastly for now, and I have to ask because it would suck if it was this stupid, but......
You have made sure it isn't on the paper in the tray right? Because that would be annoying ;-) I have actually spent hours on issues where that was the answer sadly.
And is there a Fiery, Creo or FPS on the 1000?
Our typical workflow is to use the Xerox FF print manager app to download pdf's with .xpf job ticketing. We have tested printing directly from Acrobat as well, results are the same with each method
Does it happen when printed only or will it also happen with a pdf imported direct to the Fiery/Freeflow/Creo?
When printing a duplex document 8.5x11 with simplex pages mixed in we get a faint CMYK registration bar on all of the simplex pages (printed side) throughout the document. This only occurs when a 1 sided page(s) is in a 2 sided print job. We have tried both including a physical blank page in the job as well as programming the 1 sided pages as an exception callout. Also both face up and face down output. All yield same result...faint CMYK registration bar on printed side of 1 sided sheets.