This post is more than 5 years old
2 Posts
0
46120
December 15th, 2014 21:00
Dell MEM install fails
Hi All
Previously on my ESXi 4.1 hosts I was able to setup the Dell MEM (1.1) quite easily . Now I am trying to setup 1.2 on a ESXI 5.5 host (fresh install still in eval mode).
I have a fresh install of VMware-vSphere-CLI-5.5.0-2043780 however whenever I run the setup.pl
for example setup.pl --configure --server=10.2.6.xx
I get the following (tried on 3 different PCs).
C:\MEM>dir
Volume in drive C has no label.
Volume Serial Number is 34C0-7582
Directory of C:\MEM
16/12/2014 04:05 PM
16/12/2014 04:05 PM
12/12/2014 09:08 AM 503,327 110-6093-R4_EN_MEM_Guide_web.pdf
19/09/2013 01:20 AM 3,983,015 dell-eql-mem-esx5-1.2.0.365964.zip
19/09/2013 01:20 AM 120,474 MEM-Fix_List.pdf
19/09/2013 01:20 AM 222,831 MEM-Release_Notes.pdf
19/09/2013 01:20 AM 503,327 MEM-User_Guide.pdf
19/09/2013 01:20 AM 3,039 README.txt
19/09/2013 01:20 AM 116,371 setup.pl
7 File(s) 5,452,384 bytes
2 Dir(s) 4,946,833,408 bytes free
C:\MEM>setup.pl --configure --server=10.2.6.63
Can't locate SOAP/Lite.pm in @INC (@INC contains: C:/Program Files (x86)/VMware/
VMware vSphere CLI/Perl/site/lib C:/Program Files (x86)/VMware/VMware vSphere CL
I/Perl/lib .) at C:/Program Files (x86)/VMware/VMware vSphere CLI/Perl/lib/WSMan
/WSBasic.pm line 5.
BEGIN failed--compilation aborted at C:/Program Files (x86)/VMware/VMware vSpher
e CLI/Perl/lib/WSMan/WSBasic.pm line 5.
Compilation failed in require at C:/Program Files (x86)/VMware/VMware vSphere CL
I/Perl/lib/WSMan/GenericOps.pm line 3.
BEGIN failed--compilation aborted at C:/Program Files (x86)/VMware/VMware vSpher
e CLI/Perl/lib/WSMan/GenericOps.pm line 3.
Compilation failed in require at C:\MEM\setup.pl line 20.
BEGIN failed--compilation aborted at C:\MEM\setup.pl line 20.
C:\MEM>
Any ideas ?
Thanks
Origin3k
4 Operator
•
2.3K Posts
1
December 15th, 2014 22:00
The script use the vSphere CLI which is based on PERL and the question is which minumum Version is needed and if there is a reason why the SOAP package is missing because it looks like it is already partially installed on your system.
So go to vmware.com and install the vSphere CLI or vSphere Perl SDK for WINDOWS. You can only install one version of this package. After that open a new shell window and try again.
Dont be confused about the vSphere PowerCLI which is the Powershell Version of the vSphere API.
BTW. we use VUM or esxcli to install the MeM but you have to setup all the vNetworking and iSCSI Binding manually or by using a Host Profile.
Regards,
Joerg
mrpaule
2 Posts
0
December 16th, 2014 14:00
Hi Both
Thanks for your replies. After un-installing VMware-vSphere-CLI-5.5.0-2043780.exe and installing VMware-vSphere-CLI-5.5.0-1549297.exe, it worked perfectly.
Regards