Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

'Vmware Tools driver is not initialized on source vCSA' 'Missing guest.guestFamily property' error while upgrading VCSA 6.0/6.5 to 6.7 (59157)

Last Updated: 2/18/2020Categories: TroubleshootingTotal Views: 11356Language:
Chinese (Simplified)JapaneseEnglish

6 like this article

Subscribe to get an email
newsletter with new updates

6 people found this helpful Please provide article feedback:

Symptoms

'When attempting to perform an upgrade of a vCenter Server Appliance 6.0 to 6.5 or 6.7 the operation fails with below error

VMware Tools driver is not initialized. Make sure that VMware Tools driver is initialized and is running properly on the source vCenter Server Appliance (Sample_FQDN). Also make sure that the ESXi host which contains the source vCenter Server Appliance is not under heavy load. Contact VMware support in case the issue cannot be resolved.

In the upgrade-requirements.log file you see the entries similar to the following:

2018-09-06T16:54:24.389Z ERROR transport.guestops GuestOpsOperationManager is not initialized. Missing guest.guestFamily property
2018-09-06T16:54:24.389Z ERROR upgrade_commands Vmware Tools driver is not initialized on source vCSA (sample_FQDN), Error: GuestOpsOperationManager is not initialized. Missing guest.guestFamily property
2018-09-06T16:54:24.390Z ERROR root Could not create command factory.
2018-09-06T16:54:24.391Z ERROR __main__ ERROR: Fatal error during upgrade REQUIREMENTS. For more details take a look at: /var/log/vmware/upgrade/requirements-upgrade-runner.log
2018-09-06T16:54:24.394Z INFO root Exiting with exit-code 1

If you open an SSH session to the ESXi Host running the vCSA VM, and run vim-cmd vmsvc/get.guest xx | grep guest, where 'xx' is the VM_ID of the vCSA, you will see entries similar to the below output

[root@esxi01:~] vim-cmd vmsvc/get.guest 10 | grep guest
toolsVersionStatus = "guestToolsUnmanaged",
toolsVersionStatus2 = "guestToolsUnmanaged",
toolsRunningStatus = "guestToolsRunning",
guestId = <unset>,
guestFamily = <unset>,
guestFullName = "",
guestState = "running",
guestKernelCrashed = <unset>,
guestOperationsReady = true,
guestStateChangeSupported = true,

Cause

This issue is caused when the '/etc/SuSE-release' file is either missing or corrupt on the source vCenter Server Appliance.

Resolution

To resolve this issue follow the steps below:

Create or recreate the /etc/SuSE-release file with the below content using a text editor

PATCHLEVEL = 3
VERSION = 11
SUSE Linux Enterprise Server 11 (x86_64)

Backup if the file is already available : mv /etc/SuSE-release /etc/SuSE-release-bkp)

Open text edit : vi /etc/SuSE-release

Press the Insert key

Paste the content above

Press Esc key

Save the file using :wq!

Reboot the source vCenter Server Appliance

Retry the Upgrade again.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server Appliance 6.5.x

VMware vCenter Server Appliance 6.0.x

Take Our Survey

Support Assistant