#1 2009-04-09 10:51:20

**_bb0875_**

Meetings fail to launch through Connect Add-in

We recently noticed that our meetings will not launch through the Adobe Connect Add-in but launch just fine when the Add-in isn't installed.

We are running Adobe Connect 7 SP2 on-site with the meeting and app server on the same machine and are using SSL with both.

Nothing in the logs jumps out at me as indicating what the problem is.

Any one run into a similar problem?

Thanks!

**_santhony_**

Re: Meetings fail to launch through Connect Add-in

Have you enabled the addin debug feature for the Connect Add-In ? That may give you extra information aside from the server logs as to what is happening.

Check the windows event viewer to see if there is an error listed when you attempt to launch meetings with the connect Add-In.

**_batkobiker_**

Re: Meetings fail to launch through Connect Add-in

might be an issue with virtual hosts on SSL server in front of AC
or misconfigured certificate on SSL

-flash will allways ask for c-name and not the domain-option in the certificate
-flash will allways send the get / and not the whole url this causes the timeout if connection is done within flash
-SSL handshake is done before http handshake (that is why vhosts not work gut)

try this:
use self signed certificates and read carefully the noticements, be carefull on the name of the cert when you try to connect

hope this helped

**_bb0875_**

Re: Meetings fail to launch through Connect Add-in

Thanks for the tips.

It does appear to be an SSL issue.

I get the following error when I evoke a meeting room for the first time:

Event Type:    Warning
Event Source:    FMS (Edge)
Event Category:    (269)
Event ID:    1192
Date:        4/10/2009
Time:        3:22:07 PM
User:        N/A
Computer:    CONNECT
Description:
Invalid value set for configuration key : Application/Process/Distribute = Instances, using default to be compatible with inst..

We did have an issue getting SSL to work at first and fixed the problem by leaving off the Meeting server IP from Adaptor.xml and using "localhost" instead; but I guess it wasn't a good enough fix...