Archive for September, 2013

Adobe Connect server pools/clusters and hardware-based load-balancing devices with SSL acceleration

The most robust means of implementing secure socket layer (SSL) with Adobe Connect servers is through a hardware-based SSL accelerator and similarly, the most robust means of clustering Connect servers is with a hardware-based load-balancing device (HLD). Since all enterprise-class HLDs are also SSL accelerators (any that are not both are either legacy or low-end by definition), this example-based article offers a best-practice configuration of a Connect Server pool or cluster running Connect Meetings, Adobe Presenter on-demand content, Adobe Connect Training, Curriculum and Virtual Classrooms securely behind a high-end, application-aware HLD and SSL acceleration device such as F5 BIG-IP LTM. This article does not exhaust the possible configurations, but offers a general working example.

The full tech-note is published here:


Adobe Connect Edge Server Deployment Options: part 2

This article focuses on Enterprise Proxy Connect Edge deployments and troubleshooting:

Adobe Connect Edge Server Deployment Options: part 1

This article focuses on reverse proxy Connect Edge deployments:

Enable Client-side Connect Meeting Addin Debug Logging to Diagnose Meeting Connection Problems

To facilitate troubleshooting of Connect Meeting connection issues, enable client-side Connect Meeting Addin Debug Logging according to the following tech-note:

Event Administrator or Account Administrator group permissions do not allow a user to edit AEM/ CQ Events templates

Event Administrators or Account Administrators group permissions do not allow a user to edit AEM/ CQ Events templates

Note: This issue applies to Connect version 9.1 for amelioration of Adobe Connect bug # 3629575 scheduled to be fixed in a 9.1 point release.

Issue: Connect users with only Event Administrator and/or Account Administrator group permissions are not able to edit the AEM/CQ Events templates; this happens with migrated Connect accounts. This article applies to Connect hosted accounts that have  been migrated.

To reproduce the problem: Create a user with Event Administrator or Account Administrator group permissions and log in as that user. Go to the Events management tab in CPS and try to edit an Event template. The result will be the following error:

No resource found

Cannot serve request to /content/connect/c1/##########/en/events/email/shared/absentee.html in /libs/sling/servlet/errorhandler/404.jsp

The workaround for this issue is to add Event Managers group permissions for users with Event Administrators/Account Administrators permissions to facilitate editing of Events templates. After adding the user to the Event Managers group, be sure to clear the browser cache.


Account Administrators and Event Administrators who are not Event Managers will not be able to open AEM/CQ templates belonging to migrated AEM/CQ microsites.

Empty session in the redirect after a user logs into to an Event

If you have recently upgraded to Adobe Connect 9.1 with the Events Module, you may run into a problem where after your users log into an Event via the Event Login page, they are redirected to the Adobe Connect login page with an empty session variable in the URL.  So instead of immediately letting the user into the Event (be it a Meeting, Training Course, etc) it simply redirects the user back to the Adobe Connect login page with the URL: https://{connectURL}/{eventURL}?session= .  

This is a known issue where the CQ packages for 9.1 were not applied with the installer if this was an upgrade from a previous version of Adobe Connect.

To resolve this issue, steps must be taken to update the CQ packages on the Author and Publish instance of every CQ server in the cluster/environment.

Here are the steps.  Please read this carefully.

Updating the CQ Instance for Author and Publisher after upgrading to Adobe Connect 9.1

These steps below are first done on the CQ Author instance on the CQ server, which has a 4502 port value after the FQDN. The EXACT same steps are applicable for the Publisher instance at port 4503. What you have to do is follow these steps through to the end on the Author instance (port 4502) and then REPEAT all the way through for the Publisher instance (port 4503).

First, download the following files to all the CQ servers you need to update:

These steps below are documented for performing first on the CQ Author environment and for the basis of this document, I will reference the Author instance when referring to the URLs to navigate to. HOWEVER, after you are done with these steps on the Author instance of CQ (port 4502), the EXACT SAME steps need to be cycled through again, in their entirety on the Publish instance of CQ (port 4503). For the sake of making this document as brief as possible, I did NOT repeat all the screenshots and steps for Publisher, as they are exactly the same, except a different port (if the CQ Author and Publish instances are on the same machine). If they are on separate machines, you’d obviously need to perform this on that other machine. You also need to do this on EVERY CQ server in the cluster (if you have a cluster of CQ).

On the CQ Author Server, navigate to:

http://{CQURL}:4502/crx/packmgr/index.jsp (where {CQURL} value is your FQDN for CQ)…



Log in with your admin user/password. (If you don’t login with user/pass you will see ‘No packages found’ when looking at the Package Manager).

Once into the CRX Package Manager (shown below):




Make sure you are logged in as an ‘admin’ (in top right-hand corner):


