AD connection in vCenter

Similar Questions

• vFoglight unable to connect to vcenter after disabling sslv3 7.0

  Y at - it a patch for vfoglight 7 which allows for connectivity to vcenter TLS?

  After you disable SSLv3 in vcenter, foglight is unable to connect.

  [Quartz [0] - 90] ERROR com.quest.agent.esx.task.RelationsTask - error when running: ERROR: VI SDK invoke exception: javax .net .ssl .SSLHandshakeException: remote host closed connection during handshake

  java.rmi.RemoteException: VI SDK invoke exception: javax .net .ssl .SSLHandshakeException: remote host closed connection during handshake

  at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:183)

  at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:125)

  at com.vmware.vim25.ws.VimStub.retrieveServiceContent(VimStub.java:1409)

  to com.vmware.vim25.mo.ServiceInstance. (ServiceInstance.java:85)

  to com.vmware.vim25.mo.ServiceInstance. (ServiceInstance.java:69)

  at com.quest.vmware.api.connection.VIService.connect(VIService.java:60)

  at com.quest.vmware.api.connection.VIService.login(VIService.java:82)

  at com.quest.agent.esx.task.ESXAgentTask.connect(ESXAgentTask.java:178)

  at com.quest.agent.esx.task.ESXAgentTask.run(ESXAgentTask.java:116)

  at com.quest.agent.esx.ESXAgent.runTask(ESXAgent.java:407)

  at com.quest.agent.esx.ESXAgent.esxRelationsCollection(ESXAgent.java:469)

  at sun.reflect.GeneratedMethodAccessor42.invoke (unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

  at java.lang.reflect.Method.invoke(Method.java:597)

  at com.quest.glue.core.services.EquivalenceInvocationHandler.invoke(EquivalenceInvocationHandler.java:70)

  at com.quest.glue.core.agent.AgentInteractionHandler.invoke(AgentInteractionHandler.java:186)

  to com.sun.proxy. $Proxy55.esxRelationsCollection (unknown Source)

  at sun.reflect.GeneratedMethodAccessor42.invoke (unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

  at java.lang.reflect.Method.invoke(Method.java:597)

  at com.quest.glue.core.agent.scheduler.CollectorCallback.invokeCollector(CollectorCallback.java:162)

  at com.quest.glue.core.agent.scheduler.CollectorCallback.execute(CollectorCallback.java:130)

  to com.quest.glue.core.scheduler.quartz.QuartzScheduler$ ScheduledTaskSequentialJob.execute (QuartzScheduler.java:716)

  at org.quartz.core.JobRunShell.run(JobRunShell.java:202)

  to java.util.concurrent.ThreadPoolExecutor$ Worker.runTask (ThreadPoolExecutor.java:895)

  to java.util.concurrent.ThreadPoolExecutor$ Worker.run (ThreadPoolExecutor.java:918)

  at java.lang.Thread.run(Thread.java:662)

  2015-09-01 15:25:31.798 ECHO FATAL [Quartz [0] - 90] com.quest.agent.esx.task.RelationsTask - the agent could not establish an SSL secure connection to the VirtualCenter.  Please check your configuration of the agent in order to ensure a connection correct information has been entered.

  2015-09-01 15:25:31.798 ECHO

  Thank you

  Hi JLAPRADE,

  I read a similar case, it seems that the problem could be solved either:

  1) that allows SSLv2Hello to vCenter, or

  (2) upgrade to the latest Foglight/Agent managers to the latest version.

  Regarding the #1 option:

  Client configuration file updated the vpxd.cfg in vCenter. It's the line that needs to be changed:

  TLSv1

  To add the SSLv2Hello Protocol, the client he added after a comma:

  TLSv1, SSLv2Hello

  This solves the problem for this client, but you can check with VMware.

  If the problem persists after trying these solutions or if you have problems, their implementation, please open a request of Service (SR) with the support and mention this thread.

  This is where an SR can be created: support.software.dell.com/create-service-request

  Concerning

  Gaston.

• How to change the remote ip address connection svs - vCenter was reloctated

  We just finished relocating our vCenter from one subnet to another, the IP address has changed and now we cannot add vmware port groups in the vNetwork Distributed Switch.

  When we tried to add the port profile the warning was "warning: operation successful locally but the update failed on the vCenter server.» Check if you are connected to vCenter Server. "We have checked the configuration on the 1010V link and found the culprit, the svs to vCenter connection had the old remote ip address.

  What is the preferred method to change it without destroying the config?

  Thanks in advance.

  How to do is the following:

  n1000v (config) # svs connection vcenter

  n1000v(config-SVS-conn) # no connection

  # 1.1.1.1 remote ip address n1000v(config-SVS-conn)

  n1000v(config-SVS-conn) # connect

  Essentially to turn off, change the IP address and then reactivate the connection.

• Can not connect to vcenter after reboot

  Hello VMware,

  I can not connect to vcenter after reboot with the error «Failed to connect to the Vmware research service»

  

  I tried to follow below doc but no help.

  http://www.myvmwareblog.com/2012/11/28/lookupservicesdk-SSL-certificate-verification-failed/

  I tried to play with the Vcenter screen underneath, but no luck.

  
  

  To resolve this problem, replace the VCSA IP with hostname VCSA in the search service configuration file, ls_url.txt file.

  To replace the VCSA IP address with the host VCSA name in the ls_url.txt file:

  1. Connect to the VCSA via ssh under the root user
  2. Go to the directory/etc/vmware-sso using the command:

     CD/etc/vmware-sso

  3. Make a backup copy of the file ls_url.txt using the command:

     CP ls_url.txt ls_url.txt.bak

  4. Open the file ls_url.txt using a text editor
  5. Replace the VCSA IP address with the host name of the VCSA. For example:

     https:// Lookupservice/XXXXXXXXXX/sdk

     Where XXXXXX is the host name of the VCSA.

     Note: It is usually the host name of the domain the VCSA FULL name. Make sure it matches the common name (CN) in the certificate name.

  6. Restart the VCSA services by running the command:

     restart the /etc/init.d/VMware-vpxd
     restart the /etc/init.d/VMware-SSO
     restart the /etc/init.d/VMware-InventoryService

     Or

     Restart the VCSA.

  Alternatively, you can use this workaround to regenerate the certificates for the vCenter Server Appliance.To to regenerate the certificates for the vCenter Server Appliance:

  1. Temporarily change the IP address of the vCenter Server Appliance to a different IP address, not used
  2. Restart the vCenter Server Appliance
  3. Change the IP address of the vCenter Server Appliance to the originating IP address
  4. Restart the vCenter Server Appliance
  5. Connect to vCenter Server Appliance, https://vcenterserveripmanagement Web page: 5480
  6. Click the Administration tab, and then select Yes to certificate enabled regeneration
  7. Click send to save the changes
  8. Restart the vCenter Server Appliance

• Unable to connect to Vcenter Server

  I couldn't connect to vCenter Server when you use the web client of vSphere. The administrator accesses vCenter Server by using the customer earlier in the day. ?

  Verify that the vCenter Single Sign-On service is running on the server vCenter Server

• To connect to vCenter using the same Session with PowerCLI

  Hi all

  Is it possible that we can establish multiple connections to vCenter using the same session with Powercli.

  As connect-viserver-Server "vcenter1" - domain\domainacnt of the username-password "Password".

  is to establish several connections and we want to limit, because we are in the process of report generation based on the web developing using Powercli with IIS.

  Please suggest.

  You can use the Session parameter on the cmdlet Connect-VIServer .

  I use this for the PowerShell Workflows, see workflow of PowerShell and PowerCLI

• I can't connect to Vcenter using vsphere client

  I installed vCenter 6.0 and vsphere client 6.0. I can connect to the web client, but when I am connected to vCenter using vsphere client I got error.

  

  In vsphere version 5.5 I can connect to vCenter using vsphere client 5.5.

  I can't find any information on this subject on vmware.com.

  Do vsphere 6.0 support connecting to vCenter using vsphere client?

  I guess you are using Vsphere Client beta built which has only the features of client enabled host.

  Try GA build Client to connect to vCenter. However, the latest vsphere 5.1 leave are available only in the web client.

• BDE 2.1.1 Fling Management server does not connect to vCenter

  I have the management server deployed in the environment, the plugin installed successfully and vCenter is connected to the administration via the Web interface of vCenter server. This problem occurs when I go to a data store or add it to a network.

  I get the following (via the GUI or CLI):

  Version: 2.1.1

  Welcome to Serengeti CLI

  Serengeti > Connect - host hadoop - mgmt.or1.omniture.com:8443

  Enter the user name: [email protected]

  Enter password: *.

  Connected

  Serengeti > data store, add - name defaultDS - spec DS10HadoopOR1 - shared type

  datastore defaultDS add failed: unable to connect to vCenter Server.

  The error in the serengeti.log file is a generic JAVA error. The vCenter is 5.5U2 and ESXi hosts are 5.5U1.

  --

  Chris.

  Thanks Charlie for a helping hand.

  I found some info in the serengeti.log and the serengeti - boot.log Chris post:

  Serengeti - boot.log:

  I, [2015-02 - 12 T 20: 56:27.722910 #3336] INFO -: templateVmName: vSphere Big Data Extensions - Node Template

  Serengeti.log:

  Caused by: com.vmware.bdd.utils.AuAssert: FAILURE

  at com.vmware.bdd.utils.AuAssert.FAILURE(AuAssert.java:28)

  at com.vmware.bdd.utils.AuAssert.check(AuAssert.java:43)

  at com.vmware.bdd.utils.AuAssert.check(AuAssert.java:50)

  at com.vmware.bdd.service.impl.ClusteringService.getTemplateVm(ClusteringService.java:408)

  [2015 02-12 T 14: 46:47.438 - 0700] INFO Event_Expander | com.vmware.bdd.service.event.EventScheduler: to develop events: [{me = null: VirtualMachine:vm - 136, event = VmResourcePoolMoved}]

  [2015 02-12 T 14: 46:47.626 - 0700] INFO pool-2-wire-4 | com.vmware.bdd.service.utils.VcResourceUtils: folder xxx-uuid was not found.

  [2015 02-12 T 14: 46:47.627 - 0700] INFO pool-2-wire-4 | com.vmware.bdd.service.event.VmEventManager: VM root folderxxx-uuid is not yet created. Ignore the event outside of VM.

  [2015 02-12 T 14: 46:58.393 - 0700] Event_Handler INFO | com.vmware.bdd.service.event.EventScheduler: processed 2 new events

  [2015 02-12 T 14: 46:58.394 - 0700] Event_Handler INFO | com.vmware.bdd.service.event.EventScheduler: processed events: [{me = null: VirtualMachine:vm - 137, event = VmResourcePoolMoved}, {me = null: VirtualMachine:vm - 136, event = VmResourcePoolMoved}]

  [2015 02-12 T 14: 47:13.183 - 0700] Http-8443-5 ERROR | com.vmware.bdd.rest.RestResource: rest call error

  com.vmware.bdd.exception.BddException: unable to connect to vCenter Server.

  at com.vmware.bdd.exception.BddException.INIT_VC_FAIL(BddException.java:189)

  at com.vmware.bdd.rest.RestResource.verifyInitialized(RestResource.java:1175)

  at com.vmware.bdd.rest.RestResource.addDatastore(RestResource.java:636)

  This log shows THAT BDE Server cannot find the node named "vSphere Big Data Extensions - Node Template" model.  When you deploy the BDE Fling, the management server and hadoop-model VM must be deployed in the same folder in, under a pile of vCenter.  Please check and follow the BDE 2.1.1 Fling deployment guide and deploy again.  BTW, you can customize the name of the server VM and the VM model during their deployment and make sure the correct model name together when you deploy the server VM.

• Impossible to connect to vCenter Server 5.5 using the vSphere Client

  Hello

  
  

  I'm trying to configure VMware Lab home using the link below and I have reached a stage where I need to connect to vCenter Server using the vSphere client.

  
  http://boerlowie.WordPress.com/2011/12/13/building-the-ultimate-vSphere-lab-part-9-ESXi/

  
  

  I installed the package of 5.5 full vCenter server using the simple installation option and it includes vCenter server, single sign - on, Webclient vSphere, vCenter server and vCenter Server inventory service. All the the latter is installed on a virtual machine that is running Windows server 2008 R2 guest OS.

  
  

  Whenever I try to open a session on the vCenter Server uses the vSphere client, one of the following error is displayed.

  
  

  1. you do not have the permissions to connect to the server 'vCenter server IP address.

  2. cannot complete the connection incorrect username or password-, this error is visible when I do not specify domain\username domain user name and simply enter the user name.

  
  

  For the details of the error, please see the screenshots - vSphere_client_1, vSphere_client_2 and vSphere_client_3.

  
  

  As suggested in the link below, I tried to create an SPN and then set the SPN (Principal of Service name) and the UPN (User Principal name) in the Active Directory identity Source using the web of vSphere client (please see screenshot vSphere_Webclient_2)

  
  

  http://vinfrastructure.it/2014/01/issue-in-logging-into-vCenter-server-using-Windows-ad-credentials/

  
  

  To fix the permission error, I tried to add the domain user to the Administrators group on the server vCenter (see screenshot vSphere_Webclient_1).

  
  

  However, none of the above-mentioned resolution has worked.

  
  

  So can someone please help? I am stuck because of this problem and badly need help to move forward.

  
  

  Thank you

  AJMAL
  

  Able to connect to the vSphere Client do you use the [email protected] account?

  Have you already set up permissions on the server vCenter object?

  André

• Unable to connect to vCenter Server 5.0 using the vSphere Client - unknown error.

  I am trying to connect to vCenter using vSphere client (from different computers, including the server itself) and get this:

  vSphere Client could not connect to "vCenter_Server_IP_Address".
  A unknown connection error has occurred. (The request has failed because of a logon failure. (Unable to connect to the remote server))

  I am able to connect to the host directly, but of course, can't do anything with it since the vCenter is "in da house".

  There is no problem with it, not big changes and nothing indeed directly on the server vCenter (i.e. W2008r2x64) so, my confusion deepens. 5.1 ESXi

  Any ideas what could have happened and how to fix it?

  observe the following error in the logs.

  2014-04 - 04T 13: 35:23.506 + 01:00 [error 02720 "Default" opID = SWI-f3a52464] [VdbStatement] given the driver diagnosis are 42000:1:1105: [Microsoft] [SQL Native Client] [SQL Server] could not allocate space for object ' dbo. VPX_EVENT'. 'PK_VPX_EVENT' in 'VIM_VCDB' database because the 'PRIMARY' filegroup is full. Create disk space by deleting unnecessary files, removing objects in the filegroup, a

  Follow this article to fix the problem.

  http://alexjs.EU/VMware-ESX-and-a-full-SQL-Server-database/

• When I change authentication to LDAP (EMbedded LDAP) vco for test, vco client is unable to connect to vcenter. Can someone tell me what is the problem I have

  It is seemly all things are OK configuration web page

  But vco client is unable to connect to vcenter

  Have a screenshot of the vCenter plug-in would help.

  If it is set at the session by the user that the vCO will try to authenticate with the LDAP credentials embedded on the vCenter which of course will fail.

• Fallo en vCenter fornuis after connection a vCenter 5.1

  Hola a todos,

  I have a problema as mirar bastante aun despues no he present find the respond. Vamos a migrar las granjas production version 4.1 has the 5.1 y para ello empiezo por fornuis una pequeña granja as the tests tenemos con back 4.1 ESX host con 4 maquinas office y UN vCenter. Para fornuis utilizo ISO VMware-VIMSetup-all - 5.1.0 - 1235309.

  El vCenter are a Windows Server 2003 64-bit are para las bases of datos del vCenter, Update Manager y el SSO utilizo UN SQL Server 2005. Toda the instalacion is one sin problemas y in el orden previsto, el primero con SSO su base data "Aside" in el followed del inventory service, SQL Server y el vCenter including todos los have that need. Por ultimo, el WebClient. TODO wont in el mismo servidor. The Red than no hay en don't firewall y el DNS works correctamente directa e inversamente.

  Y cuando quiero access al vCenter me don't dice that no permissions as el usuario o tengo y contrasena no son correctos. Accedo SSO al Entonces con el web client con el usuario por defecto admin@System-Domain y accedo sin problemas. Y lo than veo el vCenter are no registered in el inventario del SSO appears. El identity source esta correcto identificando el dominio y los drivers of dominio y prueba of conexion works correctamente. Veo muchos users del dominio appears in the part of SSO users are groups in las pestanas locked y disabled al mismo tiempo than no dice no are blocked or or deshabilitados.

  Leo UN KB of VMware than as this can be a los grupos claims of dominio grupos dentro anidacion problema local del servidor y the respond're poner los local con los local y dominio los con dominio, pero no lo entiendo well o o los no veo donde y como hacer esa asociacion. Tampoco veo como add users of dominio especificando el dominio is that al add users no hay campos para ello como're if all were local al SSO server.

  In este KB menciona el message than obtengo al instalar el vCenter:

  Unable to connect to VMware vCenter Server after upgrading to vCenter Server 5.1 (2035758)

  In the database of the server vCenter, users, or groups have been found who have administrator privileges and are also recognized by vCenter Single Sign On. These users are listed in the vc_admin_users_groups.txt file in the system temp folder. Use these users or groups to connect to vCenter Server.

  Pero no tengo el fichero en ruta indicada mentioned text nor is you can apply the proposal are Québec como he mentioned identity source works correctamente el respond...

  El principal problema claro think that're el vCenter no appears in el inventario SSO del pero no averiguar can not the causa of Quebec no aparezca or can not find a respond al problema. ¿Alguna sugerencia o idea?

  MUCHAS gracias to photos,.

  Kind regards

  
  

  Hola a todos,

  Bueno, me respondo a mi mismo. He fixed the problem, Québec tampoco era realmente is a problem in himself. No se if the respond are the perfecta o If only hay algo than still me pierdo pero el caso are lo I have running.

  Mirar Vmware documentation mucho Despues y th of pages web, articles y foros donde ninguno daba una respond concreta y or even information sober el del SSO behavior y el vCenter, between back informaciones encontradas en sites different he terminado por Hilaire una respond back.

  Por a lado, is dice that to access SSO administrator como al y poder configurar certain things hay than logarse con el usuario del sistema admin@System-Domain con el than efectivamente is you can access pero sin embargo no muestra el vCenter registered por el sencillo reason that no permissions tiene para ello y tampoco el add users works local desde alli. También el al SSO con entering connection works a dominio, pero tampoco en el vCenter permissions tienen como usuario stink tampoco lo muestra.

  Al final en otra web what height the "pista" that users local del servidor windows than aloja el servicio del vCenter tienen acceso permissions, pero ojo, no valen users o grupos anidados grupos dentro local porque el SSO solo without los reconoce correctamente a permissions level. Moraleja todo esto, el unico con al usuario vCenter despues del upgrade permissions are el usuario local administrator of the Máquina del vCenter.

  ASI pues, he could logarme sin problemas in vCenter el con este usuario y dar permits al Administradores del dominio in vCenter con el grupo el rol administrator there starting from este momento is he could enter sin problemas con mi dominio usuario. Lo mismo serviria if we want to include otros grupos o its users.

  I hope os sirva if os encontrais con el mismo problema.

  Kind regards

• Question of vCO Port connecting to vCenter

  Hi all

  I have a problem that I hope can be easily solved. I'm pretty sure I know what the question is, just not how to correct it. When I created vCO to connect to vCenter I get the error "Exception," org.apache.http.conn.HttpHostConnectException: connection to http://vcenter.domain.com:80 denied ' "» What I know about the environment, vCenter here is actually using port 8080 for http connections. I can't change this behavior in vCO so far. Here are two screenshots for configuration and the error itself:

  

  

  No way to change the port vCO tries to use on the side of http, or just something that I'm missing (seems likely )?

  Thank you!

  ~ Brandishes

  jaytindel,

  Apparently I completely missed this all the time, while I was completely up to date with the generation which implement a 'solution' to this question, there is always a workaround solution that must be followed. A VMware support engineer guided me to a KB and using the solution of creating a workflow to add the vCenter Server works in fact for me. This is the KB:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=2042461

  Let me know if you encounter any problems with it.

  ~ Brandishes

• Error connecting to vCenter Server

  After that a sudden loss of power I got the following error trying to connect to vcenter server:

  Internal server error

  2013-05-15 17:47:44, 772 | DEBUG | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). JobManager | Add the activity log: JOB_VC_START
  _CONNECTION > < cloudvcs0(com.vmware.vcloud.entity.vimserver:23b4fe43-1f29-4c6f-adc1-1048b2a8845c) > |
  2013-05-15 17:47:44, 773 | DEBUG | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). CJob                           | updateFailedJob (com.vmware.vcloud.ap
  i.presentation.service.InternalServerErrorException) with locale = null |
  com.vmware.vcloud.api.presentation.service.InternalServerErrorException: internal server error
  at com.vmware.vcloud.vimproxy.internal.impl.VcUpdateListenerImpl.onOuterLoopBreakWithException(VcUpdateListenerImpl.java:721)
  at com.vmware.vcloud.vimproxy.internal.impl.VcUpdateListenerImpl.outerWaitForUpdatesLoop(VcUpdateListenerImpl.java:633)
  at com.vmware.vcloud.vimproxy.internal.impl.VcUpdateListenerImpl.run(VcUpdateListenerImpl.java:343)
  Caused by: org.hibernate.exception.GenericJDBCException: could not execute the query
  at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:126)
  at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:114)
  at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
  at org.hibernate.loader.Loader.doList(Loader.java:2231)
  at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2125)
  at org.hibernate.loader.Loader.list(Loader.java:2120)
  at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:118)
  at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1596)
  at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:306)
  at com.vmware.vcloud.inventory.cache.PropertyMapDao.validateOrGet(PropertyMapDao.java:336)
  at com.vmware.vcloud.inventory.cache.PropertyMapDao.bulkValidateOrGet(PropertyMapDao.java:321)
  at com.vmware.vcloud.inventory.cache.PropertyMapDao.bulkValidateAndGetNewer(PropertyMapDao.java:267)
  at com.vmware.vcloud.inventory.cache.InventoryCacheManagerImpl.bulkGetInternal(InventoryCacheManagerImpl.java:418)
  at com.vmware.vcloud.inventory.cache.InventoryCacheManagerImpl.bulkGet(InventoryCacheManagerImpl.java:549)
  at com.vmware.vcloud.inventory.impl.InventoryServiceImpl.processUpdateSet(InventoryServiceImpl.java:931)
  to com.vmware.vcloud.inventory.impl.InventoryServiceImpl.access$ 300 (InventoryServiceImpl.java:145)
  to com.vmware.vcloud.inventory.impl.InventoryServiceImpl$ 5.run(InventoryServiceImpl.java:860)
  to com.vmware.vcloud.inventory.impl.InventoryServiceImpl$ 5.run(InventoryServiceImpl.java:826)
  at com.vmware.vcloud.common.persist.ConversationContextExecutor.execute(ConversationContextExecutor.java:46)
  at com.vmware.vcloud.inventory.impl.InventoryServiceImpl.processAndBatchUpdates(InventoryServiceImpl.java:826)
  at com.vmware.vcloud.inventory.impl.InventoryServiceImpl.handleUpdate(InventoryServiceImpl.java:799)
  at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke (unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke (unknown Source)
  at java.lang.reflect.Method.invoke (unknown Source)
  at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:309)
  at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
  at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
  at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
  to $Proxy187.handleUpdate (Unknown Source)
  at com.vmware.vcloud.vimproxy.internal.impl.VcUpdateListenerImpl.dispatchUpdates(VcUpdateListenerImpl.java:1080)
  at com.vmware.vcloud.vimproxy.internal.impl.VcUpdateListenerImpl.innerWaitForUpdatesLoop(VcUpdateListenerImpl.java:925)
  at com.vmware.vcloud.vimproxy.internal.impl.VcUpdateListenerImpl.outerWaitForUpdatesLoop(VcUpdateListenerImpl.java:594)
  ... 1 more
  Caused by: java.sql.SQLException: ORA-01555: snapshot too old: rollback segment number with the name "" too small
  ORA-22924: snapshot too old

  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439)
  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:388)
  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:381)
  at oracle.jdbc.driver.T4C8TTILob.processError(T4C8TTILob.java:789)
  at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436)
  at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
  at oracle.jdbc.driver.T4C8TTILob.read(T4C8TTILob.java:146)
  at oracle.jdbc.driver.T4CConnection.getBytes(T4CConnection.java:2313)
  at oracle.sql.BLOB.getBytes(BLOB.java:319)
  at oracle.sql.BLOB.getBytes(BLOB.java:209)
  at oracle.jdbc.driver.T4CBlobAccessor.getBytes(T4CBlobAccessor.java:464)
  at oracle.jdbc.driver.OracleResultSetImpl.getBytes(OracleResultSetImpl.java:676)
  at oracle.jdbc.driver.OracleResultSet.getBytes(OracleResultSet.java:398)
  at org.hibernate.type.AbstractBynaryType.get(AbstractBynaryType.java:101)
  at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:184)
  at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:173)
  at org.hibernate.type.AbstractType.hydrate(AbstractType.java:105)
  at org.hibernate.persister.entity.AbstractEntityPersister.hydrate(AbstractEntityPersister.java:2124)
  at org.hibernate.loader.Loader.loadFromResultSet(Loader.java:1404)
  at org.hibernate.loader.Loader.instanceNotYetLoaded(Loader.java:1332)
  at org.hibernate.loader.Loader.getRow(Loader.java:1230)
  at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:603)
  at org.hibernate.loader.Loader.doQuery(Loader.java:724)
  at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259)
  at org.hibernate.loader.Loader.doList(Loader.java:2228)
  ... 32 more
  2013-05-15 17:47:44, 774. DEBUG | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). JobString | Object - object: cloudvcs0 (com.
  name of the VMware.vCloud.Entity.vimserver:23b4fe43-1f29-4c6f-adc1-1048b2a8845c operation): JOB_VC_START_CONNECTION |
  2013-05-15 17:47:44, 842. DEBUG | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). CJob                           | Not the last pending work: [cloudvcs0 (c
  OM. (VMware.vCloud.Entity.vimserver:23b4fe43-1f29-4c6f-adc1-1048b2a8845c)], status [3] = |
  2013-05-15 17:47:44, 846. DEBUG | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). CJob                           | Last jobs update: [cloudvcs0 (c
  OM. (VMware.vCloud.Entity.vimserver:23b4fe43-1f29-4c6f-adc1-1048b2a8845c)], status = [3], [15/05/13 17:47] |
  2013-05-15 17:47:44: 964 | DEBUG | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). ValidationServiceImpl | Jump queuing of the validator for co
  validator of m.vmware.ssdc.backend.valeventhandler.ProviderVdcVALStateValidator since it is a duplicate, current validation queue length: 1 |
  2013-05-15 17:47:44, 966 | INFO | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). InventoryServiceImpl | Reception earphone stopped for VC 23 b
  4fe43-1f29-4c6f-adc1-1048b2a8845c |
  2013-05-15 17:47:44, 966 | WARN | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). InventoryRecordPurger | Records of the inventory for 23b4fe4 trap
  3 1f29-4c6f-adc1-1048b2a8845c is not active.
  2013-05-15 17:47:44, 968 | INFO | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). VcUpdateListenerImpl | Releasing the proxy property of VC
  23b4fe43-1f29-4C6F-ADC1-1048b2a8845c |
  2013-05-15 17:47:44, 968 | INFO | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). VcUpdateListenerImpl | trying to clear the instance of cell id on
  VC 23b4fe43-1f29-4c6f-adc1-1048b2a8845c (current number of retries to 0). |
  2013-05-15 17:47:44, 969 | INFO | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). VcUpdateListenerImpl | 23b4fe43-1f29-4c6f-adc1-1048b2a88 VC
  45 c: attempt to set the instance id of cells from 70 to 0.

  Caused by: java.sql.SQLException: ORA-01555: snapshot too old: rollback segment number with the name "" too small

  ORA-22924: snapshot too old

  I found these two articles in the KB:

  VMware KB: The vCloud Director Web UI reports the error: ORA-01555: snapshot too old: rollback number with n segment...

  VMware KB: Make sure that you have adequate undo tablespace before upgrading a vCloud Director Oracle database

  I added more space for the undo tablespace, new redologs, also change the setting of retention for all LOB in the vCloud regime without a different result.

  Anyone have any idea on this?

  Best regards

  I finally had an answer for the Oracle error.

  I did a full export of the vcloud database and detect an error in this table:

  ORA-31693: Table object "VCLOUD" data "" PROPERTY_MAP "impossible to load/unload and being ignored because of the error:

  ORA-02354: Error exporting/importing data

  ORA-01555: snapshot too old: rollback segment number with the name "" too small

  ORA-22924: snapshot too old

  This OPINION score details this condition:

  Export fails with ORA-2354 ORA ORA-1555-22924 errors and how to confirm the Corruption of the LOB Segment using the export utility? [833635.1 ID]

