Hi,
I installed the vSphere CLI 4.1 on the Windows Server 2003 SP2 (x32) and when I try to connect using vicfg-nas.pl it gives below error. W2K3 x32 bit is well supported according to the vSphere CLI document. I am not sure where it is going wrong then.
perl.exe - Unable to Locate Component
This application has failed to start because libxml2.dll was not found. Re-installing the application may fix this problem.
Any suggetions would be appreciated.
Thanks
The Perl installation is not in the Path environment variable. Add the following location to the Path environment variable:
I think the Perl installation is not in the Path environment variable.
C:\Program Files\VMware\VMware VI Remote CLI\Perl\bin
- Right click My Computer
- Select Properties from the context menu
- Select the Advanced system settings
- Click Environment Variables button
- Select Path in the System Variables and click Edit
- Add the following line ";C:\Program Files\VMware\VMware VI Remote CLI\Perl\bin" to the Path variable
Restart the command prompt for the Path to take effect
The Perl installation is not in the Path environment variable. Add the following location to the Path environment variable:
I think the Perl installation is not in the Path environment variable.
C:\Program Files\VMware\VMware VI Remote CLI\Perl\bin
- Right click My Computer
- Select Properties from the context menu
- Select the Advanced system settings
- Click Environment Variables button
- Select Path in the System Variables and click Edit
- Add the following line ";C:\Program Files\VMware\VMware VI Remote CLI\Perl\bin" to the Path variable
Restart the command prompt for the Path to take effect
Fantastic! worked like charm!
Thanks v much Baecke
Np have fun with it
At my customer site the CLI install put a incorrect PATH variable in, but when you preview the dialog box the most recently added one was obviously the CLI folder so I skipped past that step. I had to look again and for whatever reason the installer gave it this path variable
C:\Program Files\VMware\VMware VI Remote CLI\Perl\site\bin
not sure where "site" came from, bug perhaps?