Hi.

Instead of hijacking other one's thread having the same problem I decided to start a new thread, so sorry for double posting.

After promoting a new DC and demoting the old one we have the problem that VCenter 5.1a no longer starts.

Taking a look at the imsTrace.log file of SSOServer we see the following line:

Caused by: javax.resource.spi.ResourceAdapterInternalException: Unable to create managed connection olddc.ourdomain.com:3268

As we can see SSO still tries to contact the old dc now beeing a simple member server instead of the new one - the question is why?

We checked health of AD by running DCDIAG and BPA both not seeing any problems. Additionally we checked DNS by hand to ensure that no SRV or any other records are present which reference the old DC. Also all other AD dependent services like Exchange, SharePoint, DFS run without issue and do not indicate any problems.

We also found the krb5.conf file of SSO which still references the old DC by the following entry:

[realms]
OURDOMAIN.COM = {
    kdc = olddc.ourdomain.com
    default_domain = OURDOMAIN.COM
}

However changing that entry does not solve the problem because after a short period this entry is replaced automagically by ??? - that's the question.

Mybe someon else has some ideas what to check next.

Cheers.

Hello,

I'm trying to import an OVA file and I get the error:

"A vCenter Server resource is missing or invalid.  Either the resource was modified while the operating system was running or the server is experiencing a general problem"

This OVA file is from Cisco, it's called Prime.  I had to install another OVA file from Cisco just now and that was fine.

Is it a resourse issue on the reource pool, not sure where to look.

Thanks

I recently upgraded from vCenter 5.1 to 5.5. After the upgrade I began to get health warnings for the VMware vCenter Storage Monitoring Service that say "Service initialization failed". I have rebooted the vCenter server and restarted the services several times and that has not cleared the issue. When I look in the SMS.LOG file there is no activity in it since the date I did the upgrade (a week or more ago). All prior activity in the SMS.LOG looks to be fine up up until the upgrade occured though. I have found at least a half-dozen KB articles that describe various reasons why this error might occur but they all pertain to older versions of vCenter. Just to be thorough though I reviewed the symptoms in the articles and none of them really seem to be the same as what I am seeing. My one hypothesis is that perhaps the SMS didn't get properly re-installed during the upgrade because I don't see any SMS sub directory in the \Program Files\VMware\Infrastructure\tomcat\webapps directory but I'm not even sure if this directory should exist on a 5.5 installation.

Would appreciate if anyone has any troubleshooting advice for this type error.

Thanks,

Mike

Using vSphere Web Client 5.1
Trying to access vcenter 5.1 server

Logged in as admin@system-domain

No vcenter server listed.

Suggested troubleshooting steps:

Verify that the vCenter Server system was registered with the vSphere Web Client's Lookup Service.
Question: How do I verify this?

Logged in using Windows Session Authentication.
(User is a memeber of Administrators with full access to vCenter Server)

Message: Client is not authenticated to VMware Inventory Service.
No vcenter server listed

Question: How do I troubleshoot this?

Thank you.

I'm having problems getting the self signed certificates for vCenter v5.5 replaced with Enterprise CA certificates.  I am using the certificate replacement tool from VMware.  The SSO certificate is successfully replaced so I move on to having the Inventory service trust the SSO certificate.  They succeeds as well but I think all its doing is bouncing the Inventory service.  I then go to install the Inventory service certificate and get:

[Sat 03/15/2014 - 15:51:06.27]: The services that are restarted as a part of this operation are: vCenter Inventory Service.

Enter the location to the new Inventory Service SSL chain (default value is: c:\certs\Inventory\chain.pem):

Enter the location to the new Inventory Service private key (default value is: c:\certs\Inventory\rui.key):

Enter the Single Sign-On Administrator user (default value is: administrator@vsphere.local):

Enter the Single Sign-On Administrator password (will not be echoed):

[.] The supplied certificate chain is valid.

[Sat 03/15/2014 - 15:51:20.40]: Last operation update Inventory Service SSL certificate failed :

