sietec2
Contributor
Contributor

Unable to register orchestrator in vsphere web client (v5.5)

Jump to solution

Hello,

We are having difficulty registering orchestrator to use in the web client.  Checking https://**server-ip**/mob shows that it is registered as an extension and that the heartbeat has been received recently.  However, even after a restart of the vcenter server services and the orchestrator services, logging out and back in to the vsphere client, trying to register it manually in the web client, etc. it still is not appearing.

When trying to register it manually, what format should be used?  We have tried multiple methods

1. https://FQDN:8281

2. https://FQDN:8281/api

3. FQDN

4. FQDN:8281

5. IP

6. https://IP

7. https://IP:8281

8. https://IP:8281/api

All of those methods yield a negative result.

Also, even though the SSO is setup, and performing a test login using the orchestrator configuration web page succeeds, we cannot log into the orchestrator client!  It says the user is not authorized, even though it is the same user specified in the orchestrator configuration as administrator from active directory.  Just in case this might help, we are using MS SQL Server 2012 Enterprise for both vcenter and for orchestrator.  In order to make sure orchestrator db was fully complient, we duplicated the original vcenter db and then created an SQL login user for the vco db and populated the tables.  The configuration wizard reported success.  (It should be noted we also tried with a fresh database and let orcestrator populate the tables---that was successful too, but we still had the same problems with integration and sign on to client; so to maximize compatibility, in case the db was missing necessary objects, we replicated the vcenter db...the reason for this wsa that orchestrator can use the vcenter server db if installed in "easy mode")

We have searched the communities and found many people with the same problem but none of the cases we have found have actually been marked "solved."

Could someone please help us with this?  Although version 5.5. is awesome with regard to advancements made and new features, etc., it has been an absolute nightmare implementing.  I hope VMware is working on fixes for the bugs because if we had it to do over again, we would stay with version 5.1 for a while.

Thank you in advance for your help.  If anyone has had issues with installing (fresh or upgrade) version 5.5, we may be able to help...just ask me.  During our install, we experienced about 6 or 7 separate issues to which we have documented the resolutions (most are easy to resolve but in a production environment, any down time is not good! Smiley Happy

Sincerely.

Message was edited by: sietec2 -- changed ports that were tried from 8081 to 8281, typo.

0 Kudos
1 Solution

Accepted Solutions
sietec2
Contributor
Contributor

Solved!  After the suggestions from you, I got a hunch and checked the "vco.properties" file...then noticed something strange.  Here is the contents of the file

INSTALLER_UI=SILENT

USER_INSTALL_DIR=C:$/$Program Files$/$VMware$/$Infrastructure$/$Orchestrator$/$

CHOSEN_INSTALL_SET=CS

VC_Database_User_Name=

VC_LogOn_User_Name=administrator

JDBC_URL=jdbc:vdb:vcdb

VC_web_Service_Http_Port=8080

VC_web_Service_Https_Port=8443

VC_Http_Port=80

VC_Https_Port=443

Upgrade_or_Fresh_install_Flag=fresh

SSL_Certificate_location=C:\ProgramData\VMware\VMware VirtualCenter\SSL\

Customer_information=Windows User#

SSO_User_Name=Administrator@vsphere.local

SSO_URL=https://Our.domain.com:7444/sso-adminserver/sdk

LS_User_Name=Administrator@vsphere.local

LS_URL=https://our.domain.com:7444/lookupservice/sdk

IS_URL=https://our.domain.com:10443/

VC_SSO_USER_GROUP=administrator@vsphere.local

SSO_DISABLED=0

Notice the bold line, VC_LogOn_User_Name, it was set to administrator.  Changing that to administrator@{ourdomain.com} and restarting the orchestrator server, then logging out and back into the vcenter server web interface solved the problem and the vco server showed up!

So, if anyone has the issue where it won't register in the web client, check the server.properties file in {orchestrator_install_root} and make sure the log on username is correct for your environment!

Thanks to those that helped!

View solution in original post

0 Kudos
5 Replies
igaydajiev
VMware Employee
VMware Employee

Could you attach also {Orchestrator_INSTALL_FOLDER}\app-server\logs\server.log

0 Kudos
iiliev
VMware Employee
VMware Employee

Hi,

A few formats that should be valid:

IP

https://IP:8281

https://IP:8281/vco/api

What happens if you enter an address in one of the above formats and press 'Test Connection' button? If it doesn't say 'The connection has been established successfully', then there is an issue - maybe your vCO server has not started properly, or vCO and NGC use a different SSO server, or some other issue.

sietec2
Contributor
Contributor

Thank you, we had tried all of those except the /vco/api...but still received the same result.  As far as the SSO server, they are both set to use the same one.  I am going to attach the log files shortly, as requested in reply #1 above, maybe that will shed some light.

Thanks for the help!!!

0 Kudos
sietec2
Contributor
Contributor

We will gather the log file and attach it as soon as our privacy team verifies any sensitive data has been scrubbed. Thank you very much in advance for your help!  We very much appreciate it.:smileygrin:

Please find attached the server.log and catalina log files.  We noticed some errors regarding memory leaks in catalina log, so posted that one as well.  Thanks again.

Message was edited by: sietec2 -- added the requested log files as attachments

0 Kudos
sietec2
Contributor
Contributor

Solved!  After the suggestions from you, I got a hunch and checked the "vco.properties" file...then noticed something strange.  Here is the contents of the file

INSTALLER_UI=SILENT

USER_INSTALL_DIR=C:$/$Program Files$/$VMware$/$Infrastructure$/$Orchestrator$/$

CHOSEN_INSTALL_SET=CS

VC_Database_User_Name=

VC_LogOn_User_Name=administrator

JDBC_URL=jdbc:vdb:vcdb

VC_web_Service_Http_Port=8080

VC_web_Service_Https_Port=8443

VC_Http_Port=80

VC_Https_Port=443

Upgrade_or_Fresh_install_Flag=fresh

SSL_Certificate_location=C:\ProgramData\VMware\VMware VirtualCenter\SSL\

Customer_information=Windows User#

SSO_User_Name=Administrator@vsphere.local

SSO_URL=https://Our.domain.com:7444/sso-adminserver/sdk

LS_User_Name=Administrator@vsphere.local

LS_URL=https://our.domain.com:7444/lookupservice/sdk

IS_URL=https://our.domain.com:10443/

VC_SSO_USER_GROUP=administrator@vsphere.local

SSO_DISABLED=0

Notice the bold line, VC_LogOn_User_Name, it was set to administrator.  Changing that to administrator@{ourdomain.com} and restarting the orchestrator server, then logging out and back into the vcenter server web interface solved the problem and the vco server showed up!

So, if anyone has the issue where it won't register in the web client, check the server.properties file in {orchestrator_install_root} and make sure the log on username is correct for your environment!

Thanks to those that helped!

View solution in original post

0 Kudos