I'm a licensed meeting host and was demonstrating a meeting room this morning with two co-workers (another licensed host and a guest). To demo the guest admittance process, I logged out and tried to log back in as a guest but my admittance request pop-up box never showed up on their screens. After 30 seconds of waiting, I refreshed my browser and logged back in under my own account but Connect seemed to open up a parallel version of the same meeting room. I did not see my co-workers in the Attendee Pod nor did they see me in theirs. I could interact with the pods in my room and they could in theirs but we didn't see each others changes. After about 10 minutes the second licensed host reported that a graphic in a share pod had vanished and that the pod was completely filled with white. The guest, however, could still see that graphic but a different pod had filled with white on his screen. The the host lthen ost her connection to the room and her re-login connected her with my meeting room. The guest was eventually bumped from the now-hostless meeting and when he reconnected he also was in my version of the meeting room.
This is similar to a problem we had in the same meeting room several weeks ago when we had a problem admitting guests. At some point in the meeting the pop-up boxes would populate but the links did nothing and the pop-up boxes did not vanish after cicking. No additional guests could be admitted to the room (which was well below our 100 person limit BTW). Staff with passwords could access the room as normal, but guests appeared to be locked out.
Adobe support suggested that our original problem was due to the recent upgrade but they never specified why.
Has anyone else ever experienced such behavior? Is there anything at our end that I can troubleshoot? Can a meeting room be live twice simultaneously?
I've since learned that our local internet service was experiencing network problems during both of these problems, so now my question becomes: Has anyone experienced any similarly unexpected behavior from Connect during a period of increased network traffic?
The white pod issue I've seen before - once during a period of heavy CPU or network use (don't remember which) so the meeting hung before the screen drew (and then Flash timed out on getting the pod data altogether). The other times I've seen this in Connect was due to a bug with ActionScript 2 files with Connect 8, and I haven't seen that for a long time.
Do you host the server yourself? If not, the application.log (meeting log) files would be helpful - or, if you've got local connect add-in logging enabled on your PC, that would be even better.