Posts in Category "Events"

Event Module Tutorial Collection

The below is a great collection of Event Module tutorials by both Adobe and our some of our partners.  These cover everything from administration, creation, migration, reporting, best practices, and API integration.


Creating an Event in Adobe Connect 9
by video2brain
In this tutorial, you’ll see how to create a new event in Adobe Connect 9 and add it to the Event Catalog

Creating and Editing Event Templates
by Alistair Lee
In this video tutorial, Alistair Lee shows you how to create, edit and manage event templates – new to Adobe Connect 9.

Event Administration in Adobe Connect 9
by Alistair Lee
In this video tutorial, Alistair Lee walks through the new features available to Event Administrators in Adobe Connect 9

Adobe Connect 9: Event Migration Guide
by Alistair Lee, Adobe Systems
This tutorial features a 23-page PDF guide on Adobe Connect 9 events. It highlights the new features introduced in version 9 of Adobe Connect and discusses the impact on events that have migrated.

Creating a Two Person Event Template with Adobe Connect
by Alistair Lee, Adobe Systems
In this tutorial, you’ll see how to quickly create a new event template that features two or more speakers.

Adobe Connect Events Overview
by Alistair Lee, Adobe Systems
In this video, Alistair Lee walks through an overview of the new Adobe Connect Events module.

Adobe Connect best practices for large events and seminars
by Rocky Mitarai, Adobe Systems
This checklist is an invaluable resource for any producers of large webinars and events on Adobe Connect.

Resetting the Default Event Templates in Adobe Connect
by Alistair Lee, Adobe Systems
This tutorial walks through the steps required to reset a default template.

Campaign Tracking in Adobe Connect 9.1
by Alistair Lee, Adobe Systems
In this video tutorial, Alistair walks through some of the new features in Adobe Connect 9.1 that make measuring campaigns and optimizing your promotional channels more intuitive.

Event Registration using Adobe Connect API’s
by Dustin Tauer, Easel Solutions
In this tutorial, Dustin covers how to use the Adobe Connect API’s to register a user for an event.


Issue with upgrading CQ (Events) on standalone server


This article is for On-Premise (Licensed) Adobe Connect customers with the Events module who may be thinking of upgrading to 9.1.

