Hi mtnbiker5;
The problem is that your VMwareVCMSDS service did
not start after creation, or you have trouble connecting on the LDAP port specified
during install (Do you have a firewall configuration that somehow
blocks local loopback ports?)
Let's diagnose that further. I presume you are using Windows 2003.
If you have any logs in C:\Windows\Debug\adam*, please zip them up and upload them someplace.
The rollback action on install failure might have removed those logs as well - If you cannot find them, try the following to make sure that those logs are generated and not removed by the VC installer:
Create a dummy VMwareVCMSDS instance manually as follows
Control Panel -> Add/Remove programs -> Remove
ADAM instance VMwareVCMSDS (if it already exists)
Start->Programs->ADAM->Create a new instance
Screen 1:
Choose "A unqique instance"
Screen 2: Enter instance name as
"VMwareVCMSDS"
needs to be exactly that
Screen 3:
LDAP Port: Same as the one you chose during VC install (default is 389)
SSL Port: Same as the one you chose during VC install (default is
636)
Screen 4: Create an application data partition for the following partition: "dc=virtualcenter,dc=vmware,dc=int"
Screen 5: For both of the fields "Data
files" and "Data recovery files", set the location as C:\Program
Files\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS (essentially <VC-install-dir>\VMwareVCMSDS).
Screen 6: Leave option as "Network Service"
Screen 7: Leave option as "Current logged
on user"
Screen 8: Leave option as "Do not import LDIF files..."
Once thats done and the instance install completes, verify if the VMwareVCMSDS service comes up (Look at Service manager (services.msc)).
If the service refuses to startup, you should definitely be able to find
logs in the above mentioned directory which would yield more debug info
for us.
If the service is running, run "netstat -a -b" from the command and dump the output of that for the '
http://dsamain.exe' process here, and we'll take it from there.
Thanks.
