Comment watch tools that is not going to run when you access since vmware api, while they are installed and running

Hi all

I'm trying to run a command on a virtual machine in windows via the VMware API (vim25.jar) and I get the following error/fault.

com Sun.Xml.Internal.WS.Fault. ServerSOAPFaultException: Client has received the Server SOAP fault: a general error occurred: vix error codes = (3016, 0).

Please see the server log for more details about the exact cause of the failure.

to com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178) ~ [?: 1.8.0_77]

to com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:124) ~ [?: 1.8.0_77]

to com.sun.xml.internal.ws.client.sei.StubHandler.readResponse(StubHandler.java:238) ~ [?: 1.8.0_77]

to com.sun.xml.internal.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:189) ~ [?: 1.8.0_77]

to com.sun.xml.internal.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:276) ~ [?: 1.8.0_77]

to com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:104) ~ [?: 1.8.0_77]

to com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:77) ~ [?: 1.8.0_77]

to com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:147) ~ [?: 1.8.0_77]

to com.sun.proxy. $Proxy54.startProgramInGuest (unknown Source) ~ [?:?]

to com.test.vmware.VmGuestOperations. runProgramInGuest (VmGuestOperations.java:267) ~ [management - 0.0.1.jar:?]

The VIX 3016 error code indicates the tools are not running. However, I check if the tools and running and installed (through the java api) before calling the method "runProgramInGuest".

Please note that this fault is also found in some cases when trying to call the method "listProgramsInGuest".

When the error says, "Please see the server log", what paper I'm supposed to be looking for Guest VM operations?

Curiously, however, this happens on one of the clones of a basic VM. that is, I clone a virtual machine base three times (linked clones) and run a program in the comments. This anomaly is only visible on one of the virtual machines and runs correctly on the other two.

Infrastructure

vCenter - version 6.0.0 build 3339084

ESXi - version 6.0.0 GA, build 2494585

any ideas/suggestions why this seems to happen?

Thanks in advance

Hello

It turns out that the problem is when cloning. Linked clones are created using the diskMoveType the value "CREATE_NEW_CHILD_DISK_BACKING".

But when linked clones have been created using the value 'MOVE_ALL_DISK_BACKINGS_AND_ALLOW_SHARING' diskMoveType the problem no longer occurs.

VMware Tools are installed on the base virtual machine and I understand the basic disk is shared among related clones but I always thought that the basic disk become read only when the linked clones are created. If so, why would be a mistake "tools does not" occurs then? are not just the "vmware tools" files being read from the disk basic and performed by the RAM/vmswp clone? Am I missing something?

Can someone explain why this error occurs when Linked clones are created using 'CREATE_NEW_CHILD_DISK_BACKING '? In addition, a link/document to fully understand the Linked clones would help.

Thanks in advance

Tags: VMware

Similar Questions

Maybe you are looking for