Posts in Category "Seminars"

Moving Meeting Rooms to User Seminars Folder

In Adobe Connect 9.5, Meeting Hosts now have the ability to move normal Adobe Connect Meetings into their own User Seminars folder if they are part of a Named Webinar Manager group.

Previously, with the 9.4 release, we added new Seminar licensing called ‘Named Webiner Managers’. This essentially gives users in that new group, the ability to create and manage their own Seminar rooms (under their User Seminars folder).   In Adobe Connect 9.5, if you are a Named Webinar Manager and you are in the Meeting Hosts group and want to move one or more of your Meetings from your My Meetings folder (User Meetings > {username}) or the Shared Meetings folder to your individual User Seminars folder, you can now do this in the UI.


You will notice the new link location for User Seminars in the Move functionality.

Seminar Extensions after Connect 9.3

Beginning with Connect 9.1.1, Connect Seminar extensions in session beyond the initially scheduled time were 30 minutes and then another 30 minutes and then an additional 10 minutes provided there was not a conflict with another scheduled Seminar. Beginning with Connect 9.3, this has changed; the new in-session Seminar extension options are now unlimited as long as there is not a conflicting scheduled Seminar under the same Seminar license. If there is another scheduled Seminar that is in conflict, then you will only get a 10 minute warning before your Seminar ends, but if there is not a conflicting Seminar then this interactive pop up will allow the Seminar host to extend the Seminar:


Connect on-premise: Seminar licenses show as expired following an upgrade to version 9.3.1

Some customers may run into this issue following an upgrade from Connect to 9.3.1 if you use seminar licenses.

After the successful upgrade all seminar licenses show as expired. Re-applying the license file in the console does not help and you see the following message in the debug.log:

[03-03 13:41:48,526] http-80-24 (ERROR) Exception caught in DBRows.populate(), e=java.sql.SQLException: [Macromedia][SQLServer JDBC Driver][SQLServer]Ambiguous column name ‘DATE_END’.
[03-03 13:41:48,527] http-80-24 (INFO) 1ms spid:64 com.macromedia.airspeed.db.SQLServerUtilityQueries.setIsolationLevel(Disable Isolation)
[03-03 13:41:48,527] http-80-24 (ERROR) Exception thrown
java.sql.SQLException: [Macromedia][SQLServer JDBC Driver][SQLServer]Ambiguous column name ‘DATE_END’.
at macromedia.jdbc.sqlserverbase.ddcg.b(Unknown Source)
at macromedia.jdbc.sqlserverbase.ddcg.a(Unknown Source)
at macromedia.jdbc.sqlserverbase.ddcf.b(Unknown Source)


To resolve this, run the following query on your database to change the SQL compatibility level:

sp_dbcmptlevel ‘breeze’, 90

If your Connect database is named something other than “breeze”, then put the correct name of the database in the query.

Now re-install your license file one more time.


This is also the solution to a related issue:

Please contact Support if you still encounter issues.

Stop Sharing Button On IE Is Not Available Any More.

Description : We use to get this button on IE when we share the screen.

StopSharinghowever now this button is no longer available.

Reason being it interfaces with the DWM (Glass effect of windows 7+).

DWM : Stands for Desktop Window Manager Click here

We used to support Windows XP which had no Glass effect and thus it was not a problem. On windows 7 we used to switch the DWM off before starting the screen share. Window 8 onwards the DWM cannot be programmatically switched off and thus this button was causing problems. Many applications change the Glass area and IE is one of them. Others include Chrome, FireFox, Office etc. In case the applications change the Glass area then it’s a matter of timing to Display the button or the custom title bar the application draws.

This was actually a bug 2943337 due to which the button


Intermittently disappears. The bug is only reproducible with the applications which have custom title bars. Ex. Real Player/Office Apps/Live messenger and media players. With the Office 2007 applications the title bar is custom drawn and thus it intermittently draws over the button and it disappears. This only happens with skinned title bars, Skinned apps try to redraw their title bars so button disappears until we redraw again.

The “Red Button” never worked for 64 bit processes. This will also not work for any apps which have skinned title bar as i said earlier. Moreover this feature will not work if the process in question is sandboxed (Acrobat for example).

