VMware

This Question is Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
1 2 3 4 Previous Next 52 Replies Last post: Nov 19, 2009 4:40 PM by rmelo   Go to original post
Click to view VMMaxVM's profile Enthusiast 46 posts since
Aug 13, 2008

Hi There,

If the issue you're facing is still not resolved by applying the steps I provide on June, 29, please let us know ASAP. We want to make sure everything works fine for you.

Thanks.

Max


Click to view altapowder's profile Novice 8 posts since
Dec 31, 2008
I had this same issue yesturday and I tried all of the suggestions above and none of them worked. I contacted tech support yesturday and we were able to fix this. The issue was that our SA password on our SQL server had a semicolon ;; in the password. We changed the SA password so it no longer had a semi colon and the setup worked perfectly.
Click to view sunvmman's profile Enthusiast 78 posts since
Jun 26, 2008
yes, they came back with that answer to me also. i didn't try it, but glad you confirming that is the problem.
Click to view VMMaxVM's profile Enthusiast 46 posts since
Aug 13, 2008

Thanks. After you try, please let us know if it also works for you. We will fix this in next release.

Regards,

Max

Click to view rhcllp's profile Lurker 1 posts since
Jul 16, 2009
I ran into the same error.

The Applicaition event log told me to look at the status.txt, which said that it couldn't find a particular .exe in the C:\Windows\ADAM folder; I had ADAM on my system and had previously uninstalled it; however, it left a C:\Windows\ADAM folder.

After discovering this left-over folder, I blew away this folder, reinstalled ADAM from the vSphere REDIST folder, and then the vCenter install ran just fine.

I hope this helps.

Click to view Lukas_CZ's profile Lurker 2 posts since
Dec 11, 2005
I had same problem on Win2k8 std x64 and Oracle database. Semicolon";" in password caused installator fail on installing ADAM instance. If password was changed install works perfectly.
Click to view jwalsh's profile Novice 7 posts since
Jun 14, 2007

I have seen one instance where this error was caused by the rui.crt having text before the "-----BEGIN CERTIFICATE-----" section.

Example:


Certificate:
Data:
Version: 3 (0x2)
Serial Number: 1048580 (0x100004)
Signature Algorithm: sha1WithRSAEncryption
<snip>
-----BEGIN CERTIFICATE-----
<snip>
-----END CERTIFICATE-----

It may be worth editing the rui.crt file so it just contains the section between "-----BEGIN CERTIFICATE-----" and "-----END CERTIFICATE-----", inclusive, like this:

-----BEGIN CERTIFICATE-----
<snip>
----END CERTIFICATE-----
Click to view rmelo's profile Lurker 1 posts since
Jun 9, 2006
Adding Lightweight LDAP was more than enough on W2K8 STD 64bit.

VMware Developer

SDKs, APIs, Videos, Learn and much 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

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities