VMware Workspace ONE Community
nonsparker
Enthusiast
Enthusiast
Jump to solution

Connector Activation problem

I have tried to deploy workspace a few times and I get this error whether I use an internal or External data base. Can anyone help?

WorkspaceError.png

I have removed the extensions from the vCenter server from previous installs, I have used the vFabric Postgres external DB, changed the dns names of the va servers. Is there anything else to try?

Twitter @thickguythinapp
Website thickguythinapp.com
Reply
0 Kudos
1 Solution

Accepted Solutions
nonsparker
Enthusiast
Enthusiast
Jump to solution

I ended up redeploying with totally different IP addresses and it worked. I may have had an IP conflict or something. Thanks for the help!

Twitter @thickguythinapp
Website thickguythinapp.com

View solution in original post

Reply
0 Kudos
10 Replies
oivinde
Enthusiast
Enthusiast
Jump to solution

I've had this issue once, but after verifying that IP-Pool in vCenter was correctly configured (used static IP's on the appliances, so stay clear of the scope in the IP-pool), and cleaned up and recreated (and verified) the DNS-records (and PTR), including configuring split DNS for the gateway-va, problem was gone.

br

Oivind

Reply
0 Kudos
nonsparker
Enthusiast
Enthusiast
Jump to solution

I just double checked those, and they are all correct. The IP Pool set up correctly and the va machines are using static IPs. The PTR and DNS records are correct.

Twitter @thickguythinapp
Website thickguythinapp.com
Reply
0 Kudos
sravuri
VMware Employee
VMware Employee
Jump to solution

Do you see anything relevant in configurator or connector logs?

configurator VA: /opt/vmware/horizon/configuratorinstance/logs/configurator.log

connector VA: /opt/vmware/c2/c2instance/logs/connector.log

Reply
0 Kudos
nonsparker
Enthusiast
Enthusiast
Jump to solution

Here are the config logs, sorry the image is so big 

Screenshot_5_9_13_12_04_PM.png

Twitter @thickguythinapp
Website thickguythinapp.com
Reply
0 Kudos
sravuri
VMware Employee
VMware Employee
Jump to solution

can you also include connector log?

Reply
0 Kudos
nonsparker
Enthusiast
Enthusiast
Jump to solution

here it is

Screenshot_5_9_13_12_09_PM.png

Twitter @thickguythinapp
Website thickguythinapp.com
sravuri
VMware Employee
VMware Employee
Jump to solution

Looks like the connector is not able to access the horizon.data-strategy.com. Is that the FQDN? Does the FQDN have a PTR record?

Reply
0 Kudos
nonsparker
Enthusiast
Enthusiast
Jump to solution

It seems like the connector can not contact the gateway. I tried to ping and browse to the URL and i got nothing

Twitter @thickguythinapp
Website thickguythinapp.com
Reply
0 Kudos
nonsparker
Enthusiast
Enthusiast
Jump to solution

Yes it is the FQDN and it does have a PTR

Twitter @thickguythinapp
Website thickguythinapp.com
Reply
0 Kudos
nonsparker
Enthusiast
Enthusiast
Jump to solution

I ended up redeploying with totally different IP addresses and it worked. I may have had an IP conflict or something. Thanks for the help!

Twitter @thickguythinapp
Website thickguythinapp.com
Reply
0 Kudos