VMware Workspace ONE Community
routerlin
Contributor
Contributor

horizon workspace configurator-va 400 bad request

When config database connection , configurator-va report 400 bad request .

what ever internal database connection or external database connection.

Horizon version is  1.5.0.0 build 1220937。

0 Kudos
4 Replies
sravuri
VMware Employee
VMware Employee

Can you send the log files from configurator-va and service-va?

configurator-va: /opt/vmware/horizon/configuratorinstance/configurator.log

service-va: /opt/vmware/horizon/horizoninstance/logs/horizon.log

Also, check if tcserver is running in service-va:

service horizon-frontend status

0 Kudos
routerlin
Contributor
Contributor

service-va:~ # service horizon-frontend status

Status-ing tcServer

INFO Instance name:      horizoninstance

INFO Script directory:   /usr/local/tcserver/vfabric-tc-server-standard

INFO tc Runtime location:/usr/local/tcserver/vfabric-tc-server-standard

INFO Instance base:      /opt/vmware/horizon

INFO Binary dir:         /usr/local/tcserver/vfabric-tc-server-standard/tomcat-6.0.35.A.RELEASE

INFO Runtime version:    6.0.35.A.RELEASE

INFO Script version:     2.6.4.RELEASE

STATUS Instance is RUNNING as PID=2849

By the way, I had update workspace to 1.5.0 build 1318295,but  the error same.

0 Kudos
routerlin
Contributor
Contributor

The DNS (forward and reverse entries) was setup correctly.

I can use nslookup to resolve hostname and IP address correctly.

0 Kudos
Shailesh0SantaC
Contributor
Contributor

the OVA for workspace to 1.5.0 build 1318295, has an issue i was able to resolve by doing this --

( I could be wrong but the issue has to do with IPv6 routing on the network)


Once the ova is deployed , shut it down.

Right click on the OVA --> click edit settings --> Advanced --> IP allocation --> change the IP allocation to "IPv4" and restart the VM.


To be on the safer side I would recommend, re-deploy the OVA and before powering it up do the above change.

Good luck !!


S

0 Kudos