6.7

Table Of Contents
n
For export details, review the %TEMP%\..\vcsUpgrade\vcdb_export.out file.
The vcdb_export.err file contains errors that were identified during the export phase of the upgrade.
n
For import details, review the ProgramData\Vmware\CIS\logs\vmware\vpx\vcdb_import.out
file.
The vcdb_import.err file contains errors that were identified during the import phase of the upgrade
process.
n
For in-place upgrade log details, review the
ProgramData\Vmware\CIS\logs\vmware\vpx\vcdb_inplace.out file.
The vcdb_inplace.err file contains in-place upgrade errors.
What to do next
Examine the vcdb_inplace.* log files.
Errors and Warnings Returned by the Installation and
Upgrade Precheck Script
The installation and upgrade precheck script runs tests to identify problems on the host machine that can
cause an installation, upgrade, or migration to fail.
For interactive installations, upgrades, and migrations, the errors or warnings are displayed on the final
panel of the installer, where you are asked to confirm or cancel the installation or upgrade. For scripted
installations, upgrades, or migrations, the errors or warnings are written to the installation log file.
vSphere Update Manager provides custom messages for these errors or warnings. To see the original
errors and warnings returned by the precheck script during an Update Manager host upgrade scan,
review the Update Manager log file vmware-vum-server-log4cpp.log.
Table 81. Error and Warning Codes That Are Returned by the Installation and Upgrade
Precheck Script
Error or Warning Description
64BIT_LONGMODESTATUS The host processor must be 64-bit.
COS_NETWORKING Warning. An IPv4 address was found on an enabled service
console virtual NIC that has no corresponding address in the
same subnet in the vmkernel. A separate warning appears for
each such occurrence.
CPU_CORES The host must have at least two cores.
vCenter Server Upgrade
VMware, Inc. 225