{"id":271,"date":"2014-04-17T05:42:16","date_gmt":"2014-04-17T12:42:16","guid":{"rendered":"http:\/\/bclary.com\/blog\/?p=271"},"modified":"2014-04-17T05:42:16","modified_gmt":"2014-04-17T12:42:16","slug":"how-to-work-around-soap-request-protocol-error-with-vmware-vsphere-perl-sdk-5-5-0","status":"publish","type":"post","link":"https:\/\/bclary.com\/blog\/2014\/04\/17\/how-to-work-around-soap-request-protocol-error-with-vmware-vsphere-perl-sdk-5-5-0\/","title":{"rendered":"How to work around SOAP request protocol error with VMware-vSphere-Perl-SDK-5.5.0"},"content":{"rendered":"<p>During a move from vSphere 5.0 to 5.5 I ran into errors using the Perl scripts provided with the VMware vSphere Perl SDK for 5.5 on Fedora 20. The symptom was the following response to calling <code>vminfo.pl<\/code>:\n<\/p>\n<pre>\r\nSOAP request error - possibly a protocol issue: &lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\r\n&lt;soapenv:Envelope xmlns:soapenc=\"http:\/\/schemas.xmlsoap.org\/soap\/encoding\/\"\r\n xmlns:soapenv=\"http:\/\/schemas.xmlsoap.org\/soap\/envelope\/\"\r\n xmlns:xsd=\"http:\/\/www.w3.org\/2001\/XMLSchema\"\r\n xmlns:xsi=\"http:\/\/www.w3.org\/2001\/XMLSchema-instance\"&gt;\r\n&lt;soapenv:Body&gt;\r\n<\/pre>\n<p>I found the solution on the VMware communities at <a href=\"https:\/\/communities.vmware.com\/message\/2298661\">SOAP error with VMware-vSphere-Perl-SDK-5.5.0<\/a>, but thought I would provide the additional steps I took in the hope it will help someone else.<\/p>\n<p>The recommended solution was to use an older version of libwww-perl, in particular 5.837. But many of the packages on my system depend on libwww-perl and I didn&#8217;t want to mess with such a critical piece of my environment. The solution was to download the older version of libwww-perl, install it into a non-system location and to set the environment variable PERL5LIB to point to the new location before calling the vSphere Perl SDK scripts.<\/p>\n<pre>\r\n$ cd ~\/Downloads\/\r\n$ mkdir libwww-perl\r\n$ cd libwww-perl\r\n# Download libwww-perl-libwww-perl-5.837.tar.gz from https:\/\/github.com\/libwww-perl\/libwww-perl\/releases and save to ~\/Downloads\/libwww-perl\r\n$ tar zxvf libwww-perl-libwww-perl-5.837.tar.gz\r\n$ cd libwww-perl-libwww-perl-5.837\r\n# Pick an installation location for libwww-perl which does not interfere with your system.\r\nperl Makefile.PL INSTALL_BASE=<em>install_location<\/em>\r\nmake\r\nmake test\r\nmake install\r\n<\/pre>\n<p>Since I wrap calls to the VMware Perl SDK in bash scripts, all I needed to do to use libwww-perl 5.837 was to add the following at the beginning of the scripts:<\/p>\n<pre>\r\nexport PERL5LIB=<em>install_location<\/em>\/lib\/perl5\r\n<\/pre>\n<p>Remember to change <em>install_location<\/em> to match your environment.<\/p>\n<p>Hope that helps and thanks to the VMware community for the work around.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>During a move from vSphere 5.0 to 5.5 I ran into errors using the Perl scripts provided with the VMware vSphere Perl SDK for 5.5 on Fedora 20. The symptom was the following response to calling vminfo.pl: SOAP request error &#8211; possibly a protocol issue: &lt;?xml version=&#8221;1.0&#8243; encoding=&#8221;UTF-8&#8243;?&gt; &lt;soapenv:Envelope xmlns:soapenc=&#8221;http:\/\/schemas.xmlsoap.org\/soap\/encoding\/&#8221; xmlns:soapenv=&#8221;http:\/\/schemas.xmlsoap.org\/soap\/envelope\/&#8221; xmlns:xsd=&#8221;http:\/\/www.w3.org\/2001\/XMLSchema&#8221; xmlns:xsi=&#8221;http:\/\/www.w3.org\/2001\/XMLSchema-instance&#8221;&gt; &lt;soapenv:Body&gt; I &hellip; <a href=\"https:\/\/bclary.com\/blog\/2014\/04\/17\/how-to-work-around-soap-request-protocol-error-with-vmware-vsphere-perl-sdk-5-5-0\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;How to work around SOAP request protocol error with VMware-vSphere-Perl-SDK-5.5.0&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[],"class_list":["post-271","post","type-post","status-publish","format-standard","hentry","category-how-to"],"_links":{"self":[{"href":"https:\/\/bclary.com\/blog\/wp-json\/wp\/v2\/posts\/271","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bclary.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bclary.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bclary.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/bclary.com\/blog\/wp-json\/wp\/v2\/comments?post=271"}],"version-history":[{"count":5,"href":"https:\/\/bclary.com\/blog\/wp-json\/wp\/v2\/posts\/271\/revisions"}],"predecessor-version":[{"id":276,"href":"https:\/\/bclary.com\/blog\/wp-json\/wp\/v2\/posts\/271\/revisions\/276"}],"wp:attachment":[{"href":"https:\/\/bclary.com\/blog\/wp-json\/wp\/v2\/media?parent=271"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bclary.com\/blog\/wp-json\/wp\/v2\/categories?post=271"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bclary.com\/blog\/wp-json\/wp\/v2\/tags?post=271"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}