Unable to configure vrops on av 3.0 -
Get this error: Internal Server Error. Server encountered internal error and was unable to complete your request. Please try again later. If this issue persists contact your service provider.
Nothing relevant is indicated in the logs. Anyone else run into this problem?
Apparently it doesn't like my FQDN despite being able to ping the vrops appliance from within the AVM console using FQDN. Works using https://VROPS_IP_ADDRESS or https://VROPS_HOSTNAME
Might be a silly question but you do have vROps installed correct?
Try to also disable the firewall on the OVA.
Yep vrops is deployed and configured,, can verify that each appliance can ping each other as well. And regarding disabling the firewall are you talking about the firewall on the vrops or av appliance?
Apparently it doesn't like my FQDN despite being able to ping the vrops appliance from within the AVM console using FQDN. Works using https://VROPS_IP_ADDRESS or https://VROPS_HOSTNAME
Could you please check the below things.
1.) Ping the FQDN hostname in OVA machine, if you are trying to add vrops uisng FQDN. If it is not pinging as an entry in hosts file to get resolved the fqdn.
2.) Accept all cert as "No" then you need to upload vrops certs otherwise select option as "Yes"
If you need how to upload vrops certs let me know i will help you
I'm having this same issue and have tried all of the suggestions listed in this thread. I've also adjusted my AD configuration since that made a difference elsewhere when configuring AppVols 3. Does anyone else have any suggestions? Thanks!
I'm getting this as well. This IS still setup like the old one right? Where the username/password is what was used to setup the horizon adaptor in vrops?
I've got my vrops instance using SSO, no mention has been made as to wether or not this is supported.... I know the orchestrator connector is STILL broken in this regard.
No, you need to use the admin password you use to log into the vROPS, not the Horizon adapter account. This is only used for connecting the adapter with the broker on the connection server.
Yes, I am using the admin password used to log in to vROPS, and it's not working. I verified it works to log in to vROPS.
Using the local admin account for vrops, and pointing it to the https://IP_ADDRESS and selecting ACCEPT ALL CERTIFICATES was the magic combination. Seems I need to add my rootca to the certificate store, I'm betting the vcenter connection wont work either.
Adding a rootca should not be a task I need to drop into command line to do VMWARE. Please add it to the wizard -_-
It looks like the username has a character limitation. I can only put 20 charachters for a username.
But if my username is longer than 20 character its impossible to use this user. Why is this so?
Hey Guys,
Im getting the following error, i tried FQDN, ShortName , IP Address, vROPS Admin account, my service account and my Ad account i setup in vrops, Any ideas?