Archive for August, 2012

Connect multiple cameras in Connect meeting room


We can easily connect multiple cameras in a connect meeting room, as long as you have multiple browsers and enough ports on the PC/Mac.


To connect multiple cameras:

  • Launch Adobe Connect Add-in as a host and connect the room to your first camera or the default camera you usually use.
  • Launch another Web browser like Google Chrome or Firefox. In the browser address field enter your room link but append ?launcher=false after the Meeting room URL.
  • Login to the room and right mouse click anywhere on share pod and select the camera you want to be connected in this browser.
  • Launch the Camera Pod and you should see the video coming from the other camera.

You can do this again but using Firefox the third time.  As long as you have multiple browsers and enough ports on the PC/Mac and multiple cameras, you should be ready to go!

Java Exception Error while importing database in to the new server


Java Exception Error while importing Database in to the new server

Kind of Environment: Licensed


If you see this in debug logs:

05-26 01:40:50] console-8510-1 (ERROR) Exception thrown java.lang.NullPointerException at com.macromedia.airspeed.FeatureManager.updateFeatureSet( at com.macromedia.airspeed.FeatureManager.isDisabled(
Caused by: java.lang.NullPointerException at com.macromedia.airspeed.FeatureManager.updateFeatureSet( at com.macromedia.airspeed.FeatureManager.isDisabled(


PPS_ACCOUNTS_FEATURE table was not updated properly.

Please call Support in order to get further assistance.


Telephony conference fails to start when we have an edge server in front of Connect Origin server.


Telephony conference fails to start when we have an edge server in front of Connect Origin server.


Licensed customers who use telephony that makes call-back to Connect (Intercall, for example) must open port 9080 on their firewall so that the call-back can be made. If the Intercall bridge cannot make the call-back to this URL on port 9080 the conference will not launch. It uses the call-back URL for anything you do in the conference call – mute a user, hang-up etc. The call-back URL must provide Intercall with a direct route to the origin running the meeting room.

When we have an edge server between the telephony provider and Origin server, we need to ensure that edge listens on port 9080 (in addition to 80,443,1935) and forwards 9080 traffic to Origin server. Additionally, if the origin server is clustered, we need to ensure that the response of call-back requests is sent back to the origin server who initiated the request. We cannot let edge server send these request to load balancer and have latter load balance this traffic between the origin nodes. If we do so, half of the call-back (round robin) requests will fail.


To ensure call back is successful:

1) Make the Edge listen on ports 9080 and 9081 (in addition to current 80, 443, 1935).

2) Add redirects for each of these ports in adaptor.xml file such that

Port 9080 is redirected to origin1:9080

Port 9081 is redirected to origin2:9080

3) Change call-back URLs on both origin servers such that

Call-back URL on origin1 is

Call-back URL on origin2 is

4) Open TCP ports 9080 and 9081 to the Edge servers on the firewall.


The Connect configuration:

1) In \edgeserver\win32\conf\_defaultRoot_\adaptor.xml, add entries to map edge:ports to origins:ports as follows

origin1 IP Address:9080

origin2 IP Address:9080

2) In \edgeserver\conf\config.ini add entries to for ports on which the  Edge listens as follows:


3) On origin 1:

4) On origin 2:

Now if a meeting is launched on Origin server 2 and an Intercall conference is started, that Origin server will make a connection to the Intercall conference bridge. The call-back URL that Intercall receives will contain the port number 9081. Intercall will hit the Edge server on port:9081 and the Edge server will redirect the request to Origin server 2 because of the redirect we placed in its Adaptor.xml.

Encrypting traffic between Edge and Origin Server on 8506.


Encrypting traffic between Edge and Origin Server on 8506.


By default, the traffic between external edge and origin server is in clear. To encrypt that, follow the steps below:

Step 1:

On the remote Edge servers, edit: /breeze/edgeserver/win32/conf/_defaultRoot_/_defaultVhost_/vHost.xml:

<RouteTable protocol=""> with
<RouteTable protocol="rtmps">
<RouteEntry></RouteEntry> with
<RouteEntry protocol="rtmps">*:*;*:*</RouteEntry>

Step 2:

Secure the 8506 traffic at the Origin server on 8506 exactly as though it were client traffic inbound to port 1935 except using port 8506 instead.

On the origin servers (or on the origin’s SSL accelerator), encrypt the inbound Edge to origin traffic on port 8506. The example below shows an stunnel.conf file on origin server, add for the IP receiving rtmp traffic on the meeting server VIP:

#[rtmps-vip for Origin]

accept =

connect =InternalIP02:8506



One caveat with this technique of doing SSL, is that when you view the RTMP sequence from within a test meeting (Help>Shift>About Adobe Connect) the second leg of the RTMP sequence will read RTMP even though it is actually RTMPS. We are testing for a means to adjust that output, but it is very trivial as the first leg does read RTMPS and adjudicates both legs.

Adobe Connect Upgrade Error | Port 80 in use | Win 2003 / 2008

Problem :

My Adobe Connect service doesn’t start and I cannot get the login page to come up;

Reason :

The Adobe Connect service will not start or will not open the login page, if the server’s port 80 is in use, by any other application/process.

Solution :

