gamename
Enthusiast
Enthusiast

Eh? Move-VM Generates Error Messages, But Works Anyway!?!?

Jump to solution

Anyone seen this?

>  move-vm devdocs -datastore TCStore

move-vm : 7/22/2013 11:23:37    Move-VM        Operation is not valid due to the current state of the object.

At line:1 char:2

+  move-vm devdocs -datastore TCStore

+  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Move-VM], VimException

    + FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VimAutomation.ViCore.Cmdlets.Commands.MoveVM

Here is my version:


> Get-PowerCLIVersion

PowerCLI Version

----------------

   VMware vSphere PowerCLI 5.1 Release 2 build 1012425

---------------

Snapin Versions

---------------

   VMWare AutoDeploy PowerCLI Component 5.1 build 768137

   VMWare ImageBuilder PowerCLI Component 5.1 build 768137

   VMware vCloud Director PowerCLI Component 5.1 build 1012427

   VMware License PowerCLI Component 5.1 build 669840

   VMware VDS PowerCLI Component 5.1 build 1012428

   VMware vSphere PowerCLI Component 5.1 build 1012428

1 Solution

Accepted Solutions
LucD
Leadership
Leadership

I have seen this before, but not sure if yours is the same.

Is the VM powered on ? No, power it off.

Unregister and then register the VM.

Then try the svMotion again.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

View solution in original post

0 Kudos
3 Replies
RvdNieuwendijk
Leadership
Leadership

Is maybe the datastore in "Maintenance Mode"?

Blog: https://rvdnieuwendijk.com/ | Twitter: @rvdnieuwendijk | Author of: https://www.packtpub.com/virtualization-and-cloud/learning-powercli-second-edition
0 Kudos
LucD
Leadership
Leadership

I have seen this before, but not sure if yours is the same.

Is the VM powered on ? No, power it off.

Unregister and then register the VM.

Then try the svMotion again.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

View solution in original post

0 Kudos
johndavidd
Enthusiast
Enthusiast

I found that closing the current powershell session and opening a new one seems to resolve the issue. Running version 6.0.