• Updated the operating system on the server for Windows 2012. Now I can not connect to vcenter.

  Updated the operating system on the server for Windows 2012. Now I can not connect to vcenter.

  What version of vCenter Server do you run? Only of vCenter Server 5.0 Update 2 is currently supported on Windows 2012.

  André

• Guests who will remain not connected to vCenter

  4.1.0 ESXi and vCenter 4.1.0

  We have four hosts in a cluster, two have no problem while the other two will remain not connected to vCenter.  I checked all that in the article 1003409 (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1003409) and found no problem.

  Four servers are IBM x 3690 X 5 and all are connected to the same four SAN LUNS, the only difference is that for problem servers management interfaces are on a different subnet, but the port UDP 902 is open between them and the vCenter server.  I can reconnect manually, but they will be disconnected again in a minute or two.

  Does anyone have ideas beyond what is in the article 1003409 that I can check?

  Thank you

  Darryl

  Make sure you have port 902 open TCP , as well as UDP.

  See this article: http://kb.vmware.com/selfservice/documentLinkInt.do?micrositeID=&popup=true&languageId=&externalID=1012382

  Regarding the 902 TCP port:

  vCenter Server system uses to send data to managed hosts. This port should not be blocked by the firewall between the server and the host or between hosts

  If the problem persists, I would try to remove the host to vCenter inventory, add new. Who's going to reinstall agents vCenter on the hosts.

  EDIT: This particular excerpt was taken from the entrance to vCenter 5.x, but the same is true for vCenter 4.x (it is high on the table). To be clear, you 902 TCP and UDP open both vcenter for hosts, host to vCenter and host to host.