An MP4 recording will be published and posted within 24 hours of invoking the conversion.
- the actual amount of time it takes to convert a recording depends on many factors including:
- the length of recording
- the queue of recordings to be published on the publishing servers
- the queue of recordings within Connect prior to transfer to the publishing servers (they are submitted in parallel to the conversion servers)
- the time it takes to download the converted MP4s from the conversion servers back to Connect
- and variables commensurate with asynchronous processing
Note also that if for any reason the conversion to MP4 should fail, we will retry multiple times depending on the cause of the failure. Retries will extend the processing time required before the recording is available. The two most significant variables are the length of the recording and how many recordings are ahead in the queue.
Issue: When installing FMG as part of an on-premise Connect deployment, the fresh installation of FMG includes many default profiles in the sip. xml file. When you enter values from Connect console (port 8510 locally on the server), those values are populated to the first profile that is listed in sip.xml (sipPhone) and not to the correct sipGateway profile which is called from the workflow.xml file.
The expected behavior is that the values from Connect console should update the sipGateway profile rather than the first profile in sip.xml
Workaround: The Adobe Connect Support team is using currently approaching this problem from one of two possible ways:
- You may copy a sipGateway profile from a vertsion of FMG prior to version 2.x and paste that into FMG 2.x.
- You may call sipPhone profile from workflow.xml
Note: In FMG prior to version 2.x, sipGateway was the first profile listed in sip.xml. The workflow.xml file checks the input number and on the basis of that chooses the profile from sip.xml. With default FMG settings it will be using ‘SipGateway’ most of the time. This is scheduled to be fixed in Connect 9.3.
Issue: When using a named instance of SQL server with Adobe Connect, if you enter the name of the instance during installation, the connection to the database will fail.
Workaround: Instead of using the name of the instance, you may enable TCPIP on the instance and use the IP address and then enter the port number for which the named instance is configured on the separate line as appropriate; if the named instance is listening on port 1833 (instead of 1433), then you would use the IPAddress (192.168.1.1) and then the port number (1833) in the appropriate fields.
Using the instance name during installation after Connect version 8 will not work. The best approach is to use the port number of the instance and the IP Address of the database server.
To troubleshoot this, use SQL Server Configuration Manager:
- Make sure the instance has TCP/IP enabled.
- Check to see what port the instance is listening on for that IP.
- Use the IP address as server name (no instance name). Put the port number in the port number field.
- Make sure the named instance is listening on the port entered in Connect
Beginning with Connect version 8, the installer changed; in previous earlier versions, you would need to enter the the server instance and port on the same line. The newer installer has the port on a separate line:
PORT: INSTANCE PORT-NUMBER
DATABASE NAME: SAMPLE-NAME
CONFIRM PASSWORD: ****************
The changes in the installer (beginning with Connect version 8) caused some confusion with named instances.
A named instance will work on an initial installation. Sometimes, in an effort to troubleshoot you may initially point to a conventional instance of SQL in order to establish the installation and then point the established Connect installation to a named instance. The DB connection from an established Connect installation is more robust and forgiving than that of an initial installation. After the installation is complete, you can modify custom.ini to include the instance name.
Note: You could use the server name, but you would need to ensure that the named instance has NAMED PIPES enabled.
In Connect versions through 9.2, there is a known issue relating to sharing applications in a multi-monitor setup.
The behavior can be duplicated as follows:
- From within a Connect meeting room, click “Share My Screen” in a Share Pod
- In the Start Screen Sharing dialog that appears, choose to share “Application”, and select an application to share and click the “Share” button
- The application window needs to be located on the second monitor of the user who is sharing (you may need to drag the application window to the second monitor)
At this point, other users attending the meeting will not be able to see the shared application.
This issue is expected to be fixed in Connect 9.3
Description : If you create an “on-demand” content and associate that content with any of your events. You can definitely see that content under the list view of your Event Catalog page as shown below:
However, you will not be able to see that content under the Date view
This is by design, only Live Presentations are visible in both ( Liste View and Date View )
On Demand Presentations are visible only in List view and not in Date View.
At present this is how it works however in future probably we see some changes in this section as well.
Hope this helps answer some questions,
Some users running Ubuntu Linux and use Firefox may see problems connecting to meetings.
The same meeting loads fine in other browsers like Chrome or Chromium.
This can be related to a Security Certificate not being set for use with websites in Firefox.
Follow these steps to verify and correct this:
1. Open Firefox and select “Edit”, “Preferences”.
2. Select the “Advanced” Tab and click on “Encryption” .
3. Select “View Certificates” to open the certificate manager.
4. Select the “Authorities” Tab.
5. In the list of certificates find the one called “Verisign Class 3 Secure Server CA – G3”.
6. Select the certificate and click “Edit”.
7. Check “This certificate can identify websites” and click OK to confirm your changes.
8. Restart Firefox and retry the connection to your meeting.
Issue: When attempting to publish Captivate content that includes a random question slide linked to an empty question pool directly to an Adobe Connect server Captivate crashes. We reproduced this issue with a Captivate file composed of a quiz with a set of random questions near the end of the project. Upon clicking on the publish button, a dialog box pops up stating that there are more random question slides than questions available in the pools. The options are to click “yes” to publish or to click “no” to invoke the question pools manager and edit the quiz. Upon clicking yes to publish the file, the error message ensues warning that your attempt to publish your project to the Adobe Connect Server has failed.
Result: Captivate crashes aborting the publishing process.
Workaround: Publishing the Captivate project as a .zip file works fine.
Expected: Captivate content that includes a random question slide linked to an empty question pool should publish directly to an Adobe Connect server without any issues.
This problem is scheduled to be addressed in Connect 9.3 with Captivate 8
We’re soon starting to upgrade our Adobe Connect Hosted clusters to version 9.2, the upgrade for on-premise installations will be available soon as well.
Please make sure to go through the upgrade checklist: http://helpx.adobe.com/adobe-connect/kb/connect-92-upgrade-checklist.html
You can check your upgrade date here: http://www.adobe.com/support/connect/downloads-updates.html
This article addresses how to make sure every URL int a Connect cluster pops up like your grandmother’s trustworthy old pop-up-toaster. If some published content will not play or display properly from your Connect cluster, do the following:
- Make sure that the load balancing device in front the Connect cluster is not using sticky sessions or session awareness.
- If you are using a Big-IP LTM, make sure that Nagle’s Algorithm is turned off .
- Make sure that Clustered servers communicate with each other on ports 8506 and 8507. A simple netstat -an from the command prompt on each server will make certain each server is listening on 8507.
- Don’t try to cheat on the number of documented VIPs required on the load-balancing device or SSL accelerator. Only one VIP is not the right answer.
- When the servers cannot communicate, trouble ensues.Clustered servers need to be able to communicate with each other on port 8507. When they cannot communicate, the links to content will be broken and end users may experience hanging videos or unavailable content.
- Search in your debug log for “cluster-”
- [01-31 18:20:23,729] cluster-8507-696969 (INFO) MirrorHandler: waiting for commands” 2014-02-10T16:30:23.739-0600….
- If you do not see cluster-8507 then there is a replication communication problem on 8507
- To help facilitate troubleshooting, during setup and during upgrades, if possible, allow the servers to have external access – at least allow the monitored and screened ability to toggle external access on and off by special request if needed. This will allow you access to Adobe’s license server and also to troubleshooting tools.
- Install telnet on each server. Telnet is a great test tool. Placing telnet on each server and actually testing connectivity to each and from each server on ports 8506 and 8507 is prudent.
- It is also prudent to have a useful browser on each server. I often install FireFox on each server along with the latest available Flashplayer. You may want to install Flashplayer on IE as well even though enhanced security will render it a challenge to use for any useful troubleshooting purposes. Useful flash-enabled browsers will facilitate direct tests on any problematic content on the servers from the servers thereby eliminating network and load-balancing variables when isolating issues.
When added to a Connect archive recording URL, the following suffixed commands will force the prescribed behavior. This may help with projects that include the embedding of archive recording URLs.
- pbEIOpen=true – the event index would come up opened
- pbEIOpen=false – the event index would come up closed
- pbEIOverlay=true – the event index would show up in overlay mode
- pbEIOverlay=false – the event index would show up in persistent mode
- pbMode=normal – open in normal playback mode
- pbMode=edit – open in editing mode
- archiveOffset=parameter in milliseconds – open to a specific time in the recording
You can modify the URLs along these lines; use an “&” to concatenate multiple parameters.
Every recording will automatically append ?launcher=false&fcsContent=true. You cannot play a recording in the Connect Meeting addin; if you append ?launcher=true, it will toggle to ?launcher=false and open the recording in the browser:
This URL is an example of what a normal URL would look like during recording playback:
To change this to open with the index closed, append pbEIOpen=false like this: