Are you getting the error "Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Status 200"? I thought I bloged about this last month but apparently not. Upon upgrading to IE8 on my Windows XP Pro dev box I could not get any of my flex apps with AMF services to work. It appears as though not everyone hits this wall, even in my own test, it works from Windows 7 but not from XP.

The Adobe Bug entry for this has picked back up speed thanks to some votes and new supporting comments. I'm really suprised this has not gotten more attention, but maybe for some reason this isn't as wide spread as it could be. Or it's just that IE8 addoption is that low?

http://bugs.adobe.com/jira/browse/SDK-21005

If your available to go to Flash Camp Atlanta next week [8/28/09] there are still some tickets available. Not only should the line up result in a great one day conference but I'm sure some of the attendees will make for some good networking.

• Greg Wilson, Adobe - Keynote
• David Tucker, Universal Mind - ORM for the AIR Developer
  
• Jesse Warden - Custom Components in Flex 3 & 4
  
• Carl Smith, nGenWorks - It's a Matter of Trust
  
• Leif Wells, Roundbox Global
• Doug Knudsen, Universal Mind - Data Retrieval with the Flex Framework
  
• Ben Stucki - The Art and Science of Rich Internet Applications
  
• Christian Saylor, Universal Mind - Whistle, Wink, Kiss...The Art and Science of Falling in Love

I usualy don't do this, but if someone is looking for a room-mate for Atlanta at the Omni CNN I would be interested. I'm not wasting an astounding 60,000 Marriott points for 2 nights at a low end Marriott Residence Inn... I'll be there Thu & Fri night since I'm flying in. Send me an email if interested: russ at EmpireGP dot com.

Maybe not all of us are in positions to learn from these "The Press Releases of the Damned" but Technologizer has a great list of 7 top blunders that are all fairly recent. They cover the gamet from how Vista will change our world to the Time Warner/AOL debocle.

The Press Releases of the Damned!

I've recently been bumping into an annoying Connect bug/interface issue that has been causing me headaches. If you are administering a Connect server with a large audience this might be of interest.

My growing issue has been recordings with no sound. At first the easy blame was on the users. However after some review, it turns out that there is a flow issue with the Adobe Connect interface that I can easily reproduce in 2 ways.

1. If the meeting you are entering is locked you will be presented with a notification in the top right. If you attempt to press the hands-free button while this notification is present the hands free will appear locked. However you will not be presented with the “Camera and Microphone Access” dialogue and audio capture will not work (despite indication). 
2. If you select the hands-free button before the Share window has been completely rendered and resized you will get the same results as #1.
   

I'm guessing that this is not a major work flow issue for many. However as Connect becomes more familiar to our users, they are executing setup at a faster rate.

We have adjusted documentation to reflect this issue and warn our Hosts to make sure that they are asked for permission to use the microphone; if they are not, they are directed to unselect and reclick the hands-free lock button. I'll also be contacting Adobe with this little tid-bit through support while we try to work out a playback stability issue as well...