Cisco Cisco MeetingPlace Gateway SIM Anleitung Für Quick Setup

A Web Server fails during a web conference and all users are temporarily disconnected from 

the web-conferencing portion of their meeting. 

There was an Agent Service problem. Other Web Servers in the cluster detected that 

a server was down and began to exclude it from the load balancing cluster.

Tell users to rejoin their web conference by clicking the click-to-attend link in their meeting 

notification or by accessing the Current Meeting page from the Web. The meeting console client 
automatically tries to reconnect the user to the server. If this attempt fails, the meeting console attempts 
to connect to the server designated as the backup for that meeting. If no connection is made after 
15 seconds, the client continues attempting to contact the primary, then the backup server. After 30 
unsuccessful attempts, the client stops trying and notifies the user that it is unable to reconnect.

There was a server components problem. Other Web Servers in the cluster were 

unable to detect that a server was disabled since its Agent Service was fully functional. As a result, 
the failed Web Server was not excluded from the load balancing cluster and continued to have users 
routed to it in error.

In the Windows Services control panel, restart the Cisco Unified MeetingPlace 

Web Conferencing Service. This should restore web-conferencing functionality.

When you restart the Web Server, all manual changes made to the registry are lost. 

All Web Servers in a load balancing cluster are nonfunctional.

The SQL Server database is on a failed server.

Restore the database. Users are unable to conduct web conferences until the database is 

restored.

External users are disconnected from a web conference.

The Web Server in the DMZ has failed.

Configure another server as your external Web Server. Users are unable to conduct external 

meetings until you complete this step. To configure an external Web Server, see 

 in the 

 module.