STUMPED! HELP! Error connecting: Login (username/password) incorrect.

[michaelaghajani]

I recently installed patches to all my Hosts to the current patch. Things went smoothly so I thought

So now when I try and open a console connected to the VI server or directly to the host:

"Error connecting: Login (username/password) incorrect Do you want to try again?

The Virtual Client agent also was upgraded on the host to the latest and greatest.

DNS appears to be working

I have poked through the logs and can't find much.

I have searched for that error and dont' get anything.

Can ANYONE PLEASE tell me where I should start to troubleshoot this one. What logs should I look in?

[esiebert7625]

Here's some good troubleshooting guides...

Troubleshooting Vmware ESX Server 3 and Vmware VirtualCenter 2 - http://download3.vmware.com/vmworld/2006/mdc9694.pdf

VirtualCenter 2 Diagnostics - http://download3.vmware.com/vmworld/2006/tac4096.pdf

Make sure you database is up and VC can connect to it, check the Windows Event log on the VC server and the log file located in C:\Windows\Temp\VPX directory on the Virtual Center server

Also if you are connecting directly to the host, are you connecting as a local SC user or do you have your ESX setup to authenticate with AD? Can you log into the SC OK without the VIC?

Message was edited by:

esiebert7625

[esiebert7625]

Also these are the ESX server logs you can check...

You can check several log files on the ESX server based on the problem you are experiencing, these include:

o Vmkernel - /var/log/vmkernel – records activities related to the virtual machines and ESX server

o Vmkernel Warnings - /var/log/vmkwarning – records activities with the virtual machines

o Vmkernel Summary - /var/log/vmksummary - Used to determine uptime and availability statistics for ESX Server; human-readable summary found in /var/log/vmksummary.txt

o ESX Server host agent log - /var/log/vmware/hostd.log - Contains information on the agent that manages and configures the ESX Server host and its virtual machines (Search the file date/time stamps to find the log file it is currently outputting to.)

o Service Console - /var/log/messages - Contain all general log messages used to troubleshoot virtual machines or ESX Server

o Web Access - /var/log/vmware/webAccess - Records information on Web-based access to ESX Server

o Authentication log - /var/log/secure - Contains records of connections that require authentication, such as VMware daemons and actions initiated by the xinetd daemon.

o VirtualCenter agent - /var/log/vmware/vpx - Contains information on the agent that communicates with VirtualCenter

o Virtual Machines - The same directory as the affected virtual machine’s configuration files; named vmware.log - Contain information when a virtual machine crashes or ends abnormally

[michaelaghajani]

I am connecting local root...

[esiebert7625]

So can you log into the local console directly from the server or using putty as root or is it only through the VI client that you are having problems? If you can log into the console OK try running the command “service vmware-vpxa restart” followed by “service mgmt-vmware restart”

[TomHowarth]

I am a little confused as to your problem here?

do you have diffuculty connecting to the physical hosts machines ie. ESX

or

do you have difficultiy connecting to VC

[michaelaghajani]

I can log into the console with root fine. And I can connect directly to the hosts with VI client fine. Just when I connect to the VC server I get this error.

[michaelaghajani]

Just having difficultly connecting to VC

[sbeaver]

Which account are you using to connect to VC?

[TomHowarth]

the account that you should be using to login to VC is a Windows one.

also what is the error that you are recieveing and have you checked that the services are running?

[acastle]

I have the same problem. Maybee a different cause though....

I can't login to my VirtualCenter server with the VIClient with the windows administrator account (SQL 2005 is using nt authentication) and the web services aren't working but their running. What I can do is login to the VirtualCenter box (it auto logs in - password hasn't changed) and I can login to each ESX 3.0.1 host with the VIClient. I get the nice complaint that I shouldn't change anything because the box is managed by VirtualCenter. No updates have been applied to the ESX hosts, BUT Microsoft has released an update for the windows installer service - KB927891[/b] http://www.microsoft.com/technet/security/advisory/927891.mspx

So I installed it and it required a reboot on the VirtualCenter box. I come back from lunch to find that I can't login to VirtualCenter with the VIClient. I reset the password for the Administrator account to what it should be and bounced it to make sure it's the same as in the autologin. Good, logs in fine and I try it again with the VIClient. Still I can't login. I've spent a good couple of hours trying different things and finally I uninstalled the update and bounced the box. Miraculously I can login again and the VMware VirtualCenter 2 Welcome page works too.

[michaelaghajani]

The error is "Error connecting: Login (username/password) incorrect."

I am using the administrator of the local box as I always have. I think it might be a DNS issue for some reason..

[CWedge · Accepted solution]

First Off you should have marked this as a question and you'll get better response becase we get points

Did you install the Virtual Center 2.0.1 Patch 2? If so that is your problem.

Make sure and read these threads beforehand...

http://www.vmware.com/community/thread.jspa?messageID=594826��

http://www.vmware.com/community/thread.jspa?messageID=588439��

http://www.vmware.com/community/thread.jspa?messageID=589339��

And you need to do this.

Please follow steps below to install VC Agent manually:

1) Login to the VC 2.0 server as Administrator.

2) Open the folder for the VC 2.0 installation. By default this will be "C:\Program Files\VMware\VMware VirtualCenter 2.0\upgrade"

3. You need to use the correct file for different version of ESX server. You can find your answer in bundleversion.xml Ie.

2.0.1+ = vpx-upgrade-esx-0-linux-*

2.1.0+ = vpx-upgrade-esx-1-linux-*

2.5.0 = vpx-upgrade-esx-2-linux-*

2.5.1 = vpx-upgrade-esx-3-linux-*

2.5.2 = vpx-upgrade-esx-4-linux-*

2.5.3 = vpx-upgrade-esx-5-linux-*

3.0.0+ = vpx-upgrade-esx-6-linux-*

e.x.p = vpx-upgrade-esx-6-linux-*

4) Copy file "vpx-upgrade-esx-y-linux-xxxxx" to your ESX host, where y and xxxxx are based on bundleversion.xml.

Xxxxx is the build number,

ie.

VC 2.0.0 build number is 27704

VC 2.0.1 build number is 32042

VC 2.0.1 Patch 1 build number is 33643

(Use a secure copy utility such as WinSCP or PuTTY PSFTP to copy this file to the ESX server.)

5) Login to the ESX server as root.

6) In the directory where you copied the upgrade bundle run the command:

sh ./ vpx-upgrade-esx-y-linux-xxxxx

7) run the command:

\- service vmware-vpxa restart

\- service mgmt-vmware restart

😎 Login to the VC 2.0 server as Administrator

9) Open "Control Panel->Administrative Tools->Services" window

10) Restart "VMWare License Server" service

11) Restart "VMWare VirtualCenter Server" service

12) Now open your VI Client, try to connect to the ESX host.

Message was edited by:

CWedge@Amsa

[jgswinkels]

Hi Michael,

Are you directly on console or remotely via putty?

If you are connected via putty you have to open your ESX configuration to access root account.

Cheers,

Jan