Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Cross vCenter vMotion of a VM from vSphere 6.0U3 to vSphere 6.5U2 through PowerCLI fails with "A general system error occurred: Not initialized" (67273)

Last Updated: 8/7/2020Categories: TroubleshootingTotal Views: 4922Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Unable to cross vCenter vMotion from vCenter 6.0U3 to vCenter 6.5U2 through PowerCLI
Getting errors similar to:

PowerCLI C:\> Move-VM -VM $vm -Destination $destination -NetworkAdapter $networkAdapter -PortGroup $destinationPortGroup -Datastore $destinationDatastore
Move-VM : 21/02/2019 16:57:08   Move-VM         The operation for the entity "VM" failed with the following message: "A general system error occurred: Not initialized"
At line:1 char:1
+ Move-VM -VM $vm -Destination $destination -NetworkAdapter $networkAda ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [Move-VM], SystemError
+ FullyQualifiedErrorId : Client20_TaskServiceImpl_CheckServerSideTaskUpdates_OperationFailed,VMware.VimAutomation.ViCore.Cmdlets.Commands.MoveVM

Move-VM : 21/02/2019 16:57:08   Move-VM         21/02/2019 16:57:08     Move-VM         The operation for the entity "VM" failed with the following message: "A general system error occurred: Not initialized"
At line:1 char:1
+ Move-VM -VM $vm -Destination $destination -NetworkAdapter $networkAda ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [Move-VM], SystemError
+ FullyQualifiedErrorId : Client20_TaskServiceImpl_CheckServerSideTaskUpdates_OperationFailed,VMware.VimAutomation.ViCore.Cmdlets.Commands.MoveVM

Purpose

Enable a VM to be cross vCenter vMotioned from a 6.0 vCenter to 6.5 using PowerCLI

Cause

This is caused by different versions of TLS running on the different vCenters. In the example above the destination vCenter did not have TLS 1.0 enabled.

Impact / Risks

Security impact if enabling lower TLS versions.

Resolution

Enable the same TLS versions on the destination vCenter as is enabled on the source vCenter as per https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.security.doc/GUID-82028A21-8AB5-4E2E-90B8-A01D1FAD77B1.html.

Related Information

See also - Managing TLS protocol configuration for vSphere 6.0 Update 3 https://kb.vmware.com/s/article/2148819

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Workspace ONE Intelligence 2020/08/05 リリースのお知らせ (80240)

KB
•
Windows 2008 R2 磁盘卷变为只读并且引导失败 (2001611)

KB
•
在 VMware Fusion 中安装 OS X 10.9 Mavericks 作为客户机操作系统 (2056603)

Results 1-3 of 3

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.0.x

Take Our Survey

Support Assistant