This only applies to customers who meet ALL of the following criteria:

  • Customers who have installed CQ at the Adobe Connect 9.0 level (officially and who are upgrading to 9.1 (officially 9.1.1)
  • Customers who have installed CQ on a standalone machine (so not on the same server or servers as Adobe Connect)
  • Customers who have installed CQ on a drive other than C:/.  

We have uncovered an issue with upgrading CQ (Events Module) from 9.0 version to 9.1 version on a standalone server where you would have installed CQ on a drive other than the C:/ drive.

With Adobe Connect (the full 9.0 installer’s actual version), we introduced Adobe CQ as the backend for the Events module in Adobe Connect.  This required you to install CQ on either the same server as Adobe Connect, or on it’s own dedicated (preferred) server or servers (if in a cluster).  A typical workflow would have been to install the CQ application for both the Author and the Publisher instances of CQ on a drive other than the C:/ drive on the server (or servers).  The full installation of the original 9.0 version of CQ would have given  you the option of installing CQ wherever you wanted (say for this example, the ‘E:/’ drive).

With the latest (as of October, 2013) version of Adobe Connect and CQ (9.1.1 officially), we introduced a new version of CQ.  So customers who already installed CQ at version 9.0, would have already had CQ on a machine and would be upgrading CQ by running the new 9.1 .1 Adobe Connect installer on that server.  This is where the problem is.  The installer, for an upgrade to CQ will not give you the option to choose the installation folder/location. It just goes through and installs in the C:/ drive, which is obviously not correct if you installed in another location.

There is a workaround for this.

For now, you can work around this problem by adding a property value – USER_INSTALL_DIR=<old Installation directory> to the file <INSTALLER_ROOT>\Standard_DVD\Connect\9.1.1\Disk1\InstData\VM\ Any valid installation path can be provided but format of the old installation path has to be either E:/Connect or E:\\CONNECT (or whatever drive letter you are using).

Note: Again, the full installation of 9.1 will allow you to choose the installation directory. The issue detailed above is only for upgrades from 9.0 to 9.1 CQ.

This issue with the installer will be addressed in Adobe Connect 9.2, which will be coming in Q1 of 2014.


Is there a way to set a filter on the Event Catalog Page ?

Problem Description:-  User would like to know if there is a way to set a filter for end-users around the world who can access their organisation website and click on the public link which is associated with their site event catalog page.

For instance if they share their catalog page publically on a website : https://pub-server/content/connect/c1/7/en/events/catalog.html

All the end-users around the world who navigate to this link, can see the upcoming events. Therefore, client would like to know if there is a way to set a filter that they cannot see all the upcoming events and can only see which the host or the organization wants.

Solution :-

To achieve this use separate catalogs for different audiences. You can create folders in your Events area and put different events in each catalog. You can then make the folder public which will turn it into a separate catalog with a unique URL.





Connect On-Premise Installer for 9.1.1 on the Adobe LWS – Version Questions

Issue: There was an earlier version of 9.1 that looks very similar to the current (9.1.1), but the earlier version is missing some important updates. This will be fixed with the release of Connect 9.1.2

Solution: The normal way to check the Connect version is to poll the version.txt file at any Connect account domain name. To see an example, check this Adobe Connect hosted account for one of our training partners:

The output from this shows the versions of all components of the release: package=… patch=CPS_9.1.1.55_9.1.1.59, patch=CPS_9.1.1.59_9.1hotfix.12

This normal means of checking the build will not work with the 9.1.1 released installer. See the output from its version.txt:


The version.txt is missing the patch numbers.

Workaround technique to find the version:

Look in the downloaded zip installer for versionInfo.xml

  • The date should read: 2013/09/27:08:12:57
  • The build should read:

This is valid as of the writing of this tech-note. It is safe to say that if you see a later date and build number on a full installer download, then you are not going to see this problem and your version.txt will be correct.

Event vs. Session Expected Number of Participants for Seminars

When you create a Seminar SESSION, depending on your Seminar License quota for the number of concurrent users, it will give you the Expected Number of Participants drop down (to select over or under 600 users).

The values are:

  • Large Seminar Session (> 600 participants)
  • Regular Seminar Session (Up to 600 Participants)

If your Seminar License allows for over 600 concurrent seats, you get this option when you create a Seminar Session for a Seminar Room that exists under that License. If the quota on the License is under 600 for a maximum concurrency, you do not see this option when creating a session and it defaults to a ‘Regular’ session.



However when creating an EVENT in the Event Management area and point it to a Seminar Room, you do not get presented with an option to select a Large Seminar Session (> 600 participants) or Regular Seminar Session (Up to 600 Participants).  It will just assume the maximum for the License.  So if you select a Room to point an Event to, which resides in a Seminar License folder, which has a quota of over 600, the default for the Event ‘Session’ will be ‘Large Seminar Session (> 600 participants)’ (although you won’t see this referenced in the information for the Event).



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.


What rights an Event Manager holds as in comparison to Event administrator in Adobe connect 9 ?

Topic Discussed : Rights for both Event Administrator and Event Manager:

Solution : In connect 9 there are two new system groups added for event license users, those are Event Administrator and Event Manager.

First we will talk about an Event Administrator :

An Event Administrator :

  • Can create any number of custom templates.
  • Have full control over the Event Catalog layout and branding.
  • Can create shared templates, limit tags in the Event Catalog, create Reply To options for email triggers, and assign Event Manager role to the registered users.
  • Manage the event tags, which in turn make it possible to filter the events in the Event Catalog.
  • Can update, rename, delete, or copy existing templates
  • Can apply the Featured Event tag to display an event in the Featured Events section of the Event Catalog
  • Members of the Event Administrators group assign users to the Event Managers group, manage shared templates, event tags, and email aliases.
  • Event Administrators can also configure analytic’ s.

Now in comparison if talk about event manager :

An Event Manager :

  • Assigns attendee roles when setting up the event in the Participant Management tab.
  • Can create private template
  • Can only create a private copy of the shared templates.
  • Can only create a private copy of the existing templates.
  • Members of the Event Managers group can create events and manage their own folders in the Event library.
  • If you assign a user to this group, Adobe Connect creates a folder for this user in the User folder of the Event library.
  • Can manage only their individual My Events folders in the User Events folder.
  • Can manage events in the Shared folders if they are hosting the event and have Manage permissions for the folder that contains the event.
  • Manage their own Event library user folder, performing all file-management functions, and create and manage all aspects of an event in this folder.
  • Can view event reports.


Connect throws an error “The item is not selected” or “Please select an item” when user try to create a new event.

Problem : ( After applying patch 9.0.4 ) User when creates a new event on connect, experience an error stating “The item is not selected” or “Please select an item”

Solution : 

Check in the debug log on connect server and look for “REMOTE_CQ_TEMPLATE”. You will see this item is either missing or not found in the Database table name “PPS_EVENT_DETAILS”. The debug log would capture an entry and throws an exception stating “REMOTE_CQ_TEMPLATE” is not found or invalid.

Reason why this happens is because when user apply the patch for 9.0.4 they definitely have not executed the SQL queries provided in the patch ( and The “REMOTE_CQ_TEMPLATE” is present in the script

Therefore go to the Database, make sure the current data base is selected and run the two scripts in sequence ( First and then ).

This should resolve your problem. In case the problem still persist please contact support.



Adobe Connect Event Template throws an error “No resource found”

Problem : Some users

–  When trying the event registration page experience ” No Resource found” error.

–  When edit the event template and activate, the edits are not being saved or reflects on the template where the change is made.

–  When click on different custom/system templates experience “No Resource found”

Solution :

For users who are on our hosted server or in other words who are using our hosted services, if the above mentioned problem is what you witness/experience at your end. Please open a ticket with our base support team at 1-800-422-3623.

For license users/Users who have Adobe connect installed on premises.

Please understand the workflow of Events with CQ Author Server and CQ Publish Server. Here is the brief description on that:

There is a concept/process called as “Replication” which should be working between the two servers. We have a Replication Agent on CQ author server which uses a mechanism to publish ( activate ) content from an Author to a Publish environment and we have a “Receiver Servlet Agent”  on CQ Publish server which lifts such packaged content from the replication queue on CQ Author server. Replication to a publish instance takes place in several steps : ( Follow the figure below while i explain here )



  • The Author requests that certain content to be published (activated); this can be initiated by a manual request, or by automatic triggers which have been preconfigured in the system.
  • The request is passed to the appropriate default replication agent; an environment can have several default agents which will always be selected for such actions.
  • The replication agent “packages” the content and places it in the replication queue.
  • The content is lifted from the queue and transported to the publish environment using the configured protocol; usually this is HTTP.
  • A Servlet in the publish environment receives the request and publishes the received content;

Now Considering the above fact that i just explain here:

If a user is experiencing the problem statement shown above in the start of this blog.

There are two important things you need to check in such situations : 

First check if the replication agent exist or not and if its not, do as explained below:

  • Navigate to the CRXDE | Lite page on the author environment http://localhost:4502/crx/de/index.jspAuthor-Login   CRXDE-Lite
  • On the Left Pane where you see the Tree folder structure Go  to folder ETC ( click on plus sign )


  • Now look for folder name Replication underneath that folder ( Click on Plus sign )


  • –>Now click on a plus sign for Node name “”  which is your replication agent node, if this node does not exist ( Call us ) else —>Underneath that folder look for a Node name “Publish_Your_Publish_Instant_Name”, i am typing the name in generic form.

Note:- In the picture below you will see the replication agent name for my local server as “Publish_connect-publish_dev_com” because my public instance FQDN name is



If this does not exist, you will experience what i have explained in this blog. To fix this you need to recreate this node by following the below steps:

Click on the CRXDE-Lite home page


Navigate to Tools option on the home page.


Under the tools option, Navigate to the replication folder and hightlight the “Agents on Author” option as shown below:


Now on the right pane click on the New page option as shown below :


You will see a window where you can create a new Replication agent. You can type your Replication Agent Name and Choose the option Replication Agent then hit the create button, as shown below:


Now you will see a new replication Agent instance is created underneath your Replication agent Node on CRXDE-Lite page as shown below :


Now Double click on the agent you just created and go to edit under settings. ( Remember it will be disabled as shown below untill we check the enable option )


Change the name to Replication agent under the settings TAB and make sure its enabled, so check the box called Enabled.


Now go to the Transport Tab and Change the URI : http://localhost:4503/bin/receive?sling:authRequestLogin=1. Instead of localhost here, you can put your CQ publish instance FQDN here and hit ok without making any other change. User Name and Password will be your CQ credentials.


At the end you can do what is explained in the second step below to confirm if replication is successfully Replicating.

Secondly if the replication agent exists and still you are experiencing such issues, please do the following :

  • Double click on the replication agent “Publish_Your_Publish_Instant_Name” and click on “Test connection” link: you should receive “Replication test succeeded". If you do not receive that, call us on our support line. 



Thats about it !

I hope this blog will help you solve most of your issues related to replication.

Thanks !