I found the log files and found this:
09-23-2010,19:43:12 : Action 19:43:12:
09-23-2010,19:43:12 : Action start 19:43:12:
09-23-2010,19:43:12 : An unexpected error occured while
installing Symantec Private Branch Exchange. The error desfcription follows:
Error Number : -2147217406 Error Description: Source: Method Name:
noteDepSvcsWeStop Operation : Creation of winmgmts object for handling
09-23-2010,19:43:12 : Action ended 19:43:12:
noteDepSvcsWeStop.B2D5B6C9_4698_42F7_AC9D_955789A69556. Return value 3.
09-23-2010,19:43:12 : Action ended 19:43:12: INSTALL.
Return value 3.
I am working with our Windows engineering support team
right now to see how we can get the client installed.
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of David
Sent: Friday, September 24, 2010 5:58 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Windows Client install blows upduring the
I had this happen with a W2K system that had some corruption
in its WMI config.
I wiped out the WMI registry on the system, rebooted and then the install went
Evidence for this was found looking around the log files. I don't recall the
exact steps I needed to do, but can look for my notes.
We don't have any W2K systems to worry about any longer.
On 9/24/2010 2:51 PM, judy_hinchcliffe AT administaff DOT com
And just have an administrator run it is not the same.
I have an admin account and I still have to right click and
say run as administrator some times.
Judy's recommendation to "run as administrator" is
a good one. That an older version was uninstalled makes the hair on the
back of my neck tingle ... because of the uninstall, I recommend a Windows
reboot before installing 6.5 ... and if anything NBUish happens on the reboot,
reboot again. Turn Anti-Virus off temporarily and try the install again.
(I don't have a lot of Windows machines either, but these (3) actions
have allowed the NBU 6.5 install to complete for me (when it didn't on the
machine owner's first try).
I've had it suggested from someplace that defining a policy
for the client and opening the vnetd port (13724) first is needed, but that has
NOT been true for my cases (I usually open the firewalls after install and
define an NBU policy after that).
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu