Skip to main content
Participant
April 13, 2013
Question

Unable to restart the meeting.

  • April 13, 2013
  • 3 replies
  • 1295 views

I’m running Connect 8.0 on Windows Server 2008 R2

Connect Add-in 9.4.63.0

Flash Player 11.6.602.180

Until today everything has worked fine. Now on a couple of my meeting rooms I get the following error: “Unable to restart the meeting. Please close this window and launch the meeting again in your browser.”

I’ve tried the usual deleting IE temp files and cookies. I’ve rebooted the server and verified nothing has been installed recently on the server. This error occurs for all users.

I’ve looked in the log files on the server and don’t see anything out of the ordinary. I'm logging in with a domain account that has host rights for all the rooms, I've also tried logging in with a local server account.

Any ideas? 

This topic has been closed for replies.

3 replies

Participant
December 19, 2013

I had the same error, just did a maintenance task in SQL server to rebuild the indexes.  Ran it, took about 1 min to run and problem was gone.

Adobe Employee
April 15, 2013

Does this happen on all rooms?

Try launching the room in this manner:

http://myconnectserver.com/mymeetingname?launcher=false&mode=xml

Replace myconnectserver.com with your Connect server URL and "mymeetingname" with the name of your meeting room. After hitting enter you will be brought to your meeting room in the browser; underneath the room there should be a large white window which will post details of the room, including (most likely) more details on the reason why the room does not launch.

Now, if the reason for the room launch is exclusively FMS related there may be no error here, but I'd be willing to bet something will come up. Also, definitely reach out to Platinum Support on this one.

Jorma_at_Knox
Legend
April 15, 2013

Great tip Lauren. I'll be sure to add the 'mode=xml' to my list of tools!

Adobe Employee
April 15, 2013

It's very useful. Generally, if an error is displayed there it will also be in debug, but it's a lot easier to identify the error there than combing through debug logs. It's also useful if you don't host the server yourself and the debug log is not immediately available to you.

Happy to help!

Jorma_at_Knox
Legend
April 13, 2013

You will want to look at the error log to see what is coming up there.

You may also want to reach out to Platinum Support to see if they can assist further.

While I'd have to explore this error more, it seems like maybe there is something not working correctly with the FMS instance installed with Connect. Have you restarted that, or restarted the Connect server as a whole to see if that solves the problem?