vCenter Server Converter NfcConnectionFault error

Similar Questions

• vCenter Server displays the error message: unable to connect to the host

  vCenter Server displays the error message: unable to connect to the host

  Symptoms

  • vCenter Server cannot connect to a host when you perform operations such as:

  •

  o Storage vMotion

  o cold migration

  o cloning a virtual machine

  o the model deployment

  • Newspapers vpxd that contains an entry similar to:

  [2009-06-04 19:27:16.326 error "App" 4444] [VpxdInvtHost] IP address change for 10.223.122.143 to 10.223.127.197 unhandled, verification of the SSL certificate is not enabled.

  • You see errors similar to:

  Unable to connect to the host o

  o [2009-06-04 19:27:09.952 'Libs' 3902384 WARNING] [NFC ERROR] NfcNewAuthdConnectionEx: unable to connect to peer (numRetries = 2). Error: Unable to connect to the host 10.223.122.143: connection timed out

  • vCenter Server shows the VMS as being disconnected then connected.

  Hello

  Resolution

  Cause

  This problem can occur if an ESX host's IP address is changed while being managed by vCenter Server.

  Check the cause

  To check the cause of the problem:

  1. Log in as root to the ESX host using a SSH client.
  1. In the file etc/opt/vmware/vpxa/vpxa.cfg, find the IP address of the host. The entry looks like:

     
     10.21.48.121
     

     Note: for more information about editing the files, see installation in VMware ESX configuration files (1017022).

  Troubleshooting

  If the IP address is incorrect, perform the following steps in order. If the operation does not resolve the problem, continue to the next step. Don't skip a step.

  1. Disconnect and then reconnect the host:
  1. Right click on the ESX host in vCenter Server and click Disconnect.
  1. Reconnect the ESX host in vCenter Server.
  1. Restart the VirtualCenter agent on the ESX host:
  1. Stop the service of vpxa with the command:

     # service vmware-vpxa stop

  1. Open the /etc/opt/vmware/vpxa/vpxa.cfg file in a text editor and correct the IP address of the ESX host.
  1. Start the service of vpxa with the command:

     # service vmware-vpxa start

     Note: for VMware ESXi, you may have to restart all the management agents. For more information, see restart the agents on an ESX or ESXi Server (1003490) management .

  1. Rebuild the VirtualCenter agent on the ESX host configuration file:

     Attention: this step removes all the Statistics counters historical host and the virtual machine. If VMware ESX host is running in virtual machines that starts in a permitted CVS environment, you maybe won't be able to add the host without stopping the virtual machines first.

  1. Right click on the ESX host in vCenter Server and click Disconnect.
  1. Remove the ESX host disconnected from vCenter Server.
  1. Backup the file vpxa.cfg with the command:

     # mv /etc/opt/vmware/vpxa/vpxa.cfg /etc/opt/vmware/vpxa/vpxa.oldcfg

  1. Add the ESX host disconnected to the server vCenter inventory.
  1. Run the following command to view the contents of /etc/opt/vmware/vpxa/vpxa.cfg and confirm that the host IP address is correct:

     # cat /etc/opt/vmware/vpxa/vpxa.cfg

• VMware vCenter Server 5.1 error 'com.vmware.sps.fault.QsConnectionException '.

  

  Hello

  The submitted error occurs very frequently, in fact after every minor changes or click in vCenter Server Console.

  We are client access VI locally on the server vCenter Server.

  It will be certainly great if someone can help me on this to resolve such errors.

  Thank you

  USP

  Thus, it seems that nobody don't have faced this error before, perhaps another bug, lets close this discussion so...

