Urgent help needed: VMware-Vsphere SDK 5.1 java sample: export failed after upload 20G VM image to local location.

[Dorisliq]

Updated: Sept 23rd.

I got a problem to make the java sample running properly.

Any help will be really appreciated .

1. download VMware-vSphere-SDK-5.1.0-774886\SDK,

2. set up javahome

3. imported VMKEYSTORE, and setup in environment variable.

4. run the sample: build

5. try run" run.bat com.vmware.vapp.OVFManagerExportVMDK --url url --username xxx\yyy --password zzzzzzzz --vmname vmname

6. The export will be failed after export 20G, error"

  javax.xml.ws.WebServiceException: com.sun.xml.internal.messaging.saaj.SOAPExcept

  ionImpl: No NamespaceURI, SOAP requires faultcode content to be a QName"

Anyone met this problem before and know what we could do to fix it?

Any help will be appreciated. Thanks ^_^

Detailed Error: (Failed to disconnect could be ignored since my Java is on version 1.7.0)

#### TOTAL_BYTES 37580963840

Exported File xxxxxx-disk-0.vmdk : 22022651392

Completed Downloading the files

---------------------- Thread interrupted ----------------------

Sep 23, 2013 12:13:33 AM com.sun.xml.internal.messaging.saaj.soap.impl.FaultImpl

setFaultCode

SEVERE: SAAJ0140: No NamespaceURI, SOAP requires faultcode content to be a QName

javax.xml.ws.WebServiceException: com.sun.xml.internal.messaging.saaj.SOAPExcept

ionImpl: No NamespaceURI, SOAP requires faultcode content to be a QName

        at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11

Fault.java:185)

        at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFa

ultBuilder.java:114)

        at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMetho

dHandler.java:252)

        at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMetho

dHandler.java:222)

        at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:115)

        at $Proxy32.httpNfcLeaseProgress(Unknown Source)

        at com.vmware.vapp.OVFManagerExportVMDK.exportVM(OVFManagerExportVMDK.ja

va:567)

        at com.vmware.vapp.OVFManagerExportVMDK.main(OVFManagerExportVMDK.java:7

26)

Caused by: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: No NamespaceUR

I, SOAP requires faultcode content to be a QName

        at com.sun.xml.internal.messaging.saaj.soap.impl.FaultImpl.setFaultCode(

FaultImpl.java:115)

        at com.sun.xml.internal.messaging.saaj.soap.impl.FaultImpl.setFaultCode(

FaultImpl.java:152)

        at com.sun.xml.internal.messaging.saaj.soap.ver1_1.SOAPFactory1_1Impl.cr

eateFault(SOAPFactory1_1Impl.java:76)

        at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11

Fault.java:176)

        ... 7 more

Sep 23, 2013 12:13:34 AM com.sun.xml.internal.messaging.saaj.soap.impl.FaultImpl

setFaultCode

SEVERE: SAAJ0140: No NamespaceURI, SOAP requires faultcode content to be a QName

Failed to disconnect - com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: No

NamespaceURI, SOAP requires faultcode content to be a QName

javax.xml.ws.WebServiceException: com.sun.xml.internal.messaging.saaj.SOAPExcept

ionImpl: No NamespaceURI, SOAP requires faultcode content to be a QName

        at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11

Fault.java:185)

        at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFa

ultBuilder.java:114)

        at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMetho

dHandler.java:252)

        at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMetho

dHandler.java:222)

        at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:115)

        at $Proxy32.logout(Unknown Source)

        at com.vmware.vapp.OVFManagerExportVMDK.disconnect(OVFManagerExportVMDK.

java:214)

        at com.vmware.vapp.OVFManagerExportVMDK.main(OVFManagerExportVMDK.java:7

37)

Caused by: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: No NamespaceUR

I, SOAP requires faultcode content to be a QName

        at com.sun.xml.internal.messaging.saaj.soap.impl.FaultImpl.setFaultCode(

FaultImpl.java:115)

        at com.sun.xml.internal.messaging.saaj.soap.impl.FaultImpl.setFaultCode(

FaultImpl.java:152)

        at com.sun.xml.internal.messaging.saaj.soap.ver1_1.SOAPFactory1_1Impl.cr

eateFault(SOAPFactory1_1Impl.java:76)

        at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11

Fault.java:176)

        ... 7 more

Done.