Highlighted
Contributor
Contributor

Pre-upgrade Check error VC5.5 to VC6U

error.jpg

I built a small lab to have a view on the upgrade screens and installed a vc55 with VMware-VIMSetup-all-5.5.0-2646481-20150401.iso

I configured an ad user with an adminstrator rule and created a datacenter and a cluster to check the rights.

When i try to run the upgrade with an VMware-VIMSetup-all-5.5.0-2646481-20150401.iso i get the authentication error.

I am still able to login to the vcenter with adminstrator@vsphere.local and my ad account.

I changed the password to test different password policies but the result is the same. Did anybody else experience this error?

Regards

0 Kudos
6 Replies
Highlighted

  • BUT when you kick off the upgrade you’ll get this nice popup message (There is a problem authenticating into the legacy vCenter Server using the credentials provided by the user.) I went triple checked on my certificates and all were aligned fine, finally I went through the installation logs that gets archived on the desktops and found out that the installation is still looking for the 444 port for connectivity, thus I went back and changed the VPXD port to 444 and started the installation successfully.

from: http://notes.doodzzz.net/2015/03/24/vsphere-6-0-home-lab-upgrade-issues-faced/

Reboot the vCenter Server… I restarted the setup and the installation can continue.. weird!

from: http://blog.vmpros.nl/2015/05/16/vmware-there-is-a-problem-authentication-into-the-legacy-vcenter-se...

post the installation log. with this information we can investigate your problem...

------------------------------------------------------------------------------- If you found this or any other answer helpful, please consider to award points. (use Correct or Helpful buttons) Regards from Switzerland, B. Fernandez http://vpxa.info/
0 Kudos
Highlighted
Contributor
Contributor

Restart of the server and change of the port from 443 to 444 did not solve the problem.

http://mp-lab.de/files/vminst.log

Thanks & Regards

0 Kudos
Highlighted

i cant see any important entrys in the log...only the error you allready posted...

have you tried to install the vcenter with the service account you want to run the vcenter server? is he local admin and is he allow to run as a service ?

i would trie to log on as the service account and retry to install the vcenter server

------------------------------------------------------------------------------- If you found this or any other answer helpful, please consider to award points. (use Correct or Helpful buttons) Regards from Switzerland, B. Fernandez http://vpxa.info/
0 Kudos
Highlighted
Contributor
Contributor

I tested with the local administrator account and run in the same error.

0 Kudos
Highlighted

i have found this:

vCenter Server authentication error during upgrade
If your legacy vCenter Server SSL certificates are expired, the installer provides a general error message instead of a specific one:

There is a problem authenticating in to the legacy vCenter Server using the credentials provided by the user. Resolution: Check if vCenter server is up and running. Double check provided vCenter Server credentials.

Workaround: If you encounter an authentication error, you can check the vpxd.log atC:\ProgramData\VMware\VMware VirtualCenter\Logs to discover the exact reason for the upgrade error message.

Before upgrading, check for SSL certificate validity. Replace any expired SSL certificates for vCenter Single Sign-On, vCenter Inventory Services, vCenter Server, vSphere Web Client, or any other solution.

from: VMware vSphere 6.0 Release Notes

------------------------------------------------------------------------------- If you found this or any other answer helpful, please consider to award points. (use Correct or Helpful buttons) Regards from Switzerland, B. Fernandez http://vpxa.info/
0 Kudos
Highlighted
Contributor
Contributor

The system was 2 days old. This would be a very short time for expired Certs.

The message in vpxd.log looks similar :

2015-10-16T09:04:37.437+02:00 [02376 info 'vpxdvpxdLicenseProvider'] [LicMgr] There is now 1384 hours remaining for evaluation.

2015-10-16T09:05:05.018+02:00 [02376 warning 'statsvpxdStatsCollector'] Negative stats values detected; domain-c7, values dropped: 1

2015-10-16T09:05:15.049+02:00 [00948 error 'HttpConnectionPool-000001'] [ConnectComplete] Connect failed to <cs p:00000000095e18e0, TCP:vc-test.mp.lab:7444>; cnx: (null), error: class Vmacore::TimeoutException(Operation timed out)

2015-10-16T09:05:15.049+02:00 [04248 error '[SSO]' opID=7de46d9d] [UserDirectorySso] AcquireToken exception: class SsoClient::CommunicationException(Operation timed out)

2015-10-16T09:05:15.049+02:00 [04248 error 'authvpxdUser' opID=7de46d9d] Failed to authenticate user <administrator@vsphere.local>

2015-10-16T09:05:20.056+02:00 [04248 info 'commonvpxLro' opID=7de46d9d] [VpxLRO] -- FINISH task-internal-698 --  -- vim.SessionManager.login --

2015-10-16T09:05:20.056+02:00 [04248 info 'Default' opID=7de46d9d] [VpxLRO] -- ERROR task-internal-698 --  -- vim.SessionManager.login: vim.fault.InvalidLogin:

--> Result:

--> (vim.fault.InvalidLogin) {

-->    dynamicType = <unset>,

-->    faultCause = (vmodl.MethodFault) null,

-->    msg = "",

--> }

--> Args:

-->

0 Kudos