• vCenter Server 4.0 - Error 25003 & SQL 2005

  Hi all

  I try to install vCenter Server 4.0; Unfortunately, I won't have much luck.  I'll say this right at the front; I have never installed vCenter Server before or dirty with database.  I apologize in advance for any stupid errors.  The installer dies on me with this error:

  ""Error 25003.Setup failed to create the server vCenter. repository".

  Equipment: that I install vCenter Server 4.0:

  • Windows Server 2008 64 bit (computer is on a domain)

  Equipment database:

  • Running SQL Server 2005 on a Windows 2003 64-bit (computer is on a domain)

  How I created a SQL 2005 database.

  1. a law on databases and selected click 'New database'.

  How I created a Data Source Name (DSN)

  1. Has launched the 32-bit version of Data Source ODBC Administrator located in the: C:\WINDOWS\SysWOW64\odbcad32 (someone recommended ODBC running this way to fix 25003).

  2. SQL Server DSN must connect is a W2K 64 bit running SQL 2005.

  3. The default use "verify the authenticity of the ID connection via integrated Windows authentication.

  4. Connect to the new SQL server database.

  How do I install vCenter Server:

  1. Choose the option to use an existing supported database.

  2. Leaving the username and password fields empty database.

  3. By using a local administrator for the service account account.

  That people is what I did.  If you guys need more information, or have a few storms of brain on what I'm doing wrong please post.

  I think that this may be a good starting point.  If you have any other questions, after return

  http://www.VMware.com/PDF/vSphere4/R40/vsp_40_esx_vc_installation_guide.PDF

• 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]

• VMWare v6.0 to 6U1 or 6U2 Upgrade - external PSC - 1603 errors in vCenter Server

  Hi all

  I was wondering if someone met the upgrade a version 6.0 VMWare install to U1 or U2 upgrade and received a 1603 error.

  The installation runs correctly on the external PSC, but when running against the vCenter Server fails and has a 1603 error and did a restore.

  The VCSServiceManager component installation failed with error code "1603". Check the logs for more details

  I tried all the other threads suggesting to have .net installed 3.5, the ipv4 stack and database permissions but are all there.

  Any help would be greatly appreciated.

  For those who have encountered this problem in the future, was the way I solved this:

  Question has been connected to the VMWare SysLog Collector Service. There is a problem with the new syslogcollection MSI being able to upgrade, uninstall or reinstall on the legacy.

  Best way to solve this problem is to remove the reference to the old service of library of Windows Setup syslog collector. The way I did it was to use the Windows Installer CleanUp legacy.

  Post this, remove installation held as scheduled and transmitted "installation VCSServiceManager.

  If you come across this issue - you can test it by trying to run the msi syslogcollector contained in the directory of files binary vCenter.

• vCenter Server Appliance error 6.0 #1009 after update

  Hi guys.

  A few days ago I updated my client vCenter Server device of vpx of b. 6.0 to 6.0 update works fine, but when I log in web client, I have error #1009.

  

  Journal

  

  I tried all the work arrounds:

  Stop the web client, clear the cache of serenity, start the web client and nothing.

  I disabled the Update Manager and web client and Site Recovery Manager plugins works very well. Then I reload Update Manager and Site Recovery Manager and fails again.

  Update Manager to update to the latest version and fails again.

  Any tips? Help? Wishes?

  I just opened a SR with Vmware, but I don't always have a solution or something. I want to wait for a solution before the restoration, but I can't live without feature Site Recovery Manager.

  Thank you

  Kerchief!

  VMware support solved this situation.

  My browser has settings to Spanish. So, I changed to English languaje of firefox, and the Vmware web client works very well!

  Greetings Vmware support.

