This post is more than 5 years old
2 Posts
1
152387
Error 2000000 with fresh install of OMIVV 3.0 and vCenter 6.0
We recently installed vCenter 6.0 in our lab. I downloaded the OMIVV OVF and deployed a brand new instance of the appliance. (I experimented with 2.3.0 in the past, but never got it working, so just threw all that out.) The connection to the vCenter went without a hitch, but the web client is showing an "Error 2000000" dialog whenever I click through the interface. When I used the first-time configuration wizard, I was able to enter all the passwords, but the list of hosts was empty, even though this vCenter has 8 attached. Without being able to select a host, I wasn't allowed to proceed through the wizard.
It seems like this error has been reported in prior versions, but it's slightly different in OMIVV 3.0, so I thought I should start a new thread. It says:
An unknown exception has occurred and has been logged in the extended logs.
Severity: CRITICAL
Error: 2000000
Date and time:
Details:
An unknown exception has occurred and has been logged in the extended logs. If the issue continues, please restart your appliance. If this does not resolve the issue, please contact Dell Support.
Things I've tried:
- Enable and disable the web proxy settings (no change in behavior)
- Disconnected and reconnected the vCenter in the administrative interface several times
- Made sure the vCenter and OMIVV appliance are on the same network, with no firewalls between
- Re-registered the vCenter using the official FQDN, such that name -> numeric -> name results in the same name being returned
I downloaded the support bundle and looked through the logs, but didn't see anything obvious. I'd be happy to start over and upload a clean log file or files if that would help.
Any hints on where to go from here?
Joseph Jackson,
Computing Services,
Carnegie Mellon University.
mickpsk
1 Message
2
October 15th, 2015 08:00
Hi,
Of course is related to certificate that has been change for custom certificate.
Please follow this KB
# vCenter Server certificate validation error in VMware vCenter Site Recovery Manager and other solutions that run on a separate system
kb.vmware.com/.../2109074
That one will redirect for thw KB that depend of your infrastructure deployement type (separate PSC or Embedded).
That's one works for one of my customer.
Have a nice day.
sandyb1980_6dab42
8 Posts
0
July 22nd, 2015 06:00
you are not alone!
I have deployed OMIVV v3 appliance, it works fine with a windows based vCenter 5.5 server but I get the same error as you when trying to use it with a vCenter 6 appliance.
An unknown exception has occurred and has been logged in the extended logs.
Severity: CRITICAL
Error: 2000000
Date and time:
Details:
An unknown exception has occurred and has been logged in the extended logs. If the issue continues, please restart your appliance. If this does not resolve the issue, please contact Dell Support.
I have tried the same actions you have along with clearing cache
#service vsphere-client stop
# rm -rf /etc/vmware-vsphere-client/SerenityDB/serenity/*
# service vsphere-client start
as this has worked for other web client plugin issues previously.
did you get anywhere?
JosephJackson
2 Posts
0
July 22nd, 2015 08:00
Unfortunately, I haven't heard anything at all on this issue other than your reply. At least I know it's not just me! :-)
Joe.
Myles Gray
9 Posts
0
July 23rd, 2015 13:00
Here too :/
Myles Gray
9 Posts
0
July 24th, 2015 17:00
If you log in as the SSO admin it seems to work, looks like a permissions problem.
Myles Gray
9 Posts
1
July 25th, 2015 18:00
Worked it out guys, if you're using signed certs and you replace the machine cert in vCenter 6 then in the log:
/var/log/vmware/vsphere-client/logs/vsphere_client_virgo.log
You'll see an error like this at some point:
c.vmware.vim.vmomi.client.http.impl.AllowKnownThumbprintVerifier Mismatched thumbprint {thumbprint here}, rejecting connection
It seems using signed machine certs actually breaks a service within the vcenter server.
I reverted my certificate back to stock, re-registered the plugin and it now works.
This is obviously not an ideal situation, so i'm going to try adding the vCenter as a subordinate to my AD CA and see if it will work that way after re-signing all solution users.
Myles
PavithraM
1 Message
0
July 31st, 2015 01:00
Hi Joseph,
Good to hear about using OMIVV 3.0.
The error posted by you occurs when it fails to meet the below conditions:
1. DNS settings of OMIVV and vCenter are not same or DNS settings are not enabled in either OMIVV or vCenter.
2. Both OMIVV and vCenter have different time setting.
Can you kindly check on the above settings and make sure they are correct.
~Pavithra
Wilbertk
1 Message
1
December 14th, 2015 12:00
Thanks Mickpsk. I had an related issue with a HP OpenView plug-in. The VMware KB article did the trick. Thanks!
I have written down my experience on https://nogietscom.wordpress.com/2015/12/13/error-while-opening-hp-management-tab-within-vsphere-web-client-6/