I recently did a decent size batch print (2000 tickets). For some reason, one account with 17 tickets ended up printing on about 500 tickets. Most were blank with bits and pieces of what should be on the ticket. It only happened to one account out of all that were batch printed; the rest were fine. This isn't the first time it has happened so I'm reaching out! Has this happened to anyone...and do you know why this would happen? It's a waste of ticket stock!!
Thanks!
Genie
We have had this same issue. Did you figure out what it was?
We had a similar issue, with a batch print back in January. Of course we're in an interesting situation where our office is a cloud-based, hosted environment. Adding to the issue, we're RAMP clients as well. So we log into a cloud-based environment and then launch a hosted application from within that hosted environment.
At the time we submitted a ticket and this is the response we got in return:
Did you get all of the tickets you needed as well as the problem ones or was it just the problem tickets? Normally when you get weird characters like that it is because of an issue in the data of the print job as it is being transmitted to the printer. When you print in RAMP, the print job is rendered into a file that is then sent to the RAMP Terminals Server's print queue. The RAMP Terminal Server print queue then sends it to the printer on the machine where 2X is running (in your case this would be the Citrix server). From there the path depends on whether the printer is connected to the local PC or has a network connection and if there is a local Windows Print Server on the local network. If there is a problem with the transmission from the machine where 2X is installed to the printer itself it can lead to the printer being unable to print the information properly and will lead to strange characters. If the end of print job signal at the end of the print job is not properly recognized the printer may have to time out before printing the job (similar to the symptoms listed in TASK ticket #8476). Depending on if the printer is connected locally to the PCs or networked I would have your IT folks look at the settings and cabling to see if there might be an intermittent problem causing trouble. If they are locally connected, make sure there are not additional interface cables plugged in. If possible, a locally connected printer using a locally installed 2X client would help reduce the variables during troubleshooting and testing.
We've also changed our set-up from EMF to PDF and that seems to have solved the issue for us.
I've seen this occur during a batch print when there were contiguity problems in the facility. Try going in to Facility Manager and running the "check completeness" report on the map in question. If you find errors - usually missing or duplicate contiguity - and you fix them, remember to run the facility update scripts to get the fixes into the performances that are already built.
Hi all,
So we are having a similar issue here but it's quite a strange one and we can replicate it on an order by order basis. The facility does not have any contiguity errors/duplications.
Basically, the occasional ticket is printing off the top two lines on one ticket and the rest of the information on a second ticket. This seems to occur if the constituent has purchased something else on a different ticket design in the same order. We can replicate this if we try and print the whole order again (ie. it prints over two tickets again) but if we just print the tickets to the one show in the order it prints them properly (ie. on one ticket).
The shows for which this issue has appeared are both printed on ticket designs we created in V12 and are being printed alongside something else that uses ticket designs from V11. This is our best guess as to the cause at the moment.
Does anyone else see this or have any advice before we raise with Tessitura?
Apologies if that isn't clear - it's quite hard to explain.
B
Just a thought about troubleshooting - not an answer exactly, but you might try repeating the same batch print, but print to file instead of printing to a boca. Then you can check the file for any odd line breaks or spots where the fields otherwise don't line up properly. That might give a clue about what's triggering the weird breaks in printed tickets.
Hi All,
We managed to resolve our printing issues by changing paper size from A4 to Letter in advance printer settings.
Best regards,
Dmitrij
We had the same issue, and checking/fixing contiguity TOTALLY FIXED IT!!
Thank you so so so much! It was driving me crazy!
-Kyle