VMjkasalVM's Posts

I ran in to the exact same issue yesturday while updating VMware tools. The only fix I found was probably the same you found which has a VMware KB article dedicated to it found here. http://kb... See more...
I ran in to the exact same issue yesturday while updating VMware tools. The only fix I found was probably the same you found which has a VMware KB article dedicated to it found here. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2007298 The cause only states "This error occurs because the virtual machine is missing a necessary setting." What is the missing setting??? This must be a bug or over looked compatability issue. It seems that this issue has only popped up recently in my enviornmennt. It is also only occuring on VMs that were created in vSphere 4 (4.1) and migrated to esxi 5.0 GA hosts. And another curve ball, not all VMs are experiancing this in my enviornment. Only a few thus far. I know vsphere 5.0 up1 was released last thurdsday (March 15, 2012) maybe there is a fix there. I have not read the release notes in great detail yet, but I don't see any mention of this as a known issue or resolved issue. Release notes for 5.0 up1: http://www.vmware.com/support/vsphere5/doc/vsp_esxi50_u1_rel_notes.html#resolvedvmwaretools Not a solution, but your not alone atleast
ASW20ST, thanks for the workaround. Your solution worked for me too. You and I have the exact same setup except the OVA was on my D:\ (Secondary Drive) Looks like a possible bug somewhere. VMw... See more...
ASW20ST, thanks for the workaround. Your solution worked for me too. You and I have the exact same setup except the OVA was on my D:\ (Secondary Drive) Looks like a possible bug somewhere. VMware must be looking for the zlib1.dll in the wrong location.
The new ISO is out. The release note mention that this was fixed. https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=HPVM09 **Edit** I just heard from a buddy of... See more...
The new ISO is out. The release note mention that this was fixed. https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=HPVM09 **Edit** I just heard from a buddy of mine that the link still goes to the Aug version. I click the link now and I too get the Aug version. Their load balancers might not be working correctly or changes are syncing. Try back later maybe. What I downloaded was the following... VMware vSphere Hypervisor 5 (ESXi) and Updates - 5.0 Sep2011 ESXi HD-USB-SDImgeInstlr (Z7550-00235.iso)
I think this maybe an issue with my templates. A freshly installed OS works. Thanks
Here is the failure in the log. VMware: Srm::Installation::Utility::ReadFromPipe: INFORMATION: Command output: VMware: Srm::Installation::Utility::LaunchApplication: INFORMATION: Executable ... See more...
Here is the failure in the log. VMware: Srm::Installation::Utility::ReadFromPipe: INFORMATION: Command output: VMware: Srm::Installation::Utility::LaunchApplication: INFORMATION: Executable finished executing. Result code=0 VMware: Srm::Installation::DirectoryChanger::~DirectoryChanger: INFORMATION: Restored directory. Directory=C:\Windows\SysWOW64 VMware: Srm::Installation::VMInstallCertificate: INFORMATION: Certificate installed successfully. VMware: Srm::Installation::Utility::LaunchApplication: INFORMATION: Launching executable. Command line="C:\Program Files (x86)\VMware\VMware vCenter Site Recovery Manager\external\perl-5.8.8\bin\perl.exe" -p -iBAK -e "s|()||" "C:\Program Files (x86)\VMware\VMware vCenter Site Recovery Manager\config\extension.xml" VMware: Srm::Installation::Utility::ReadFromPipe: INFORMATION: Command output: VMware: Srm::Installation::Utility::ReadFromPipe: INFORMATION: Command output: VMware: Srm::Installation::Utility::LaunchApplication: INFORMATION: Executable finished executing. Result code=0 VMware: Srm::Installation::VMModifyXmlAdminEmail: INFORMATION: extension.xml modified successfully. VMware: Srm::Installation::Utility::LaunchApplication: INFORMATION: Launching executable. Command line="C:\Program Files (x86)\VMware\VMware vCenter Site Recovery Manager\external\perl-5.8.8\bin\perl.exe" C:\PROGRA 2\VMware\VMware vCenter Site Recovery Manager\external\perl-5.8.8\bin\reloc_perl -a -i -t C:\PROGRA 2\VMware\VMware vCenter Site Recovery Manager\external\perl-5.8.8 VMware: Srm::Installation::Utility::ReadFromPipe: INFORMATION: Command output: VMware: Srm::Installation::Utility::ReadFromPipe: INFORMATION: Command output: Can't open perl script "C:\PROGRA~2\VMware\VMware": No such file or directory VMware: Srm::Installation::Utility::LaunchApplication: INFORMATION: Executable finished executing. Result code=2 VMware: Srm::Installation::Utility::GetMsgFromErrorTable: ERROR: MsiGetActiveDatabase() failed. Trying MsiOpenDatabase(). VMware: Srm::Installation::Utility::GetMsgFromErrorTable: INFORMATION: Error message is Failed to update Perl installation directories.%n%nDetails:%n VMware: Srm::Installation::Utility::GetMsgFromErrorTable: ERROR: MsiGetActiveDatabase() failed. Trying MsiOpenDatabase(). VMware: Srm::Installation::Utility::GetMsgFromErrorTable: INFORMATION: Error message is %n%nPress Retry to try again or press Cancel to exit installation. VMware: Srm::Installation::Utility::GetMsgFromErrorTable: ERROR: MsiGetActiveDatabase() failed. Trying MsiOpenDatabase(). VMware: Srm::Installation::Utility::GetMsgFromErrorTable: INFORMATION: Error message is VMware vCenter Site Recovery Manager VMware: Srm::Installation::Utility::GetInstallerWnd: ERROR: GetMsiProperty(ProductName) failed. Trying alternate method. VMware: Srm::Installation::Utility::GetInstallerWnd: INFORMATION: Attaching to window with title "VMware vCenter Site Recovery Manager" Next I will test using Win 2k3 R2 x64 and see if the error occurs. I have now tried on several vms in several enviornments (used different templates) and can reproduce the error everytime.
I have tried both installing from a UNC and local. Both cause the error.
Wrong button was pushed, this has not been fixed (Casualty of having a 3 year old) I tried Disabling UAC and the exact same issue occurs.
I am getting an error when I try and install SRM. It gets almost to the end and then an error occurs stating the following. Failed to Update Perl installation directories. Details: Can’t ope... See more...
I am getting an error when I try and install SRM. It gets almost to the end and then an error occurs stating the following. Failed to Update Perl installation directories. Details: Can’t open perl script “C:\PROGRA~2\VMware\VMware”: No Such file or directory Press Retry to try again or press Cancel to exit installation. Here are the environmentals: I am running a Windows 2008 R2 VM with SQL 2008 Ent R1 64bit installed. 1 vCPU, 2GB RAM, 40GB C:, 10GB Installer used – Vmware-srm-4.1.0-267817 I am installing to “C:\Program Files (x86)\VMware\VMware vCenter Site Recovery Manager\”. **Note that the difference between the install path and the error path. The installer is truncating the directory path. I have tried installing to multiple locations including the and also changing the directory structure names thinking the lengths of the directories had something to do with it. No matter what the directory names are, the installer truncates the path. I am running the installer with admin privileges (R Click, Run as Admin) and have also tried running the installer in compatibility mode. I have also attempted to resolve the issue using the suggestion located below with no luck. Does anyone have any ideas? I’ve searched high and low and havn’t found a solution. Thanks JKasal
In case someone stumbles apon this post. I too had the same issue only on ESX 4 (Classic). The fix for me was restarting the management services on the recieving host (Host where the VMs were mi... See more...
In case someone stumbles apon this post. I too had the same issue only on ESX 4 (Classic). The fix for me was restarting the management services on the recieving host (Host where the VMs were migrating too.) service mgmt-vmware restart service vmware-vpxa restart
Thanks Java. These helped a ton!
Oh Wow! That will help. Is there anyway to perform these actions remotely (Excluding iLO, DRAC etc..) Thanks Joe
Hey Guys, Hoping someone can help me out here. Can you perform a vmkping in anyway from an ESXi 4 host, is so How? I'm starting to make the switch from ESX 4 classic to ESXi and PowerCL... See more...
Hey Guys, Hoping someone can help me out here. Can you perform a vmkping in anyway from an ESXi 4 host, is so How? I'm starting to make the switch from ESX 4 classic to ESXi and PowerCLI and I ran into a command road block Thanks, Joe
My enviornment too has been bit by this bug. I've contacted VMware and there is still not bug fix. The issue still remains even in Updated 1. Only the work around is a viable solution. For good m... See more...
My enviornment too has been bit by this bug. I've contacted VMware and there is still not bug fix. The issue still remains even in Updated 1. Only the work around is a viable solution. For good measure, here is a link to the official KB article. http://kb.vmware.com/kb/1011294 VMware also stated they have seen many calls on this issue. Come on VMware lets get this one patched!
Yup ran into the exact same issue after a HW upgrade on 2K8. I even ran into an issue updating the VMware tools in windows Server 2008 64bit. I had to manually force an uninstall and then manua... See more...
Yup ran into the exact same issue after a HW upgrade on 2K8. I even ran into an issue updating the VMware tools in windows Server 2008 64bit. I had to manually force an uninstall and then manually reinstall the tools. Here is the link to the thread that discusses that part.... http://communities.vmware.com/message/1285631#128563. Sorry slight tangent there... Back to the issue at hand, did the Techs ever send you that KB article? Thanks
I too am getting the Same error. By any chance, did any of you Install Windows 2008 64 Bit using the Vista 64bit VM option? The Guests I am having issues with were setup this way. I am wonderin... See more...
I too am getting the Same error. By any chance, did any of you Install Windows 2008 64 Bit using the Vista 64bit VM option? The Guests I am having issues with were setup this way. I am wondering if the work around for Early adopters of Win2k8 screwed our selves by Creating Vista 64 Bit VMs to install Win2K8 on. Thoughts? Jkasal