Posts in Category "Administration"

Adobe Connect ID’s are changing from INT to BIGINT

UPDATE: THIS ARTICLE IS FOR XML API DEVELOPERS ONLY.  If you are not using the XML API with Adobe Connect to write your own custom built applications that integrate with Adobe Connect, please do not worry about the message below as it will not apply to you.

Due to the growing popularity of Adobe Connect, more and more customers rely on Adobe Connect for their collaboration needs and this naturally requires that we make adjustments to accommodate the growth.  We want to make you aware of an upcoming adjustment to the ID values in Adobe Connect databases to support longer values which will accommodate growing customer use of Adobe Connect.

What is being changed?

Starting with release 9.5.2, Adobe Connect will migrate the ID values in Connect databases from INT to BIGINT/Long.

What is the impact?

This change will impact any applications using Adobe Connect Web Service APIs.

How will Adobe Connect Web Service APIs be affected?

The change is for those APIs which consume/return id values i.e. which have a parameter in request/response which is an Id. (examples: sco-id, account-id, folder-id, etc).  The id fields in such APIs would return/accept larger values. The support and behavior of existing APIs remains same.

What does this mean for you?

In case you are interpreting ids as integers the new values might overflow. We strongly recommend using strings to represent id values. In case you still need to represent/store ids as a numeral please use integral data type with higher capacity. (Preferably 64 bit)

What is the timing?

We expect to release Connect 9.5.2 in the first quarter of 2016, so the change should be made as soon as possible in order to be ready prior to the release.

Estimating Bandwidth Consumption in Connect Meetings:

Estimating bandwidth consumption in Connect 9.x Meetings:

The following tables may be used for estimating the amount of bandwidth that will be required for a Connect Meeting based on the features used.

Screen Share:

Screen Share Frame Rate Quality Bandwidth
Low 2 65 500
Medium 4 80 800
Standard 6 90 1200
High 8 100 2000


With reference to VoIP, it is independent of any settings. There is no metric comparable to frame rate or quality or bandwidth with VoIP;  a single metric of micRate is used. Currently we use following values:

Number of VoIP users Without UV With UV
<4 22 kHz 22 kHz
>=4 11 kHz 8 kHz

Note: In a simple test during which a song was played via VoIP for a single user, up bandwidth consumed was 44 kbps when the number of VoIP users was < 4.

Webcam video:

Webcam Video Frame Rate Resolution Quality Bandwidth
Normal Widescreen
Low 4 160×120 214×120 70 200
Medium 4 320×240 427×240 70 300
Standard 8 320×240 427×240 70 300
High 20 640×480 854×480 90 600

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.

Named Vs Concurrent Pricing Model

Problem: What is the difference between a Named and a Concurrent pricing model?

Environment: Hosted/Licensed

In order to understand the difference we present you with two different accounts having Named and Concurrent pricing models.

Named Host Pricing Model

As an example, I would take up the example of my local account. Below is the license information of my account.

We read the following information for a Named Host license.  In Named Host Pricing Model, you need to check two values.

  • Meeting Hosts
  • Concurrent Users Per Meeting

Named Host Pricing Model
Meeting Hosts:   5 / 5      (Consider this value as Mx)

Meeting Peak Concurrent Users:   Unlimited   (Soft Limit: Unlimited)
Concurrent Users Per Meeting:   100   (Soft Limit: 100)  (Consider this value as Mn)

Burst Pack Minutes (Total Used/Total Purchased):   0 / 0
(Balance:0 – Disabled)

Max meetings that can run simultaneously <= Mx

Total number of users who can enter in a meeting <= Mn

In this case Mx=5 and Mn=100

So you can run 5 meetings simultaneously with a cap of 100 users in each of these meetings.

So not more than 100 user can be present in any of these meeting rooms.

See this hierarchy:


Concurrent Attendee Pricing Model

For Concurrent pricing models we only consider ‘Concurrent Users Per Meeting’, since there is no restriction on how many concurrent meetings you can run.