[Sat 03/15/2014 - 15:51:20.41]: Cannot determine if Inventory Service is registered with Single Sign-On - errorlevel is 1

If I look at the logs, I see the following:

[Sat 03/15/2014 - 15:51:15.43]: The Inventory Service is installed at "C:\Program Files\VMware\Infrastructure\Inventory Service"

[Sat 03/15/2014 - 15:51:15.44]: Rollback path is "C:\ssl-certificate-updater-tool-1308332\backup"

[Sat 03/15/2014 - 15:51:15.45]: Rollback path is "C:\ssl-certificate-updater-tool-1308332\backup\IS"

[Sat 03/15/2014 - 15:51:18.03]: Determining whether Inventory Service is registered with Single Sign-On ...

Intializing registration provider...

Getting SSL certificates for https://FP-CSVC01.domain.loc:7444/lookupservice/sdk

com.vmware.vim.vmomi.core.exception.CertificateValidationException: Server certificate chain not verified

Return code is: SslHandshakeFailed

1

[Sat 03/15/2014 - 15:51:20.39]: "Cannot determine if Inventory Service is registered with Single Sign-On - errorlevel is 1"

[Sat 03/15/2014 - 15:51:20.39]: Exiting Inventory Service update SSL certificate due to errors

Obviously there is something about the CA chain that it doesn't like.  If I look at my cert store on the vCenter server, I have my Root CA in the Trusted Root store.  In the Intermediate Store I have both the Root and Intermediate.  If I browse to the lookup service (https://FP-CSVC01.domain.loc:7444/lookupservice/sdk) from a web browser, the certificate shows as valid and throws no errors so there should be nothing wrong with the certificate.

The format of the chain.pem in the Inventory directory is correct as well.  It is the Inventory cert, followed by the Intermediate cert, followed by the Root cert.  No extra spaces anywhere.

I have also tried to manually replace the certificates and it essentially fails at the same spot.  SSO replacement goes fine then I go to unregister the Inventory service and the SSL handshake fails.

Funny thing is that if I am using vCenter 5.1, I get past this all without issue.

Thoughts??

Last week we updated our vCenter Server from 5.0 to 5.1. And since that moment we experience some delay while opening vm console windows.

We used to have a black screen for about 1 or maybe 2 seconds before we got to see our vm console screen.

But now we have to watch a black screen  9 to 10 seconds before we get to see our vm console.

Has anyone got any ideas what i can do to speed up this process?

One weird thing i noticed.

In the vCenter database we used to have the following tables.

VPX_HIST_STAT1

VPX_HIST_STAT2

VPX_HIST_STAT3

VPX_HIST_STAT4

But now i see these tables are not here anymore, instead i see a lot of new tables.

VPX_HIST_STAT1_1

VPX_HIST_STAT1_2

VPX_HIST_STAT1_3

etc.

and also

VPX_HIST_STAT2_1...

VPX_HIST_STAT3_1...

VPX_HIST_STAT4_1...

etc

I have no idea if this have something to do with each other, but i can't check the fragmentation of the performance history anymore.

use vCenter5
go
dbcc showcontig (VPX_HIST_STAT1)
go

Gives error: Msg 5239, Level 16, State 1, Line 1
Unable to process object ID 2102298549 (object 'VPX_HIST_STAT1') because this DBCC command does not support objects of this type.

Any help would be appreciated, thank you.

I am using vSphere ESXi 4.1 on one of our hosts and we had some issues that we had to remove one host from our vCenter. Now when we are trying to add the host back again to vCenter its giving an error of permission denied. This is because the lockdown mode is enabled.

When I try to disable it through console the option "Configure lockdown mode" is grey.

I have experienced this problem with the 5.1 upgrade including the latest 5.1.0b. In fact the latest patch makes it impossible to add users explicitly via the vSphere client whereas previously I could do this.

The problem description is as follows:

• Users do not authenticate via the web client or via vSphere client
• Users receive the error "Cannot complete login due to an incorrect user name or password" on the vSphere client
• Users receive the error "The authentication server returned an unexpected error: ns0:RequestFailed: Internal Error while creating SAML 2.0 Token. The error may be caused by a malfunctioning identity source.

Things I have tried:

• I have followed this article but the solution re: RPC server not available does not apply as this does not appear in the logs @ http://kb.vmware.com/kb/2034798
• Added new domain users
• Explicitly added users in the vSphere client giving them full administrative privileges and propogating to all child objects
• Domain groups which the users are part of (IT Operations) are added under SSO administrators group (SSO Users and Groups --> Groups --> __Administrators__ have the principals 'ITOperations' and 'Domain Admins' - they are both Active Directory groups)

Observations:

• Putting the user in the 'Domain Admins' group allows the user to successfully log-in to both vSphere and web clients - obviously this is not a practical solution to the problem but unsure as to why it works - members of the IT Operations group can successfully log-in to the vCenter server so also unsure as to what permissions would be required for this to work.
• Granting users explicit access via the vSphere client used to work in previous version of 5.1.0 - with 5.1.0b the users get the "Cannot complete login" error

Our set-up:

• vCenter sits on Server 2008 R2 Enterprise
• Active Directory runs in our environment and handles all log-ins - SSO should be set-up to intergrate itself with AD but not sure why it's not working
• 1 ESXi 5.0 host

imsTrace log:

2013-01-03 13:48:51,781, [castle-exec-1], (LocalisAccessHelper.java:567), trace.com.rsa.ims.localis.LocalisAccessHelper, DEBUG, vCenter.Company.local,,,,Invoking GetAllLocalOSDomains() Local OS call
2013-01-03 13:48:51,842, [castle-exec-1], (LocalisAccessHelper.java:575), trace.com.rsa.ims.localis.LocalisAccessHelper, DEBUG, vCenter.Company.local,,,,GetAllLocalOSDomains Local OS call status 0
2013-01-03 13:48:51,855, [castle-exec-1], (LocalisAccessHelper.java:523), trace.com.rsa.ims.localis.LocalisAccessHelper, DEBUG, vCenter.Company.local,,,,Invoking GetUserGroupsByName(COMPANY\vspheretest) Local OS call
2013-01-03 13:48:51,958, [castle-exec-1], (LocalisAccessHelper.java:531), trace.com.rsa.ims.localis.LocalisAccessHelper, DEBUG, vCenter.Company.local,,,,GetUserGroupsByName Local OS call status 6
2013-01-03 13:48:51,964, [castle-exec-1], (GroupAccessLocalIS.java:313), trace.com.rsa.ims.admin.dal.localis.PrincipalAccessLocalIS, DEBUG, vCenter.Company.local,,,,Lookup failure: [GroupInfo.c:254] NetUserGetLocalGroups failed: Access is denied.

2013-01-03 13:48:51,969, [castle-exec-1], (SecurityTokenServiceImpl.java:117), trace.com.rsa.riat.sts.impl.SecurityTokenServiceImpl, ERROR, vCenter.Company.local,,,,Error while trying to generate RequestSecurityTokenResponse
com.rsa.common.UnexpectedDataStoreException: Unexpected Local OS exception
    Caused by: com.rsa.ims.localis.LocalisAccessError: Local O/S Identity Source Error: LOCALIS_STATUS_INTERNAL, extended error: 5 : [GroupInfo.c:254] NetUserGetLocalGroups failed: Access is denied.

imsRuntimeAudit log:

2013-01-03 13:48:51,580, <longstring1>,<longstring2>,,192.168.0.110,AUTHN_LOGIN_EVENT,13002,SUCCESS,AUTHN_METHOD_SUCCESS,<longstring3>,<longstring4>,<longstring5>,<longstring6>,vspheretest,vspheretest,SYSTEM,,,,,,000000000000000000001000f0022001,LDAP_Password,,,,,,,,,,,,,

vpxd log:

