V5 vSphere Client VI - connectivity to vCenter Server via the non-ideal DNS configuration

Similar Questions

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

• Windows 7 64 bit Pro connects to SQL Server on the Windows Server 2008 R2 Standard domain

  I put upgraded to Windows 7 Professional computers to Windows XP Professional, but I have a problem with getting one of software programs management of stock that allows us to connect to our SQL Server 2008 R2 Standard Windows on new Windows 7 computers.

  Our computers are connected to a domain, and therefore SQL Server. Computers Windows XP allows each user to standard domain to connect and to connect to SQL Server via the stock management software.

  But on the standard domain of Windows 7 Pro computer users unable to connect to SQL Server, but administrator accounts of area on the same Windows 7 Pro computers can connect to SQL Server through the inventory control program.

  I have set up the alias of the server, the server name and port number via the SQL Server Client Network utility ( cliconfg.exe ) so I know this isn't the problem because it works when I'm logged on as a domain administrator.

  There seems to be something to do with permissions of user domain and Windows 7 Pro. There seems to be a change from Windows XP Pro to Windows 7 Pro that does not allow standard domain users to connect to a SQL Server. But I can't find anything about and cannot practice how to solve this problem, except to make all users, domain administrators that is obviously not a good thing to do. So basically I think I need to create a group policy that allows users to connect to SQL Server, but I have no experience in doing this and don't know where to start.

  Thank you for all that you guys help and I hope someone can give me the solution to this problem.

  This issue is beyond the scope of this site and must be placed on Technet or MSDN

  http://social.technet.Microsoft.com/forums/en-us/home

  http://social.msdn.Microsoft.com/forums/en-us/home

• 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

• 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

• Connecting to vCenter Server 4.1 - new installation

  VMware ESXi 4.1.0 build-348481

  VMware vSphere Web Access Version 4.1.0 Build 426686

  VMware vCenter Server Version 4.1.0 Build 491557

  VMware vSphere Client Version 4.1.0 Build 491557

  I used vSphere Client to access a single ESXi host for some time.  No problem with the single host management.

  It is my first installation of vCenter Server (on Windows Server 2008 R2 Standard 7601 Service Pack 1).

  As Microsoft IIS Web server was already running on this host, I used alternative ports for tomcat services:

  80 > 8080

  443 > 446

  Web Services-> 8081

  When I connect to localhost:446, I can open a vSphere Web Access session and see the following:

  

  How to contact the ESXi host and view its inventory this server?

  Then I tried using vSphere Client to administer the server vCenter Server, but cannot connect.  The error is:

  "A communication error has occurred when sending data to the server. (The underlying connection was closed: an unexpected error occurred on a send.) »

  It doesn't matter if I run the Client vSphere on the same host as the center of vSphere, or a remote host.

  I tried to use the IP addresses and host names.  No difference.

  I have disabled the firewall on the host vSphere Center.  No difference.

  Both host ESXi and vCenter Server have valid license keys.

  What should I do to get vSphere Client to connect to the server from vSphere?

  Hello

  I change ports instead IIS as vCenter server, but if you use port 446 you specify port (446) thatcustom in vSphere client as well. In the field of connection for the vSphere client

  How to contact the ESXi host and view its inventory this server?

  After establishing the connection with vCenter server, you must create the object data center and add your ESXi autonomous server to vCenter server. After you will see ESXi inventory in vCenter server

  See you soon
  Artur
  

  Please, do not forget the points of call of the "useful" or "correct" answers

• Maximum number of connections to vCenter Server

  I wonder what experience people is on the threshold for the maximum number of client connections simultaneous vSphere that can connect to a server vCenter Server to access computers virtual virtual guests, using VMware vSphere client without causing performance problems or the server crash.  The simultaneous client connections vSphere how your environments have been able to support?  Of course, there are many variables that are forward-looking statements outlining exact impossible, but illustrative, that's what I'm looking for.  In this case vCenter Server has 8 GB of RAM and 1 GB/s Ethernet.

  Thank you

  Hello

  For vSphere 4.0, the number of concurrent connections to VC is 20 and for vSphere 4.1 is 100.

  Reference:

  http://www.VMware.com/files/PDF/Techpaper/vsp_41_perf_VC_Best_Practices.PDF

  Page 7

  Please consider awarding points.

• 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

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

• No VRM server registered with vCenter Server for the site 'Live '.

  I have SRM 6.1 and vSphere replication 6.1 installed on both sites.

  The ECP is connected to the vCenter server.

  I get this error message: failed to create the protection group. No VRM server registered with vCenter Server for the site 'Live '.

  Screenshot attached, no one knows what is happening here?

  

  However, there was a mismatch in the meantime server on all except VRA in the remote site, it is now resolved and the issue disappeared.

  Strange, how the error related to the site online, however.

  Thank you for pointing me in the right direction.

• possible to install the client tools OBIEE and OBIEE server in the same machine

  Hello
  
  possible to install the client tools OBIEE and OBIEE server in the same machine.
  
  Ex:
  
  Last week I've updated Patch BP1 in my local system, in the process, we got the update also oracle Client tool
  
  But in my Administration tool in the built-in tool automatically updated, we need to install the client tool in my system?
  
  My doubt:
  Please check this screenshot
  http://ScrnSht.com/sskbjb
  Please help me,
  
  Thank you

  You should not install client tools because they will be automatically installed w install the server. The 11g installation guide says "do not install client tools on the same computers that host your server instances Oracle Business Intelligence, client tools are already installed on these computers (as part of the installation of Oracle Business Intelligence)."

  so useful, mark it as good or useful.

• deploy a virtual machine for the model stored in EXSI server via the command line

  Hello

  Is it possible to deploy a vm from a template stored in exsi server via the command line?

  The structure is shown in the attached picture. I want to deploy the model under "Templates" folder to a virtual machine "VM" sub-folder by command line of any machine.

  

  Hello

  PowerCLI can help you achieve this goal. Using PowerCLI, you can deploy remote host model.

  Here is an example for the same.

  http://www.harryjohn.org/deploy-multiple-VMs-from-template/

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

• VSphere Client multiple connections to a single server vCenter Server?

  I have a vCenter Server that manages a few hosts. I know it's a bad habit to manage guests individually using vSphere Client, but I was wondering if I can have multiple connections to the same server vCenter Server vSphere client using the same Windows credentials?

  It seems counterproductive to only allow a connection to the server vCenter Server...

  Yes - by default, a connection up to 25 to vCenter

• Cannot connect directly to Esx via the vSphere Client.

  Hello

  I can not connect directly to ESX through the le VSphere client. I have the following message:

  "Can not connect to "xxx"vSphere Client. Un unknown connection error has occurred. (

  The customer not able to send a complete application on the server. (Underlying connection was closed. An unexpected error has occurred when sending.)). »

  
  

  Le ESX reply to ping et name resolution are correct. They are seen by the vCenter and sshh connection to ESX is possible.

  
  

  Version: Esxi, 5.5.0, 1892794

  VSphere Client 5.5.0, 1880841 on Windows XP SP3
  

  
  

  Thank you for your help

  Have a look here: vSphere Client 5.5 and WindowsXP/Windows2003 & #8211; Unknown connection error & laquo; Mike Landry & #8230;