As an example of the license info on my local account below :

Concurrent Attendee Pricing Model
Meeting Hosts:   16 / Unlimited  (Consider this value as Mx)

Meeting Peak Concurrent Users:   100   (Soft Limit: 100)  (Consider this value as Mn) 

Concurrent Users Per Meeting:   Unlimited   (Soft Limit: Unlimited)
Burst Pack Minutes (Total Used/Total Purchased):   0 / 0
(Balance:0 – Disabled)

Mx=Unlimited Hosts(There is no restrictions on number of hosts, hence not limiting the number of meetings you can run)

Mn=No of users who can join a meeting when counted together in all the active meetings.

Here Mn=100 and say we are running 5 meetings so In total 100 users can join.

User in Meeting1+Meeting2+Meeting3….+Meeting5<=100.

See this hierarchy.


Please Note : The above license limit values have been used here for demonstration purpose. Individual user accounts would have their own limits as per the license they have purchased.

Please refer our official document for complete information about these licensing models :

Please contact support if you have further queries on the same.

Troubleshooting Verbose Meeting Addin Logging

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):

  • Windows (32 bit) :

In: C:\Windows\System32\Macromed\Flash\mms.cfg
or C:\Windows\System32\mms.cfg

  • Windows 7 (64 bit):

In: c:\Windows\SysWOW64\Macromed\Flash\mms.cfg
or c:\Windows\SysWOW64\mms.cfg

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.

Terms of Service Notification on Adobe Connect Hosted Accounts

Changes made to the Adobe Connect Terms and Conditions (ToS) in Connect 9.4 are related to the new licenses introduced in Adobe Connect 9.4. Note that the first administrative login will be presented with the ToS dialog. If the first administrative login is an automated API call, this call will fail until the ToS dialog is manually cleared.

22.6: “Named Virtual Classroom Manager” means an individual that has the ability to host a Meeting in a Virtual Classroom, track user completion and course results for Meeting Attendees in Virtual Classrooms, and manage advanced registration, branded event pages, and email options. A Named Virtual Classroom Manager is a type of On-demand User.

22.7: “Named Webinar Manager” means an individual that has the ability to host a Meeting with Meeting Attendees up to the number of seats purchased, as well as manage advanced registration, branded event pages, email options, and reporting.  A Named Webinar Manager is a type of On-demand User.

The new licensing options were also added to sections 2.1, 3 and 19, and 20.  Similarly, in line with the new licensing, we also exchanged the term ‘seminar’ for ‘webinar’ in several locations.

For more information on Adobe Connect 9.4, see

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.

On-premise Server: Add user-agent info to access logs

If you run your own Connect server you may want to add user-agent information to the tomcat access logs.

Here’s how to add the information:

1.  Take a backup copy of the server.xml located in \Connect\9.x\appserv\conf\.

2.  Open the file in an XML friendly editor and locate the line:


<Valve className=”org.apache.catalina.valves.AccessLogValve” directory=”../../logs/tomcat”
prefix=”tomcat_access.” suffix=”.log” pattern=’%h %l %u %t %m “%U” %{BREEZESESSION}c %s %b %T’ resolveHosts=”false”/>


3.  Edit the line to include %{User-Agent}i . It should look like this:


<Valve className=”org.apache.catalina.valves.AccessLogValve” directory=”../../logs/tomcat”
prefix=”tomcat_access.” suffix=”.log” pattern=’%h %l %u %t %m “%U” %{BREEZESESSION}c %s %b %T %{User-Agent}i‘ resolveHosts=”false”/>


4. Restart the Connect service and load any page of Connect.

The log output in \Connect\logs\tomcat\tomcat_access.-date-.log should now include user-agent information: – – [23/Feb/2015:11:39:45 +0000] GET “/common/help/en/support/meeting_test.htm” breezbreezhvc7xdcgu5h3cqwm 200 16703 0.017 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0


Enjoy logging!