Scanners randomly coming up with very old performance

Steve,

I’m not aware that we have seen this kind of thing before.  Usually our N-Scan scaners scan for the right show, or are configured for the wrong show, or don’t scan at all.

I don’t have a scanner in front of me right now.

However, I’m wondering if the scanner is correctly registering the bar code.

If I remember correctly. The N-Scan software will show the number it scanned on the screen.  If you are also printing the barcode value under the barcode on the ticket do these match?

This would give you a sense if this is a printing, scanning issue.  Or some sort of scanner software or backend issue.

Hope this is helpful.

From: N-Scan [mailto:groups-n-scan@tessituranetwork.com] On Behalf Of Steve Lang
Sent: Wednesday, January 08, 2014 5:09 PM
To: Thomas Brown
Subject: [N-Scan] Scanners randomly coming up with very old performance

I'm wondering if anyone else has ever experienced this, and can hopefully help shed some light.  On the rarest of occasions, inevitably once every few months, when our FOH is scanning at the door for a performance that is scanning without issue, a ticket for the correct show will trigger one of the very first performances we build when going live with Tessitura back in 2007.  A quick scan a second time and the ticket scans no problem.  Here are some of my thoughts:

- we are using the Ticket No data element as the barcode; we've had no other issues with using this, but should we switch to using the N-Scan Number element?

- there is no entry for Doors Open and Doors Close for performances that season as we were using NScan then.  I'm wondering if I should just put values in there now?

Again, any insight would be greatly appreciated.

Thanks,
Steve