vCenter 5.1 Install fails to validate Inventory service with SSO Admin

[DSeaman]

I've been working through a fresh install of vCenter 5.1 and writing a series of blog posts ( http://derek858.blogspot.com/2012/09/vmware-vcenter-51-installation-part-1.html ) along the way documenting the entire process. I ran into several problems, was able to overcome them, but I've now run into a roadblock that I need some help with.

Configuration is:

Remote SQL 2008 R2 database

Single Server 2008 R2 VM for all vCenter services

Utilized the "manual" install process for SSO, Inventory service and vCenter server

Replaced untrusted SSL certificates with trusted certs as I installed each service

Installed SSO service as a primary node for a future "HA" cluster

All seemed to be working just fine until I was going through the vCenter 5.1 installation process. I got most of the way through the wizard until I got to the "vCenter Inventory Service Information" screen. The lookup service URL was correct and so was the Inventory service URL. Note: This is AFTER you input the SSO administrator name and lookup service URL, which validate just fine. When I click next I get:

Setup failed to validate VMware vCenter Inventory Service, error occurred while talking to the vCenter Single Sign on admin service."

In the vminst.log file I found:

VMware VirtualCenter-build-799731: 09/16/12 11:38:55 Util_GetParentPath returns C:\Users\svc-vctr02-001\AppData\Local\Temp.
VMware VirtualCenter-build-799731: 09/16/12 11:38:55 Command line to execute -action validate_register -isurl https://D001VCTR02.contoso.net:10443 -lookupserviceurl https://D001VCTR02.contoso.net:7444/lookupservice/sdk
VMware VirtualCenter-build-799731: 09/16/12 11:38:55 Launching without console output capture.
VMware VirtualCenter-build-799731: 09/16/12 11:38:55 Util_Launch::Wait: 1 Hide: 1
VMware VirtualCenter-build-799731: 09/16/12 11:38:55 Found "C:\Users\svc-vctr02-001\AppData\Local\Temp\{A4400513-2688-45A9-8439-CA991F4E4106}\jre\bin\java.exe"
VMware VirtualCenter-build-799731: 09/16/12 11:39:01 Process returned 6
VMware VirtualCenter-build-799731: 09/16/12 11:39:01 Util_Launch::done Res: 1
VMware VirtualCenter-build-799731: 09/16/12 11:39:01 Return code is 6 (successful operation however may not                    necessarily need return code 0.
VMware VirtualCenter-build-799731: 09/16/12 11:39:01 An error occurred while talking to the SSO admin service Res: 6
VMware VirtualCenter-build-799731: 09/16/12 11:39:01 ExecuteISCmd::done Res: 26009
VMware VirtualCenter-build-799731: 09/16/12 11:39:01 VMValidateISInfo::IS Validation Not Successful
VMware VirtualCenter-build-799731: 09/16/12 11:39:01 Setting property IsInfoOk =
VMware VirtualCenter-build-799731: 09/16/12 11:39:01 Getting Property UILevel = 5
VMware VirtualCenter-build-799731: 09/16/12 11:39:01 Getting Property ProductName = VMware vCenter Server

In the vcregtool.log I found:

[2012-09-16 11:39:01,675 main  DEBUG com.vmware.vim.vmomi.client.http.impl.ClientFactory] Creating HTTP client with following properties:
End point: https://D001VCTR02.contoso.net:10443/vmomi/sdk/
Thread pool: null
Result interceptor: null
[2012-09-16 11:39:01,675 main  DEBUG com.vmware.vim.vmomi.client.http.impl.CompiledHttpConfiguration] Reserving CompiledHttpConfiguration@19182761 to Client@282117077
[2012-09-16 11:39:01,862 main  ERROR com.vmware.vim.dataservices.vcregtool.RegisterVC] Error communicating with SSO Admin Service
java.lang.NullPointerException
at com.vmware.vim.dataservices.vcregtool.RegisterVC.parseSslTrustAnchor(RegisterVC.java:591)
at com.vmware.vim.dataservices.vcregtool.RegisterVC.createAdminClient(RegisterVC.java:774)
at com.vmware.vim.dataservices.vcregtool.RegisterVC.validateRegister(RegisterVC.java:245)
at com.vmware.vim.dataservices.vcregtool.RegisterVC.doRegistrationValidation(RegisterVC.java:1318)
at com.vmware.vim.dataservices.vcregtool.RegisterVC.main(RegisterVC.java:1334)
[2012-09-16 11:39:01,862 main  DEBUG com.vmware.vim.vmomi.client.http.impl.CompiledHttpConfiguration] Removing Client@282117077 reference from CompiledHttpConfiguration@19182761, 0 active clients left.
[2012-09-16 11:39:01,862 main  DEBUG com.vmware.vim.vmomi.client.http.impl.CompiledHttpConfiguration] Shutting down CompiledHttpConfiguration@19182761 as there are no more clients.
[2012-09-16 11:39:01,862 main  ERROR com.vmware.vim.dataservices.vcregtool.RegisterVC] Failed to perform validate_register action
com.vmware.vim.dataservices.vcregtool.exception.RegistrationException
at com.vmware.vim.dataservices.vcregtool.RegisterVC.createAdminClient(RegisterVC.java:785)
at com.vmware.vim.dataservices.vcregtool.RegisterVC.validateRegister(RegisterVC.java:245)
at com.vmware.vim.dataservices.vcregtool.RegisterVC.doRegistrationValidation(RegisterVC.java:1318)
at com.vmware.vim.dataservices.vcregtool.RegisterVC.main(RegisterVC.java:1334)

VMware VirtualCenter-build-799731: 09/16/12 11:46:20 End Logging

Anyone have ideas?

[DSeaman]

Instead of trying to troubleshoot, I completely blew away the entire vCenter 5.1 installation and started over. I got past the error in this post, but now stuck at the error someone else got over here: http://communities.vmware.com/message/2115369?tstart=0

Certainly by far the most troublesome vCenter install in history....

[legaultp1]

hello

i got the same problem however, i managed to fix it

here how i did it.

i uninstalled then reinstalled the inventory service which fixed the issue.

after that, i managed to install the vcenter server.

Regards

[edwardm007]

I had the same issue during an upgrade to 5.0.1b.  I installed SSO on a separate dedicated server, then upgrade Inventory Service.  I did not reboot, then upgraded vCenter Service.  It said it couldn't validate Inventory Service.  In services I saw that Inventory Service was in a disabled state and when I tried to start, it said the service had been marked for deletion.  I rebooted at that time.  After reboot, there was no Inventory Service listed, but it showed up in Programs.  I uninstalled, reinstalled, it still found my original Inventory Service database file and was able to proceed with VC upgrade.