VMware

This Question is Answered

1 "helpful" answer available (6 pts)
14 Replies Last post: May 7, 2009 7:15 AM by KWROBE  

VMware Tools Won't Upgrade after ESX 3.5 Update 4 posted: Apr 9, 2009 6:22 AM

Click to view KWROBE's profile Novice 17 posts since
Nov 10, 2008

I just updated our ESX 3.5 hosts to Update 4 and now our VMs show there is an update for VMware Tools. However, the update fails right near the end of the upgrade with a Error 1722.

Any thoughts on what could be causing this?

-Ken

Click to view A13xxx's profile Enthusiast 37 posts since
May 8, 2008
have you tried removing the current tools and then installing the new ones from fresh
Click to view A13xxx's profile Enthusiast 37 posts since
May 8, 2008

I had this the other day, the first solution worked for me but on my other server i had to manually copy the installer files of the mounted drive to the local drive of the VM and install from there. That worked, have you tried copy to local and install from there?
Click to view A13xxx's profile Enthusiast 37 posts since
May 8, 2008
have you tried checking and updating the vmware tools before power on in the vm settings?

Re: VMware Tools Won't Upgrade after ESX 3.5 Update 4

7. May 6, 2009 12:54 PM in response to: KWROBE
Click to view muchacho's profile Novice 2 posts since
May 6, 2009
The solution that works for me for this error at this VM (Windows 2003 OS) was to start the following services.

  • Distributed Transaction Coordinator. (usually a culprit for installation failures that i have found anyway...)
  • COM+ System Application.

If these services where not started, start this services and retry the update or install.
You can stop these services (if you want) after the installer has finished
Click to view RParker's profile Champion vExpert 5,784 posts since
Dec 6, 2006
* Distributed Transaction Coordinator. (usually a culprit for installation failures that i have found anyway...)
* COM+ System Application.

Neither of which affect Windows Installer service, because those services are not even running..... Windows installer errors are mostly caused by temp files from previous installations, that interfere with current installations. Cleaning out the temp in many cases, or change the temp location can fix it.

1722 is a generic error it happens on any Windows installer, not just VM Ware tools, so it's something else at the OS level, it could be memory problems, or swap / disk space free, corrupt data, lots of things. But the above services are not related.

http://s254920738.onlinehome.us/resources/VMW_Q109_LGO_vExpert_k.jpg

Click to view muchacho's profile Novice 2 posts since
May 6, 2009
I Start those services and then and only then could I install VMware tools. Another example, you can not install SQL unless Distributed Transaction Coordinator is enabled and running...
Click to view RParker's profile Champion vExpert 5,784 posts since
Dec 6, 2006
I Start those services and then and only then could I install VMware tools. Another example, you can not install SQL unless Distributed Transaction Coordinator is enabled and running...

That's called 'dependencies'.. Service A needs service B which needs Service C running. Since service C isn't running, at the time service B starts, it starts. A starts, and sees that B is now running because C is now started.

But C does not depend on B or A to run, hence your scenario. It was a trigger to start a chain of events. But SQL server needs neither to run, as I said, neither of these are running, both manually started, but neither start at the time MSI runs.

What does Distributed Transaction Coordinator do?

The Distributed Transaction Coordinator (DTC) service coordinates transactions that update two or more transaction-protected resources, such as databases, message queues, files systems, and so on. These transaction-protected resources may be on a single computer or distributed across many networked computers.

You might need it to RUN SQL, but not install MSI installations.

http://s254920738.onlinehome.us/resources/VMW_Q109_LGO_vExpert_k.jpg

Click to view COS's profile Expert 725 posts since
Dec 12, 2005
I would try to uninstall the the tools, bounce the VM gracefully then re-install.
Of course if you haven't already.

Also, make sure on every VM, you disconnect all their CD-ROM devices. Not only just by unchecking "Connected" and/or "Connect at power on" but ALSO Select "Client Device".

Click to view marvinms's profile Enthusiast 94 posts since
Jun 28, 2007

When I ran into this issue, I found that if I was logged onto the VM (Windows) while I installed the Tools, it worked.

The may account for the service being started or my logon authorization allow it to run.

VMware Beta Programs

Want to be Considered for Future Beta Programs?

Learn More

VMware Developer

Download SDKs, APIs, videos,
training, and more in the Developer community.

Learn More

Developer
Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld
Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

Only VMware ... Delivers Nexus 1000V

Ensure consistent, policy-based network capabilities to virtual machines across your data center.

Learn More

Communities