2013-01-03T13:48:50.565Z [00620 info '[SSO]' opID=C001001B-00000004-3b] [UserDirectorySso] Authenticate(vspheretest, "not shown")
2013-01-03T13:48:52.049Z [00620 error '[SSO]' opID=C001001B-00000004-3b] [UserDirectorySso] AcquireToken SsoException: Unexpected SOAP fault: ns0:RequestFailed; request failed.
2013-01-03T13:48:52.049Z [00620 error 'authvpxdUser' opID=C001001B-00000004-3b] Failed to authenticate user <vspheretest>
2013-01-03T13:48:56.051Z [00620 info 'commonvpxLro' opID=C001001B-00000004-3b] [VpxLRO] -- FINISH task-internal-574 --  -- vim.SessionManager.login --
2013-01-03T13:48:56.051Z [00620 info 'Default' opID=C001001B-00000004-3b] [VpxLRO] -- ERROR task-internal-574 --  -- vim.SessionManager.login: vim.fault.InvalidLogin:
--> Result:
--> (vim.fault.InvalidLogin) {
-->    dynamicType = <unset>,
-->    faultCause = (vmodl.MethodFault) null,
-->    msg = "",
--> }
--> Args:
-->

Hello,

I was successfully able to install my vCenter Server 5.5. For identity sources I have vsphere.local as default but I have also set-up AD (Integrated Windows Authentication) under configuration. I want to be able to log on using an AD account.

I am able to set vCenter Server permissions using the AD account (users / groups populate just fine from AD domain) and set it with role of Administrator. However I can't log on using the AD account to vCenter server. I keep getting that the username / password is incorrect though I know it isn't. Am I missing something? I have tried in context of

domain\user

user@domain.local

user itself but no go.

Any advise is greatly appreciated.

Regards,

GV

Hi.

Instead of hijacking other one's thread having the same problem I decided to start a new thread, so sorry for double posting.

After promoting a new DC and demoting the old one we have the problem that VCenter 5.1a no longer starts.

Taking a look at the imsTrace.log file of SSOServer we see the following line:

Caused by: javax.resource.spi.ResourceAdapterInternalException: Unable to create managed connection olddc.ourdomain.com:3268

As we can see SSO still tries to contact the old dc now beeing a simple member server instead of the new one - the question is why?

We checked health of AD by running DCDIAG and BPA both not seeing any problems. Additionally we checked DNS by hand to ensure that no SRV or any other records are present which reference the old DC. Also all other AD dependent services like Exchange, SharePoint, DFS run without issue and do not indicate any problems.

We also found the krb5.conf file of SSO which still references the old DC by the following entry:

[realms]
OURDOMAIN.COM = {
    kdc = olddc.ourdomain.com
    default_domain = OURDOMAIN.COM
}

However changing that entry does not solve the problem because after a short period this entry is replaced automagically by ??? - that's the question.

Mybe someon else has some ideas what to check next.

Cheers.

Dear VMware Community!

I don't have any web interface after install. Could you help me to solve this issue?

I installed successfully VMware-ESXi-5.5.0, and then downloaded and deployed VMware-vCenter-Server-Appliance-5.5.0.5101-1398493.

