Author Archive: Sushma

Invalid value “null” appears in string “Password length must be between null and null characters” in Event Registration page

Problem Description :

Invalid value “null” appears in string “Password length must be between null and null characters” in Event Registration page.

Conditions in which this issue is expected to occur :

If you are running a Connect 9 server with a version prior to 9.2.x, you might encounter this problem with your Events module in the following conditions :

  • Create an Event with Register without password as “No”
  • Participants try to register for the event
  • Participants encounter error even though their password satisfies the requirement criteria

event3

 

Environments affected :

On Premise Licensed versions on 9.x prior to 9.2.x

Solution:

We have discovered this to be a known bug.Bug#2964597. This issue has already been fixed in version 9.2.x, so upgrading your server to the recent version should help resolved this issue for you.

Workaround :

Till the time you are unable to upgrade your server due to any restrictions, you may choose to setup your events with Register without password as “yes” while creating your events.

Please do review the following article if you are planning to setup your events without a password required :

http://blogs.adobe.com/connectsupport/participants-get-an-enter-password-prompt-while-registering-for-an-event-even-though-host-has-enabled-the-option-to-register-without-password/

 

Participants get an Enter Password prompt while registering for an Event even though Host has enabled the option to register without password

If you have created an Event and  enabled the option for participants to be able to Register without the need to enter a password, you might run into this situation. Please note the clear conditions  below under which this specific issue is expected to happen :

Conditions :

  • Event Host created an Event and enabled the Register without Password option

Registerwtpwd

  •  Participants try to register for the Event and they only get a Login & Name field options on the page
  • There is no option present for a password

  RegScreen1

  • When participants try to login to the actual event, instead of being able to enter the event with just their login, they still get a prompt to enter a password.

Login Screen

Reason behind this behavior :

  • In these cases we have found that whenever users tried to register for the event, they were getting created in the system as full fledged users
  • This happens due tot he fact that the Event User Policy in your account should be set to All users created should be Full System Users

Event user policy-1

  • This is configurable from under  Administration tab > Account > Edit Information > Event User Policy
  • Due to this setting, all the participants who get registered for the event, get created as Registered System Users and which is why they are presented with a password prompt
  •  So if you want to have your participants for an Event be able to login to it without a password, you should make sure you have the policy turned off.
  • From the below options, you can either choose option 1 -> All users created from Event are guest users or you can choose the option 3 -> where Event Managers would get the right to choose whether they want the users to enter as guest users or registered users. This option 3 would be configurable on a per Event basis in this case according tot he requirement of the event.

Event user policy-2

 

 

 

Unable to share images and flash files in meeting room after changing the default port from 80 to another port

We have recently discovered a new problem where you might run into an error when trying to share any content in a meeting room, eg images, flash files etc., if you have changed the default HTTP port of the Connect server from 80 to any other port.

Environment : On Premise Installation

Method: Follow this blog procedure to change the default http port of the Connect server : http://blogs.adobe.com/connectsupport/configure-your-adobe-connect-8-server-to-override-the-default-http-port-80/

Result: On-demand contents work fine but any contents shared in the meeting room are blank

Workaround: Use only default ports to avoid this issue.

Additional Information:  The meetings should launch fine but you might not be able to view any content in the meeting room. If you launch a content from content library it works fine. 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.

Update/Renew your licenses on Connect on premise installation

Upon few requests I’m listing the steps to renew/update your licenses on the Connect server installation.

Conditions in which these steps should be followed :

  • If you have purchased additional licenses on your existing Connect account and you wish to update them on the server
  • You have an Adobe Connect server installation on your own premises
  • You want to update additional license on your existing license key and not a completely new serial key

Please follow the below steps to update your license file on the server :

  • Goto the Connect server and launch the Admin Console :  http://localhost:8510/console
  • Navigate to the License Settings tab
  • Click on the First link which says : Download your license file from Adobe
  • It is necessary to download a fresh copy of your license file after renewal or on purchasing additional licenses to see the refreshed additions.
  • Once it is downloaded Click on Browse on Step 2 and upload the file just downloaded
  • Save the page and your license should be refreshed.

license-update

If you have a clustered environment setup for the Connect servers, it is not necessary to apply these steps on all the servers.Doing it on any one of them is sufficient as it updates the settings in the DB.