Port 80 can be in use by other web servers[like IIS,Apache Tomcat], if installed on the same machine, as the Connect server machine. It is highly recommended, that you should ensure that no other application (or IIS), is listening on port 80.

Additionally, if you’re running on a Win 2003/2008 server, and if you have your SQL server installed on the same box as Connect, it is very likely that you might run into this issue.

SQL Server Reporting service on Windows 2003/2008, are bound to listen on port 80 by default. This would prohibit Adobe Connect, to start or launch the login page, since the port would be occupied, by the SQL’s reporting service. To fix this problem, ensure that this service is not running or listening on port 80.

In order to ensure that, port 80 is not in use by this service, we can run the following command to find out :

  • Open a command prompt window on the Connect server
  • Run the command netstat -a -b
  • This command determines, the list of ports, which are in use by the system, along with their process names, & via this process name, we can identify, which service/process, is using port 80.
  • If you find port 80 in use by a system.exe process, which has a Process Id(Pid) 4, ensure your SQL Server’s Reporting service is not running.
  • Once this service is stopped or alternately configured to listen on any other port, you should be able to start the Adobe Connect service successfully and get to the login page as well.


Adobe Connect 8 | Login page not coming up after upgrade | SSL

Problem :

I upgraded my Adobe Connect 7 server to version 8 and I can’t get the login page to come up. I tried connecting to the admin console through localhost:8510/console and it doesn’t get through that either.

Reason :

Adobe Connect 8 requires an additional modification, in the configuration files, for SSL to be enabled. Starting Connect 8, we need to enable, the 8443 connector separately for SSL to work; the connector is turned off by default.

Solution :

If you have SSL configured and you are performing an upgrade to version 8, you are required to follow these steps, to enable SSL completely :

√ Navigate to {root}\Breeze\appserv\conf   folder on your Adobe Connect server

√  Save a backup copy of server.xml file

√  Now open the file in an editor

√  Search for the below tags and ensure that these lines are uncommented :

<Executor name=”httpsThreadPool”

<Connector port=”8443″ protocol=”HTTP/1.1″

√  Please note that these are two separate tags which can be located separately within the file.

√  Save the file and restart the Adobe Connect services.


Note  :  These settings are also applicable for your Adobe Connect 9 server with SSL configured.


Adobe Connect 9 | Meetings fail to work on MAC OS X – 10.5(Leopard)

Problem :

I’ve recently installed Adobe Connect version 9 in my test environment and any meeting rooms does not seem to work on my MAC Leopard(10.5). Meetings work just fine on higher versions or on Windows platforms.

Reason :

With Adobe Connect 9, Adobe has released a new version of meeting addin, which has stopped support for Mac OS X 10.5 (Leopard). The reason behind this, is due to the fact, that Apple has deprecated the screen sharing APIs for OS 10.5.

Solution :

If you have already installed Adobe’s new Connect 9 and are still running your MAC pc on an older version(10.5)/Leopard, go ahead and upgrade it to a higher version and you will be able to open your Connect 9 meeting rooms fine with the addin.


Note : All Leopard users will still be able to attend meetings from within the browser and will be able to use all basic functionalities, except from the functionalities provided by addin, like screen sharing.


Adobe Connect Recording Grey pod | Displays Nothing is being shared

Problem :

I have an Adobe Connect recording that does not display the content that was shared in the meeting. It comes up with a grey pod instead which says : “Nothing is being shared”

My content was visible to everyone during the live session, however, its now blank in the recording.


You might be running into this issue when the content that was being brought in the share pod, has some permission conflicts, with the permissions of the user, who brought it to the room, or with the meeting.

Steps to avoid the problem :

The permissions issue has been seen to occur in such cases, where, if the host of the meeting was not a part of actual Meeting Hosts group, but, rather was a promoted guest. Such user, although gets permissions to facilitate the meeting with complete host rights, however, the user is not able to get proper permissions on the content which is being brought in the meeting and which is why the content fails to display in the share pod.

This issue can also surface if the host of the affected meeting room was not a host of the meeting template, where this content was originally uploaded.

Secure Connection Issue with Mac OS X 10.8

Please refer to the following technote for more information:

Adobe Connect install fails with java.sql.SQLException

Problem :

My Adobe Connect installation completed successfully, however, it keeps getting failed each time at the database configuration page.

Following is the error message I encounter each time :

java.sql.SQLException: [SQLServer JDBC Driver][SQLServer]  SET LANGUAGE failed because ‘ENGLISH’ is not an official language name or a language alias on this SQL Server.

Reason :

If you are running into this error, you might want to check the collation settings on your SQL server. If this setting on the SQL server is not correctly setup to the right English language option, you are very likely to run into this issue.

There are several English-language settings available, and the collation setting on the SQL server must match the collation setting in the Adobe Connect database installation script.

Solution :

In order to resolve this issue, you may follow the following steps :

1. On your SQL Server, modify the collation setting to use SQL_Latin_GENERAL_CP1_C1_AS, as the default language. You may find more information on Collation fundamentals on the Microsoft’s website :

2. Once done, open the Connect database configuration page again using the configuration console (http://localhost:8510/console) and complete the database configuration wizard.