Archive for August, 2012

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

Posted on August 19, 2012 by | Comments (0)

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.

Solution:

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

Posted on August 19, 2012 by | Comments (0)

Problem :

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

Solution:

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

Posted on August 19, 2012 by | Comments (0)

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 : http://helpx.adobe.com/adobe-connect/kb/configure-software-based-ssl-connect.html

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

Meeting does not launch in IE 9

Posted on August 17, 2012 by | Comments (0)

Issue:

While try to launch a meeting in IE 9, Add-in does not launch and gives an error: “Could not find language file….”

Solution:

Disable “Do not save encrypted pages to disk” option by following the below steps:

1: On the Tools menu, click Internet Options.
2: On the Advanced tab, scroll to Security, and uncheck “Do not save encrypted pages to disk” check box.

Try to launch the meeting again and it should launch fine.

Screenshare does not work in Chrome

Posted on August 17, 2012 by | Comments (0)

Problem:

Google has now disabled the Flash NPAPI plugin by default and have made the PPAPI Flash as the standard. More details on mitigation are available in http://helpx.adobe.com/adobe-connect/kb/google-chrome-browser-incompatibility.html

Solution:

Adobe Connect engineering team is creating a new Chrome extension to fix this issue. This extension is supposed to be rolled out in September.

Installing add-in for all user profiles

Posted on August 14, 2012 by | Comments (0)

Problem:

The applications function is to automatically install the Adobe Connect Pro Meeting Addin into the correct system user profile upon system login. Thereby removing any end user effort for additional addin installations when attending Adobe Connect Meetings.

Reason:

The application is designed to be pushed and installed by a system administrator on all user workstations. Once installed the application will automatically install the addin into the logged in users profile once the user logs into Windows.

Solution:

You can download the Connect Add-in Checker from http://www.adobe.com/go/adobeconnect_addinchecker.

Steps to be implemented are shown below:

1. Login using Adminstrator user.
2. Run Setup.exe – (for the initial install to be more silent try Setup.exe –I silent).
3. The application will be installed into “Program Files\Adobe\Acrobat Connect Pro Add In Checker”.
4. Login using a non admin user.
5. An application should start up (may not be visible). Wait several moments and check the expected flash folder for connectaddin.exe.If application does not appear to have started, check blocked programs to see if it was intercepted

Windows XP:
C:\Documents and Settings%user%\Application Data\Macromedia\Flash Player[www.macromedia.com|http://www.macromedia.com]\bin\connectaddin

Windows Vista:
C:\Users\$user$[AppData]\Roaming\Macromedia\Flash Player[www.macromedia.com|http://www.macromedia.com]\bin\connectaddin

6. Test logging into meeting room, verify that meeting launches within the Connect Pro Meeting addin.

Silent installation of Connect add-in

Posted on August 14, 2012 by | Comments (0)

Problem:

Silent installation of Connect add-in.

Reason:

If you want the Add-in install wizard to run in background, you can install the Add-in Silently.

Solution:

The command to install add-in silently is: Setup.exe /SP- this disables “This will install… Do you wish to continue?” prompt at the beginning of Setup. Of course, this will have no effect if  the DisableStartupPrompt [Setup] section directive is set to yes.

Very silent would be: /SILENT, /VERYSILENT – this Instructs Setup to be silent or very silent. When Setup is silent,the  wizard and the background window are not displayed but the installation progress window is. When a setup is very silent, this installation  progress window is not displayed. Error messages during installation are displayed and the Startup  prompt if you haven’t disabled it with DisableStartupPrompt or the  ‘/SP-‘ command line option explained above.

Adobe Connect Operation size error

Posted on August 10, 2012 by | Comments (0)

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 :

          DB_MAX_ROWS=20000

          DB_TRANS_MAX_UPDATES=400

4) Restart the Adobe Connect services

 

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

 

Adobe Connect | Override the default SMTP port

Posted on August 10, 2012 by | Comments (1)

 

Problem :

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

Environment :

Adobe Connect Licensed 8.x, 9.x

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 different port for smtp :

    1.  Navigate to the {root-install}\breeze\8.x\appserv\conf  folder on your Adobe Connect server(Note : The path would be under 9.x folder for a 9.x Connect version)

    2.  Open the ConnectProSvc.conf  file in an editor

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

            wrapper.java.additional.22=-Dmail.smtp.port=XXX, where XXX denotes your smtp server’s port.

    4.  If you’re using gmail, following extra wrapper should be required :

   wrapper.java.additional.23=-Dmail.smtp.starttls.enable=true

    5.  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

Posted on August 10, 2012 by | Comments (0)

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 : abc.connect.com:XXXX, 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.

10. The web url to access your Adobe Connect site would now change to http://abc.connect.com:XXXX, after making these changes.

 

Please Note :  Changing the default http port is only supported for on demand contents as of now. Contents might not work if accessed from a meeting room.

We have logged a Feature Enhancement Request regarding this targeted as 3744993. Engineering is currently reviewing the feasibility of including this feature in a future release.