vCenter 4.1/ADAM issues

[AureusStone]

Hi all,

I have had issues adding two vCenter servers to linked mode since upgrading to 4.1.

Hoping to get it fixed I have uninstalled vCenter, removed ADAM and attempted to reinstall.  But I keep getting the error 28038.. refer to jointool-0.log

Now I can't even get it installed.  I had heaps of issues with ADAM previously.

One problem is the jointool-0 file isn't even created.

I have looked at all of the KB articles and tried everything, but it still won't work.

DNS is fine.

Installing with a domain admin account.

I have fixed all of the file permissions/registry permissions to allow the network service access.

Removed Active Directory Lightweight Directory Sercives and ADAM directory.
Copied ldifde.exe from a dc.

Removed old installation directories.

I have even built a new server.  But it still is not working.

Running Server 2008 64bit

My status file in temp has the following.

"
-----------------
Jointool run failed: null

"

Not very helpful.

The only thing I haven't touched is the DB, but everything was working normally before I uninstalled vCenter.

Any ideas?

[AureusStone]

Still can't get it working.

Any ideas?

[DSTAVERT]

This might be an oportunity to talk to VMware. File an SR.

[AureusStone]

Yeah may need to.

I have attempted the install using SQL express and it works fine. 😕

I have given the user account in Oracle DBA rights now and it still will not work.

Is there any entries in the DB that could be causing this?

[AureusStone]

Just an update.

This problem is now resolved.  VMWare support has provided me with a workaround.  I would like to know the cause of this issue, but the main thing is it is working.

Solution from VMWare below.

2. Reinstall the VC 4.1, but this time please do not use existing     
    database but SQL express. It will create a SQL express instance on 
    your VC server, after the install you can remove it.               
                                                                       
3. When it finished, please ensure that the VC service started and you
    can connect to it. The inventory will be empty.                    
                                                                       
4. Stop the VC service and open a regedit                             
                                                                       
5. In Computer -> HKEY_LOCAL_MACHINE -> SOFTWARE -> VMware, Inc. ->   
    VMware VirtualCenter -> DB registry entry you will see 5 field.    
    1. is the name of the ODBC connection, change it to your oracle ODBC
    2. is the username, change it to your oracle username              
    3. password, leave it empty, we will modify later                  
    4. is the ODBC driver, wich is currently "SQL Native Client". Change
       it to "oracle" (no quotes)                                      
    5. is the version, leave it 10.                                    
                                                                       
6. Go to the program directory, which should be C:\Program            
    Files\VMware\Infrastructure\VirtualCenter Server.                  
7. Run "vpxd.exe -p" command which will ask for database password twice
8. Confirm in the registry that the 3rd field is populated with the   
    encrypted password.                                                
9. Try to start the VC service.