Posts in Category "Reporting"

New Adobe Connect Support Blog Subscription Option

Now you can stay on top of the new articles and posts by subscribing to the Adobe Connect Support Blog. Simply go to the Adobe Connect Support Blog home page and enter your email address and check off the categories about which you would like to be notified. Click “Subscribe me” and you will begin receiving  regular updates:




Reporting Enhancements with 9.5 release – Overview

I’m briefly describing here the new Reporting features that were introduced as part of Connect 9.5 release earlier this year. These reports have been added as part of this release to allow Adobe Connect Administrators to have a better view of the usage of their Connect accounts.

Availability : Hosted/Licensed setup

These reports are available under Reports -> System Usage tab. Both the reports can be downloaded in CSV format for further analysis.

Meeting Sessions Report >>

The meeting sessions report provides a summary of various meeting sessions that happened over a period of time and provides details per session such as start and end time, duration, session type (meeting/ seminar/ virtual classroom), total and peak participants.
  • Goto the Reports tab and go under System Usage Reports 



  • Select Meeting Session Usage from the dropdown and click Next


  • Select Date Range for filters and add or remove Report fields to be shown on the Report
  • Create Report
  • The report would be generated and it shows Meeting Usage Data Summary accordingly for the Reporting fields selected for display.
  • The report is available to be downloaded in CSV format or saved for later review by Administrators.
Meeting Usage Report >>

The meeting usage report provides a summary of meeting activity over a period of time. Users can find out total user minutes clocked as well as the peak concurrent users for the given period.

  • Goto the Reports tab and go under System Usage Reports as in Pic-1 above.
  • Select Meeting Usage from the dropdown and click Next


  • Select Date Range for filtering data based on a time duration to be shown on the Report
  •  Create Report
  •  The report would be generated and it shows graphical representation of Meeting Usage Data for the time duration selected. 


  • The graphical report shows the Peak Concurrent Meeting users connected over different dates and the Total User Minutes that were consumed during those dates.
  • The Report can be downloaded in CSV format or saved for later review by Administrators.


Note  :  As indicated on these reports, reports from Reports section may take upto 24 hrs to reflect the latest data, depending upon the synchronization with the Reporting Database.


Hope these exciting features are helpful for you in your usage of Adobe Connect System Reports !



Avoiding Inaccurate Completion Reports when a Meeting is Part of a Curriculum

When a meeting is part of an Adobe Connect Curriculum, a trainee can click on the Meeting and complete the Meeting task prescribed in the Curriculum prior to the Meeting taking place.



One way to help manage this is to choose the Meeting options to block Meeting access illustrated in the screen captures below:





The Meeting access options may be inconvenient to use, so here is another option to add a Meeting to a curriculum, while at the same time restricting the ability for a trainee to complete the Meeting task prior to the Meeting taking place:

Step one: The first step is to set a date and time under the Meeting properties. Make sure the date and time correspond to when the Curriculum task takes place. Note that this date and time has no effect on when the Meeting can be used. It is strictly an administrative tool to help with Meeting invitations and has no effect on when the meeting can be opened, Meeting persistence, etc. In this example I have set the meeting to October 22, 2014 at 12:45 for 1 hour:



 Step two: Download and unzip the Meeting Curriculum Wrapper:

Note that it is zipped twice to facilitate download:


Step three: Identify the Meeting sco ID from the Meeting that you wish to add to the Curriculum and copy it to the clipboard:

The Meeting SCO is in the Meeting URL:


Note: You can also see the Meeting sco ID by pasting ?mode-xml at the end of the Meeting URL and reading it from the output:


Step four:  Edit the index.htm in the unzipped LaunchMeetingInCurriculum folder by pasting in the Meeting sco ID from the Meeting that you wish to add to the Curriculum. Use your favorite text editor such as notepad or textpad. Where the index.htm reads,  Enter the SCO of the Meeting, Virtual Classroom or Seminar var meetingScoID_str = ‘1660065186’; change the default Meeting sco ID, 1660065186, to the Meeting sco ID of the Meeting that you wish to add to the curriculum, in the case of my example here, the Meeting sco ID is: 502114549. Be sure to save the changes:


Step five: Zip all the edited contents of the LaunchMeetingInCurriculum folder and rename it to represent the Meeting that you wish to add to the Curriculum. This will help you identify it and differentiate it from other Meetings with which you use this wrapper:



Step six: Upload the edited zip file to the Adobe Connect Content Library:




Step seven: Import the wrapper from the Content Library into the Curriculum:


Note: Import options; the wrapper is Content and points to the Meeting:





