We have published a technote regarding the Release Notes for the upcoming 9.0.3 Adobe Connect release.
Please review the technote here:
http://helpx.adobe.com/adobe-connect/release-note/connect-903-release-notes.html
We have published a technote regarding the Release Notes for the upcoming 9.0.3 Adobe Connect release.
Please review the technote here:
http://helpx.adobe.com/adobe-connect/release-note/connect-903-release-notes.html
We have just published a technote regarding Adobe Connect 9 Windows Add-in support for the Chrome browser.
Please review the technote here:
http://helpx.adobe.com/adobe-connect/kb/connect-9-add-in-windows-chrome.html
We have just published a technote regarding known issues to avoid in Adobe Connect 9 when running large Seminars over 600 users.
Please review the technote here:
http://helpx.adobe.com/adobe-connect/kb/issues-avoid-running-large-seminars.html
We have just released a technote outlining our support for Windows 8 with Adobe Connect. Please review the technote here:
http://helpx.adobe.com/adobe-connect/kb/windows-8-support-connect-8.html
PROBLEM -: I have upgraded/installed Connect 9 on my server having timezone set to east of Japan.
When i start the connect services i get the error -:
“The Adobe connect service service on local computed started and then stopped.Some services stop automatically if they are not in use by other services or programs”.
On checking the ConnectProService.log file you have the following error
2012/08/23 09:56:32 | STATUS | wrapper | --> Wrapper Started as Service
2012/08/23 09:56:32 | STATUS | wrapper | Java Service Wrapper Standard Edition 64-bit 3.3.9
2012/08/23 09:56:32 | STATUS | wrapper | Copyright 1999-2009 Tanuki Software, Ltd. All Rights Reserved.
2012/08/23 09:56:32 | STATUS | wrapper | http://wrapper.tanukisoftware.org
2012/08/23 09:56:32 | STATUS | wrapper |
2012/08/23 09:56:32 | ERROR | wrapper | License Error:
2012/08/23 09:56:32 | ERROR | wrapper | The license keys are incorrect.
2012/08/23 09:56:32 | ERROR | wrapper | Please verify that the wrapper.license.* properties match exactly
2012/08/23 09:56:32 | ERROR | wrapper | and that the following property values match those required for the license:
2012/08/23 09:56:32 | ERROR | wrapper | wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperStartStopApp
2012/08/23 09:56:32 | ERROR | wrapper | wrapper.app.parameter.1=org.apache.catalina.startup.Bootstrap
2012/08/23 09:56:32 | ERROR | wrapper |
2012/08/23 09:56:32 | ERROR | wrapper | A license can be obtained from the Java Service Wrapper site:
2012/08/23 09:56:32 | ERROR | wrapper | http://wrapper.tanukisoftware.org/doc/english/purchase.html
2012/08/23 09:56:32 | ERROR | wrapper |
2012/08/23 09:56:32 | ERROR | wrapper | Licenses can be generated for any of the following Host Ids.
2012/08/23 09:56:32 | ERROR | wrapper | The first Host Id is recommended.
2012/08/23 09:56:32 | ERROR | wrapper | Host Ids:
2012/08/23 09:56:32 | ERROR | wrapper | 005056af0080 (#1)
2012/08/23 09:56:32 | ERROR | wrapper | 005056af000b (#2)
2012/08/23 09:56:32 | ERROR | wrapper |
2012/08/23 09:56:32 | ERROR | wrapper | Optional host name for license: Breeze20
2012/08/23 09:56:32 | STATUS | wrapper | <-- Wrapper Stopped
REASON -: This is being caused by the bug within Tanuki Java Service Wrapper that is used with Connect 9 causing the failure of connect services when the server timezone is set to east of Japan.
You can cross check by setting the server timezone to west of Japan, The connect services would start.
SOLUTION -: Applicable only for Connect 9 servers having timezone east of Japan.
1. Download http://wrapper.tanukisoftware.com/download/3.5.15/wrapper-windows-x86-64-3.5.15-st.zip
2. Extract the file wrapper-windows-x86-64-3.5.15-st.zip
3. Locate the wrapper.exe on wrapper-windows-x86-64-3.5.15-st\bin folder
4. Navigate to directory /breeze/9.0.0.1/appserv and rename the file ConnectProSvc.exe to ConnectProSvc.exe.orig
5. Copy the file wrapper.exe from step 3 and paste it to /breeze/9.0.0.1/appserv folder.
6. Rename the file /breeze/9.0.0.1/appserv/wrapper.exe to ConnectProSvc.exe
7. Navigate to /breeze/9.0.0.1/TelephonyService folder and rename TelephonyService.exe to TelephonyService.exe.orig
8. Copy wrapper.exe from step 3 and paste it to /breeze/9.0.0.1/TelephonyService folder.
9. Navigate to /breeze/9.0.0.1/TelephonyService/ folder and rename wrapper.exe to TelephonyService.exe
10. Start Connect and Telephony services
The problem only affects servers with time zones between +10:00 and +11:59 UTC. Therefore, the problem can affect licensed customers in Australia (East coast) and New Zealand.
ISSUE -: I want to purchase/deploy SSL certificates for my connect server.
SOLUTION -: This document is valid for software/hardware SSL configuration with Adobe connect server.
1. Download Openssl from here openssl
2. Follow the steps 2,3 and 4 from kbdoc http://blogs.adobe.com/connectsupport/generating-self-signed-certificates-for-adobe-connect/
3. Open command prompt and execute the command
cd C:\openssl\bin
openssl req -new -nodes -keyout myserver.key -out server.csr -newkey rsa:2048
This creates a two files on C:\openssl\bin
The file myserver.key contains a private key; do not disclose this file to anyone.
The file server.csr is Certificate Signing Request (CSR).
You will now be asked to enter details to be entered into your CSR.
What you are about to enter is what is called a Distinguished Name or a DN.
For some fields there will be a default value, If you enter ‘.’, the field will be left blank.
—–
Country Name (2 letter code) [US]: US
State or Province Name (full name) []: Texas
Locality Name (eg, city) []: Houston
Organization Name (eg, company) []: Your Company
Organizational Unit Name (eg, section) []: Your Department
Common Name (eg, YOUR name) []: my.connect.server.com
Email Address []:
Please enter the following ‘extra’ attributes to be sent with your certificate request
A challenge password []:
An optional company name []:
—–
Use the name of the connect server domain name as Common Name (CN).
The fields optional company name and challenge password can be left blank
Your CSR would now have been created on C:\openssl\bin . Open the server.csr in a text editor and copy and paste the contents into the trusted Certificates Issuing Authority (CIA) ( like verisign , thawte) enrollment form where you are requesting the SSL certificates to be generated.
Once the SSL certificates has been published via CIA you can use it as SSL certificate file along with the key file myserver.key generated on step 3
PROBLEM -: Whenever the connect server is restarted , I cannot open the login page/meeting room stuck on connecting bar.
I have migrated/installed the SSL configuration to stunnel , When i start stunnel service , it prompts for passphrase
SOLUTION -: It looks like the key file has the passphrase and it needs to be removed.
1. Make sure that the S-Tunnel executable has been installed as a windows service and is set to automatic.
You can install the stunnel as windows service as per the steps below
Open command prompt and change the current prompt to stunnel directory as - cd C:\Breeze\x.x.x.x\stunnel
stunnel.exe -install
2. If you have a passphrase on your SSL certificates , Remove it using openssl command
You can download openssl from here openssl
To install openssl , follow the steps 2,3 and 4 from kbdoc http://blogs.adobe.com/connectsupport/generating-self-signed-certificates-for-adobe-connect/
3. Open Command Prompt and execute the command
cd C:\openssl\bin
openssl rsa -in certificate.key.current -out server.key.new
4 . The above command looks for certificate.key ( exsisting SSL key file) , removes the passphrase and generates the new key file server.key.new
5. Copy the server.key.new file , rename it according to the existing key file name convention under stunnel folder.
6. Restart the stunnel service to verify that the key file does not prompts for passphrase.
PROBLEM -: I want to generate self signed certificates for our internal testing purpose. I need to apply SSL certificates on my connect server
SOLUTION :-
Please note that Adobe does not supports self signed certificates on production enviroment.
This is for internal testing purpose.
1. Download OpenSSL , You can download it from here openssl
2.Extract it on C:\
3. Windows 7/vista users might have to gain/allow the administrative rights prompt to extract/copy the files on C:\ , Alternate is to copy the openssl.zip file on any other location , unzip it and copy the extracted openssl folder on C:\
4. Make sure that the openssl.exe is located on C:\openssl\bin folder
5. Open command prompt and execute the command
cd C:\openssl\bin
openssl.exe req -x509 -nodes -days 365 -newkey rsa:2048 -keyout meeting-domain.com.key -out meeting-domain.com.crt
Provide the following information while generating the certificate files
Country Name
State/Province Name
Locality Name
Organization Name
Organization Unit Name
Common Name
EMail Address
I have attached a screenshot for reference , Make sure that you provide the exact domain name of your connect server on common name information as highlighted in screenshot as well as in above step
When the process is completed , This would generate two files on C:\openssl\bin named as -:
meeting-domain.com.crt –> Certificate file.
meeting-domain.com.key –> Key file.
These two files (Certificate and key file) are self signed SSL certificates and can be used to secure either the meeting connection or application server having the domain name my.connect.server.domain.com as per the screenshot or as per the common name provided by you.
You can follow the SSL KB Doc to configure the SSL certificate/key file on your Adobe connect server
PROBLEM -: E-mail sending completely stops and fails with the following lines on debug.log :
[07-24 10:30:36] sche (INFO) Scheduler Sending EmailAs a wokaround to fix the issues you simply log into the server console , go into the section, and click save again to have emails start working again but after somedays the issue resurfaces
SOLUTION -:
1. Check the custom.ini file has the following parameter -:
SMTP_HOST=your-smtp-server-domain
Replace your-smtp-server-domain with the domain name/IP of your smtp server.
2. Add the following additional lines on custom.ini
SMTP_CONN_TIMEOUT=110000
SMTP_IO_TIMEOUT=110000
3. Restart the connect services to apply the changes
PROBLEM -: Meeting users are getting re-connected to the meeting room randomly within a second.
My connect server is hosted on Amazon EC2 cloud on windows 2008 R2 OS.
SOLUTION -:
1. Capture the connect add-in logs generated on the user’s computer joining on the meeting room, To generate addin logs follow the KB Doc http://helpx.adobe.com/adobe-connect/kb/enable-logging-acrobat-connect-professional.html
The connect addin logs would be generated on client/user side , not on the server side.
2. Open the connectaddin log file generated under your documents folder when you expreience reconnects.
3. If you find the lines -:
Player TRACE: StreamHandler::public/all/screenshare_0::NetStream onStatus for stream: public/all/screenshare_0, code: NetStream.Play.InsufficientBW
4. And your server is hosted in the Amazon EC2 cloud and has Win 2008 64 bit OS.
5. The fix for this is to switch onto Win 2003 OS
6. This is a known issue reported by a lot of users having Win 2008 server hosted on Amazon EC2 cloud, on this video streaming issue. You can check the blog at http://forums.adobe.com/thread/572258