This is nmap scan results of vCenter Server Appliance:
Starting Nmap 6.40 ( http://nmap.org ) at 2013-11-18 10:47 Środkowoeuropejski czas stand.
Host is up (0.00s latency).
Not shown: 96 closed ports
PORT     STATE    SERVICE
22/tcp   open     ssh
135/tcp  filtered msrpc
8009/tcp filtered ajp13
8080/tcp filtered http-proxy
MAC Address: 00:0C:29:A1:86:C9 (VMware)
Nmap done: 1 IP address (1 host up) scanned in 0.86 seconds

I hope that some of you faced with this problem, because I can't find a solution!:-)

In attached file you can find screenshot form console.

Cheers!

By the way, from default virtual machine hardware version is 7, I upgraded it to 10 but without any change.

in vcenter we show temperature alarms  . i cant find any problem in hp ilo. what is problem ? it can be sensitivityof the alarm ? how can i understand what is solution. what is sensitivity %50 or %90 ?

Configuration: vCenter Virtual Appliance running 5.1.0.  2 x identical ESXi hosts running 5.0U1.  VCVA is running on ESXi host 'a'.

Symptom: vCenter complains of a disconnect in communication with the host, but automatically reconnects after a moment.  ESXi hosts do not experience any issues - no reboots, no interruption to running VMs on them or connections to applications on the VMs.  Have not been able to find any seemingly relevant messages in the logs on either ESXi hosts.

Times of events:

Oct 30, 3:07PM - disconnect from host 'b', automatically reconnected after a moment

Nov 6, 10:35PM - disconnect from host 'a', automatically reconnected after a moment

Nov 20, 8:00AM - disconnect from host 'a', automatically reconnected after a moment

The key errors that I've located are in the vCenter vpxd.log files.  Same pattern of messages for each occurrence (didn't see these messagea at any other time).

Does anyone have any ideas as to what service is connecting to what, or where I might look for further information regarding this issue?  I've not come up with any useful KB articles or discussion posts regarding these messages.

Any ideas would be appreciated!

2012-10-30T19:07:09.172Z [7FEFA22BD700 info 'commonvpxLro' opID=474CFF98-00005D8C-e] [VpxLRO] -- BEGIN task-internal-44909 --  -- vmodl.query.PropertyCollector.retrieveContents -- 98223be0-04ed-2fc5-75e4-e246662b83c5(52f148c6-b51f-212a-9f3f-613de90a774a)
2012-10-30T19:07:09.174Z [7FEFA22BD700 info 'commonvpxLro' opID=474CFF98-00005D8C-e] [VpxLRO] -- FINISH task-internal-44909 --  -- vmodl.query.PropertyCollector.retrieveContents --
2012-10-30T19:07:11.877Z [7FEFA22FE700 error 'HttpConnectionPool-000000'] [ConnectComplete] Connect failed to <cs p:00007fef9c692d60, TCP:hostname.fqdn.com:443>; cnx: (null), error: N7Vmacore15SystemExceptionE(Name or service not known)
2012-10-30T19:07:11.877Z [7FEFA31F3700 warning 'VpxProfiler' opID=HB-host-444@28464-c0785c1b] ClientAdapterBase::InvokeOnSoap: (hostname.fqdn.com, vpxapi.VpxaService.retrieveChanges) [SoapRpcTime] took 20014 ms
2012-10-30T19:07:11.877Z [7FEFA31F3700 error 'vpxdvpxdVmomi' opID=HB-host-444@28464-c0785c1b] [VpxdClientAdapter] Got vmacore exception: Name or service not known
2012-10-30T19:07:11.878Z [7FEFA31F3700 error 'vpxdvpxdVmomi' opID=HB-host-444@28464-c0785c1b] [VpxdClientAdapter] Backtrace:
--> backtrace[00] rip 00007fefa8297a84 Vmacore::System::Stacktrace::CaptureWork(unsigned int)
--> backtrace[01] rip 00007fefa8176ae2 Vmacore::System::SystemFactoryImpl::CreateQuickBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)
--> backtrace[02] rip 00007fefa80d7da5 Vmacore::Throwable::Throwable(std::string const&)
--> backtrace[03] rip 00007fefa825fd3c Vmacore::SystemException::SystemException(int, std::string const&)
--> backtrace[04] rip 00007fefa82846dd /usr/lib/vmware-vpx/libvmacore.so(+0x3e66dd) [0x7fefa82846dd]
--> backtrace[05] rip 00007fefa8166bec /usr/lib/vmware-vpx/libvmacore.so(+0x2c8bec) [0x7fefa8166bec]
--> backtrace[06] rip 00007fefa82956f3 /usr/lib/vmware-vpx/libvmacore.so(+0x3f76f3) [0x7fefa82956f3]
--> backtrace[07] rip 00007fefa828a5c2 /usr/lib/vmware-vpx/libvmacore.so(+0x3ec5c2) [0x7fefa828a5c2]
--> backtrace[08] rip 00007fefa828599f /usr/lib/vmware-vpx/libvmacore.so(+0x3e799f) [0x7fefa828599f]
--> backtrace[09] rip 00007fefa6bff7b6 /lib64/libpthread.so.0(+0x77b6) [0x7fefa6bff7b6]
--> backtrace[10] rip 00007fefa62c8c6d /lib64/libc.so.6(clone+0x6d) [0x7fefa62c8c6d]
-->
2012-10-30T19:07:13.336Z [7FEFA31F3700 info 'vpxdvpxdVmomi' opID=HB-host-444@28464-c0785c1b] [ClientAdapterBase::InvokeOnSoap] Invoke done (hostname.fqdn.com, vmodl.query.PropertyCollector.cancelWaitForUpdates)
2012-10-30T19:07:13.337Z [7FEFA31F3700 warning 'VpxProfiler' opID=HB-host-444@28464-c0785c1b] [VpxdHostSync] GetChanges host:hostname.fqdn.com (192.168.1.187) [GetChangesTime] took 21474 ms

