VMware Cloud Community
mhashemi
Contributor
Contributor
Jump to solution

Cannot use Connect-VIServer

I have two machines, both with PowerCLI 5.1 R1. One machine is Server 2003 with .Net 2.0 SP1, .Net 3.0 SP1, and .Net 4 installed (let's call this server1). The other machine is Windows 7 with .Net 4.5 installed (let's call this workstation1). The machine called server1 is also the vCenter server

When I open PowerCLI on workstation1, it connects just fine. When I open PowerCLI on server1, I receive the following error:

Connect-VIServer : Method not found: 'Int32 System.Threading.WaitHandle.WaitAny
(System.Threading.WaitHandle[], Int32)'.
At line:1 char:17
+ Connect-VIServer <<<<  server1
    + CategoryInfo          : NotSpecified: (:) [Connect-VIServer], MissingMet
   hodException
    + FullyQualifiedErrorId : System.MissingMethodException,VMware.VimAutomati
   on.ViCore.Cmdlets.Commands.ConnectVIServer

What am I missing?

Thanks.

0 Kudos
1 Solution

Accepted Solutions
jdptechnc
Expert
Expert
Jump to solution

Install this package, which includes .Net Framework 3.5 but also the latest service packs for 2.0 and 3.0.

http://www.microsoft.com/en-us/download/details.aspx?id=25150

Then I would also go download the security patches for .NET framework from Microsoft, as there have been quite a few released since these versions of .NET were released.

Please consider marking as "helpful", if you find this post useful. Thanks!... IT Guy since 12/2000... Virtual since 10/2006... VCAP-DCA #2222

View solution in original post

0 Kudos
4 Replies
aravinds3107
Virtuoso
Virtuoso
Jump to solution

Check this post(http://communities.vmware.com/thread/398412?start=0&tstart=0) and see if it helps

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful |Blog: http://aravindsivaraman.com/ | Twitter : ss_aravind
0 Kudos
iw123
Commander
Commander
Jump to solution

does it behave differently if you run the powercli console as administrator?

*Please, don't forget the awarding points for "helpful" and/or "correct" answers
0 Kudos
LucD
Leadership
Leadership
Jump to solution

From the Release Notes, you need "NET Framework 2.0 with Service Pack 2"


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
jdptechnc
Expert
Expert
Jump to solution

Install this package, which includes .Net Framework 3.5 but also the latest service packs for 2.0 and 3.0.

http://www.microsoft.com/en-us/download/details.aspx?id=25150

Then I would also go download the security patches for .NET framework from Microsoft, as there have been quite a few released since these versions of .NET were released.

Please consider marking as "helpful", if you find this post useful. Thanks!... IT Guy since 12/2000... Virtual since 10/2006... VCAP-DCA #2222
0 Kudos