Versions Compared

Version Old Version 2 New Version 3
Changes made by

Conor McCann

Scott McDonald

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

/Scan-10.210.9.249/0003810.210.9.249 <ApplicationUniqueness> A(ESX).S(ESX vSphere Uniqueness).P(vSphere) - WARN - Connection failed unexpectedly
System.Exception: Error connecting to vSphere: ---> System.MissingMethodException: Method not found: 'Void VMware.Vim.VimClient..ctor()'.
at iQuate.iQSonar.Connection.vSphere.vSphereClient.CreateConnection(IPAddress target, Int32 port, ConnectionOptions options)
— End of inner exception stack trace —
at iQuate.iQSonar.Connection.vSphere.vSphereClient.CreateConnection(IPAddress target, Int32 port, ConnectionOptions options)
at iQuate.iQSonar.Connections.SecuredConnectionFactory.CreateConnections(IPAddress target, Int32 port, ConnectionOptions options, IEnumerable`1 credentials, String instance)

The UI may display the following message in the Project Activity details:
 "Skipping Strategy because of missing Protocol connection vSphere (audit=ESX@AU.1:ESX_vSphereUniqueness)

Image Added 

Solution:

The issue was down to the version of PowerCLI installed on the scan server. An uninstall of Powercli 5.5 release 2  PowerCLI-5.5.0-1931983.exe (which is currently part of iQSonar scan perquisites documentatin)  is required and reinstalled Powercli 5.5 release 1 PowerCLI-5.5.0-1295336.exe

...