Hi every one,

i have join the vCenter node to our Domain

and reboot the VM appliance vCenter.After that, i check and it's ok vCenter Appliance is join our Active directory domaine Windows Server 2003.

Now,i try to add a new source identity, i have an error: Provided credentials are not valid

this is my configuration when i try to add a new source

• identity source type: Active Directory as LDAP Server
• Name: ourdomain.com
• Base DN for users: OU=Users,DC=OURDOMAIN,DC=COM
• Domain name: OURDOMAIN.COM
• Domain alias: OURDOMAIN
• Base DN for groups: OU=Users,DC=OURDOMAIN,DC=COM
• Primary server URL: ldap://DC1.OURDOMAIN.COM:389
• Secondary server URL:
• Username: Administrateur@ourdomain.com
• Password: PasswordofAdministrateur

When i click test connection, it's work i have seccuessfuly test but whene i try to add this source i have this error: Provided credentials are not valid

Any one can help me please ?

Best regards

I've been trying to get my vCenter Server Appliance 5.1 install to migrate to 5.5 OK, but it's giving me headaches.  Some interface elements are missing, I can't get consoles to work, etc.

That said, can I just start with a fresh vCenter Server Appliance install 5.5 instead?  What settings are even stored within vCenter vs. the individual ESXi host machines?  Is this OK to do on a live system?

Hi all,

I'm having a problem with the webaccess feature on my vcenter server 4.1.

Until yesterday everything works fine, but since this morning no one can login to the webaccess interface provided by vcenter server.

When someone try to login gets the error

"The server was unable to process your log in request.  Please check with your server administrator."

I checked the vcenter server, rebooted it, checked tomcat service, firewall permissions and so on.

I also tryied to login into the hosts' webaccess directly and everythings works fine...

Someone could help me?

Access through VIC works fine.

We are unable to open the console of any VM through vSphere Web Client following the upgrade to 5.5 This goes for all user groups including administrators.

When you right click on the VM to get the menu the Console selection turns from colored to gray. Has anyone else see anything similar? Is there a fix available?

Thanks in advance!

Jason

This is my inital step into the Vmware world and it isn't going well.

Downloaded the latest vCenter Server appliance  5.1.0.5100 and created a new VM in VMware Workstation 8.0.4.

Started the VM and let it work it's way through the install.

browse (Firefox 15.0.1) to https://10.1.5.7:5480 and I log in using root & the default password.  Get the EULA & accept.

The wizard starts.  Select the config with default settings then select Start.

During SSO I get:

Failed to execute '/usr/sbin/vpxd_servicecfg sso write embedded embedded     CENSORED  CENSORED':
VC_CFG_RESULT=702(Error: An unexpected error ocurred during the installation of the appliance SSO service. Please collect a support bundle and file a service request.)

