Hi, the issue here is on your prime client. I think what's most likely is that a piece of software is missing which is required by the failing process or there's some misconfiguration. If you haven't, it's a good idea to go through the client configuration section of the benchmarking guide to make sure all software has been installed and each step has been exactly followed.
However, let's try running the problematic command manually:
Please open a PowerCLI window on your prime client and run the following command:
C:\VMmark2\tools\VMmark2PSbe.ps1 <your VC> <your VC username> '<your VC password>' localhost C:\vmmark2\tmp\Then go to C:\vmmark2\tmp and paste the contents of the file named VMmark2PSbe.txt into this thread or zip and attach onto the thread.
The expected response from running the above command in the PowerCLI window will be
"VMmark2PSbe 1.2 waiting for commands"
If you see this, just hit control-c to kill the command.
Thanks,
Rebecca