How to Remove a Course End Date in Connect

This solution is only applicable to only on premise customers; hosted much-tenancy customers are not able to edit the needed file.

tngdate.fw

On the Connect server, go to:

<CONNECT_HOME>/<release>/appserv/apps/course/sco_edit.xsl

Search for:

<xsl:variable name=”disable-date-closed-sel”  select=”boolean(/results/sco/date-end or (/results/params/param[@name=’date-end’] and /results/params/param[@name=’date-end’]!=’unset’) or (/results/nav/@style=’wizard’) )”/>

Remove the section highlighted in bold italic: or (/results/nav/@style=’wizard’)

Restart the Connect Services

The course end date is removed.

tngdate1.fw

On-premise Connect without Webinars Throws an Error when Moving Meetings

On-premise Connect customers running version 9.5 who do not have the Webinar option enabled will see an error when trying to move meetings via the GUI in Connect Central:

Webinar95Bugon-prem.fw

This will be fixed in an upcoming release and in the meantime we have two workaround options:

CSO: Resolved and Restored – DATE (09DEC2015)

From 9:05 to 10:30 AM MST, all Adobe Connect customers hosted on NA1 would have been unable to login or use any Connect related services. This has been repaired and customers are now able to login

Adobe Connect ID’s are changing from INT to BIGINT

UPDATE: THIS ARTICLE IS FOR XML API DEVELOPERS ONLY.  If you are not using the XML API with Adobe Connect to write your own custom built applications that integrate with Adobe Connect, please do not worry about the message below as it will not apply to you.


Due to the growing popularity of Adobe Connect, more and more customers rely on Adobe Connect for their collaboration needs and this naturally requires that we make adjustments to accommodate the growth.  We want to make you aware of an upcoming adjustment to the ID values in Adobe Connect databases to support longer values which will accommodate growing customer use of Adobe Connect.

What is being changed?

Starting with release 9.5.2, Adobe Connect will migrate the ID values in Connect databases from INT to BIGINT/Long.

What is the impact?

This change will impact any applications using Adobe Connect Web Service APIs.

How will Adobe Connect Web Service APIs be affected?

The change is for those APIs which consume/return id values i.e. which have a parameter in request/response which is an Id. (examples: sco-id, account-id, folder-id, etc).  The id fields in such APIs would return/accept larger values. The support and behavior of existing APIs remains same.

What does this mean for you?

In case you are interpreting ids as integers the new values might overflow. We strongly recommend using strings to represent id values. In case you still need to represent/store ids as a numeral please use integral data type with higher capacity. (Preferably 64 bit)

What is the timing?

We expect to release Connect 9.5.2 in the first quarter of 2016, so the change should be made as soon as possible in order to be ready prior to the release.

CSO : DATE (20 NOV 2015) – Adobe Connect Access Intermittent for DA2 Datacenter – RESOLVED

UPDATE #4:

As of 1:05 PM ET,  while we are still waiting on Level 3 to confirm on their end that the issue is resolved, further testing by our Technical Operations team was able to confirm that network traffic has returned to normal levels and Adobe Connect services are no longer appearing to be impacted.
We are marking this as resolved and a full incident review will be conducted.  Out of this, a statement will be prepared and delivered.

 

UPDATE #3:

As of 12:50 PM ET, we are still waiting on the service provider.  Level 3 is experiencing major issues across possibly multiple locations although we still do not have confirmation outside of Chicago.

The issue is still intermittent depending on the network route that customers are taking to our Dallas datacenter.  Customers may have packet loss but still get to the Connect account.  They may experience slower load times and performance issues.  Other customers may experience timeouts.   Customers not going through affected areas will not see an issue.
Update to follow.

 

UPDATE #2:

As of 12:00 PM ET, we have identified this being a carrier issue currently in the Chicago area. It appears to be an outage on the Level 3 network where it is affecting customers routing to our Dallas datacenter (DA2) through Chicago.  It may possibly be impacting other routes as well, but currently the teams are waiting on official word from Level 3 on this issue.

 

UPDATE #1:

As of 11:15 AM ET, there is intermittent connectivity to Adobe Connect meetings and the Adobe Connect web application for all clusters in the DA2 datacenter.  This affects accounts on the following clusters:

NA3, NA4, NA5, NA7, NA10, NA11

The teams are currently engaged and investigating this issue.

Update to follow.

 

Connect 9.5 Edge Server Installation Instructions

Note: The upgrade installer described in this article below is deprecated. For instruction on the latest 9.5 installer, please see the following article: 9.5 Connect Edge Proxy Server Full Installer