Starting vCenter Server I get:

Failed to execute '/usr/sbin/vpxd_servicecfg sso write embedded embedded     CENSORED  CENSORED':
VC_CFG_RESULT=702(Error: An unexpected error ocurred during the installation of the appliance SSO service. Please collect a support bundle and file a service request.)
Failed to execute '/usr/sbin/vpxd_servicecfg service start':
VC_CFG_RESULT=101(Error: vCenter Server failed to start.)

I thought that a fully packaged VM with a wizard would at least give me a nearly functioning setup.

I've tried setting the hostname/static IP.  No difference

Configure database was set to embedded by the wizard.  Since this will be a small installation (2 ESXi hosts, <30 clients) that should be sufficient.

Trying to change the SSO deployment type always fails with "Error: VPXD must be stopped to perform this operation."

Configure Authentication/Configure Services don't go anywhere.

Trying a custom configuration gave the same results.

Anyone have an idea as to what I'm doing wrong?

Good day, and I hope yours is better than mine...

Just downloaded and set up VCSA 6.0 U2.  Finally got it to join my domain*.  Added admin group from domain and gave them permissions.  Every time I tried to use NT authentication (the checkbox) it would error out.

I found and followed articles 2020970 and 21112283.  Now I am unable to log into the web client nor the vSphere client.

web client yeilds this

A server error occurred.

[500] SSO error: Cannot connect to the VMware Component Manager https://vcenter.sso.unitedpolicefcu.com/cm/sdk?hostid=827ac00b-1131-452e-b9fa-6b69a3a3f7ef

Check the vSphere Web Client server logs for details.

          vsphere client says

Windows session credentials cannot be used to log into this server   (which is what started the 2 KBs above)

or

Cannot complete login due to incorrect user name or password  (I tried SSO Admin, domain user, appliance root user)

I have tried the certificate replacement steps (option 8, then 8, then 3, then 4, then 8 again).  Each ends with errors similar to this:

2016-03-29T18:35:36.382Z   Updating certificate for "com.vmware.vim.eam" extension

Status : 0% Completed [Operation failed, performing automatic rollback]

Error while performing Cert Replacement operation, please see /var/log/vmware/vmcad/certificate-manager.log for more information.

Performing rollback of Root Cert...

Get site name

hq

followed by this at the end of the roll back

Updated 0 service(s)

Rollback Status : 40% Completed [Rollback machine Cert...]                 

Rollback Status : 50% Completed [Rollback vsphere-webclient Cert...]                 

Rollback Status : 60% Completed [Rollback vpxd Cert...]                 

Rollback Status : 70% Completed [Rollback vpxd-extension Cert...]                 

2016-03-29T18:36:23.960Z   Updating certificate for "com.vmware.vim.eam" extension

Error while reverting certificate for store : vpxd-extension

Rollback Status : 0% Completed [Rollback operation failed]

Error while performing rollback operation, please try Reset operation...

please see /var/log/vmware/vmcad/certificate-manager.log for more information.

Thanks for the help from Stumped in Miami.

*  And for those of you getting Error 11 on trying to join the domain go into the SCVA web portal, drill down to the actual network settings and switch the DNS to manual.  Sorry I can't be specific on the actual path to this setting.  Although I gave it specific DNS at set up and a static IP I finally found that it had reverted to getting DNS from DHCP...  Hope this helps.

I have two host running ESXi 5.0 which I have succesfully added to my vcenter (5.0 client and server).  However one of the hosts is missing 3 vm's from its inventory.  I can connect directly to the ESXi 5.0 server and see all vm's running.  I am sure it is not coincidence that these three servers are my only linux servers (canned Squid proxy servers).

1) I stopped and started the Vcenter server services.  same results.

2) I have removed and readded the host. same results, but I do want to note that during the add process I did see that all servers showed in the list of vm's running on the host.

Thanks for any help!

J