Cisco Cisco Unified MeetingPlace Web Conferencing Guia De Resolução De Problemas
1) Check system files consistency
0) Exit
Select:
In the example above, the installer has detected Cisco MeetingPlace Web installed in folder
C:\Latitude\MPWEB. The main version is 4.2.7.106 and the current patch level is 3. The Patch
Installation Package used here contains all patches up to level 20.
Select 1 and hit Enter to start the installation consistency check.
C:\Latitude\MPWEB. The main version is 4.2.7.106 and the current patch level is 3. The Patch
Installation Package used here contains all patches up to level 20.
Select 1 and hit Enter to start the installation consistency check.
The installer verifies every file in your installation and outputs a message for each file that does not
correspond to the official version stored in the master file list.
correspond to the official version stored in the master file list.
If the installer detects an inconsistency, it displays one of the following messages:
<file_name> is missing.
The <file_name> file is not present in your Cisco MeetingPlace Web installation. Certain
files are not installed depending on the installation options you chose. For example, "audio
service" related files are not installed if you chose basic installation, or files in the Templates
folder are not installed on an external server in a DMZ−C configuration. The list of missing
files can be reviewed to ensure that your installation is not corrupted.
files are not installed depending on the installation options you chose. For example, "audio
service" related files are not installed if you chose basic installation, or files in the Templates
folder are not installed on an external server in a DMZ−C configuration. The list of missing
files can be reviewed to ensure that your installation is not corrupted.
♦
<file_name> is at patch level <x> (instead of <y>).
The patch level for the file <file_name> is not the one that was expected. This can indicate an
inconsistent patch installation on your system. Note that the first time you run the installer, it
is not known what patch level is installed and it is assumed patch level 0 (no patches
installed). If a patch level has been installed before, you will receive numerous
"
inconsistent patch installation on your system. Note that the first time you run the installer, it
is not known what patch level is installed and it is assumed patch level 0 (no patches
installed). If a patch level has been installed before, you will receive numerous
"
<file_name> is at patch level X (instead of 0)
" messages. This is
normal.
♦
<file_name> is customized.
The <file_name> file content does not match the content of the original file and its timestamp
value is higher than one of the original files. The installer therefore assumes this file has been
customized.
value is higher than one of the original files. The installer therefore assumes this file has been
customized.
♦
<file_name> is customized (overwritten by file <other_file_name>).
The <file_name> file content does not match the content of the original file but corresponds
to another file that is part of the Cisco MeetingPlace Web distribution. The installer therefore
assumes that this file has been customized by replacement with another file (typical context:
templates for internal / external servers in DMZ configurations, mpagent.exe and
mpagentext.exe − the secure version of mpagent.exe for external sites in the DataSvc
folder, and so forth).
to another file that is part of the Cisco MeetingPlace Web distribution. The installer therefore
assumes that this file has been customized by replacement with another file (typical context:
templates for internal / external servers in DMZ configurations, mpagent.exe and
mpagentext.exe − the secure version of mpagent.exe for external sites in the DataSvc
folder, and so forth).
♦
<file_name> is customized with incorrect timestamp (<= <ts_value>). Possible version
mismatch.
mismatch.
The <file_name> file is detected as a customized file but its timestamp value is too low and
indicates a possible version mismatch. This occurs when the Cisco MeetingPlace Web
installation is supposed to be at patch level <x> and the customized file timestamp is lower
than the timestamp (<ts_value>) of the original file that is compatible with patch level <x>.
indicates a possible version mismatch. This occurs when the Cisco MeetingPlace Web
installation is supposed to be at patch level <x> and the customized file timestamp is lower
than the timestamp (<ts_value>) of the original file that is compatible with patch level <x>.
♦
<file_name> is based on patch level <x> or below.
This is an extension of the previous message that gives more details about the possible
version mismatch. Based on its incorrect timestamp, it appears that <file_name> has been
version mismatch. Based on its incorrect timestamp, it appears that <file_name> has been
♦
6.