VMware Cloud Community
KennyMacCormik
Enthusiast
Enthusiast
Jump to solution

vCenter Server 6.0 Update 1b installation failure

Greetings,

I'm trying to install vCenter 6.0 to Windows Server 2012 R2 (all latest patches applied). I'm choosing Embedded instalation with Postgres DB. But the installation fail with the following erro message

"com.vmware.cisreg.sso_connection": "Unable to connect to vCenter Single Sign-On: Failed to connect to SSO; uri:https://IVAVC1.IVA.local/sso-adminserver/sdk/vsphere.local"

vminst.log states following

2018-01-25 17:29:02.688+03:00| vcsInstUtil-3343021| I: Leaving function: ParseStatusFile

2018-01-25 15:28:56.277+03:00| vcsInstUtil-3343021| I: Entering function: ParseStatusFile

2018-01-25 15:28:56.277+03:00| vcsInstUtil-3343021| I: ParseStatusFile: curr error msg: "Unable to connect to vCenter Single Sign-On: Failed to connect to SSO; uri:https://IVAVC1.IVA.local/sso-adminserver/sdk/vsphere.local"

2018-01-25 15:28:56.277+03:00| vcsInstUtil-3343021| E: ParseStatusFile: Displaying error message for "com.vmware.cisreg.sso_connection": "Unable to connect to vCenter Single Sign-On: Failed to connect to SSO; uri:https://IVAVC1.IVA.local/sso-adminserver/sdk/vsphere.local"

2018-01-25 15:54:21.578+03:00| vcsInstUtil-3343021| I: Entering function: ShowMessageQueue

2018-01-25 15:54:21.578+03:00| vcsInstUtil-3343021| I: Leaving function: ShowMessageQueue

2018-01-25 15:54:21.578+03:00| vcsInstUtil-3343021| I: Entering function: ShowMessageQueue

2018-01-25 15:54:21.578+03:00| vcsInstUtil-3343021| I: Leaving function: ShowMessageQueue

2018-01-25 15:54:21.578+03:00| vcsInstUtil-3343021| I: ParseStatusFile: got error or success

vc-install.txt

  [44] vmware-vws.msi                   2018-01-25 15:20:16 [00:00:04]

  [45] vcsservicemanager.msi            2018-01-25 15:20:20 [00:43:52]

  [46] revert-transaction               2018-01-25 16:04:12

.NET Framework 3.5 installed and patches as well. There is no onther software on this server. This is clean installation right after server was deployed. We've tried to redeploy server but this was not very helpful.

Tags (1)
Reply
0 Kudos
1 Solution

Accepted Solutions
daphnissov
Immortal
Immortal
Jump to solution

I have to strongly recommend that you deploy the vCSA rather than the legacy Windows-based vCenter. Moving forward, Windows will not be available as a platform and so it's end of life. It's also way easier to deploy and configure the vCSA and so you could side-step this whole issue entirely.

View solution in original post

Reply
0 Kudos
4 Replies
daphnissov
Immortal
Immortal
Jump to solution

Out of curiosity, why are you installing a new Windows-based vCenter instead of deploying the appliance? Secondarily, why installing such an old build of vCenter 6.0 rather than the latest?

Reply
0 Kudos
KennyMacCormik
Enthusiast
Enthusiast
Jump to solution

Hi

I'm installing windows vCenter because I'm used to it.

I'm using such old build beacause U3 1d failed with the same error. U3 either.

Reply
0 Kudos
daphnissov
Immortal
Immortal
Jump to solution

I have to strongly recommend that you deploy the vCSA rather than the legacy Windows-based vCenter. Moving forward, Windows will not be available as a platform and so it's end of life. It's also way easier to deploy and configure the vCSA and so you could side-step this whole issue entirely.

Reply
0 Kudos
KennyMacCormik
Enthusiast
Enthusiast
Jump to solution

Ok, thank you for the information. I will try installing vCSA.

Reply
0 Kudos