After upgrading my vCenter to 8.0 Update 3 I went to login, and the login box itself was grayed out, with a ‘no entry’ sign when I attempted to click it, and Bizarrely I now had a Use RSA ID option?
Solution: Login Grayed Out
Apparently, this is a known problem with this update, and the ‘fix’ is to clear the browser cache, which I attempted to do.
However the problem persisted, the only way I could fix the problem was to delete ALL BROWSING DATA.
Thankfully after a browser restart, I was up and running again.
Related Articles, References, Credits, or External Links
Today I found I could no longer log in to the VCSA vCenter appliance;
Exception in invoking authentication handler User password expired
Solution
Just because I can’t log into the web console, I could still log into the the appliance via SSH. Then invoke the shell command, and reset the root password with the passwd command;
Now if you wish, you can Disable VCSA Password Expiration: Administration > Edit > No > Save.
Related Articles, References, Credits, or External Links
Note: I’ve had the same problem on a freshly installed vCenter 5.1 as well.
I upgraded my Virtual Center from 5.0 to 5.1 yesterday, and post upgrade I could no longer login, it would tell me “Unknown user or bad password”.
During the upgrade I did see this error, but after that the install completed successfully.
Error 29155.Identity source discovery error
As it turns out this was the root cause of my problem.
Solution
1. Firstly install the ‘Web Client’ on the Virtual Center. Note: You will need Adobe flash installing for this to work. (Sometimes this needs a reboot, and the firewall turning off, and/or adding to trusted sites in IE, before it works).
Note: The Web Client is on the Virtual Center install CD.
2. Connect to the the server on https://localhost:9443 log on (Note: Use the username of admin@System-Domain and the password you used when you installed Single Sign on earlier). Expand Sign on and Discovery > Configuration > Select the ‘Add’ icon.
3. Supply your domain details as follows, those ldapURL’s simply point to the domain controller(s).
4. Scroll down and enter the domain logon credentials, then select ‘Test Connection’.
5. It should say connected successfully, if not check the comms and the details you entered are correct.
6. Click the ‘Add to Default Domains’ Icon.
7. Finally save the changes by selecting the ‘Save’ icon, you should now be able to authenticate to the vCenter with your domain credentials.
Related Articles, References, Credits, or External Links
Not the most descriptive of errors! In fact this has got nothing to do with the busyness of the web server at all.
Solution
What’s actually happening is the RSA agent on this machine (in this case a web server) cannot communicate with the RSA Authentication Manager. In my case the web server was in a DMZ, and the RSA Authentication Manager Appliance was in another DMZ. The ports required (TCP 5500, UDP 5500, and TCP 5580). were not open from the agent to the appliance. Once I fixed that, we were up and running.
Related Articles, References, Credits, or External Links
This used to quite common when attempting to contact the HP Management Homepage, (or the local insight manager page) you can no longer get access.
ERROR: Username and password do not match
Solution
With much older versions of the Systems Management Homepage (before it used domain user names and passwords) you could simply copy over the CPQHMMD.DLL file from a server you knew the password for, and then you could get in.
Then they switched to domain authentication, and when that broke you could navigate to C:compaqwbemhomepage, edit the cpqhmmd.ini file with the following entries;
Then restart the Server (or the HP Services if that’s easier) and you could log in.
With newer versions of the HP Management Homepage those files no longer exist!
1. Head over to www.hp.com and do a drivers/software search for the model of your server, select the operating system you are using and look in the “Software – System Management” section. Locate, download, and install the HP Management homepage software.
Note: Don’t panic this will not need a reboot.
2. It says Administrators always gets access but I still add it in anyway (Note: If this is a domain controller, the local Administrators group is the domain admins group anyway).
3. Set as follows.
4. I’m leaving mine open from any server.
5. Now we are in! (hooray!) and I’ve got a broken BBWC (boo!).
Related Articles, References, Credits, or External Links
