Cisco Cisco Unified MeetingPlace Web Conferencing
Release Note, Cisco MeetingPlace Web 3.0 (Release 4.2.7.106)
Page 34 of 39
OL-6038-01 Cisco Systems, Inc.
Revision Date: 5/17/04
13.2 Notable issues:
CR17421 - Upgrade to 4.2.7 produces Database Schema Error
Workaround:
Workaround:
see Field Alert - Upgrade to MPWeb 4.2.7 failed due to Database schema version could not be read.doc
CR18371 - Error extracting support files: The parameter is incorrect
Workaround:
Workaround:
See Field Alert -
Upgrade MPWeb to 4.2.7 fails with “Error extracting support files: The parameter is
incorrect” during reboot
CR18374 - Connect to http://locahost. Error message "Error connecting to database"
Solution: Open Administrator Tools > ODBC > System DSN > select MPWeb and click Configure
button > click Next > change “NT Authentication” to “SQL Authentication”
Solution: Open Administrator Tools > ODBC > System DSN > select MPWeb and click Configure
button > click Next > change “NT Authentication” to “SQL Authentication”
CR16118 - InstallShield error when installing MeetingPlace Web
Due to an InstallShield problem, the MeetingPlace Web installation fails when the MeetingPlace Web
files are being unpacked.
Workaround: To fix this (according to an InstallShield knowledge base article), delete the c:\program
files\common files\installshield\engine directory. The MeetingPlace Web installation should work
successfully on the next attempt.
Due to an InstallShield problem, the MeetingPlace Web installation fails when the MeetingPlace Web
files are being unpacked.
Workaround: To fix this (according to an InstallShield knowledge base article), delete the c:\program
files\common files\installshield\engine directory. The MeetingPlace Web installation should work
successfully on the next attempt.
CR16117, CR15922 - MeetingPlace for Outlook on the internal MeetingPlace Web server
may cause incorrect registry values (C-architecture only)
On a networked MeetingPlace system, if MeetingPlace for Outlook is installed on the same machine as
the MeetingPlace Web internal server, then web conference will not work for some meetings, depending
on which MeetingPlace server the meeting is scheduled on. Users click Join Web Conference button and
see "If you are having difficulty connecting to Data Conference, please click here". The "here" link takes
them nowhere. The WebShare window will refresh about once every 20 seconds. The correct registry
value should be:
DataConfSlaveNumber = 0
DataConfSlaveIPAddr = blank
DataConfSlaveIPAddr0 = blank
To change these values, locate the file dcconfig.exe and double click it.
may cause incorrect registry values (C-architecture only)
On a networked MeetingPlace system, if MeetingPlace for Outlook is installed on the same machine as
the MeetingPlace Web internal server, then web conference will not work for some meetings, depending
on which MeetingPlace server the meeting is scheduled on. Users click Join Web Conference button and
see "If you are having difficulty connecting to Data Conference, please click here". The "here" link takes
them nowhere. The WebShare window will refresh about once every 20 seconds. The correct registry
value should be:
DataConfSlaveNumber = 0
DataConfSlaveIPAddr = blank
DataConfSlaveIPAddr0 = blank
To change these values, locate the file dcconfig.exe and double click it.
1. Change Step 2 input box to zero (the number 0)
2. Clear any entries in the input fields under Step 3
2. Clear any entries in the input fields under Step 3
This incompatibility issue will be fixed in MeetingPlace for Outlook 4.2.7 (not yet available)
Cannot join DC on Public Meetings for internal users in split-DNS DMZ deployment
DC Load Balancing introduced a new tag called DataConfServer. In split-DNS DMZ deployment –
meaning that the same URL, such as meetingplace.xyz.com, is being resolved by internal DNS to the IP
address of the internal MPWeb and by external DNS to the IP address of the external (DMZ) MPWeb –
this tag should return a blank value when internal users attempts to join a public meeting data conference.
However, that does not happen so internal users cannot join data conference if meeting is public. Please
contact MeetingPlace Customization Services for assistance.
DC Load Balancing introduced a new tag called DataConfServer. In split-DNS DMZ deployment –
meaning that the same URL, such as meetingplace.xyz.com, is being resolved by internal DNS to the IP
address of the internal MPWeb and by external DNS to the IP address of the external (DMZ) MPWeb –
this tag should return a blank value when internal users attempts to join a public meeting data conference.
However, that does not happen so internal users cannot join data conference if meeting is public. Please
contact MeetingPlace Customization Services for assistance.