On occasion it can be difficult to get verbose addin logging to work. The tech-note describing how to set it up is here: Enable logging | Meeting Add-in
The tech-note correctly describes where to place the customized mms.cfg file for use with both 64 bit and 32 bit Windows clients as well as for the Mac OS.
If after following the instructions in the tech-note, you still do not see any verbose addin logs, one possible cause is that there may be an additional mms.cfg file in an alternate location on the client that is blocking the log creation process. To remedy this, add the customized debug mms.cfg to the following locations after renaming any existing mms.cfg files (to allow them to be restored after verbose logging or debugging is complete):
Here are the locations (more than in the tech-note):
After placing the mms.cfg in both folders, be sure to close all addin browsers and then to open the addin only in the one Meeting that you wish to troubleshoot.
Problem Description :
If you do not have any TLS version enabled in your browser settings, then your browser may fail to establish a secure connection to your Adobe Connect servers and thus may show the following symptoms :
- Meeting connection test fails at Step 2 of connecting to the FMS server
- Meetings connect however are very slow and experience frequent disconnects even if they get connected
If you’re experiencing any of the above symptoms with your meetings, it is recommended that you take a look at your browser TLS settings .
Most browsers nowadays, automatically have TLS settings enabled by default, however some browsers may still not have it enabled. You may need to enable it from the browser settings. Following is how it can be enabled in IE :
Environment : All Adobe Connect Hosted accounts
Reason Behind this behavior :
Due to security reasons , all Adobe Connect Hosted environments only support TLS 1.0, 1.1, 1.2 versions. All SSL versions (SSL 2/SSL 3) are disabled due to security reasons and open vulnerabilities.
It is therefore required that your browser is able to support a secure ssl connection using any of the available TLS versions.
For better understanding, I’ve also put a screen capture as below :
Symptoms: Installing with clean images on servers, the Connect Installation with the appropriate local Administrator permissions seemed to be successful but upon clicking “Done” its hangs indefinitely. Restarting the services does not help and the Connect Configuration Console on the local Connect server will not come up. Rebooting the VM will not bring Connect up. In the error.log, it reads:
“Start up error: java.lang.Exception: invalid backup folder: \\connectsharedstorage\connect.” START_UP START_UP_ERROR….
Note: replace connectsharedstorage\connect with your UNC path to shared storage.
Solution: This error indicates that shared storage is expected by the database but is not configured on the Connect server. This may inadvertently be overlooked during an upgrade instance when a new server (perhaps with a new OS) replaces an older server. The fresh Connect installation, upon pointing to an existing upgraded database that has possibly been updated by script or maybe by the older server image, is expecting shared storage to be in place, but it is not yet configured on the new Connect server. To get past this, edit the Shared Storage entry in the PPS_Config table of the Connect Database to “NULL” and restart the services.
The begin screen-sharing button in Connect is obscured by the task-bar when resolution on a laptop screen is set to 1366×768. You will see this happen, if you use a laptop with 1366×768 screen resolution, attempt to share your screen in Connect. The effect is that the start screen sharing button is hidden behind the Windows task bar at the bottom of the screen:
The expected behavior is for the start screen share button to be accessible.
The workaround options are to either move the task-bar or change the screen resolution in order to expose the button, but since the start screen-sharing button is already highlighted or in focus albeit unseen, if you simply hit the enter key, screen-sharing will begin. Keep in mind that 1366×768 is the default screen resolution for some laptops.
Note: This is only reproducible in high DPI mode and it is not limited to the Connect Screen-sharing dialog. See how the basic operating system “Save As” dialog exhibits similar behavior at the same resolution:
Multiple Adobe Connect on-premise customers have informed us that some of their security scans are reporting that the version of FMS used in Adobe Connect is unsupported. There are no known open security issues in the version of FMS used in Connect today. The FMS components that are embedded in Adobe Connect on-premise deployments are fully supported under the maintenance and support agreements for Adobe Connect. If any vulnerabilities are discovered in these components of Adobe Connect, they will be addressed per the guidelines of those support agreements.
There might be certain circumstances when you might not be able to view the webcam shared in a meeting in full screen mode. You might come across this situation on some mobile devices when using an Adobe Connect meeting room.
Situations under which this might occur :
- Enter a meeting as a host from a desktop pc and start sharing your camera
- Join the same meeting as a participant from a tablet or iPad device
- Click on the webcam option from the left
- The webcam video remains in small size and does not become full screen automatically
Affected Environments Discovered until now :
Connect 9.3/9.4 Hosted/Licensed Environments
Mobile app 2.3 on tablets or iPad
Additional Information :
This has been discovered as a bug and in under investigation by our Mobile Engineering.
Please keep tracking this page for latest updates and status. Bug#3963153.
The following are best practices mentioned for screen resolution with Adobe Connect:
1. Set the screen resolution settings to 1024×768 pixels for screen-sharing or application or window sharing.
2. Lower screen resolution results minimal usage of network bandwidth.
3. If you are using a very large screen the optimum settings may be 800 x 600.
Upon creating a Meeting, if you deactivate the Mini Control Panel from Meeting >Preferences > Screen Share> Uncheck ‘Enable Mini Control Panel for Screen Share’, those settings will not propagate from a template to new meetings. If for example, you move the Meeting with the deactivated Mini Control Panel to the Shared or My Template folder and create a new Meeting, the Mini Control Panel will be activated in the new Meeting room.
Deactivate the Mini Control panel in the Connect Meeting room in every session.
This is a reported bug and is pending review.
Meeting invitation emails are not received by users of Gmail.
Adobe Connect version – 9.3 and above
Email domain- Gmail
There are a number of reasons why Connect email messages may not arrive in your inbox. Some of them are mentioned below:
– Emails from domain ‘email@example.com’ are marked as SPAM
– Filters are created in the GMAIL account settings forcing the Meeting invitation emails sent to Trash and deleted automatically.
– Forwarding is enabled in GMAIL account Settings > Forwarding and POP/IMAP.
Check to make sure that GMAIL is not blocking Connect email:
1. Ensure email from domain ‘firstname.lastname@example.org’ are not marked as SPAM:
-Sign in to Gmail.
-Click the down arrow in your search box. A window appears to specify your search criteria.
-Fill in the search field with email address ‘email@example.com‘.
– At the top of the search window, click on the drop-down menu under “Search”> select Mail & Spam & Trash.
– Click Search Mail button.
-Look for the message in the search results displayed.
2. Disable Forwarding or if it is enabled, then ‘Keep Gmail’s copy in the inbox’ is selected:
-Sign in to Gmail.
-Click the drop-down arrow of the wheel icon >Click settings > Click ‘Forwarding and POP/IMAP‘> Click the radio button ‘Disable forwarding‘.
-Note: If ‘Forward a copy of incoming mail to‘ is selected, then select ‘Keep Gmail’s copy in the inbox’
3. Ensure that if POP is enabled, then ‘Keep Gmail’s copy in the inbox’ is selected:
-Sign in to Gmail.
-Click the drop-down arrow of wheel icon >Click settings > Click ‘Forwarding and POP/IMAP‘> Click radio button ‘Disable forwarding‘.
-Under ‘When messages are accessed with POP‘ select ‘Keep Gmail’s copy in the inbox’
4. Ensure there are no filters created in the GMAIL account settings forcing the Meeting invitation emails sent to Trash:
-Sign in to Gmail.
-Click the drop down arrow of the wheel icon >Click settings > >Click ‘settings‘ > Click ‘Filters’.
-Select any Filter created with the email address ‘firstname.lastname@example.org‘> Click Delete.
Adobe Connect Meeting hangs on connecting in Safari Web Browser.
Operating system- Mac OS X 10.7.4, 10.8, 10.9 & Windows 7, 8, 8.1
Adobe Connect version – 9.3 and above
Web Browser- Safari
When safe mode is enabled in the Safari Web Browser it prevents the Adobe Connect Add-in from launching. This is a Sandbox restriction. The respective Adobe Connect domain should be enabled in order to launch the addin in Unsafe Mode.
In order to disable the sandbox restriction, refer to the steps mentioned below:
1. With the website open (e.g., akash.adobeconnect.com), Choose Preferences from the Safari menu.
- Select Manage Website Settings in the Security tab of the Preferences panel.
- Select your website (e.g., akash.adobeconnect.com) from the list of “currently open websites.”
4. Select Run in Unsafe Mode from the pop-up menu.
5. In the subsequent alert, click Trust.
6. Click Done, and close the Preferences panel.
We recommend stopping Safari and launching it again after making the Security Preferences change.