Step eight: Test the Curriculum item; unless the time and date coordinate with the actual Meeting schedule, the pop up will deter the trainee from gaining premature access to the Meeting and skewing the Curriculum completion report:


 Conclusion: With proper management and administration, an Adobe Connect Curriculum accurately measure the progress and completion of trainees. There are two ways to prevent a trainee from completing a Meeting curriculum task prior to the meeting taking place, the first is to block access to the Meeting and the second is to use the Meeting Curriculum wrapper.

Query for meeting host usage

Problem: How to know the host usage for connect account?

Environment: Hosted/Licensed

Reason: An account administrator would like to know how many meeting hosts are on the account in order to know their license utilization.


  • Adobe connect provides system usage report where you can check the meeting host usage on your account.
  • In order to pull up this report, you have to navigate to Reports tab -> System usage.
  • In system usage report from the drop down select Group as a report type, now point meeting host group.
  • Filter the report date wise and generate the report.



  • Watch a video tutorial here

XML API Tips: Internal-error When Executing Reporting Calls

Periodically when executing a reporting API call, you may get an unexpected return as shown below:

<status code=”internal-error”>
<exception>java.sql.SQLNonTransientConnectionException: [Macromedia][SQLServer JDBC Driver][SQLServer]Cannot open database “XXXXXXXXX” requested by the login. The login failed.</exception>


Where the ‘XXXXXXXXX’ would be the database name of the database your request was trying to hit.

This is expected if you are making one of the ‘reporting database API calls‘ during the exact time that the db is locked for a small restore.  As previously discussed, the reporting database is not real-time. It is synched occasionally and can be behind by as much as 24 hours.   That error (you would see it in the logs and in your response) is thrown when the DB is being restored.  When the db is being restored, the DB is locked down and the result will be a failed login (internal-error).  The reporting DB is log shipped every 15 minutes.  So every 15 minutes there will be a small restore.  All you’re application needs to do is retry when you get that message.  It could be as much as a minute of downtime, but most of the time is less.


XML API Tips: Reporting API Calls and the Reporting Database

One common question from API developers revolves around the existence of our reporting database vs our production database on Adobe’s Hosted platform.  There are a few API calls that will hit the reporting database rather than production, to retrieve information.  This is by design and is to prevent some of the more expensive APIs from being run on a multi-tenant environment’s production database.  The current calls that are redirected to our reporting database and not to our production (real-time) database are:


As you can see, these are all the ‘bulk’ API calls.  There is one additional call that is currently (as of Adobe Connect 9.2.2) being directed to the reporting database rather than production, and that is:


This action will be shifted to the production database in the next major release of Adobe Connect.

The reason this is important is that the reporting database is not real-time like production.  It is delayed, sometimes up to 24 hours.  So it is recommended that if you need to have real-time information in your application, you avoid making the calls above and use other APIs to retrieve the desired data.

Connect Reports Never Returning Data in Firefox

The Adobe Connect Reports module is Flex based and for longer queries (reports on courses or curricula with large enrollments for example), sometimes the report can take many minutes to return data back to the browser.  Previously we have worked on issues with the reporting module in which the busy cursor (spinning wheel) continues to spin indefinitely and doesn’t return data because the query took too long to return.  We have made adjustments to the DB views and code to fix the performance of the reports in the latest versions of Adobe Connect and up until recently, we had solved this problem for users running the latest versions of the application.

However recently we have seen with newer versions of the Firefox web browser, the reports once again spin indefinitely and not return data in the Flex based reports in some instances where the queries are large.  Investigation into this lead us to determine that after a period of 5 minutes, we saw a socket write error in the debug log like the one below:

[05-29 10:15:30,623] http-80-15 (INFO) Exception caught in Rows.parse(), e= org.xml.sax.SAXException

ClientAbortException: Software caused connection abort: socket write error

After changing various FireFox timeout settings to no avail, we noticed the following newer setting ‘network.http.response.timeout’, which was introduced in Firefox 29 (the current version is 30). The default value for this timeout is 300 seconds (5 minutes).  In previous versions there was no default value.

After changing it to a longer value, the reporting now works in our testing. With the current implementation of the reporting module, there is no way for Flex to detect that the http response has timed out. Until we can address this in the Flex code and provide a warning, we just have to be mindful of this setting in FireFox.

To change this setting, you simply type this in the Firefox browser address bar: about:config and hit enter.

You will see a page with all of the configurable settings.  Search for ‘network.http.response.timeout‘ to isolate just the one setting you need to change (there are a lot of settings to scroll through otherwise).  The default value is 300 seconds (5 minutes).  If you are running into the situation where your reports are not coming back with data (and you are running the latest version of Adobe Connect , 9.2 and above), you can adjust this setting to see if it helps (if you are using Firefox as a browser).  If you anticipate users having to run large queries (like curriculum reports with large enrollments in the 1000s of users), you will need to adjust this setting.


Type ‘about:config’ in the address bar. Then search for ‘network.http.response.timeout’


