Hi,
This morning I find that I am unable to login to my vCentre 5.5 server via either the vSphere Client or vSphere Web Client, using my AD integrated authentication... I can login using administrator@vsphere.local account...
vCentre was installed on 17th December 2013 and my AD login was working on the 13th February 2014 (58 Days) but not today 17th February 2014 (62 Days)...
I am thinking that there is a '60 day' bug in my vSphere setup...
vSphere Server 5.5.0 - Version Build 1378903
vSphere Client - Version 5.5.0 Build 1281650
vSphere Web Client - Version 5.5.0 Build 1369380
The vSphere Web Client error is "The authentication server returned an unexpected error: ns0:RequestFailed: Failed to establish server connection. The error may be caused by a malfunctioning identity source."
I can confirm that KB2035510 does not apply, as my short NETBIOS domain name is already in the Domain Alias field for my AD identity source
I know that vCenter Server 5.5.0b Build 1476387 is available, but I am reluctant to install/upgrade without knowing if this issue is resolved...
If there is a quick fix (that does not involve upgrading) to this problem I would prefer that rather than rushing blindly into a 5.5.0b upgrade at this point in time...
Any help will be appreciated...
Martin
Are you using these products in evaluation?
If yes, then you will need to procure a license or the vCenter and the ESXi hosts will not function anymore.
Many of us still evaluating the vSphere and vCenter in our test environments. Sometimes, it takes more than 60 days to evaluate where trial edition expires.
We can't extend the trial edition in ESX host, either we have to reinstall it or license it. vCenter also have to follow the same way as ESX does. But, here we can keep old database contents as it is when you reinstall the vCenter software.
This document using vCenter 4.0 and SQLEXPRESS 2005 (built in) database. At the time of installation of vCenter 4.0, it installs SQLEXPRESS 2005 by default unless any other Database specified. Mostly, we are using built-in database is SQLEXPRESS 2005 for testing environment.
When you install vCenter 4.0, it installs SQLEXPRESS 2005 and creates a database called "SQLEXP_VIM". You can view this thru SQL Server Configuration Manager console.
Start --> All Programs --> Microsoft SQL Server 2005 --->Configuration Tools ----> SQL Server Configuration Manager
Creating DSN
=================
Create a System DSN for this database using ODBC (Administrative Tools à Data Sources (ODBC) either before/after expiry of your vCenter trial period.
Open the ODBC Database Administrator Source, Select "System DSN" and Click "Add" Button and Select "SQL Native Client"
Provide the Datasource name (recommened to use as "SQLEXP_VIM")
Select, the server and database name (mostly local host, since it is installed on the same server where we installed vCenter earlier)
Leave the Authentication as default. It is important to change the default database to
VIM_VCDB as shown in the picture: (Select in the list)
Press Next and leave them to default settings and Test Connectivity.
Use the Add/Remove Programs to uninstall the vCenter 5.0 after trail period is over.
Reinstalling the vCenter
When you reinstall the vCenter on same server, select the "Use an existing supported database" on database section. Then, enter "sqlexp_vim" as the DSN and press "Next" and leave blank for UN/PW
Select "Do not overwrite, leave my existing database in place" and press "Next", leave it default
After complete database selection, continue with your installation as usual.
Once the vCenter installation completed, open it thru vSphere Client, you can see your old settings such as Datacenter, Cluster and other configuration. Again, your evalution periods starts with 60-days again.
Note : This is for Vcenter 4.X ..it should work with 5.x as well however I have not tested it....I'm not responsible if some thing goes worng. ![]()
Hi,
I wish it was that simple, but the vCenter Server and all ESXi Hosts are fully licensed...
Thanks
Martin
Hi,
I am not evaluating vSphere still - this is a fully licensed install...
Thanks
Martin
Have you tried with local administrator? At least one of them should work.
The administrator@vsphere.local account is working, so I can access vCentre...
Unfortunately, I am not allowed to use the generic admin account for extended period, due to company audit & oversight 'compliance' restrictions...
Martin
If possible remove and re-add the permissions for domain users. For a test user and see if it works.
