vRO 6.0.1 mac osx client install issues. Cannot connect to host message after install.

[qc4vmware]

I can't seem to get the client to install on my mac and I am out of ideas as to what is going on.  The 5.5.2 client seems to be working fine and if I stream the 6.0.1 client down that also seems to work.  I just can't get the local install to run.  I always get the message "Cannot connect to host" when I try to run it.  If I revert back to the 5.5.2 client it works fine and I can connect to my 5.5.2 instances.

OSX version 10.10.2

Java version 7 update 75 (at least that is the last installer I ran, jdk installed shows at 1.6.0 in /System/Library/Java/JavaVirtualMachines)

I am also seeing this error in the install log :

Install Uninstaller:      vRealize Orchestrator (Install All Uninstaller Components)

                          Status: ERROR

                          Additional Notes: ERROR - Error installing uninstaller: java.util.zip.ZipException: error in opening zip file

Because if this it doesn't seem like the uninstall app runs and I have had to manually back out the install (of which I might be leaving some residue).  I am manually removing the .vmware file from my home directory and also removing ~/Library/Preferences/.com.zerog.registry.xml then removing the orchestrator directory from the applications folder before re-running the client install.

Paul

[Burke- · Accepted solution]

Paul, please file an SR on your side. Feel free to reference the bug I submitted (1409281) when I had the same issue. Customer filed SRs help push resolutions

-- Burke Azbill

[tschoergez]

This is a known issue for the 6.0.1 client 😞 (Internal Bug nr: 1409281)

Unfortunately I am not aware of any workaround, except using Java 1.7 and use the vRO WebStart client for 6.0.1

Regards,

Joerg

[qc4vmware]

:smileyconfused: *sigh* I guess I really have to get around to my beta testing so this stuff doesn't slip through the cracks... This is super frustrating for me.  Thankfully I also have Fusion on my system and can run the windows client which seems to be working.  I'll go ahead and log a bug for it.

[qc4vmware]

Is there any chance someone can update the "Known Issues" section of the release notes so others don't spend 4 hours of their weekend putzing around with this issue?

[cdecanini_]

When you open the SR please mention that this known issue is not mentioned in the release notes and that a bug should be open so the doc team fixes it.

[qc4vmware]

I updated my case and requested the release notes get updated.