1 2 Previous Next 23 Replies Latest reply on Jun 14, 2013 4:41 AM by dmc Go to original post
      • 15. Re: Invoke-VMScript "The guest operations agent could not be contacted."
        dmadden Enthusiast

        For "GuestRpcSendTimedOut" or the initial problem description of this thread?

         

        If you're curious why you're receiving "GuestRpcSendTimedOut", then I would:

         

        a) examine the performance of the VM at the time of the errors (performance charts in vcenter or guest OS tools such as perfmon or top)

        b) Enable vmware tools logging (KB 1017256), reproduce the error and examine the log

        c) Check the ESX server logs at the time of the error for any VM operations (hostd/vmkernel/messages)

         

        For the problem in the initial problem description (guest operations agent could not be contacted), we've requested a variety of different logs. The investigation is still ongoing so I can't say with certainty what exact logs to take a look at since the root cause has not been determined.

        • 16. Re: Invoke-VMScript "The guest operations agent could not be contacted."
          Konflikt Novice
          vExpert

          Thank you for your reply dmadden. Unfortunately my vmware account is not connected to our vSphere licences, so i cannot open a support request. Is there any possibiliy to open a support request without this, or i have to connect with my management, and get that account which has the licences?

          Thank you in advance.

          • 17. Re: Invoke-VMScript "The guest operations agent could not be contacted."
            dmadden Enthusiast

            I would need a support request to be filed.  However, if you can get your management to open the support request but provide your contact details, then I can work with you to troubleshoot the issue.  Thanks.

            • 18. Re: Invoke-VMScript "The guest operations agent could not be contacted."
              LucD Guru
              vExpertCommunity WarriorsUser Moderators

              Thanks for the info.

              I'll follow those steps next time I see the message again.

              • 19. Re: Invoke-VMScript "The guest operations agent could not be contacted."
                Konflikt Novice
                vExpert

                Dear dmadden,

                 

                I have opened a support request about this issue with our main VMware account.

                The issue deatils are the following: Support Request Confirmation Number: 12183217306. I can use that account to upload any other informations. But please regarding this support request please use my email address in the feature for contact. (you can see it at the end of the reqaust support description)

                 

                Thank you in advance.

                • 20. Re: Invoke-VMScript "The guest operations agent could not be contacted."
                  MKguy Virtuoso

                  I'm not sure how otheres fared with their support requests in the meantime, but I just tracked the issue down by coincidence to the ESXi-side Reload VM operation that Backup Exec triggers on each VM backup too.

                   

                  The following procedure is consistently reproduceable:

                  1. Confirm Invoke-VMScript works currently (restart VMware Tools):

                  Invoke-VMScript -ScriptText 'ipconfig' -VM $vm -GuestCredential $creds

                  --> Is being executed OK

                   

                  2. On the ESXi shell of the host running the VM (I actually don't know any other way to trigger the Reload-VM task manually), get the VM ID (or VMX path) with vim-cmd vmsvc/getallvms | grep -i [MyVMName]


                  3. Now reload the VM via vim-cmd vmsvc/reload [ID]

                  The vmware.log of the VM will now record the following:

                  2012-11-19T15:56:59.760Z| vmx| VmdbPipeStreamsOvlError Couldn't read: OVL_STATUS_EOF, (11) Resource temporarily unavailable.
                  2012-11-19T15:56:59.760Z| vmx| VmdbCnxDisconnect: Disconnect: closed pipe for pub cnx '/db/connection/#6/' (-32)
                  2012-11-19T15:56:59.760Z| vmx| VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#6/'
                  2012-11-19T15:56:59.771Z| vmx| SOCKET 2 (78) recv detected client closed connection
                  2012-11-19T15:56:59.771Z| vmx| Vix: [1889886 mainDispatch.c:2984]: VMAutomation: Connection Error (4) on connection 1.
                  2012-11-19T15:56:59.818Z| vmx| VmdbAddConnection: cnxPath=/db/connection/#b/, cnxIx=3
                  2012-11-19T15:56:59.866Z| vmx| Vix: [1889886 vigorCommands.c:940]: VigorHotPlugManagerEndBatchCommandCallback: vmdbErr = -24

                   

                  4. Try running the Invoke-VMScript command again and it will fail with "The guest operations agent could not be contacted":

                  Invoke-VMScript -ScriptText 'ipconfig' -VM $vm -GuestCredential $creds

                  Invoke-VMScript : 19.11.2012 16:57:06    Invoke-VMScript        The guest operations agent could not be contacted.
                  Bei Zeile:1 Zeichen:16
                  + Invoke-VMScript <<<<  -ScriptText 'ipconfig' -VM $vm -GuestCredential $creds
                      + CategoryInfo          : NotSpecified: (:) [Invoke-VMScript], ViError
                      + FullyQualifiedErrorId : Client20_VmGuestServiceImpl_RunScriptInGuest_ViError,VMware.VimAutomation.ViCore.Cmdlets.Commands.InvokeVmScript

                   

                  5. Restart the VMware Tools Windows service in the VM and Invoke-VMScript will work again until the next reload. Vmware.log messages during tools restart:

                  2012-11-19T15:57:41.261Z| vcpu-0| TOOLS autoupgrade protocol version 0
                  2012-11-19T15:57:41.261Z| vcpu-0| TOOLS ToolsCapabilityGuestTempDirectory received 0
                  2012-11-19T15:57:41.265Z| vcpu-0| GuestRpc: Reinitializing Channel 0(toolbox)
                  2012-11-19T15:57:41.265Z| vcpu-0| GuestRpc: Channel 0 reinitialized.
                  2012-11-19T15:57:43.180Z| vcpu-0| GuestRpc: Channel 0, guest application toolbox.
                  2012-11-19T15:57:43.186Z| vcpu-0| TOOLS ToolsCapabilityGuestTempDirectory received 1 C:\Windows\TEMP\vmware-SYSTEM
                  2012-11-19T15:57:43.201Z| vcpu-0| TOOLS autoupgrade protocol version 2
                  2012-11-19T15:57:43.202Z| vcpu-0| TOOLS ToolsCapabilityGuestConfDirectory received C:\ProgramData\VMware\VMware Tools
                  2012-11-19T15:57:43.203Z| vcpu-0| TOOLS Received tools.set.version rpc call, version = 8389.
                  2012-11-19T15:57:43.203Z| vcpu-0| ToolsSetVersionWork did nothing; new tools version (8389) matches old Tools version
                  2012-11-19T15:57:43.204Z| vcpu-0| TOOLS unified loop capability requested by 'toolbox'; now sending options via TCLO
                  2012-11-19T15:57:43.205Z| vcpu-0| Guest: toolbox: Version: build-652272
                  2012-11-19T16:00:28.567Z| vcpu-0| TOOLS unified loop capability requested by 'toolbox-ui'; now sending options via TCLO
                  2012-11-19T16:00:28.567Z| vcpu-0| GuestRpc: Channel 6, guest application toolbox-ui.

                   

                   

                  I confirmed this behavior for Windows 2003 R2 x86 and Windows 2008 R2 VMs in the following environment:

                  VMware vSphere PowerCLI 5.0.1 build 581491

                  VMware ESXi 5.0.0 Update 1 build-821926

                  VMware Tools  8.6.5.11852 (build-652272) (the 5.0 U1 tools) as well as 9.0.0.15210 (build-782409) (the 5.1 GA tools)

                   

                  Seeing how the ESXi reload function triggers this issue, it's not Symantec's fault (for once).

                  • 21. Re: Invoke-VMScript "The guest operations agent could not be contacted."
                    MKguy Virtuoso

                    For the record, I am also able to reproduce this issue exactly the same way on ESXi 5.1 / vCenter 5.1 / PowerCLI 5.1.

                     

                    It affects Linux guests too.

                    • 22. Re: Invoke-VMScript "The guest operations agent could not be contacted."
                      Novice

                      Hi,

                       

                      if you observe the following lines in the hostd.log you're running in an issue which will be fixed in vSphere 5.0 U2 and 5.1 U1 (Ref.: PR850673).

                       

                      TS [XXX info 'vm:/vmfs/volumes/<UUID>/<VM>/<VM>.vmx' opID=XXX] CheckVMStateForGuestOperation: GuestOps are not ready.
                      TS [XXX info 'Default' opID=XXX] AdapterServer caught exception: vim.fault.GuestOperationsUnavailable
                      

                       

                      Best Regards,

                      Tobias Sutor

                      1 2 Previous Next