3 Replies Latest reply on Jun 4, 2019 7:25 AM by vijaypks

    VMware.VimAutomation.Logging.SoapInterceptor not found

    Sumafu Lurker

      Hi,

       

      I'm trying to reboot a VM with PowerCli and then wait until the vm is running. I user this command for this:

       

      Get-CIVM -VApp $VCloudVappName -Name $VCloudVmName | Restart-CIVMGuest -Confirm:$false -WhatIf | Wait-Tools
      

       

      This works at least the last command. Wait-Tools every time gets an error

       

      Connect-VIServer : Die Datei oder Assembly "VMware.VimAutomation.Logging.SoapInterceptor, Version=1.0.0.646, Culture=neutral, PublicKeyToken=null" oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden.
      In C:\tmp\reboot.ps1:13 Zeichen:1
      + Connect-VIServer -Server $VCloudHost -Credential $mycredsVCloud
      + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          + CategoryInfo          : NotSpecified: (:) [Connect-VIServer], FileNotFoundException
          + FullyQualifiedErrorId : System.IO.FileNotFoundException,VMware.VimAutomation.ViCore.Cmdlets.Commands.ConnectVIServer
      
      Wait-Tools : Die Datei oder Assembly "VMware.VimAutomation.Logging.SoapInterceptor, Version=1.0.0.646, Culture=neutral, PublicKeyToken=null" oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden.
      In C:\tmp\reboot.ps1:15 Zeichen:104
      + ... VCloudVmName | Restart-CIVMGuest -Confirm:$false -WhatIf | Wait-Tools
      +                                                                ~~~~~~~~~~
          + CategoryInfo          : NotSpecified: (:) [Wait-Tools], FileNotFoundException
          + FullyQualifiedErrorId : System.IO.FileNotFoundException,VMware.VimAutomation.ViCore.Cmdlets.Commands.WaitTools
      

      It's a german error message, but it says something like "File or assembly ... or a dependency not found. The system can not find the specified file.

       

      I have PowerCli Version 6.5.1, the latest VIX Tools, and I already restarted my Computer

      Can someone help me?

        • 1. Re: VMware.VimAutomation.Logging.SoapInterceptor not found
          Adam Soerries Novice
          vExpert

          I ran into this same issue, and was able to resolve it with the following command.

          PS> Install-Module VMware.VimAutomation.Sdk

          If you have not already done so, you may need to first use the Save-Module command.

          • 2. Re: VMware.VimAutomation.Logging.SoapInterceptor not found
            cryton2707 Enthusiast

            I ran into the same issue with a connect-viserver.

             

            To resolve it.

            I had forgotten to uninstall the previous version of Vmware powercli from the control panel.

            So the old Setup.exe version of powercli. Simply uninstalled from control panel and it started working fine from the module.

            • 3. Re: VMware.VimAutomation.Logging.SoapInterceptor not found
              vijaypks Lurker

              If you installed VMware power CLI run below command

               

               

               

               

               

               

              1. Save all modules in temp folder in C drive ...

               

               

               

               

               

               

              its will give list of modules installed

               

               

               

               

               

               

              2 Copy the files you downloaded to the offline computer

               

               

               

               

               

               

              3.Move the copied files to C:\Windows\System32\WindowsPowerShell\v1.0\Modules

               

               

               

               

               

               

              4. #Set the participation to false and ignore invalid certificates for all users

               

               

              Set-PowerCLIConfiguration -Scope AllUsers -ParticipateInCeip $false -InvalidCertificateAction Ignore

               

               

               

               

               

               

               

               

               

               

               

              5.#Connect to our vCenter Server using the logged in credentials

               

               

              Connect-VIServer  10.x.x.x