Table Of Contents
Troubleshooting the Cisco Unified MeetingPlace Web Conferencing Release 5.3 Installation
Problems with the Cisco Unified MeetingPlace Web Conferencing Installation
What to Do First
Checking the Cisco MCS Operating System Release
Locating the Software Download Page on Cisco.com
Obtaining Additional Assistance
Problems with Cisco Unified MeetingPlace Web Conferencing Server Connections
Resolving HTTP Connection Problems
Resolving HTTPS Connection Problems
Troubleshooting the Cisco Unified MeetingPlace Web Conferencing Release 5.3 Installation
This chapter explains how to troubleshoot common problems that can occur when installing Cisco Unified MeetingPlace Web Conferencing.
Topics in this section include:
•Problems with the Cisco Unified MeetingPlace Web Conferencing Installation
•Problems with Cisco Unified MeetingPlace Web Conferencing Server Connections
Problems with the Cisco Unified MeetingPlace Web Conferencing Installation
Topics in this section include:
•What to Do First
•Checking the Cisco MCS Operating System Release
•Locating the Software Download Page on Cisco.com
•Obtaining Additional Assistance
What to Do First
If the web server is not working properly, try the following troubleshooting steps:
1. Restart the Cisco Unified MeetingPlace Web Conferencing services.
a. From the Windows Start menu, choose Settings > Control Panel > Administrative Tools > Services.
b. Right-click Cisco MeetingPlace Web Conferencing and choose Start.
c. If you stopped any other gateway services, restart them by right-clicking the appropriate service and choosing Start.
d. Close the Services control panel.
2. If the server is still not working properly, reboot the server.
3. If the server is still not working properly, run the Cisco Unified MeetingPlace Web Conferencing installer again in Repair mode.
4. If the server is still not working properly, collect the following installation logs and contact your Cisco support representative. Cisco Unified MeetingPlace Web Conferencing installation logs are in C:\WINNT\.
–mpwebstp.log
–mpwebstp-jvm.log
–mpwebstp-sql.log
–mpwebstp-sqlsp3.log
Checking the Cisco MCS Operating System Release
You must have the Cisco MCS OS installed on a Cisco MCS before attempting to install Cisco Unified MeetingPlace Web Conferencing. To check the release of your Cisco MCS operating system, complete the following.
Before You Begin
To find out what release of the Cisco MCS operating system you are required to have, see the Release Notes for your release of Cisco Unified MeetingPlace Web Conferencing.
Procedure
Step 1 From Start > Settings, choose Control Panel.
Step 2 From the Help menu, choose About Windows and confirm the release of your operating system.
Step 3 Click OK.
Locating the Software Download Page on Cisco.com
Procedure
Step 1 Open your web browser to www.cisco.com and click Log In. Log in by using your Cisco.com user name and password.
Step 2 Click Technical Support > Downloads.
Step 3 From the Software Center page, locate the "Related Tools" section in the lower right. Click Software News.
Step 4 From the Software News page, scroll down to the "New Voice Software now available on Cisco.com" section. Click win-OS-Upgrade-K9 2000-2-6sr1.exe or a later release.
Obtaining Additional Assistance
If there is a problem with a Windows service or the web server loses its connection, go to the drive:\Program Files\Cisco Systems\MPWeb\datasvc directory and run dcdiags.bat as soon as possible to generate a server log. All diagnostic information is stored under \Cisco Systems\MPWeb\Diagnostics.
Zip these files, along with the meeting information, such as the start time, time of connection loss, browser versions and so on, and send them to your Cisco support representative for additional assistance.
Problems with Cisco Unified MeetingPlace Web Conferencing Server Connections
The web server must be able to connect to itself using the hostname you configured on the Web Server administrative page. This is also the hostname end-users use to connect to this web server.
Connection problems are most likely because of firewall-related configurations. Following are steps to troubleshoot and correct the problem.
Topics in this section include:
•Resolving HTTP Connection Problems
•Resolving HTTPS Connection Problems
Resolving HTTP Connection Problems
The following example assumes the web server's hostname as hostname.domain.com.
Procedure
Step 1 From the web server, use a web browser to connect to http://hostname.domain.com.
Step 2 If you receive an error message, add the following line to the C:\WINNT\System32\drivers\etc\hosts file:
127.0.0.1 hostname.domain.com
Remember to replace your web server's actual FQDN for hostname.domain.com.
Step 3 Try to connect to http://hostname.domain.com again.
Resolving HTTPS Connection Problems
Complete the following steps if the web server only allows HTTPS traffic. The following example assumes the web server's hostname as hostname.domain.com.
Procedure
Step 1 From the web server, use a web browser to connect to https://hostname.domain.com.
Step 2 If any security warning dialog boxes appear, configure SSL to not show these dialog boxes. For detailed information, see Microsoft Knowledge Base Articles 813618 and 257873 on the Microsoft website.