VMware

This Question is Not Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
9 Replies Last post: Nov 18, 2009 12:47 AM by likid000  

Error: Server version unavailable at 'https://1.1.1.1/sdk/vimService.wsdl' when connecting to virtual center with connect.pl posted: Nov 4, 2009 4:12 AM

Click to view likid000's profile Novice 6 posts since
Dec 3, 2005

Hi,

I have a strange problem, I have 3 RHEL 5.4 servers that are clones of each other, I have install the SDK on all 3 of them, version:

I have installed VMware-vSphere-SDK-for-Perl-4.0.0-161974

and on 2 servers whith connect.pl it works great:

  1. /usr/lib/vmware-vcli/apps/general/connect.pl --server 1.1.1.1 --username XXX --password XX

Connection Successful
Server Time : 2009-11-04T11:53:30.449415Z

On the third server it doesn't work:

  1. /usr/lib/vmware-vcli/apps/general/connect.pl --server 1.1.1.1 --username XXX --password XX

Error: Server version unavailable at 'https://1.1.1.1/sdk/vimService.wsdl'

I am connecting to a VC with esx 3.5, on the third server I can access the url 'https://1.1.1.1/sdk/vimService.wsdl' with no problems

Any idea what can be the problem ?

Thnx

Click to view lamw's profile Champion 2,803 posts since
Nov 27, 2007
Does the following work:

/usr/lib/vmware-vcli/apps/general/connect.pl --url https://1.1.1.1/sdk --username XXX --password XX

=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/
vGhetto Script Repository
VMware Code Central - Scripts/Sample code for Developers and Administrators
VMware Developer Comuunity
Getting Started with the vMA (tips/tricks)
Getting Started with the vSphere SDK for Perl
Twitter: @lamw

http://engineering.ucsb.edu/~duonglt/vmware/vexpert_silver_icon.jpg

If you find this information useful, please award points for "correct" or "helpful".

Click to view haplo2000's profile Lurker 3 posts since
Aug 17, 2009

do you use a proxy?

if so, deactivate the proxy (look in the enviroment) an then try again

Click to view haplo2000's profile Lurker 3 posts since
Aug 17, 2009

I am not firm with Redhead. On Suse you can edit /etc/sysconfig/proxy or you can do over yast.

Perhaps you have set proxy setting for yum but normaly the connect.pl script get the proxy setting form user env.

try to start connect.pl with --verbose for more debug infos

Click to view haplo2000's profile Lurker 3 posts since
Aug 17, 2009

ok, you can try the following.

uninstall vsphere sdk 4 for Perl and install the VI Perl 1.6, thats the version before sdk 4. there is a better failure output.

Developer Social Media

Communities