Look at the (the first package listed in the list). If the’s icon is a blue cube (as shown above) and the size is 8.7MB, it was NOT updated by the Adobe Connect 9.1.1 installer and needs to be deleted and updated with the new package.

The old package that should be updated would look like this:



The new package would look like this (it will have the Adobe Connect Logo and will be a larger 10.4 MB in size):



You need to Delete the old package and upload the new one (downloaded from the link at the top of this document).

First, click on the ‘’ package name in the list to expand the information and options below it.




Then click the ‘More’ dropdown in the top right-hand corner of the options menu and select ‘Delete’ from the dropdown options (shown below):




Confirm the deletion by pressing ‘Delete’ button:



You will now see the package is deleted and it gets removed from the list.  You also see the deletion being logged at the bottom in the Activity Log area.  If you see a red error in there, it is probably because you are not logged in as an admin, therefor it won’t be deleted.




Now, click on the ‘Upload Package’ link at the top of the page (shown below as well):


In the ‘Upload Package’ pop up window, navigate to your ConnectEventApp.jar that you downloaded above, and select it.  Do NOT click ‘Force Upload’ option.




Once the package has finished uploading, you will now see the following (below) in your packages:




Now you need to INSTALL the package.

In the top right-hand corner you see the ‘Install’ link in blue (shown below as well):



Click Install.

In the ‘Install Package’ dialogue that comes up, be sure to select ‘MERGE’ as the Access Control Handling option. By default this is ‘Overwrite’. Select ‘Merge’ and then click the ‘Install’ button.




You will see a lot of logging in the ‘Activity Log’ area below the package until it finishes with a ‘Package installed’ message (shown below).



Now navigate to CRXDE Lite on the CQ Author server:

http://{CQURL}:4502/crx/de/index.jsp (where {CQURL} value is your FQDN for CQ)…

Drop down through the following path shown below: (content>connect>c1>jcr:content)



Look in the Properties tab and confirm that:

The ‘cookiePrefix’ value is equal to the DB_PREFIX= value in your custom.ini located on your Adobe Connect server at: C:\Connect\9.1.1\custom.ini.



Look at the ‘serverUrl’ value and make sure it matches your Adobe Connect Host value (FQDN) of your Adobe Connect system.



This is the full view:



Now navigate to the system console on the CQ Author server:

http://{CQURL}:4502/system/console (where {CQURL} value is your FQDN for CQ)…

Log in again as an admin if it prompts you.




On this page, search for ‘connect’ (or scroll down until you see the item below).

You will be taken to the item (bundle): ‘connect-osgi-service’




Click on the item to expand:




Confirm the version of the bundle.




The latest version for 9.1 should be:

If your version is different (older) than this version (as in this example where my version is:, you need to update the bundle.

Click ‘Install/Update’ button in the header above the item information (shown below):

On the ‘Upload/Install Bundles’ pop up window, click on:

‘Start Bundle’ and make sure it is checked.

Click ‘Choose File’ button and navigate to your ‘connect-osgi-service.jar’ that you downloaded from the top of this document.

Click ‘Install or Update’ button.



Once this is done, search again for ‘connect’ in this page and find the ‘connect-osgi-service’ item again.

Click on the third button on the right (the one that looks like two arrows moving in different directions and it will say ‘Update’ if you hover over it with your pointer) (shown below):



It should update quickly, and show ‘Active’.


Now, REPEAT all the steps above for the PUBLISHER instance of CQ. All the URLs and steps will be the same except the URLs will use 4503 rather than 4502.

Once you do this through and repeat for the Publisher instance at 4503, Stop and Restart the Services.

  • First stop Adobe Connect CQ-Author, then stop Adobe Connect CQ-Publish.
  • Then start Adobe Connect CQ-Author, then start Adobe Connect CQ-Publish.



Remember to clear your browser cache!!!

Now test your Events to see if they are working correctly.


If you do not have the ‘’ package visible in your Package Manager on both 4502 and 4503 (the same place you uploaded and installed the ‘’ file), please follow the same steps to Upload this package (which can also be downloaded from the links above) and Install on both 4502 and 4503). Remember to upload, and then install choosing the ‘Merge’ option. Once this uploads, it should show up in the list as below:


If you already see that hotfix, you do not need to do this step. If you do have to add this hotfix, please do so and then stop/restart the CQ services again. This also needs to be done on EVERY CQ Author and Publisher instance in the cluster.


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, ,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


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 :

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 :

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 :




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.


‘Not Found’ Error when trying to schedule a Seminar Session

UPDATED: 12-09-2013 – (Includes SQL statement below, to identify Events that point to a Seminar Room that have been deleted).  