• We get an error when I try to collect data from vCenter Server. But the Collection of Cluster works!

  Hello

  I m getting a strange errormessage when he tries to load my vCenter Server inventory.

  I have configured my vCenter Server as the endpoint server and I was able to load the Clusters. When I klick collection of data in a Cluster (Cluster of EQL 1) I can load all the data and the State is 'successful', but when I try to load the inventory FRO the vCenter Server (to get the models) im getting this error message:

  The treatment [inventory], error details error: illegal managed object reference type, folder.

  The same schows Agent logs:

  [26.08.2014 16:48:16] [Info]: start: treatment Workitem ID [2e38598e-4385-4b2d-bc88-fd2b773d1f98] [inventory]

  [26.08.2014 16:48:16] [Debug]: [[inventory]] [inventory] VirtualMachine.Admin.Hostname = vCenter

  [26.08.2014 16:48:16] [Debug]: [[inventory]] VirtualMachine.Admin.ParentIdentity = [inventory]

  [26.08.2014 16:48:16] [Debug]: [[inventory]] [inventory] VirtualMachine.ManagementEndpoint.Name = vCenter

  [26.08.2014 16:48:16] [Debug]: [[inventory]] VirtualMachine.ManagementEndpoint.Identity = [inventory]

  [26.08.2014 16:48:16] [Debug]: [[inventory]] [inventory] VirtualMachine.ManagementEndpoint.Endpoint0 = vCenter

  [26.08.2014 16:48:16] [Debug]: [[inventory]] [inventory] VirtualMachine.Admin.Name = inventory

  [26.08.2014 16:48:16] [Error]: <? XML version = "1.0" encoding = "utf-16"? >

  < Boolean > false < / Boolean >

  Error parsing [inventory], details of the error:

  System.ArgumentException: Illegal managed object reference type, folder.

  at DynamicOps.Vrm.Agent.vSphere.VSphereGetHostsRequest.ExecuteImpl)

  at DynamicOps.Vrm.Agent.vSphere.VSphereHypervisorServiceProvider.GetHosts (ManagementEndpoint managementEndpoint)

  to DynamicOps.Vrm.Agent.Collector'3.get_Hosts)

  to DynamicOps.Vrm.Agent.Collector'3.CollectManagementEndpoints)

  to DynamicOps.Vrm.Agent.CollectInventory'3.Collect)

  to DynamicOps.Vrm.Agent.BaseHypervisorAgent'3.EnumerateHypervisorResources (collector collector 3, WorkItem workItem, PropertyBagHelper propertyBagHelper)

  to DynamicOps.Vrm.Agent.BaseHypervisorAgent'3.ProcessWorkitem (WorkItem workItem, task of the chain, PropertyBagHelper propertyBag)

  to DynamicOps.Vrm.Agent.vSphere.VSphereAgentService.ProcessWorkitem (WorkItem workItem, task of the chain, PropertyBagHelper propertyBag)

  to DynamicOps.Vrm.Agent.BaseAgent.ProcessWorkitem (WorkItem workItem)

  I hope that someone had an idea, im out of ideas.

  THX Steven

  There is no data for the endpoint collection... And I'm not entirely sure of how you added the vCenter object it... y at - it a calculation object named "vCenter? To answer your specific questions about the models, however, they must be stored on a cluster that is part of the tissue group for data collection to pick them up... They are not considered as a global entity (as a resource calculation). Add models to one of the clusters and then to collect data on it, and you should be fine.

• vCenter install error: Error 25003 Setup cannot create vCenter Server repository

  Hello

  I build vCenter server install 5.5.0U1C with the two server model where the instance a host DB and others welcome rest the vCenter Binaries.Below is the error that I got when running vCenter

  I ran the query

  SELECT CASE WHEN 'A' = 'a' THEN 'NOT CASE SENSITIVE' ELSE 'CASE SENSITIVE' END

  
  

  I got back as "NOT case sensitive.

  
  

  But if I'm correct error it says precisely because of the failure as "the database is installed using insensitive case" that proves this query.

  
  

  I fell the Mode Case Insensitive mode case-sensitive mode by changing the ranking "SQL_Latin1_General_CP1_CS_AS'.

  
  

  I have this time received the error

  
  

  

  
  

  I have no idea which has now gone wrong make install failed.

  
  

  BTW, the version of the Client on the remote DB server and application server are the same and I use MS SQL 2012 SP1 with windows 2008 R2 SP1 on windows OS both side.

  
  

  Please help me find the solution, I have really now clueless with the cause of it.

  
  

  
  

  Thanks in advance

  
  

  BR,

  
  

  MG
  

  Nevermind, I got this problem fixed by the server being destruction and reconstruction new virtual machine and install this on it.

