Connect V7 various problems and solutions.
Wed, 08/27/2008 - 1:24pm — aml
We had several weird problems with Connect ever since we switched to version 7 last month. It is too early to say with any certainty, because of the sporadic nature of the problems, but we think Adobe has given us solutions that work.
Our first problem was that the web interface was extremely slow when a user would access it via a web browser. A simple fix of reindexing the SQL table did the trick and everything is lightning fast again.
The second problem was not such an easy spot. It started with some people not being able to open up meetings in Connect. At first random, then no one was able to. Also another symptom of this problem was that sometimes the html would not parse the whole way on the web ui and you would get a half populated page with a little bit of code at the end....weird....but after you refreshed it was fine. We also had problems with pods acting funky...sometimes the sharepod would not completely load a ppt or a shared image, but sometimes it would.
The first solution was to clear the browsing history (cache) on the local client browser and that seemed to fix some things, but then these problems came right back. After talking to an engineer at Adobe they found that we had 32 GB of orphaned files in our Connect implementation. This along with the clustering we do really messed things up good. Their second solution was to get rid of the orphaned files. To do that on a two node cluster you need to first make backups of the content directories. The then stop the adobe services on both servers, delete the content directory on one server, then restart the services on both service. The Adobe service will then use the database to populate the server's content directory with the proper meeting files. After that server is sync'd up, you delete the content directory on the other one and do the same thing. After we did that we now have 0 GB of orphaned files and we have not yet seen any of the problems we were having recently. *crossing fingers* hope we don't!
We did these changes this past weekend and it is Wednesday and still not problems....we are hopeful!
If anyone would like any further information on this or anything else please feel free to email me at aml@psu.edu
Andy