Copy link to clipboard
Copied
Fortunately no showstoppers, but it was concerning...
The below issues were experienced yesterday during a live event webinar. Fortunately they impacted only those with Host permissions. Fortunately the attendees were not impacted. For this event we had 5 different hosts, all separately logged in from different machines, from 3 different physical locations (Florida, PA, Texas). This was in a Seminar room. I assume they are specific to the latest upgrade, because we never experienced these problems before.
Issues experienced by Hosts:
1. When first logging in, the Share pod with a PPTX file shared was not loading for the hosts. The rest of the Connect room/pods loaded and displayed fine, but the PPTX Share pod was in a continual 'preload' state with the preloader animation (spinning circle/lines) showing. This happened with two different Share pods with PPTX files loaded into them prior to the event so that they would be ready once the event started. Workaround: stop the share and restart it after the hosts had already logged in.
2. Poll pods: when I select the Pod Options > "Hide" option to hide the poll from the stage, it doesn't go away. It stays. The only way to get rid of them was to drag it to the Presenter Only Area. A minute later I found out that, even though it was off of the stage for me and Attendees, it was still on the stage for the other Hosts, and the only way to get rid of them was to manually drag each poll to the POA on each and every host's machine.
Note: this issue did not impact the first poll used during the event, but it did the second and third polls, which were both introduced to the stage at the same time. Perhaps two polls on the stage at the same time caused the issue?
3. Q&A pod: Export to RTF does not export all of the questions! I would need to go back to look at exactly what questions it did export, but of the 12 questions asked during the event, only 4 of them were in the "Export to RTF" file. Fortunately, the "Email Q&A" transcript works fine - all 12 questions were in the text emailed.
We're on a hosted instance of Connect.
That is a question better answered by Adobe's team. However, I've never seen a bandwidth issue do anything other than cause the entire room to disconnect. I've not seen specific pods appear/disappear due to bandwidth constraints.
Copy link to clipboard
Copied
Hi,
The 3 issues mentioned above are indeed very concerning. .
Though I am sure we should be able to reproduce the 3rd issue in house if it is consistently reproducible. . I am not sure about the 1st 2..
This is the 1st incident of this kind reported after the upgrade, but we will require your help to provide some repro steps for the 1st 2 issues.. please do report to our support team in case you face this issue again or let us know anything which could have caused this.
Thanks
Sameer Puri
Copy link to clipboard
Copied
My chat pod spontaneously closed during a meeting this afternoon. Could this be another bug?
Copy link to clipboard
Copied
@JJones,
Was there more than one person in the room at Host rights? It wouldn't be the first time that someone got curious and hid/changed a pod without realizing that it affected everyone in the room.
Copy link to clipboard
Copied
There were three Hosts in the room but none report going anywhere near the
Hide option for the chat pod. Could there be a keyboard shortcut for this
that a Host perhaps stumbled upon without realizing it?
Copy link to clipboard
Copied
I don't see a keyboard shortcut for closing a pod, http://help.adobe.com/en_US/connect/9.0/using/WS5ae85155c1a0214d1172e081227b89777b-8000.html. If it happened once, I would chalk it up to someone just not knowing that hiding the chat pod would do it for everyone, and I'm guessing they won't do it again. It may not hurt to communicate that any changes that a Host makes to a room affects everyone in the room, just to ensure that it doesn't happen again. If the problem persists, then there may be some condition that leads to the pod being hidden and Adobe may be able to help identify it and provide a resolution.
Just because no one admitted to closing the pod, doesn't mean they didn't.
Copy link to clipboard
Copied
Thanks for the thorough response. What got my attention is that it
happened right when our IT team noted that our bandwidth capacity had
peaked. Can you tell me if each individual pod creates its own stream with
the Adobe server or is the entire Connect window, and all the pods within
it, a single stream?
Copy link to clipboard
Copied
That is a question better answered by Adobe's team. However, I've never seen a bandwidth issue do anything other than cause the entire room to disconnect. I've not seen specific pods appear/disappear due to bandwidth constraints.
Copy link to clipboard
Copied
For those following this thread, I did consult Connect Tech Support about
this. They tell me that each connect room establishes a single stream
regardless of how many pods are active. This doesn't exactly rule out a
single pod crashing due to network traffic delays but it does make it far
less likely.
Copy link to clipboard
Copied
Thank you JJones for publicly sharing your insights and any info to help the future visitors--small but very nice crowd-sourcing jesture.
Not many community members come back to post their tacit knowledge in the forums.
Respect and regards,
Ashish
Copy link to clipboard
Copied
Hi JJones
Bandwidth issues will have no impact on the hiding of a pod. I am pretty sure somebody hit it and is refusing to admit it :-). All connect pods come in a single stream and a bandwidth issue may cause an entire Meeting reconnection instead of a single pod getting hidden.
Thanks
Abhinav
Copy link to clipboard
Copied
A follow-up to my original post. The issues mentioned in that post occurred during a Tuesday afternoon webinar.
The following Thursday we held a webinar with 3 hosts. Only one of the issues above was experienced on Thursday: after one of the hosts (me) hides a poll pod, it goes away as intended for everyone except for one or more hosts.
On Tuesday, when we first saw this issue, most (not all) of the poll pods would not go away for every host. The workaround was for the host to drag the pod off the stage. This happened for all of the hosts at different times on Tuesday.
On Thursday, only 1 of the 3 hosts experienced this issue, and it only happened one time, for one of the polls (we had about 11 polls during that webinar).
It's definitely a bug, but not a huge issue if the hosts know to drag the pod off stage.