Yes downgrading IE will help probably but it’s not something we can recommend in good faith as it will expose the users to all kinds of security bugs. (Not recommended)

o    Windows 8 and onwards the button is not even an option as DWM can’t be switched off by programs programmatically and the button itself has issues when DWM is on

o    As of today this button has been disabled permanently.

Hope this helps those users who are expecting the red buttons on their IE when sharing the Application or Windows and not desktop using Adobe Connect Meeting Room,


Empowering Your Seminar Hosts to Create Seminar Rooms

The question comes up on occasion, “Why can’t my Seminar Hosts create seminar rooms?”

The answer is that they have been affected by an intermittent bug, which we realize may cause some confusion, if not chagrin. There is a workaround available, which we’ve outlined below.


As an Administrator, create a typical account with Meeting and Seminar Host permissions (as a test):


Log in with that account and this is what you may see in the Shared Seminars directory. There is no ability to create a Seminar and the Seminar license is not viewable:


If you switch back to the administrative account log-in, you will see the Seminar license sub-directories:



Resetting the permissions on the Seminar license sub-folder using the to “Reset to Parent” button in the Connect Central GUI has no effect on the permissions. You must manually add the folder permissions to the Seminar license sub-folder instead of using the “Reset to Parent” option:


Once the Seminar license sub-folder permissions are manually edited, the Seminar Host is able to view and manage the Seminars including the ability to create new Seminar rooms under the Seminar license sub-folder:


The workaround is very easy so this is a low priority bug and we will address it in a future release. At the time of the writing this tech-note, the shipping Connect release is 9.3.1.d.

Troubleshooting Microphone and Camera Issues in Connect Meetings

When both the web camera and the microphone do not work in an Adobe Connect Meeting, it is often caused by a restriction setting in the mms.cfg file.

The mms.cfg file it is found in the following directories:

  • Windows 32: C:/Windows/system32/Macromed/Flash (32-bit Windows)
  • Windows 64: C:/Windows/SysWOW64/Macromed/Flash (64-bit Windows)
  • MAC: MainDisk:Library:Application Support:Macromedia

Renaming or deleting the mms.cfg to mms.old is one way to solve the issue, but often it is more prudent (less intrusive) to edit the file. Open the mms.cfg in any text editor and look for the line:


Delete the setting AVHardwareDisable from mms.cfg and save the file. This setting deliberately prevents the Meeting SWF from gaining access to cameras and microphones on the Meeting client.

Deleting Corrupted Ghost Meetings on Adobe Connect On-premise Servers

Deleting Corrupted Ghost Meetings on Adobe Connect On-premise Servers

Perhaps due to network outages or hardware failures, etc., there are rare occasions when the Adobe Connect database may become disconnected from the Adobe Connect server while active Meeting sessions are ongoing. It is prudent to avoid database outages while Connect is in use and to publish maintenance schedules so that Meetings are not in session when the database is taken offline for administrative reasons. In most cases when the database is disconnected, once it is reconnected, Connect will be fine and all Meetings will be functional upon full recovery of all systems. In the rare instance, that a Meeting is corrupted through a database outage and cannot be deleted through the Connect Central GUI, you may need to manually delete the Meeting room from the content library directory structure and possibly also from the database itself. If you see displayed at the corrupted Meeting URL, a gray window without any menu or pods, or if you see the following error when you hit a corrupt Meeting URL, you may need to manually delete the Meeting:

Request Not Processes” – “For further assistance, please refer to the Adobe Connect support center or contact Adobe Connect support

If the Meeting cannot be deleted through the Connect Central GUI, delete the content folder for the corrupted Meeting. You can identify it by its sco ID in the Connect\content directory:


Restart the Connect and FMS services. If that fails to remove remnants of the corrupt Meeting from the database, try recreating the folder mentioned, (even with empty content), then attempt to delete the room again. If that fails, you may need to delete the Meeting references from the database manually:

sco: update pps_scos set disabled = getUTCdate() where SCO_ID=XXXXX

Note: XXXXX represents the actual sco ID of the meeting.

