1 2 Previous Next 21 Replies Latest reply on Nov 18, 2019 1:30 AM by genericUserName232

    PowerCLI Guest OS Cmdlets Error - The 'propSet' paramter should not be null.

    genericUserName232 Novice

      Hey,

       

      I am using the PowerCLI cmdlets for VM management, they all seem to work fine except for the cmdlets regarding interaction with the guest OS on my VMs.

       

      Calling the Invoke-VMScript successfully executes a Script on a VM, but returns the following Error Message in Powershell:

      InvokeScriptError.PNG

      Calling Copy-VMGuestFile returns the same Error, however i can not transfer files from the VM to my system. The full Error is:

      FullyQualifiedErrorId : Client20_VmGuestServiceImpl_DownloadFileFromGuest_DownloadError,VMware.VimAutomation.ViCore.Cmdlets.Commands.InvokeVmScript

       

      The Server hosting the VMs is in a different network than my system executing the PowerCLI cmdlets, and it seems to me that outgoing requests from the VMs Guest OS to my system are blocked, while i can send and execute requests to/on the VMs. I can not connect to the server from the Guest OS in a VM.

       

      What causes the Error "The 'propSet' paramter should not be null." ?

      Do i have to open any ports regarding the VMs?

       

      Thank you for your help.

        • 1. Re: PowerCLI Guest OS Cmdlets Error - The 'propSet' paramter should not be null.
          Gidrakos Hot Shot

          Have you checked this thread here? Copy-VMGuestFile - The 'propSet' paramter should not be null. Error

           

          It seems it can be caused by either a blocked port or an improper/broken installation.

          • 4. Re: PowerCLI Guest OS Cmdlets Error - The 'propSet' paramter should not be null.
            genericUserName232 Novice

            Thank you for the answer. I checked it out before, and it seems like the same problem. However their workaround using the VMWare-PowerCLI shell directly does not work for me, and there is no direct answer to their problem. How can i find out which ports i have to open? There are none mentioned in the documentation for Invoke-VMScript using vCenter Server/ESXi 5.0 and later.

            • 6. Re: PowerCLI Guest OS Cmdlets Error - The 'propSet' paramter should not be null.
              LucD Guru
              User ModeratorsvExpertCommunity Warriors

              Can you do a

               

              Get-Module -Name VMware* -ListAvailable

               

              • 7. Re: PowerCLI Guest OS Cmdlets Error - The 'propSet' paramter should not be null.
                genericUserName232 Novice

                Result for Get-Module -Name VMware* -ListAvailable

                 

                Capture.PNG

                • 8. Re: PowerCLI Guest OS Cmdlets Error - The 'propSet' paramter should not be null.
                  LucD Guru
                  Community WarriorsUser ModeratorsvExpert

                  That doesn't look right.
                  You seem to have a mix of an older version (probably installed with an .EXE or an .MSI) and a newer version (installed from the PowerShell Gallery).

                   

                  The best solution now would be to uninstall everything, including the entry that should still be there under Programs and Features in the Control Panel.

                  Once you uninstalled that, manually delete all remaining PowerCLI folder (see the list you created in your previous reply).
                  Then, to make sure we start from a clean situation, reboot your station (some files in use might only get removed during a reboot).

                   

                  Once done, install again with the Install-Module cmdlet.
                  When you then do a Get-Module, you should only see the modules listed in the 1st part of the output in your screenshot.

                   

                  You can find more info on this process in Welcome PowerCLI to the PowerShell Gallery – Install Process Updates

                  • 9. Re: PowerCLI Guest OS Cmdlets Error - The 'propSet' paramter should not be null.
                    genericUserName232 Novice

                    Hey, thank you for your reply. I uninstalled everything and installed PowerCLI from your shared link, sadly Invoke-VMScript still returns the same error,

                    i think it might be due to some firewall issues or closed ports, since the VMs are hosted in a different network than i am in.

                     

                    Get-Module -Name VMware* -ListAvailable returns now:

                    Capture.PNG

                    • 10. Re: PowerCLI Guest OS Cmdlets Error - The 'propSet' paramter should not be null.
                      LucD Guru
                      Community WarriorsvExpertUser Moderators

                      Did you already try adding the Verbose switch on the Invoke-VMScript cmdlet?


                      Also, can you check the vmware.log file of the VM you are trying to reach?
                      There might be some further clues in there.

                      • 11. Re: PowerCLI Guest OS Cmdlets Error - The 'propSet' paramter should not be null.
                        genericUserName232 Novice

                        Thank you for your reply.

                         

                        -Verbose tells me that Invoke-VMScript finished execution, no error messages.

                         

                        I checked the logs, didnt find anything related to propSet, but i dont really know what i am looking for there..

                        • 12. Re: PowerCLI Guest OS Cmdlets Error - The 'propSet' paramter should not be null.
                          LucD Guru
                          vExpertCommunity WarriorsUser Moderators

                          The vmware.log should tell you that the interaction with the VMware Tools was started, and if it completed.

                          Feel free to attach an extract from the time interval where you launched the cmdlet.

                          • 13. Re: PowerCLI Guest OS Cmdlets Error - The 'propSet' paramter should not be null.
                            genericUserName232 Novice

                            hey, this is the entire log from yesterday, i used Invoke-VMScript a cpl of times, I guess thats where the GuestOps.* come from?

                             

                            2019-11-11T08:54:00.631Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

                            2019-11-11T09:16:33.909Z| mks| I125: SOCKET 377 (141) Creating VNC remote connection.

                            2019-11-11T09:16:33.910Z| mks| I125: MKSControlMgr: New VNC connection 1

                            2019-11-11T09:16:33.971Z| mks| W115: VNCENCODE 377 failed to allocate VNCBlitDetect

                            2019-11-11T09:16:33.972Z| mks| I125: VNCENCODE 377 VNCEncodeChooseRegionEncoder: region encoder adaptive. Resolution: 1810 x 864

                            2019-11-11T09:16:33.974Z| mks| W115: couldn't find space for 512x2048 frame 10 alloc 0 max 5148672

                            2019-11-11T09:16:34.291Z| vmx| I125: Tools_SetGuestResolution: Sending rpcMsg = Resolution_Set 1920 1005

                            2019-11-11T09:16:34.430Z| vcpu-1| I125: Guest: DXUM_devapi: 2019-11-11T10:16:34.0422| Thread ID: 2656 |Application requested vm3ddevapi version 2

                            2019-11-11T09:16:34.484Z| mks| I125: VNCENCODE 377 encoding desktop size: (1920x1005x24depth,32bpp)

                            2019-11-11T09:16:34.598Z| mks| W115: VNCENCODE 377 failed to allocate VNCBlitDetect

                            2019-11-11T09:16:34.598Z| mks| I125: VNCENCODE 377 VNCEncodeChooseRegionEncoder: region encoder adaptive. Resolution: 1920 x 1005

                            2019-11-11T09:17:06.816Z| mks| I125: SOCKET 377 (141) recv error 0: Success

                            2019-11-11T09:17:06.816Z| mks| I125: SOCKET 377 (141) VNC Remote Disconnect.

                            2019-11-11T09:17:06.816Z| mks| I125: MKSControlMgr: Remove VNC connection 1

                            2019-11-11T09:38:24.034Z| vcpu-3| I125: CDROM: Emulate GET CONFIGURATION RT 0 starting feature 0

                            2019-11-11T09:46:48.413Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

                            2019-11-11T09:47:37.794Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

                            2019-11-11T09:51:19.999Z| mks| I125: SOCKET 378 (141) Creating VNC remote connection.

                            2019-11-11T09:51:20.000Z| mks| I125: MKSControlMgr: New VNC connection 2

                            2019-11-11T09:51:20.083Z| mks| W115: VNCENCODE 378 failed to allocate VNCBlitDetect

                            2019-11-11T09:51:20.084Z| mks| I125: VNCENCODE 378 VNCEncodeChooseRegionEncoder: region encoder adaptive. Resolution: 1920 x 1005

                            2019-11-11T09:51:20.403Z| vmx| I125: Tools_SetGuestResolution: Sending rpcMsg = Resolution_Set 1810 864

                            2019-11-11T09:51:20.517Z| vcpu-3| I125: Guest: DXUM_devapi: 2019-11-11T10:51:20.0498| Thread ID: 5824 |Application requested vm3ddevapi version 2

                            2019-11-11T09:51:20.665Z| mks| I125: VNCENCODE 378 encoding desktop size: (1810x864x24depth,32bpp)

                            2019-11-11T09:51:20.790Z| mks| W115: VNCENCODE 378 failed to allocate VNCBlitDetect

                            2019-11-11T09:51:20.791Z| mks| I125: VNCENCODE 378 VNCEncodeChooseRegionEncoder: region encoder adaptive. Resolution: 1810 x 864

                            2019-11-11T09:51:20.793Z| mks| W115: couldn't find space for 512x2048 frame 10 alloc 0 max 5148672

                            2019-11-11T09:51:27.547Z| mks| I125: SOCKET 378 (141) recv error 0: Success

                            2019-11-11T09:51:27.547Z| mks| I125: SOCKET 378 (141) VNC Remote Disconnect.

                            2019-11-11T09:51:27.547Z| mks| I125: MKSControlMgr: Remove VNC connection 2

                            2019-11-11T09:51:53.993Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:51:53.993Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:51:53.993Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:51:53.994Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:51:53.994Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 45

                            2019-11-11T09:51:53.994Z| vcpu-1| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 45

                            2019-11-11T09:51:53.994Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 47

                            2019-11-11T09:51:53.994Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 47

                            2019-11-11T09:51:53.994Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 43

                            2019-11-11T09:51:53.994Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 43

                            2019-11-11T09:51:53.994Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 42

                            2019-11-11T09:51:53.994Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 42

                            2019-11-11T09:51:53.994Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 59

                            2019-11-11T09:51:53.994Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 59

                            2019-11-11T09:51:53.994Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 65

                            2019-11-11T09:51:53.994Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 65

                            2019-11-11T09:51:53.994Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:51:53.994Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:51:53.998Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:51:53.998Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:51:53.998Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 45

                            2019-11-11T09:51:53.998Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 45

                            2019-11-11T09:51:53.998Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 47

                            2019-11-11T09:51:53.998Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 47

                            2019-11-11T09:51:53.998Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 43

                            2019-11-11T09:51:53.999Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 43

                            2019-11-11T09:51:53.999Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 42

                            2019-11-11T09:51:53.999Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 42

                            2019-11-11T09:51:53.999Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 59

                            2019-11-11T09:51:53.999Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 59

                            2019-11-11T09:51:53.999Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 65

                            2019-11-11T09:51:53.999Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 65

                            2019-11-11T09:51:53.999Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:51:53.999Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:59:22.082Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:59:22.082Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:59:22.083Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:59:22.083Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:59:22.083Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 45

                            2019-11-11T09:59:22.083Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 45

                            2019-11-11T09:59:22.083Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 47

                            2019-11-11T09:59:22.083Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 47

                            2019-11-11T09:59:22.083Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 43

                            2019-11-11T09:59:22.083Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 43

                            2019-11-11T09:59:22.083Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 42

                            2019-11-11T09:59:22.083Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 42

                            2019-11-11T09:59:22.083Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 59

                            2019-11-11T09:59:22.083Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 59

                            2019-11-11T09:59:22.084Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 65

                            2019-11-11T09:59:22.084Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 65

                            2019-11-11T09:59:22.084Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:59:22.084Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:59:22.088Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:59:22.088Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:59:22.088Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 45

                            2019-11-11T09:59:22.089Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 45

                            2019-11-11T09:59:22.089Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 47

                            2019-11-11T09:59:22.089Z| vcpu-3| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 47

                            2019-11-11T09:59:22.089Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 43

                            2019-11-11T09:59:22.089Z| vcpu-3| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 43

                            2019-11-11T09:59:22.089Z| vcpu-3| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 42

                            2019-11-11T09:59:22.089Z| vcpu-1| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 42

                            2019-11-11T09:59:22.089Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 59

                            2019-11-11T09:59:22.089Z| vcpu-3| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 59

                            2019-11-11T09:59:22.089Z| vcpu-3| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 65

                            2019-11-11T09:59:22.089Z| vcpu-3| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 65

                            2019-11-11T09:59:22.090Z| vcpu-3| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T09:59:22.090Z| vcpu-3| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

                            2019-11-11T11:23:21.640Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

                            2019-11-11T11:39:41.010Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

                            2019-11-11T11:50:51.004Z| vmx| I125: VigorTransportProcessClientPayload: opID=10c466da-c8-5063 seq=1012293: Receiving GuestOps.CreateTemporaryFile request.

                            2019-11-11T11:50:51.364Z| vcpu-1| I125: VigorTransport_ServerSendResponse opID=10c466da-c8-5063 seq=1012293: Completed GuestOps request.

                            2019-11-11T11:50:51.383Z| vmx| I125: VigorTransportProcessClientPayload: opID=18ddcdb0-7-506b seq=1012305: Receiving GuestOps.StartProgram request.

                            2019-11-11T11:50:51.602Z| vcpu-0| I125: VigorTransport_ServerSendResponse opID=18ddcdb0-7-506b seq=1012305: Completed GuestOps request.

                            2019-11-11T11:50:51.619Z| vmx| I125: VigorTransportProcessClientPayload: opID=52dfac15-61-5074 seq=1012317: Receiving GuestOps.ListProcesses request.

                            2019-11-11T11:50:51.836Z| vcpu-3| I125: VigorTransport_ServerSendResponse opID=52dfac15-61-5074 seq=1012317: Completed GuestOps request.

                            2019-11-11T11:50:56.854Z| vmx| I125: VigorTransportProcessClientPayload: opID=5ee9a942-da-50aa seq=1012345: Receiving GuestOps.ListProcesses request.

                            2019-11-11T11:50:57.123Z| vcpu-1| I125: VigorTransport_ServerSendResponse opID=5ee9a942-da-50aa seq=1012345: Completed GuestOps request.

                            2019-11-11T11:50:57.147Z| vmx| I125: VigorTransportProcessClientPayload: opID=150cff47-d0-50b0 seq=1012357: Receiving GuestOps.InitiateFileTransferFromGuest request.

                            2019-11-11T11:50:57.372Z| vcpu-1| I125: VigorTransport_ServerSendResponse opID=150cff47-d0-50b0 seq=1012357: Completed GuestOps request.

                            2019-11-11T11:50:57.472Z| vmx| I125: VigorTransportProcessClientPayload: opID=3f310ba6-18-50ba seq=1012369: Receiving GuestOps.InitiateFileTransferFromGuest request.

                            2019-11-11T11:50:57.757Z| vcpu-1| I125: VigorTransport_ServerSendResponse opID=3f310ba6-18-50ba seq=1012369: Completed GuestOps request.

                            2019-11-11T11:50:57.778Z| vmx| I125: VigorTransportProcessClientPayload: opID=47cfdde6-59-50c6 seq=1012381: Receiving GuestOps.InitiateFileTransferFromGuest request.

                            2019-11-11T11:50:58.000Z| vcpu-1| I125: VigorTransport_ServerSendResponse opID=47cfdde6-59-50c6 seq=1012381: Completed GuestOps request.

                            2019-11-11T11:50:58.032Z| vmx| I125: VigorTransportProcessClientPayload: opID=1aac2ddb-7-50d0 seq=1012393: Receiving GuestOps.DeleteFile request.

                            2019-11-11T11:50:58.244Z| vcpu-1| I125: VigorTransport_ServerSendResponse opID=1aac2ddb-7-50d0 seq=1012393: Completed GuestOps request.

                            2019-11-11T12:18:25.347Z| vmx| I125: VigorTransportProcessClientPayload: opID=33b71e1-7e-a6c8 seq=1014159: Receiving GuestOps.CreateTemporaryFile request.

                            2019-11-11T12:18:25.737Z| vcpu-1| I125: VigorTransport_ServerSendResponse opID=33b71e1-7e-a6c8 seq=1014159: Completed GuestOps request.

                            2019-11-11T12:18:25.751Z| vmx| I125: VigorTransportProcessClientPayload: opID=33b16c6f-c2-a6ce seq=1014171: Receiving GuestOps.StartProgram request.

                            2019-11-11T12:18:25.979Z| vcpu-0| I125: VigorTransport_ServerSendResponse opID=33b16c6f-c2-a6ce seq=1014171: Completed GuestOps request.

                            2019-11-11T12:18:25.995Z| vmx| I125: VigorTransportProcessClientPayload: opID=50a7bce1-cc-a6d4 seq=1014183: Receiving GuestOps.ListProcesses request.

                            2019-11-11T12:18:26.218Z| vcpu-1| I125: VigorTransport_ServerSendResponse opID=50a7bce1-cc-a6d4 seq=1014183: Completed GuestOps request.

                            2019-11-11T12:18:31.232Z| vmx| I125: VigorTransportProcessClientPayload: opID=520ba3b9-bf-a71a seq=1014195: Receiving GuestOps.ListProcesses request.

                            2019-11-11T12:18:31.521Z| vcpu-1| I125: VigorTransport_ServerSendResponse opID=520ba3b9-bf-a71a seq=1014195: Completed GuestOps request.

                            2019-11-11T12:18:31.544Z| vmx| I125: VigorTransportProcessClientPayload: opID=577dd0dd-4-a720 seq=1014207: Receiving GuestOps.InitiateFileTransferFromGuest request.

                            2019-11-11T12:18:32.797Z| vcpu-0| I125: VigorTransport_ServerSendResponse opID=577dd0dd-4-a720 seq=1014207: Completed GuestOps request.

                            2019-11-11T12:18:32.823Z| vmx| I125: VigorTransportProcessClientPayload: opID=5c37f032-fb-a732 seq=1014242: Receiving GuestOps.InitiateFileTransferFromGuest request.

                            2019-11-11T12:18:33.030Z| vcpu-1| I125: VigorTransport_ServerSendResponse opID=5c37f032-fb-a732 seq=1014242: Completed GuestOps request.

                            2019-11-11T12:18:33.062Z| vmx| I125: VigorTransportProcessClientPayload: opID=7301c914-6e-a73c seq=1014254: Receiving GuestOps.InitiateFileTransferFromGuest request.

                            2019-11-11T12:18:33.265Z| vcpu-1| I125: VigorTransport_ServerSendResponse opID=7301c914-6e-a73c seq=1014254: Completed GuestOps request.

                            2019-11-11T12:18:33.296Z| vmx| I125: VigorTransportProcessClientPayload: opID=121588e8-b5-a744 seq=1014266: Receiving GuestOps.DeleteFile request.

                            2019-11-11T12:18:33.496Z| vcpu-1| I125: VigorTransport_ServerSendResponse opID=121588e8-b5-a744 seq=1014266: Completed GuestOps request.

                            2019-11-11T13:07:37.277Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

                            2019-11-11T13:08:52.655Z| vmx| I125: VigorTransportProcessClientPayload: opID=3cddd392-b8-4573 seq=1017452: Receiving GuestOps.CreateTemporaryFile request.

                            2019-11-11T13:08:52.937Z| vcpu-1| I125: VigorTransport_ServerSendResponse opID=3cddd392-b8-4573 seq=1017452: Completed GuestOps request.

                            2019-11-11T13:08:52.953Z| vmx| I125: VigorTransportProcessClientPayload: opID=6e3766c6-e2-457b seq=1017464: Receiving GuestOps.StartProgram request.

                            2019-11-11T13:08:53.203Z| vcpu-1| I125: VigorTransport_ServerSendResponse opID=6e3766c6-e2-457b seq=1017464: Completed GuestOps request.

                            2019-11-11T13:08:53.220Z| vmx| I125: VigorTransportProcessClientPayload: opID=773c89b1-f2-4586 seq=1017476: Receiving GuestOps.ListProcesses request.

                            2019-11-11T13:08:53.455Z| vcpu-2| I125: VigorTransport_ServerSendResponse opID=773c89b1-f2-4586 seq=1017476: Completed GuestOps request.

                            2019-11-11T13:08:58.469Z| vmx| I125: VigorTransportProcessClientPayload: opID=4d2c9a59-89-45c3 seq=1017499: Receiving GuestOps.ListProcesses request.

                            2019-11-11T13:08:58.705Z| vcpu-0| I125: VigorTransport_ServerSendResponse opID=4d2c9a59-89-45c3 seq=1017499: Completed GuestOps request.

                            2019-11-11T13:08:58.731Z| vmx| I125: VigorTransportProcessClientPayload: opID=5271d32f-fb-45cb seq=1017511: Receiving GuestOps.InitiateFileTransferFromGuest request.

                            2019-11-11T13:08:58.944Z| vcpu-1| I125: VigorTransport_ServerSendResponse opID=5271d32f-fb-45cb seq=1017511: Completed GuestOps request.

                            2019-11-11T13:08:58.966Z| vmx| I125: VigorTransportProcessClientPayload: opID=7fea532a-92-45d3 seq=1017523: Receiving GuestOps.InitiateFileTransferFromGuest request.

                            2019-11-11T13:08:59.176Z| vcpu-1| I125: VigorTransport_ServerSendResponse opID=7fea532a-92-45d3 seq=1017523: Completed GuestOps request.

                            2019-11-11T13:08:59.202Z| vmx| I125: VigorTransportProcessClientPayload: opID=385f2f99-39-45dd seq=1017535: Receiving GuestOps.InitiateFileTransferFromGuest request.

                            2019-11-11T13:08:59.408Z| vcpu-1| I125: VigorTransport_ServerSendResponse opID=385f2f99-39-45dd seq=1017535: Completed GuestOps request.

                            2019-11-11T13:08:59.441Z| vmx| I125: VigorTransportProcessClientPayload: opID=635aeff3-6f-45e5 seq=1017547: Receiving GuestOps.DeleteFile request.

                            2019-11-11T13:08:59.643Z| vcpu-1| I125: VigorTransport_ServerSendResponse opID=635aeff3-6f-45e5 seq=1017547: Completed GuestOps request.

                            2019-11-11T13:12:37.884Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

                            2019-11-11T13:13:17.947Z| vmx| I125: VigorTransportProcessClientPayload: opID=VmConfigFormMediator-applyOnMultiEntity-4988643-ngc:71220635-fb-1c-539c seq=1017854: Receiving Disk.ConnectionControl request.

                            2019-11-11T13:13:17.948Z| vmx| I125: VigorTransport_ServerSendResponse opID=VmConfigFormMediator-applyOnMultiEntity-4988643-ngc:71220635-fb-1c-539c seq=1017854: Completed DiskEarlyDevice request.

                            2019-11-11T13:13:17.948Z| vmx| I125: VigorTransportProcessClientPayload: opID=VmConfigFormMediator-applyOnMultiEntity-4988643-ngc:71220635-fb-1c-539c seq=1017855: Receiving Disk.SetBackingInfo request.

                            2019-11-11T13:13:17.948Z| vmx| A100: ConfigDB: Setting sata0:0.deviceType = "atapi-cdrom"

                            2019-11-11T13:13:17.948Z| vmx| A100: ConfigDB: Setting sata0:0.clientDevice = "TRUE"

                            2019-11-11T13:13:17.948Z| vmx| A100: ConfigDB: Setting sata0:0.fileName = "emptyBackingString"

                            2019-11-11T13:13:17.962Z| vmx| I125: VigorTransport_ServerSendResponse opID=VmConfigFormMediator-applyOnMultiEntity-4988643-ngc:71220635-fb-1c-539c seq=1017855: Completed DiskEarlyDevice request.

                            2019-11-11T13:13:17.964Z| vmx| I125: VigorTransportProcessClientPayload: opID=VmConfigFormMediator-applyOnMultiEntity-4988643-ngc:71220635-fb-1c-539c seq=1017856: Receiving HotPlugManager.BeginBatch request.

                            2019-11-11T13:13:17.964Z| vmx| I125: VigorTransport_ServerSendResponse opID=VmConfigFormMediator-applyOnMultiEntity-4988643-ngc:71220635-fb-1c-539c seq=1017856: Completed HotPlugManager request.

                            2019-11-11T13:13:17.967Z| vmx| I125: VigorTransportProcessClientPayload: opID=VmConfigFormMediator-applyOnMultiEntity-4988643-ngc:71220635-fb-1c-539c seq=1017863: Receiving HotPlugManager.EndBatch request.

                            2019-11-11T13:13:17.967Z| vmx| I125: VigorTransport_ServerSendResponse opID=VmConfigFormMediator-applyOnMultiEntity-4988643-ngc:71220635-fb-1c-539c seq=1017863: Completed HotPlugManager request.

                            • 14. Re: PowerCLI Guest OS Cmdlets Error - The 'propSet' paramter should not be null.
                              LucD Guru
                              vExpertUser ModeratorsCommunity Warriors

                              That confirms that there is nothing wrong with the actual Invoke-VMScript.
                              The sequence in the vmware.log shows that all steps are executed successfully.

                               

                              I'm still not convinced that you are running in a clean situation.

                              Two options:

                               

                              1. Can you install PowerCLI 11.5.0 on a fresh station (no previous PowerCLI installs), and try from there
                              2. Go back to the old 6.5 R1 version. First, delete the current folders, then download the EXE and install.

                               

                              Needless to say that I'm not in favour of option 2.
                              You'll be using an old version, and missing out on new features, improvements and bug fixes.

                              1 2 Previous Next