• VSphere Web client and client heavy cannot connect to Vcenter server 5.5, web client fails with 2032 error before the connection, then the work after one minutes ferw.

  Hi all

  I really need help here.  I have a new installation of Esxi5.5 and installed the server vcenter build 5.5.0.5201 device 1476389.

  I have host files properly configured for DNS and Server 2008 R2 running that I use to connect with the client or web client heavy.

  Initially, I get an error with the web client to connect, he began to paint Vmware and when it comes to 'r' in the name it fails with #2032, so I can no longer

  access the page at all, he says: connection refused for the page. If I wait a while I can connect again.

  heavy client vSphere fails at this time as well.  However, I cannot communicate directly with Vsphere client to server esxi host and it works all the time.

  There seems to be a problem with the device of vcenter server because the thick client fails, and does not open a backup program using vcenter server

  inventory when this happened.

  Please help, it drives me crazy...

  Dan

  Hello

  Since I found the solution to the problem of connecting to the device of vcenter.  It is a conflict of IP address on the network.  There was a machine with the same IP address virtuall

  as the vcenter server.  This caused intermittent problems etc.. Why web client would still work if I have the vmware client open I do not know

  so thank you for your help.

  Dan

• Errors in the charge installing vcenter Server 5.5 with respect to the SQL database

  I do a new install of vCenter Server 5.5 on a new Windows 2008 R2 server. The database for this facility is pointing at a 32-bit Windows 2003 SP2 server. I installed SQL Native Client 10.0 on server vCenter Server 64-bit, and then I could make my DSN ODBC 64-bit connection. The vCenter Server install could very well recognize it, but after the installation got going he wrong on the database with the following error:

  Error 25003.Setup cannot create vCenter Server repository. The main reasons for this failure are:

  -The database is installed using insensitive case.

  -The database is remote and the client database version does not match the database version. If this problem continues to persist, see KB 1003960 for further assistance.

  Well, I know that the version of the client and the version of database do not match. SQL native client on the sql server is 9.00.5000.00 and the version on the server vCenter Server is 10.50.1600.1.

  I know that this version of vCenter is compatible with an installation of 32-bit sql server 2005 on a 32-bit server, 2003.

  I am not familiar too if they want upgrade me sql native client on the sql server, but is not compatible with the version of sql server on this server and there are several database for other applications on this server, so I don't want to jump into something like that.

  Any help would be greatly appreciated.

  Thank you.

  I install the native client SQL 2005 and give a shot.

• Error adding Vcenter server to view administrator

  I'm making a Point of Concept with Horizon see 5.5.

  I can not add a server vcenter for the Manger of the view. I get an "error record vCenter entered.

  If I look in the log file I have this

  2013-10 - 15 T 05: 42:55.736 - 07:00 ERROR (0814-0 D 38) < TP-Processor2 > [Connection4] connection to the server vCenter Server https://SRV-vCenter.clasd.net:443 / sdk failed.

  I'm completely lost on what to do.

  I have solved my problem. I put the username as domain\username. Once I put it as username@domain everything worked.

