Hi all. I'm not certain this is the correct forum in which to post this but here goes.
Ever since we moved to the Nscan system we've had issues off and on with random scanners connecting, updating their profiles and apparently being ready to scan tickets, and then when a ticket is scanned a message pops up saying "Could not connect to server". It's very bizarre behavior. Sometimes going out of the Nscan software and back in will fix the problem. Sometimes a reboot of the scanner will fix it. However, there are times when neither of these will work and the scanner is worthless that night. Again, this happens randomly among the scanners. It's not always scanner 1 or 2, for instance.
I'm just wondering if anyone else who is using Nscan has seen this issue, and if so have you resolved it?
We sometimes see a message “Could not connect to server” and it is because our Wi-FI is not available at the moment in that location.
Sabina
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Jon HarrisonSent: Monday, March 04, 2013 12:19 PMTo: Sabina SpilkinSubject: [Tessitura Technical Forum] Nscan and ticket scanners
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
I contacted the Tessitura guy that helped set this up for us and he did say that it sounded like a wifi issue. What's strange is that the scanners don't indicate there's any issue with the wifi. The scanner bars are full or almost full and other scanners right there are working fine. It's so confusing but it's good to know that others experience the same problem. So neither of you have worked out a permanent fix or solution to this issue?
ok, I have battled the scanners in our venues for a year when we moved into our new space and I finally got them working correctly and very reliable. The infamous "cannot connect to server" was killing me. Every time I was scanning tickets it would work fine and the minute I would walk away the message would appear for an usher. There was no common factor when the message would appear. This is how we fixed the issue:
--obviously check the overlap of the AP's (should overlap 50%) and make sure they are on a stable pipe (this was never an issue for us but i thought I should mention it)
--turn off the SSID from broadcasting.
--make sure the security on the AP's is WPA not WPA2 and reconfigure the profile on the scanner to match.
I have not had any issues for 6+ months. I hope this helps you and good luck. Feel free to email me if you have any questions.
Travis
Normal 0 false false false EN-US X-NONE X-NONE
It's great to see this conversation, and we'd love to have seen it last year! We have had the same issue, on and off, since last October at least, and have only recently reached a reasonable level of stability.
Unknown said: --obviously check the overlap of the AP's (should overlap 50%) and make sure they are on a stable pipe (this was never an issue for us but i thought I should mention it) --turn off the SSID from broadcasting. --make sure the security on the AP's is WPA not WPA2 and reconfigure the profile on the scanner to match.
We arrived at all three of these solutions as well! In addition, we make sure that there is one wifi channel that scanning uses *exclusively*: this cropped up early on, and we've added language to our contracts for visiting companies spelling out what channels they may/may not use.
We tried many other things as well, though the above are the ideas that were the most useful.
I agree - it's great that we are having this discussion. Maybe the Tessitura folks can chime in if they have any information, but at least it would be good for them to share this information with organizations in future Nscan installations, perhaps make it part of their documentation or something. I'm going to run all of this by my manager and go from there, but finally it looks like we may be able to fix our problems! Yea!!!
If you were wondering what hardware we are currently using here you go.
Hardware:
Access Points
--Meru dual channel AP 150's (7 of them covering all three venues)
Scanners
--Mc 55 (12 of them)
Ah, good information. We use the MC55 and 75A models. We have about 16 55's and 6 75A's. We're using Juniper access points on a Juniper switching network infrastructure.
I have another detail to add from the Guthrie. We also discovered that one of our WAP's was bad. It allowed the scanners to connect to it and worked some of the time. At other times it would send garbage back to the scanners and they would not be able to connect to the server. We installed a new WAP and shut down the bad one. Things have been stable since then. I agree that it was a VERY frustrating and hair pulling out issue.
Thanks so much for posting this, Lou! We are experiencing this exact issue, and would like to keep what is left of our hair!