Modify the value by clicking on the 300 value itself and then entering the new value when prompted.



Using the XML API and Microsoft Excel to obtain additional reporting from Adobe Connect

Sometimes customers need a custom report that is not included in the normal reports in the Adobe Connect UI.   They can obtain this data by running an API call, however the results get displayed in a browser (in an XML result set) and is not in a user-friendly format as-is.  In lieu of actually building an application that can parse and display the XML in a nice format for the user to be able to display in a useful manner, we can simply use Microsoft Excel to display the data in a nice tabbed report format.

An example of this would be as follows:

Say, you want to report on what users are in a particular group within Adobe Connect, and there is no good established report to actually display this data (other than in the datagrid in the Users and Groups area)…

Here’s what you can do.

Log into the account in a browser, as an admin.

Run the following API (or any API you need to run to obtain the data you are looking for):


group-id= principal-id of group you want to report on

 The results will get returned in the browser in XML format (as seen in the screenshot below):

Save the current page as an XML file by going into the browser options and select ‘Save As’ and make sure you save the page as ‘.xml’.



After saving the XML locally, open up Microsoft Excel (on Windows) and select Data > From XML Data Import.



Click OK through all the next pop ups that show up after selecting the XML file and just select the defaults:

xml-3 xml-4


Once the data loads in the worksheet, it will be formatted in a nice tabbed display as you see below:


Brad’s Short-list for Connect Cluster SaaS Monitoring Options

There are many options on the monitoring theme that are worth considering when trying to decide how to keep trach of Connect server resources in a cluster. Articles describing clustered environments are on the Connect Users Community :  Simply search the User’s Community using the keywords: cluster, pool, edge, SSL, etc.

To effectively monitor your Connect cluster SaaS options can sometimes be cost effective than home-spun solutions; here are some staff picks with some commentary:

Sumologic– It resembles Splunk. The main difference is that Sumologic is hosted and managed externally and Splunk is hosted and managed on-premise. With Sumologic, there is not any need for software licensing, hardware investments or internal administrator expertise.  Splunk offers a similar service called splunk>storm, but it is not as mature as Sumologic and lacks some of the alerting capability found in Sumologic.

Loggly An alternative to Sumologic could be Loggly which offers a similar service; it seems that the alerting service is not exactly built in.  It requires a little more work and is called AlertBirds.

Note: It is possible to take an on-premise option like Cacti and port it to Sumologic, so you could effectively kill 2 birds with one stone.  You can setup a forwarder in 30 seconds and be searching the logs in no time at all.

Monitis – Provides capabilities similar to those of Nagios along with external monitoring.  The Monitis community writes custom monitors thereby enriching the options.

LogicMonitor – An alternative to Monitis could be something like LogicMonitor.  You may be able to port your existing Nagios checks over to it (check and verify).  This si a simple solution, installing the monitor and having basic checks like CPU, Memory, Bandwidth, Disk Usage, Disk IO and external ping, http, https and udp monitors setup would take all of 20 minutes.

Pingdom– An alternative to RedAlert at a lesser cost.  It is trusted by millions and is easy to use and has more endpoints than comparable options.  It takes five minute setup.

The beauty of a SaaS monitoring solution is that you do not need to worry about scaling your monitoring solution every time you scale your Connect architecture.  You can have a single solution for 20 Connect Clusters vs having to add Cacti servers, Nagios servers, Splunk architecture and licensing to handle the additional monitoring needs commensurate with expansion.  With a SaaS solution, there in not any build-out time.  You can literally have 20 monitors up and running in under an hour, and work on adding additional ones at your leisure in between casts with your new Deceiver 8 Fly Combo.

With reference to basic on-premise monitoring, make sure you use standard perfmon counters for things like CPU, Memory etc. For meeting count and meeting user monitoring you may use the FMSAdmin API with scripts to make various calls and then parse the data and pass it to an option such as Cacti.  To insure robustness, the FMSAdmin service should be restarted routinely. You could also use similar counters to pull data directly from the Connect database, but this is not without risk as Connect updaters and upgrades can introduce changes that may require rework of your custom counters.

Connect Training Course does not Produce Completion Report

Issue: When a course is started and left open, perhaps while multitasking or looking up additional references, etc., it may timeout and work of the trainee in the course can be lost.

How to approach this – As with many symptoms, there is often more than one ameliorating approach; two are offered below:

One very quick way to help with  this is to increase the session time-out value in Connect

  •  At the top of the Connect Central administrative window, click Administration.
  • Click Account.
  • Click Session Settings.
  • Enter a timeout length in minutes that is long enough to cause fewer instances of timeouts.
  • Click Save.

Another way to approach this is to use Adobe Presenter 9 to create the training content. Presenter 9 handles sessions and bookmarking that is not supported in previous versions of Presenter.