Last Minute Managing of Large Adobe Connect Hosted Seminars

Currently, as of Connect 9.3.1, Adobe Connect hosted Seminars may launch on regular Connect Meeting server instead of their designated Webinar servers. If Seminar preparation keeps the Seminar room open for an extended period just prior to to the actual Seminar itself, the Seminar may remain on a Meeting server that is not rated for a large capacity Seminar. Simple precautions will avoid this from happening.

In order to avoid this, on the day of the scheduled Webinar, be sure to open the Seminar room only 30 minutes prior to the start of the Seminar session. By opening the Seminar earlier and keeping it open for final editing right up to the start of the Seminar session, you can lock the seminar onto a regular Connect Meeting server rather than on a Webinar server designed for large capacity sessions. While you can certainly spend as much time as needed to prepare your seminar room in advance of the actual session, you should close the Seminar room for at least seven minutes prior to the actual scheduled Seminar session. Seven minutes is the time it takes the Seminar room to process garbage collection from editing and preparation activities before opening up for the real event.

Adobe is looking at ways to automate the transition from a regular Meeting server to a Webinar server with an eye toward  future release. In the interim, just be sure to time your final Seminar preparation to allow for transition to a Webinar server where large Seminar concurrency is supported with robustness.

Adobe Connect Add-in Compatibility with the Google Chrome Browser

Updated January 27, 2015:

Note: This article only applies to Adobe Connect on-premise server deployments. Adobe Connect hosted clients are unaffected.

The Google Chrome browser is currently shipping with two versions of the Flash plugin.  The default PPAPI and also the NPAPI Flash plug-in. The following versions of Adobe Connect installations are incompatible out of the box with the default PPAPI plug-in:

  • 9.1.2
  • 9.1.1
  • 9.0.1 – 9.0.4
  • 8.2.2

PPAPI plug-in incompatibility results in the Adobe Connect Add-in not being detected and launched in Chrome when invoked in a Connect Meeting. Even if the Add-in is installed, the meeting opens in the browser and not in the Connect Add-in. Upon attempting to share ones screen (a Connect feature supported in the Add-in but not in the browser), the following message appears:


Google Chrome, with the release of Version 40, will no longer use their whitelist to allow NPAPI  plugins to run without requiring approval: Chrome users will not be able to use the Adobe Connect Add-in for the above listed versions of Connect. To address this problem, Adobe is patching the following Connect versions for use with Chrome:

  • 9.1.2
  • 9.1.1
  • 9.0.4
  • 8.2.2

These patches will fix the incompatibility problems with the PPAPI plug in. Adobe Connect servers that are not running one of these versions (or a later version) will need to be upgraded to the nearest later version to the one currently installed and then apply the appropriate Connect PPAPI patch.

There should not be any change in the behavior for Flash Player NPAPI in January because Flash Player is not listed among the applications  that are going to be removed in January:

Workarounds until the patches are available:

  • You can attend Adobe Connect Meetings without the Adobe Connect Add-in, however the Add-in is required for enhanced functionality like screen sharing and making offline recordings.
  • Turn off auto-upate in Chrome so that you do not upgrade to a version of Chrome that is problematic.
  • Alternatively you can use any browser other than Chrome with Adobe Connect.
  • Manually enable NPAPI by clicking on the “Plug-in blocked” message in the URL bar and choosing “Always allow plug-ins on [website]”



Note: In April 2015, this will no longer be an option as NPAPI support will be disabled by default in Chrome and Google will un-publish extensions requiring NPAPI plugins from the Chrome Web Store. Google will however provide an override for advanced users in the form of an ‘enable-npapi’ flag and enterprise policy to temporarily re-enable NPAPI.

PDF document does not upload into Adobe Connect

Problem: Adobe Connect could not process this document for viewing. (Either the full document does not upload or some pages of within a document do not upload)



Adobe Connect Hosted/Licensed


Use the “Sanitize Document” Feature to get rid of all the following types mentioned in the image attached below. Depending on the version of Acrobat you are running, you may need to install a trial version of Adobe Acrobat Pro to use this feature.