Hope you would find this article useful when you want to update your licenses next time.

 

 

What files to download from LWS for Connect server installation/upgrade

I have received requests from some users to publish what all files are necessary to be downloaded when planning to do an install or upgrade on Adobe Connect server. I know this should have confused many of us, but here I’m listing the required files.

Environment – On Premise

  • Login to your LWS account : http://licensing.adobe.com
  • Goto Licenses > Downloads

LWS-1

  • Choose your product : Connect Lic General
  • Choose the desired version. I am choosing version 9 here
  • Click on Connect Lic General hyperlink at the bottom

LWS-2

  • Download both the highlighted packages for the installation

LWS-3

  • The All Platform Multilanguage/NA package contains the actuall installer files
  • The All Platform Package extractor is the extractor utility specially bundled with the installer and only this utility should be used to extract the installer files

 

I hope this makes the download process simpler for your install/upgrade next time.

 

Update your Presenter content in Connect

I have received requests from lot of users to publish the steps of how we can update an already published content on Connect server which is tied to a course/curriculum.

Please follow the below steps only if you have published your content in the below manner to Connect :

  •  Create a Presenter Powerpoint content
  •  Publish the file locally on your desktop as a zip file instead of publishing it to the Connect server directly.
  •  Once the zip file is published, upload the zip to your Connect content library

If you have published your Presenter content to Connect in the above manner, and you would like to make any changes to the content, you can do so by the below steps :

  • Make the desired changes in the Presenter file & save them.
  • Republish the file locally on your desktop as a new zip
  • Now login to your Connect application and navigate to the already published content
  • Click on Upload content and browse the new Zip file and Save.

 

Please note that although it displays a message there that : ” The content should be in the following format:  *.ppt, *.pptx , however you can also upload your zip file published from Presenter as well here as it is identified by the content type of the file being uploaded, which is ppt/pptx in a content published via Presenter.

upload-content

Please note that if your content is tied to a training or course item, it is NOT recommended to make changes to its content once the course has been made live for users as this may cause inconsistency in their reporting status. If your content is tied to a course/curriculum and you have updated the content after it is already in use by the users, only updating the original content would not update it in the actual course. You will need to update it from the course as well.

  • If it is a course, Goto the course and goto Select Content again and resave the content
  • If it is a curriculum, goto the curriculum, click the desired item from the left, on right hand panel under Course, click on Goto Source, now under that course, click on Select Content and resave the content

update-curr

 

update-curr-1

  • Please note that when you will go to update the content in the actual course/curriculum, you will get a warning message :

update-curr-2

  • Hence it is recommended not to modify the uploaded content in a training/course unless highly important, once it has been made live, else it might cause the above inconsistencies.

 

Adobe Connect Addin; Unable to screen share with PPAPI plugin enabled in Google Chrome

If you are using Google Chrome and trying to share your screen in a meeting session, you might encounter one of the below issues :

Problem#1

Users cannot screen share when using Google Chrome

Solution:

Add [*.]adobeconnect.com to Google Chrome list of exceptions

Steps:

1. Launch Google Chrome

2. Enter chrome://settings/contentExceptions#ppapi-broker in the address bar

3. Add the exceptions as follows:

3a. Under the Hostname pattern, add this string: [*.]adobeconnect.com

3b. Under Behavior: Allow

3c. Click Done

4. Launch your Connect meeting in the add-in mode

 

Problem#2

Users launch meeting in the Flash Player (launcher=false),  when clicking on the ‘Share My Screen’ button, users get an error “Adobe Connect Add-in is incompatible with default settings of your version of Google Chrome.”

Solution:

1. Adding the exceptions to Google Chrome by following the steps in Problem#1

2. Close the meeting

3. Re-launch the meeting within the Connect add-in (launcher=true)

 

Following error might be visible in the meeting room upon screen sharing :

Addin_error

 

Environments in which the scenario might produce :

Windows , Adobe Connect Addin , Google Chrome browser, Hosted/On-Premise Solution

 

Upgrade to Adobe Connect 9.1 causes Avaya Adaptor to be broken

Problem :

If you’ve upgraded your Adobe Connect server to version 9.1 and you already have Avaya adaptor configured, you might find it broken after the upgrade.

