I am creating my new lab. I installed VM's for DC, SQL2008R2 and vCenter.
I had problems with installing SSO on vcenter server, which I finally resolved.
I installed vCenter Server and it was working OK, until I restarted the server. In the mean time I added more memory to vCenter VM, but it should not have any influence, since vCenter SSO service is starting without problems. SQL is on different server and is started.
Only VMWare VirtualCenter Server and VMWare VirtualCenter Management WebServices are failing to start with vendord specific error 2.
vpxd.log is attached.
Am I the only one who thinks VMWare made new vCenter installation too complicated?
Aparently making any hardware changes to your VC server can cause vcenter service's connection to SSO to fail.
Besides what Asnivor mentions, you have following in your error log: [Vpxd::ServerApp::Init] Init failed: Ldap error
Check if your DNS is configured correclty, can you resolve the FQDN correctly?
Asnivor: Tried that and it didn't help.
spravtek: I was looking at LDAP problem from AD perspective. (DNS is working A/PTR are configured using DHCP DDNS)
I even added "LAB\vcadmin" (AD user under which VMWare VirtualCenter server Service is running) into Domain Admins, because I thought it is trying to change something in LDAP/AD.
Your answer helped me to find the problem. It was similar to problem you pointed out.
It wasn't com.vmware.vcIntegrity key in ADSI Edit. vpxd-xx.log pointed me that I have instance of service created with name CN=5a58bc84-5f0e-4cd1-933e-70b3cfad4937 and because of the existing instance, it is failing to create new instance with same name.
So, the resolution was:
Open ADSI Edit, Connect with same info from your link (Eg localhost:389...)
Open "DC=virtualcenter,dc=vmware,dc=int", open "OU=Instances", not "OU=Health". Delete container "CN=5a58bc84-5f0e-4cd1-933e-70b3cfad4937"