Author Archive: Sushma

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.

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.


Adobe Connect meetings won’t load with Firefox & Flash 11.3 update

Problem :

You may be running into this issue with your Adobe Connect meeting room, if you happen to notice, one of the following symptoms, while trying to launch your meeting room :-

  • My Adobe Connect meeting rooms fail to load in Firefox at all since I’ve updated my flash plugin to the latest FP 11.3/FP13 update
  • Sometimes my Firefox completely crashes when I try to launch an Adobe Connect meeting
  • Even the meeting connectivity test page returns a completely blank page

Reason :

Adobe Connect users who have Firefox and Flash 11.3 & higher, and  Real Player installed on their system, might be a victim of one of the above problem symptoms.

Starting with Flash player 11.3, a protected mode feature has been recently added as a new security enhancement with Firefox browser, which currently seems to cause issues with your Adobe Connect meeting rooms, if you have Real Player version 14 or lower installed as well.


1)  If you have Real Player installed on your machine, please update it to the latest version available, version 15 or higher, in order to resolve this issue.

For details, you may please visit the Download and install RealPlayer page on the RealPlayer knowledge base site.

2)  If upgrading your real player doesn’t help fix this issue, then, downgrade your Adobe flash plugin to a slightly earlier version than FP 11.3

You may follow these steps for downgrading your flash plugin  :


 * Update * :  A new Flash player update (11.4.402.265), has now been released, which contains the fix for this issue. Users may download it and install it from here.

Adobe Connect 8 support for IPv6 network

Problem :

I want to have my Adobe Connect Server work on IPV6 ip address networks as well along with IPV4 ip address networks


Adobe Connect does have configuration support  for an IPv6 network. The setting is not turned on by default for the FMS server. Users can simply turn it on at the backend, by a simple configuration, if they would like to setup their Adobe Connect 8 server with an ipv6 network.

Here are the steps to turn on IPv6 support with your Adobe Connect server :

√ Navigate to the {root-install}\breeze\comserv\win32\conf folder on your Adobe Connect server

√ Open the server.xml file in an editor

√ Look for the following line in the file :

      <NetworkingIPv6 enable=”false” />

√ Modify the value to ‘true’ . By default this value is set to to ‘false’

√  Restart your Adobe Connect services

Your Adobe Connect server should be ready to work with your IPv6 network now.

Note : This setting is also applicable to your Adobe Connect version 9 server.

Adobe Connect 8 unusual Firefox script errors

Problem :

My Adobe Connect site keeps displaying unusual javascript code or errors. Randomly, the images & content does gets partially loaded, but none of the links are usable. I am unable to browse my site or do anything on the server. I have tried all the latest browsers FF 11 & later, Chrome, IE9.

Reason :

If you’ve recently upgraded your Adobe Connect server to version 8 & you’re still continuing to use the legacy method to implement ssl through adaptor.xml, you are very likely to run into this issue, with the latest browser updates.

Solution :

Use Stunnel, the recommended and supported method, to secure your Adobe Connect 8 server. Stunnel comes with a support for the latest Openssl libraries and thus has compatibility, across all latest browser versions.

Adobe Connect has dropped support for the old method, configuring ssl through adaptor.xml. Adobe recommends users to start using Stunnel, which comes bundled with Connect 8 install, a more pertinent way to secure your server; & avoid running into any abnormal issues.

If you would like to know the steps to configure Stunnel, you may simply refer the following knowledge base article :

Note : Contact Adobe Support if you come across any issues while setting this up.

Adobe Connect Operation size error

Problem :

I am unable to upload any content to my Adobe Connect meeting room. Every time I try to upload, I am encountered by an error :  Operation Failed – Error Code: operation-size-error, SubCode: missing.

I am even unable to upload any content to the server itself.

Reason :

Adobe Connect, by default, is set up with a limit, configured for a maximum number of row/transaction updates, allowed by a SQL query.

The reason to have these parameters, is to provide more control, to the system admins, over normal users, running large queries/transactions. System admins can increase these values, at the server side, if they encounter this issue.

Solution  :

If you are running into this error, you can simply go ahead & increase the max update limit, by following the below outlined simple steps :

1) Navigate to the {root-install}\breeze\8.x folder on your Adobe Connect server

2) Open the custom.ini file in an editor

3) Add the following parameters to the file :



4) Restart the Adobe Connect services


Note : This solution only applies to on-premise installs.


Adobe Connect | Override the default SMTP port


Problem :

I cannot configure my SMTP server with Adobe  Connect, because my SMTP server requires a different port, other than the default 25.

Solution :

If you have an SMTP server that is setup to use a different port other than the default port configured with connect, here are a few simple steps you can follow to achieve it.

Connect can be configured to use a differnt port for smtp :

    1.  Navigate to the {root-install}\breeze\8.x\appserv\conf  folder on your Adobe Connect server

    2.  Open the ConnectProSvc.conf  file in an editor

    3.  Add the following additional java wrapper anywhere in the file :  

  , where XXX denotes your smtp server’s port.

    4.  Restart the Adobe Connect services to allow the changes to take effect.


Configure your Adobe Connect 9 server to override the default HTTP port 80

Problem :

I want my Adobe Connect server to listen on a different port other than the default port 80 for http traffic.

Environment :

Adobe Connect 8/9 On Premise Install

Solution  :

You may now follow a few simple steps, to make any other custom port, work as the default http port, with your Adobe Connect server webapp. Here are the steps outlined below :

1.  Navigate to the following folder on your Adobe Connect server :

          {root-install}\breeze\8.x.x\appserv\conf   or   {root-install}\breeze\9.x.x\appserv\conf

2.  Open the server.xml file in an editor

3.  Search for the following lines in the file which specify the http connector tag :

        <Connector URIEncoding=”utf-8″ acceptCount=”250″ connectionTimeout=”20000″ enableLookups=”false” executor=”httpThreadPool” port=”80″ protocol=”HTTP/1.1″ redirectPort=”443″/>

4.  Modify the port value from 80 to XXXX, where XXXX is the custom port you would like to use.

5.  Now, open the {root-install}\breeze\9.x\custom.ini file and verify in case you have the following parameter in the file: http_port.

Ensure the parameter does not have a value set to the default, 80.

6.  Goto the Connect configuration console page (http://localhost:8510/console) and open the Server Settings page.

7.  Modify the Adobe Connect host parameter, to include the port number(XXXX), with the web url, that is set for your Adobe Connect server.

        Eg :, where XXXX denotes the custom port you want to use.

8.  Modify the Http Port parameter to the desired custom port value : XXXX

9.  Restart the Adobe Connect services to allow the changes to take effect.


Please Note :  The web url to access your Adobe Connect site would now change to, after making these changes.