You might also run into this issue if you have a fresh installation of 9.1 and you are configuring Avaya adaptor for the first time

Reason :

The adaptor path is incorrect in the telephony configuration files in version 9.1

Environments Affected : Connect 9.1.1 Licensed

Solution :

  • Locate the following folder on your Adobe Connect 9.1.1 root installation : {Connect-Root}\9.1.1\TelephonyService\conf
  • Create a backup copy of  telephony-settings.xml file
  • Open the file in a text editor and locate the following lines for Avaya adaptor : <telephony-adaptor class-name=”com.macromedia.breeze_ext.telephony.AvayaAdaptor” enabled=”true” id=”avaya-adaptor”>
  • Replace the line with the following : <telephony-adaptor class-name=”com.macromedia.breeze_ext.telephony.Avaya.AvayaAdaptor” enabled=”true” id=”avaya-adaptor”>
  • Save the file and reopen the file with IE to make sure there are no errors.
  • Next, Create a backup copy of  telephony-capabilities.xml file
  • Open the file in a text editor and locate the following lines for Avaya adaptor : <telephony-adaptor class-name=”com.macromedia.breeze_ext.telephony.AvayaAdaptor” enabled=”true” id=”avaya-adaptor”>
  • Replace the line with the following : <telephony-adaptor class-name=”com.macromedia.breeze_ext.telephony.Avaya.AvayaAdaptor” enabled=”true” id=”avaya-adaptor”>
  • Save the file and reopen the file with IE to make sure there are no errors.
  • Restart the Adobe Connect & Telephony services.

 

Mandatory SQL Server 2008 upgrade with Adobe Connect 9.1

Adobe Connect 9.1 comes up bundled with SQL Server 2008 version. With your upgrade to Connect 9.1, your existing SQL server would automatically get upgraded to 2008 version if an earlier version is currently in use.

You may choose to upgrade your SQL server yourself separately which should be done prior to upgrading the Connect server to 9.1.

The 9.1 installer has a system check which validates the current SQL server version present on the server and if an earlier version is detected, following message would be presented to the user :

Minimum SQL Server

 

Points to Consider :

~  You may choose to use the SQL 2008 bundled with the installer and continue with the upgrade. The installer would automatically upgrade the SQL server version with Connect upgrade.

~  However, if your organization has a different procedure for deciding upgrades on SQL server, you may first work on getting that updated and attempt the Connect installation once the SQL update is complete. The installer would Quit on the above window if you do not choose to upgrade the SQL server to version 2008 or if it is not already updated to that version.

~  It is recommended to  review the entire system requirements here, http://www.adobe.com/products/adobeconnect/tech-specs.html ,before you decide to upgrade the Connect environment to ensure a hassle free upgrade.

~  We have also created a small upgrade checklist which talks about most of the new changes in functionality brought in 9.1 and the associated documentation http://helpx.adobe.com/adobe-connect/kb/connect-91-upgrade-checklist.html

 

Planning to upgrade to Adobe Connect 9.1 ?? Checkout the Mandatory System Requirements

If you are planning to upgrade your Adobe Connect server soon, do review the minimum system requirements mandatory for your server before you plan the upgrade.

Connect 9.1 onwards, we have introduced a minimum system requirements check in the installer which would not let you continue the installation if your server doesn’t meet the Minimum Recommended Technical Specifications required for it to be operational. You may review the system requirements for 9.1 here :  http://www.adobe.com/products/adobeconnect/tech-specs.html

It is also recommended to review the Upgrade Checklist here which talks about most of the new changes in functionality brought in 9.1 and the associated documentation : http://helpx.adobe.com/adobe-connect/kb/connect-91-upgrade-checklist.html

During the installation activity, the installer verifies the system hardware and proceeds with the installation only if the machine meet the minimum system requirements. If the minimum recommendations are not followed, you might encounter the following error during your installation and the installer completely quits :

 

Minimum-Requirements

 

Why was minimum requirements check added to the installer ?

¤  The check for minimum system requirement was added in 9.1. This was done to address numerous feedback we received from customers where users were unable to determine what was the cause of failed deployments  if it occurred due to insufficient system requirements.

¤  Having this check ensures in the very beginning of the installation that the installation is not expected to fail due to insufficient requirements which was otherwise only figurable after the installation completed and failed and cause lots of frustration to users.