Anyone have any tips/advice on this?
Assuming the error triggers when you attempt to release the job, I would start with 2 questions. First, it seems like a script issue so I would ask if you have a script assigned to the print server (providing the scripts and/or details about it would be useful). Second, is this error only seen on jobs that have a significant number of varying attributes (i.e. not 95 pages of mono letter followed by 86 pages of color, but a 1 color page at X paper size followed by 2 mono pages at x paper size followed by 4 pages mono at y paper size, etc... such that you end up with an incredibly long string as shown in your screenshot (which only accounts for 31 of the 181 pages in your document)?
If you do not have a script in place on the print server, then you should open a ticket with Pharos. Presuming you do have a script in place, and it only happens on lengthy jobs, my guess is that your script is parsing through the attributes for some reason. Without the script and logs from the print server assigned to the release station showing the error in action (assuming a decent level of logging in the script), it would be hard to comment further, but the general gist is that it appears some kind of manipulation is attempted on a string and the specific instructions being passed are not possible to make.
For example, if I have a username of "steven" and the script call a LEFT function with a value of 3, we wind up with "ste". However if we use the LEFT or SUBSTRING function and tell it to take the first 7 characters (which includes a position that does not exist since my name is only 6 characters long), you could expect to see an error. Incorporating String.Length would make the script intelligent to help automatically handle an unexpected result, likewise wrapping the commands in a try/catch statement and giving a more informative error that helps pinpoint exactly where the problem is occurring. Again, assuming you have a script in place you can try to narrow down which one it is and then search for the substring and left functions to see where the error may be occurring.
I have tried releasing the attached document from the Print Center application and also from Pharos Station. It printed fine and Job attributes are 180 pages of 612x792, Duplex, Letter, Mono, 1 page of 612x792, Letter, Mono, Simplex.
So, as Steven said please check your environment, probably scripts are creating problem.
By the way, which version of Uniprint are you using?
This was seen in Uniprint 9.0 and as far as I know it was subsequently fixed in the Uniprint 9.0 Print Services Revision 126. Can you verify that you have applied this Hot Fix.
Thank you all for your responses! We are using Uniprint 9.0, so that makes sense. We have not applied the Hot Fix you posted; we will try applying the fix.
Thank you again!
Sorry I took a while to get back to you on this.
In discussing this with my supervisor, we've decided to upgrade from Uniprint 9.0 to Uniprint 9.0 R2. We believe this is going to be the best long-term solution for this and other issues we've been having.
Thank you for your time!