If you run into a ‘Not Found‘ error while trying to schedule a Seminar Session (or modify an existing session’s timeframe) in Adobe Connect 9.1, you may be running into a known situation where there may have been an Event Session scheduled on a Seminar Room and then that Seminar Room was deleted.  When you create an Event in the Event Management area of Adobe Connect and then point that event to a Seminar Room, it creates an ‘Event Session’ on the Seminar Room Calendar (just like a normal Seminar Session).  Event Sessions appear in orange on the calendar and normal Seminar sessions appear in blue.

What happens when you delete a Seminar Room normally, is that any ‘Seminar Sessions’ that have been created for that room will also be deleted.  However Events do not get deleted, as they can still technically be used for other content items, rooms, etc.  They also contain reporting data.  So we do not actually delete the Event itself.  But we do remove the Event ‘session’ from the Seminar Calendar.  This causes confusion because at a glance, there appears to be no sessions scheduled on the calendar for the slot that was once taken up by the Event Session, before the Seminar Room got deleted.  Any attempt to modify an existing Seminar Session or Event Session’s time, or creating a new Seminar Session or Event Session that conflicts with the deleted Seminar Room’s Event (that is still present), will lead to a ‘Not Found’ error.


This is an example of an Event Session scheduled on the Seminar Calendar


This is what the Seminar Calendar looks like if you delete the Seminar Room but leave the Event active. It will not show up any longer on the calendar but will still be affecting other sessions for that time slot it used to belong to.


The ‘Not Found’ error


The workaround is to delete the Event.  You cannot modify the Event’s time to expire it.  Once the Event is deleted, you will be able to create new, or modify existing sessions to use during that specific time.

Notes and Tips:

This issue is slated to be fixed in an upcoming release later this year (2013).

The Event Management system allows you to create Events that extend across a long period of time (multiple days). Do not schedule an Event for a Seminar Room, that extends beyond the exact time you actually need to use the Seminar Room for, otherwise you will lock up the Seminar Room Calendar for everyone else on the account and no one else will be able to create a Seminar Session. This also may manifest itself if your account was recently upgraded to 9.1 and you had existing Events that are persistent for a long period of time that extends into the future.

If you need assistance identifying what active Event may be pointing to a deleted Seminar Room, you can contact Adobe Support who may be able to identify this by looking in the system logs.

When your users delete Seminar Rooms, they will get the following warning (below) before deleting the room, indicating that there is a linked item.  This is indicating that there is an Event pointing to this seminar.  They should also delete the Event that points to this room IF that Event is still active or will happen in the future.  If the Event is past, it does not need to be deleted as it won’t conflict with future sessions that are created by other users.


This is the warning users will get if they try to delete a Seminar Room that has a Session associated with it.



The following SQL will help identify (for On-Premise customers) an active (or still to come) Event that points to a Seminar Room that has been deleted.  When copy/pasting, make sure to clean up any extra lines, spaces, etc.    Change out the text in BLUE with your values.  The ‘lic’ value is the sco-id of the SEMINAR LICENSE FOLDER.   The start and end dates are the dates to search on, for an active Event.  If you suspect you may have a long term event somewhere on the system you need to search on, make sure your search criteria spans that entire date range.


declare @lic int;
declare @start nvarchar(30);
declare @end nvarchar(30);
set @lic = XXXXXX;
set @start = ‘2013-12-10 15:31:00‘;
set @end = ‘2013-12-31 16:29:00‘;


a.sco_id , a.account_id , a.folder_id,, a.url_path,
a.source_sco_id,  a.date_begin, a.date_end
from pps_scos a (nolock)
where a.source_sco_id in
(select sco_id from pps_scos (nolock)  where folder_id= @lic and disabled is not null)
and (  ( a.date_begin >= @start and a.date_end <= @end)
or (a.date_begin <= @start and a.date_end >= @start )
or (a.date_begin <= @end and a.date_end >= @end )
or (a.date_begin <= @start and a.date_end >= @end)  )
and (a.type = 16 or a.type=5)
and disabled is NULL


Seminar Session Dropdown Box Limit



One thing seminar users may run into in Adobe Connect 9.1 with scheduling seminars is a UI limitation with the dropdown box that contains the list of all available Seminar Rooms on the account.  Currently, this dropdown box only lists up to 1000 Seminar Rooms (in alphabetical order).

As of 9/12/2013, currently the plan is to increase this limit for possibly the next release of Adobe Connect.  At the current time, if you reach 1000 seminar rooms across all of your seminar licenses, the dropdown box will not list any past the 1000th item.

If you run into this problem when scrolling through the list of available seminars, the only current methods to bypass this issue are to:

  • Delete/remove older Seminar Rooms that are no longer needed or used.
  • Rename seminar rooms to push the specific room to the top of the list.
  • Use the XML API (Web Services) to schedule seminar sessions (view blog entry here).