Connect 9.5 server installation instructions:

  1. Create a folder <Installation_Directory>/950/edgeserver
  2. Download the Edge 9.5 (based on AMS 5) installer
  3. Run the self-extracting .exe file downloaded in step#2 to <Installation_Directory>/950/edgeserver
  4. Refer the following articles for deployment options:
    1. http://www.connectusers.com/tutorials/2011/06/edge_server_deploy/
    2. http://www.connectusers.com/tutorials/2011/06/edge_server_deploy2/
  5. Run <Installation_Directory>/950/edgeserver/win32/vcredist_x64.exe
  6. Run the following commands as administrator:
    1. cd <Installation_Directory>/950/edgeserver/win32AMSAdmin.exe -install
    2. AMSMaster.exe -install
    3. sc start amsadmin
    4. sc start ams
  7. Confirm that services “Adobe Media Administration Server” and “Adobe Media Server (AMS)” are running
  8. If services need to run using specific user credentials, then be sure to set the credentials in service properties and restart the services

Estimating Bandwidth Consumption in Connect Meetings:

Estimating bandwidth consumption in Connect 9.x Meetings:

The following tables may be used for estimating the amount of bandwidth that will be required for a Connect Meeting based on the features used.

Screen Share:

Screen Share Frame Rate Quality Bandwidth
(kbps)
Low 2 65 500
Medium 4 80 800
Standard 6 90 1200
High 8 100 2000

VoIP:

With reference to VoIP, it is independent of any settings. There is no metric comparable to frame rate or quality or bandwidth with VoIP;  a single metric of micRate is used. Currently we use following values:

Number of VoIP users Without UV With UV
<4 22 kHz 22 kHz
>=4 11 kHz 8 kHz

Note: In a simple test during which a song was played via VoIP for a single user, up bandwidth consumed was 44 kbps when the number of VoIP users was < 4.

Webcam video:

Webcam Video Frame Rate Resolution Quality Bandwidth
(kbps)
Normal Widescreen
Low 4 160×120 214×120 70 200
Medium 4 320×240 427×240 70 300
Standard 8 320×240 427×240 70 300
High 20 640×480 854×480 90 600

Login page doesn’t load post 9.5 upgrade

Issue: After upgrading the existing version of Adobe Connect to 9.5, login page doesn’t load

Environment: Adobe Connect License

Description: When we try to open the login page it just gets refreshed or throws an error below in the screenshot:

Login

In the debug.log file you will see the below error:

[10-28 00:26:41,151] http-80-21 (INFO) [*********************nu6qn:142.150.192.244] GET http://[Domain_URL]/admin?domain=Domain_URL
[10-28 00:26:41,157] http-80-21 (INFO) BaseServlet.keepSessionAlive(), extending session cookie
[10-28 00:26:41,163] http-80-21 (WARN) potential cross-site request forgery (CSRF) attack thwarted (user:test {user-id=878994, cookie=breezbreezkvga2ffczirnu6qn, account-id=7, ip=X.X.X.X}, ip:X.X.X.X, uri:/admin, error:tokenFromCookie is missing, tokenGeneratedFromCookie:null, tokenFromRequest:null)
[10-28 00:26:41,170] http-80-21 (INFO) [*********************nu6qn:142.150.192.244] GET http://[Domain_URL]/
[10-28 00:26:41,178] http-80-21 (INFO) [*********************nu6qn:142.150.192.244] DONE total: 8ms, queries: 2ms, conn: 0ms, xsl: 0
[10-28 00:26:41,184] http-80-21 (INFO) [*********************nu6qn:142.150.192.244] GET http://[Domain_URL]/admin?domain=[Domain_URL]
[10-28 00:26:41,192] http-80-21 (WARN) potential cross-site request forgery (CSRF) attack thwarted (user:test {user-id=878994, cookie=breezbreezkvga2ffczirnu6qn, account-id=7, ip=X.X.X.X}, ip:X.X.X.X, uri:/admin, error:tokenFromCookie is missing, tokenGeneratedFromCookie:null, tokenFromRequest:null)

Solution:

The issue has been identified as a bug in 9.5. The bug number is #4072617. Till the time this bug gets fixed we have a workaround in place.

Replace the web.xml file at C:\Connect\9.5.0\appserv\web\WEB-INF with the one that gets installed with the installer. The file that gets installed with the installer is web.xml.install

Take the backup of web.xml.install file and replace it with the original web.xml file.

Note: If the environment has NTLM/SSO enabled, those settings need to be put again in web.xml file

Large Seminar Sessions need to be scheduled 45 minutes before start of Session

In Adobe Connect 9.5 Seminar sessions need to be scheduled 45 minute(s) prior to the start time of large seminars to allow for implementing > 600 participants (license purchased for Webinar 1000 Managers)

9.5-SeminarSession

Instant sessions created from the large seminar room will only allow < 600 participants

9.5SeminarSessions

Previously with 9.4, the expected number of participants had to be selected in order to distinguish between regular Seminar Sessions (up to 600 Participants) and large Seminar Sessions (> 600 Participants)

Regular Sessions

This option is no longer listed with 9.5 since we now have dedicated webinar servers to accommodate large seminar licenses for both standby mode and scheduled sessions.