• VCenter Server 5.1 SSL certificate update - error

  Hi all

  We set up a new Windows 2008 R2 server as a vCenter Server 5.1

  Now, I try to install the new certificates for all parts of vCenter (server, inventory, web client service,...) with the Windows certification authority.

  I'm stuck at the update server certificate SSL vCenter with the 'Certificate SSL Automation Tool'.

  This is part 5. in this guide (5. the cmd screen shot):

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 2041600 #updatestepsplanner

  All credentials are correct, but I still get the same error (vc-update - ssl.log):

  [26.04.2013 - 10:42:54, 99]: copy the new certificates and keys 'C:\ProgramData\VMware\VMware VirtualCenter\SSL. '... »
  [26.04.2013 - 10:42:55: 00]: creating the PKCS certificate file...
  Could not reload vCenter SSL certificates
  [26.04.2013 - 10:42:56: 22]: ""cannot reload the server vCenter SSL certificates. " The certificate could not be unique. » »
  [26.04.2013 - 10:42:56, 24]: new certificates and keys deleting...
  [26.04.2013 - 10:42:56: 25]: restoration of the certificates and the original keys...
  1 Datei () kopiert.
  1 Datei () kopiert.
  1 Datei () kopiert.
  [26.04.2013 - 10:42:56: 25]: attempt to restore...
  Could not reload vCenter SSL certificates
  [26.04.2013 - 10:42:57, 08]: ""cannot reload the server vCenter SSL certificates. " The certificate could not be unique. » »
  [26.04.2013 - 10:42:57: 10]: new certificates and keys deleting...
  [26.04.2013 - 10:42:57: 10]: restoration of the certificates and the original keys...
  1 Datei () kopiert.
  1 Datei () kopiert.
  1 Datei () kopiert.
  [10: 42:57, 13 - 26.04.2013]: failure of the update of the certificate of vCenter.
  
  
  So I tried the manual way, as it is mentioned in this guide:
  http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 2035005

  I'm stuck here too, get a 'result of Method Invocation: vpx.fault.SecurityConfigFault ' after ""Invoke method ': "

  1. Go to https://localhost/mob/?moid=vpxd-securitymanager & vmodl = 1 on the server vCenter Server and load the certificates for the configuration using the managed object browser.
  2. Click continue if you are prompted with a warning on this certificate.
  3. Enter a vCenter Server administrator user name and password when prompted.
  4. Click reloadSslCertificate.
  5. Click the calling method. If successful, the window displays this message: result of Invocation of method: Sub.

  
  

  I tried to fix this, but there is not really a solution for this:

  http://communities.VMware.com/thread/429035

  so, I need help with this question

  SOLVED!

  Steps to follow:

  1. stop the vCenter service

  2. search for your ID in LS_ServiceID.prop in the folder C:\ProgramData\VMware\VMware VirtualCenter

  3. copy this ID (e.g. {C4672589-9258-42B1-90E2-1EF268BBD402}: 5 )

  4. change your vpxd.cfg in the same folder and replace

  vCenterService

  with

  your ID

  5. start vCenter Service

  Then, the SSL automation tool works!

  You need to undo changes.

• Weird error with vCenter Server 5.1 plugin

  Hello

  I installed orchestrator device 5.1 with vCenter plugin. Everything is green and seems well configured.

  I am able to connect with the vCenter client and access all workflows of my!

  But when I access parts of plugin and wants to explore the vCenter Server, orchestrator returns me this error:

  [16:29:50.477 2013-04-15] [E] the authorization to perform this operation was denied. : System.View/Folder - group-d1(IP vCenter)

  I don't understand why. The user that I configured in the configuration of the plugin vCenter is an administrator and has all privileges...

  You have an idea?

  Thanks for your help.

  Concerning

  Hello!

  Are you sure the user that you have configured to connect to vCenter has the appropriate permissions to this level?

  Even for an administrator at the level of the root in vCenter you can remove/override the lower-level permissions.

  Using SSO?

  And: What authentication policy for the vCenter Plugin have you configured?

  With a ' user' logs also the user connect to vSphere WebClient / vCO must have the appropriate permissions.

  You can try to reconfigure the vCO to use a "shared session", then for all operations of the user you set up (hopefully with administrative permissions in vCenter) is used for all operations.

  See you soon,.

  Joerg

• Try to use the converter to push a VMX and VMDK existing in the environment file. Have you tried the Converter 4.3 and 5.0, continues to crash or delay. A 5.1 with ESXI 5.1 vCenter server hosts going conversion.

  Try to use the converter to push a VMX and VMDK existing in the environment file. Have you tried the Converter 4.3 and 5.0, continues to crash or delay. A 5.1 with ESXI 5.1 vCenter server hosts going conversion.

  Take a look at this article. You can try Converter standalone 5.0.1 or 5.1 beta.

  http://KB.VMware.com/kb/2033315