Hi...

You folks are my last hope before I reach for the almight cigarette, a bottle of rum and a loaded revolver!!!

Here's the situation, one of my techies added a user to the VSphere / Vcenter server.  Unfortunately now when I try and delete said user, I keep getting from the vSphere client:

Call "AuthorizationManager.RemoveEntityPermission" for object "AuthorizationManager" on vCenter Server "VSPHERE.prodnet.local" failed.

I have tried this with many different accounts hoping I could get around it and have come up flat.  Adding insult to injury I have tried to use the PowerShell command but find that more painful than my first divorce!

Again, the user is at the top level of the vCenter server and deleting this account hasn't worked for me thus far...

PLEASE HELP...  The pistol is provoking me!!!

I've got a VM, and the vendor is suggesting it's running at 2.xGHZ vs the 3.x GHZ recommended..

How do I properly determine the speed at which the CPU is running at?

I know the "Consumed" value fluctuates wildly..

Thanks ,

Rich

Hi all,

We have a test vCenter server 6.5 appliance with a lot of custom alarms definitions. Is there a way to reset all those alarms to their default values? I found the following article but it doesn't apply to vSphere 6.0 and above:

     VMware Knowledge Base

I tested it but my vCenter was then unable to start anymore with an error message in vpxd.log:

     [Originator@6876 sub=alarmMo opID=CreatePredefinedAlarms-bc5816b] Upgrade from pre VC5.0 version not supported in VC 6X

Is there any solution?

Many thanks for your help! :-)

Franck

  I recently removed a physical host from a vCenter Server virtual appliance and am not able to add it back to vCenter Server because I get an error about the datastore already existing.  I am running a simple vCenter Server environment with two physical hosts and shared storage.  I have only been administering vCenter for a few months, so I am relatively new to the technology and processes.  I have searched the Internet for a few days now, but have not found any documentation of anyone experiencing the same problem as I (which I find odd considering how simple my configuration and problem), so I wanted to get some help from the VMware community.

  I got an error message one day that vCenter Server couldn't connect to one of the two hosts so I removed the host (instead of disconnecting and connecting as I should have done).  Now I am not able to connect the host to vCenter server because the shared storage datastore conflicts with the same datastore used by the existing host in vCenter Server.  The error message I get is ""Datastore 'datastore_name' conflicts with an existing datastore in the datacenter that has the same URL (ds:///vmfs/volumes/UUID/), but is backed by different physical storage."  I try to unmount the datastore from the host, but get the following error message: "The resource 'Datastore Name: datastore_name VMFS uuid: UUID' is in use."  The error stack says, "Call "HostStorageSystem.UnmountVmfsVolume" for object "storageSystem" on ESXi "IP address" failed.  Cannot unmount volume 'Datastore Name: datastore_name VMFS uuid: 'UUID' because file system is busy. Correct the problem and retry the operation."  I have tried removing all virtual machines from inventory, putting the hosts in maintenance mode, rebooting the physical hosts, but none of my troubleshooting is helping.

  I am not sure what steps to take to get this datastore unassociated with the host so that I can add it back into vCenter Server.  Any help you can provide me is appreciated.

Hi all,

I am using four ESX 4.1u1 hosts + vCenter & VUM (Advanced Plus vSphere edition, virtual Win2008 R2 64bit machine) with Oracle database (on a separate physical server). I would like to install MS SQL on the same virtual server where vCenter and VUM are running, but I have a few questions:

1. Is it wise to migrate to MS SQL and to have it installed on the same server as vCenter and VUM ? If so, SQL 2008 or SQL 2008 R2 - which is better for VMWare ?

2. From compatibility matrices I think vCenter 4.1u1 supports the newest SQL (MS SQL 2008 R2 64bit) in both Standard and Enterprise editions, so it seems to me that standard edition is sufficient. In the case of VUM, there is nothing about editions. Is Standard edition OK ?

3. Is it possible to migrate the existing database (both vCenter and VUM tables reside in the same Oracle database instance) to MS SQL without loss of data ? Do I need some extra paid tools for this or is it somehow possible from the vCenter itself ?

Thank you in advance for any comments and opinions.

I was wondering if it's possible to Storage vMotion the vCenter 6.0 Appliance?

Basically, we need to move it to a new cluster. So, I've put the datastore from the new cluster in the old cluster. I would like to 1) Storage vMotion it to that datastore and 2) vMotion it (now that it's on a datastore both clusters can see) to the new cluster.

Just wondering if this is possible or should I look at alternate methods?

Load on vCenter is generally around 40% CPU, 45% Memory Consumed. It is about 300GB in size. External PSC that will also be moving with it.

Thank you!

VCSA with Embedded PSC v6.7 (Build 9451876)

VMCA configured as Subordinate CA to a Windows 2012 R2 Enterprise Root CA. (SHA256 Hash / 2048 bit Key)

VMCA replaces the SSL certificate on a ESXi v6.5 (Build 5969303) host and the 'certification path' is complete. All works as expected, no browser errors.

VMCA replaces the SSL certificate on a ESXi v6.7 (Build 8169922) host and the 'certification path' is incomplete. Still get the standard browser errors. The root CA and VMCA certificates are NOT in the path, only the ESXi host certificate!

ESXi v6.5 Host - Complete Certification Path.
A dump of the SSL connection using the TestSSLServer utility (GitHub - pornin/TestSSLServer ) shown below.   Connection: mc-esxi-v-204.momusconsulting.com:443 SNI: mc-esxi-v-204.momusconsulting.com   TLSv1.0:      server selection: uses client preferences      3-- (key:  RSA) RSA_WITH_AES_128_CBC_SHA      3-- (key: RSA)  RSA_WITH_AES_256_CBC_SHA      3f- (key: RSA) ECDHE_RSA_WITH_AES_128_CBC_SHA      3f- (key: RSA) ECDHE_RSA_WITH_AES_256_CBC_SHA   TLSv1.1: idem   TLSv1.2:      server selection: enforce server preferences      3f- (key: RSA) ECDHE_RSA_WITH_AES_256_GCM_SHA384      3f- (key: RSA) ECDHE_RSA_WITH_AES_128_GCM_SHA256      3-- (key: RSA)  RSA_WITH_AES_256_GCM_SHA384      3-- (key: RSA)  RSA_WITH_AES_128_GCM_SHA256      3f- (key: RSA) ECDHE_RSA_WITH_AES_256_CBC_SHA384      3f- (key: RSA) ECDHE_RSA_WITH_AES_256_CBC_SHA      3f- (key: RSA) ECDHE_RSA_WITH_AES_128_CBC_SHA256      3f- (key: RSA) ECDHE_RSA_WITH_AES_128_CBC_SHA      3-- (key: RSA)  RSA_WITH_AES_256_CBC_SHA256      3-- (key: RSA)  RSA_WITH_AES_256_CBC_SHA      3-- (key: RSA)  RSA_WITH_AES_128_CBC_SHA256      3-- (key: RSA)  RSA_WITH_AES_128_CBC_SHA ========================================= +++++ SSLv3/TLS: 1 certificate chain(s) +++ chain: length=3 names match:        yes includes root:      yes signature hash(es): SHA-256 + certificate order: 0 thumprint:  A18830247B90395EE003D706CE3AEB3CDA96BC6D serial:     E032A1675443F48D subject: EMAILADDRESS=admin@momusconsulting.com,CN=mc-esxi-v-204.momusconsulting.com,OU=Momus Labs,O=Momus Consulting,L=Basingstoke,ST=Basingstoke,C=GB issuer:     CN=VMCA-mc-vcsa-v-204,OU=Momus Labs,O=Momus Consulting,L=Basingstoke,ST=Hampshire,C=GB valid from: 2018-10-06 14:22:12 UTC valid to:   2020-10-05 12:06:47 UTC key type:   RSA key size:   2048 sign hash:  SHA-256 server names:    mc-esxi-v-204.momusconsulting.com + certificate order: 1 thumprint:  6313EF9061D1ED748298F0DB7D693F6CC2099046 serial:     5D0000000BA3C47E6295F579B400000000000B subject:    CN=VMCA-mc-vcsa-v-204,OU=Momus Labs,O=Momus Consulting,L=Basingstoke,ST=Hampshire,C=GB issuer:     CN=Momus Root CA on mc-addc-v-101,DC=momusconsulting,DC=com valid from: 2018-10-06 12:06:47 UTC valid to:   2020-10-05 12:06:47 UTC key type:   RSA key size:   2048 sign hash:  SHA-256 + certificate order: 2 thumprint:  A3BD98D6B6C712A510E11669A84D0571C2D2F0F1 serial:     65F1DEEF09DD1A9A436075662D731F0F subject:    CN=Momus Root CA on mc-addc-v-101,DC=momusconsulting,DC=com issuer:     CN=Momus Root CA on mc-addc-v-101,DC=momusconsulting,DC=com valid from: 2018-10-05 15:11:29 UTC valid to:   2028-10-05 15:21:28 UTC key type:   RSA key size:   2048 sign hash:  SHA-256 (self-issued) ========================================= Server compression support: no Server sends a random system time. Secure renegotiation support: yes Encrypt-then-MAC support (RFC 7366): no SSLv2 ClientHello format (for SSLv3+): yes Minimum EC size (no extension):   256 Minimum EC size (with extension): 256 ECDH parameter reuse:  no Supported curves (size and name) ('*' = selected by server):   * 256 secp256r1 (P-256) =========================================   WARN[CS006]: Server supports cipher suites with no forward secrecy.

ESXi v6.7 Host - Incomplete Certification Path.
Again, a dump of the SSL connection is shown below.   Connection: mc-esxi-v-205.momusconsulting.com:443 SNI: mc-esxi-v-205.momusconsulting.com   TLSv1.2:      server selection: enforce server preferences      3f- (key: RSA) ECDHE_RSA_WITH_AES_256_GCM_SHA384      3f- (key: RSA) ECDHE_RSA_WITH_AES_128_GCM_SHA256      3-- (key: RSA)  RSA_WITH_AES_256_GCM_SHA384      3-- (key: RSA)  RSA_WITH_AES_128_GCM_SHA256      3f- (key: RSA) ECDHE_RSA_WITH_AES_256_CBC_SHA384      3f- (key: RSA) ECDHE_RSA_WITH_AES_256_CBC_SHA      3f- (key: RSA) ECDHE_RSA_WITH_AES_128_CBC_SHA256      3f- (key: RSA)  ECDHE_RSA_WITH_AES_128_CBC_SHA      3-- (key: RSA)  RSA_WITH_AES_256_CBC_SHA256      3-- (key: RSA)  RSA_WITH_AES_256_CBC_SHA      3-- (key: RSA)  RSA_WITH_AES_128_CBC_SHA256      3-- (key: RSA)  RSA_WITH_AES_128_CBC_SHA ========================================= +++++ SSLv3/TLS: 1 certificate chain(s) +++ chain: length=1 names match:        yes includes root:      no signature hash(es): SHA-256 + certificate order: 0 thumprint:  9CB7BEC3BD58491A36069B182093F22BE9813042 serial:     FD682ECC9662D00C subject: EMAILADDRESS=admin@momusconsulting.com,CN=mc-esxi-v-205.momusconsulting.com,OU=Momus Labs,O=Momus Consulting,L=Basingstoke,ST=Basingstoke,C=GB issuer:     CN=VMCA-mc-vcsa-v-204,OU=Momus Labs,O=Momus Consulting,L=Basingstoke,ST=Hampshire,C=GB valid from: 2018-10-06 14:44:04 UTC valid to:   2020-10-05 12:06:47 UTC key type:   RSA key size:   2048 sign hash:  SHA-256 server names:    mc-esxi-v-205.momusconsulting.com ========================================= Server compression support: no Server sends a random system time. Secure renegotiation support: yes Encrypt-then-MAC support (RFC 7366): no SSLv2 ClientHello format (for SSLv3+): yes Minimum EC size (no extension):   256 Minimum EC size (with extension): 256 ECDH parameter reuse:  no Supported curves (size and name) ('*' = selected by server):   * 256 secp256r1 (P-256) =========================================   WARN[CS006]: Server supports cipher suites with no forward secrecy.

Any ideas?

Thanks

M

How to get an alarm when SIOC triggered?

I have run into a strange issue which occurs following the enablement of two PSC 6.5 nodes in an HA configuration as part of a rolling upgrade from 5.5.

The first PSC node in a new site was migrated from an original Window vCenter 5.5 SSO to PSC 6.5, and subsequently a second new node was joined to the first site in order for replication to be established. I'm using a Citrix NetScaler to load balance the configuration and I noticed at some point after the successful HA repointing was done that I am unable to access the https://hosso01.sbcpureconsult.internal/psc URL. The second node, https://hosso2.sbcpureconsult.internal/psc works correctly and redirects to the load balanced address psc-ha-vip.sbcpureconsult.internal for authentication before displaying the PSC client UI. Irrespective of whichever node is selected I am able to log in to vCenter, then choose Administration, System Configuration, select a node then Manage, Settings or CA without receiving any errors.

If I deliberately drop the first node out of the load balancing config on the NetScaler I don't have any issues when accessing the /psc URL by either host name or load balancer name, but if I try to connect to the first node by its own DNS name or IP I get an HTTP 400 error and the following entry in:

/storage/log/vmware/psc-client/psc-client.log

[2018-10-08 12:05:20.347] [ERROR] tomcat-http--3 com.vmware.vsphere.client.security.websso.MetadataGeneratorImpl - Error when creating idp metadata.

java.lang.RuntimeException: java.io.IOException: HTTPS hostname wrong:  should be <psc-ha-vip.sbcpureconsult.internal>

It appears that the HTTP 400 error is because the psc-client Tomcat application doesn't start up correctly on the first node anymore, along with an error in..

/storage/log/vmware/rhttpproxy/rhttpproxy.log

2018-10-08T13:27:10.691Z warning rhttpproxy[7FEA4B941700] [Originator@6876 sub=Default] SSL Handshake failed for stream <SSL(<io_obj p:0x00007fea2c098010, h:27, <TCP '192.168.0.117:443'>, <TCP '192.168.0.121:26417'>>)>: N7Vmacore3Ssl12SSLExceptionE(SSL Exception: error:140000DB:SSL routines:SSL routines:short read)

I've repeated the same steps in my lab environment that I experienced in the customer site and can confirm the same behaviour. Let me explain however that all other vCenter functionality is correct and this issue only affects the /psc URL.

Could this be deemed 'correct' behaviour? If I choose https://psc-ha-vip.sbcpureconsult.internal/psc (which is the load balancer address) I am initially only able to connect if the second node is online and happens to be selected.

I am happy to provide detailed steps of the upgrade process, but in the first case I would like to confirm that it should be possible to access the /psc URL on each node deliberately?

I know the version is very old, and that's exactly the problem. Before upgrading, I need to back up all the data. The problem is that I'm unable to connect an external usb drive to the virtual machines.

This is what I have on the host itself (jmicron is the name of the hdd adapter/rack that I've connected to the server on the usb port):

lsusb

Bus 01 Device 16: ID 152d:9561 JMicron Technology Corp. / JMicron USA Technology Corp.

Bus 01 Device 03: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub

Bus 01 Device 01: ID 0000:0000

Bus 08 Device 01: ID 0000:0000

Bus 07 Device 01: ID 0000:0000

Bus 06 Device 01: ID 0000:0000

Bus 05 Device 01: ID 0000:0000

Bus 04 Device 01: ID 0000:0000

Bus 03 Device 01: ID 0000:0000

Bus 02 Device 01: ID 0000:0000

In the screenshot you can see the available devices that I have which I can configure for passthrough (accessed through Configuration - Advanced Settings - Configure passthrough).

I've no idea to associate what I'm seeing here in "lsusb" and what the vmware client shows me.

Any help is much appreciated.

This is a new VCSA 6.5 adn the domain is almost new.

When trying to add the VCSA to Active Directory it is reporting:

Idm client exception: Error trying to join AD, error code [41887], user [administrator@domain], domain [domain.com], orgUnit [Computers]

Have not found a message that will help me with this error.

Tried to do it from the cli using SSH but it failed also.

Replacing external PSC 6.5 U1 with Microsoft CA certs - they comprise of an Intermediate and Root CA.

All goes well until the very last stage where Services can't start successfully.

Console error will say:

Status : 85% Completed [starting services...]

Error while starting services, please see log for more details

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

Error while replacing Machine SSL Cert, please see /var/log/vmware/vmcad/certificate-manager.log for more information.

Performing rollback of Machine SSL Cert...

Checking the certificate-manager.log, I find that there are services that fail to start due to a timeout:

2017-10-05T05:33:28.195Z INFO certificate-manager Running command :- service-control --start  --all

2017-10-05T05:33:28.196Z INFO certificate-manager please see service-control.log for service status

Service-control failed. Error Failed to start vmon services.vmon-cli RC=1, stderr=Failed to start sca, cm, vapi-endpoint services. Error: Operation timed out

2017-10-05T05:41:26.324Z ERROR certificate-manager None

2017-10-05T05:41:26.325Z ERROR certificate-manager Error while starting services, please see log for more details

2017-10-05T05:41:26.325Z ERROR certificate-manager Error while replacing Machine SSL Cert, please see /var/log/vmware/vmcad/certificate-manager.log for more information.

2017-10-05T05:41:26.325Z ERROR certificate-manager {

    "resolution": null,

    "detail": [

        {

            "args": [

                "None"

            ],

            "id": "install.ciscommon.command.errinvoke",

            "localized": "An error occurred while invoking external command : 'None'",

            "translatable": "An error occurred while invoking external command : '%(0)s'"

        },

        "Error while starting services, please see log for more details"

    ],

    "componentKey": null,

    "problemId": null

}

2017-10-05T05:41:26.326Z INFO certificate-manager Performing rollback of Machine SSL Cert...

There was a KB with something similar but this isn't an error while publishing cert using dir-cli.

Anyone seen this before?

After migrating from Windows 5.5 vCenter to VCSA 6.5 Update1 (intermediate step to 6.7) everything was working well. After the migration the vcenter machine cert was soon to be expired so I replaced it, though I did notice https://vc.domain.com:7444 was still using the old cert. I didn't worry about this as the old cert was not expired. A month or so passes by with vcenter being very stable. Completed host upgrades to 6.5U1 using VUM over the weekend - In the mean time the cert bound to 7444 expired, which caused problems with the Migration wizard to 6.7. Also, VUM service had stopped and wouldn't start (perhaps it was ok until I rebooted the VCSA and now VUM wont start)

With the help of VMWare support we fixed this by replacing the cert in the STS_INTERNAL_SSL_CERT. This fixed the expired cert for 7444 but did not help with the VUM issues. I'm pretty well stuck, I am just waiting on VMWare support to help. In the mean time I thought I'd post here in case someone could possible help.

Regards

I get the following errors in the SSH session when executing service-control --start vmware-updatemgr:

Error executing start on service updatemgr. Details {

    "resolution": null,

    "detail": [

        {

            "args": [

                "updatemgr"

            ],

            "id": "install.ciscommon.service.failstart",

            "localized": "An error occurred while starting service 'updatemgr'",

            "translatable": "An error occurred while starting service '%(0)s'"

        }

    ],

    "componentKey": null,

    "problemId": null

}

Service-control failed. Error {

    "resolution": null,

    "detail": [

        {

            "args": [

                "updatemgr"

            ],

            "id": "install.ciscommon.service.failstart",

            "localized": "An error occurred while starting service 'updatemgr'",

            "translatable": "An error occurred while starting service '%(0)s'"

        }

    ],

    "componentKey": null,

    "problemId": null

}

tail -f updatemgr-utility.log give this:

[2018-10-10 23:29:10,255 INFO] Install Key store for Jetty

[2018-10-10 23:29:11,579 INFO] Keystore installed successfully.

[2018-10-10 23:29:11,953 INFO] Updating VUM extension with VC

[2018-10-10 23:29:12,236 INFO] Updating CM service info

[2018-10-10 23:29:12,402 ERROR] CM ReRegisterService failure. Exception is (cis.cm.fault.ComponentManagerFault) {

   dynamicType = <unset>,

   dynamicProperty = (vmodl.DynamicProperty) [],

   msg = '',

   faultCause = <unset>,

   faultMessage = (vmodl.LocalizableMessage) [],

   errorCode = 0,

   errorMessage = 'UNKNOWN'

}

[2018-10-10 23:29:12,402 ERROR] Unable to update CM service info

Tail on cm.log give me this while starting service:

2018-10-10T23:24:35.847Z [pool-2-thread-1 [] WARN  com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore (f15657f3-ac72-40f0-8c90-3e948201000c)] Call to lookup service failed; uri:https://VCENTER.DoMain.int/lookupservice/sdk [(vmodl.fault.InvalidArgument) {

   faultCause = null,

   faultMessage = null,

   invalidProperty = Invalid certificate

}]

2018-10-10T23:24:35.847Z [pool-2-thread-1 [] ERROR com.vmware.cis.services.cm.service.ServiceManagerImplTemplate (f15657f3-ac72-40f0-8c90-3e948201000c)] reRegisterService v1: Failed to re-register c39131ca-cda5-446d-a6ac-44b51348c107 (vpxd-extension-a6f84462-5ea2-11e6-ada6-0050569777b5@vsphere.local, com.vmware.vcIntegrity/vcIntegrity 6.5.0)

com.vmware.vim.binding.vmodl.fault.InvalidArgument: null

        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_141]

        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[?:1.8.0_141]

        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_141]

        at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1.8.0_141]

        at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_141]

        at com.vmware.vim.vmomi.core.types.impl.ComplexTypeImpl.newInstance(ComplexTypeImpl.java:174) ~[vlsi-core.jar:?]

        at com.vmware.vim.vmomi.core.types.impl.DefaultDataObjectFactory.newDataObject(DefaultDataObjectFactory.java:25) ~[vlsi-core.jar:?]

        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.ComplexStackContext.<init>(ComplexStackContext.java:30) ~[vlsi-core.jar:?]

        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.parse(UnmarshallerImpl.java:150) ~[vlsi-core.jar:?]

        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.unmarshall(UnmarshallerImpl.java:101) ~[vlsi-core.jar:?]

        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:88) ~[vlsi-core.jar:?]

        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:83) ~[vlsi-core.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.SoapFaultStackContext.setValue(SoapFaultStackContext.java:40) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.processNextElement(ResponseUnmarshaller.java:127) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.unmarshal(ResponseUnmarshaller.java:70) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.unmarshalResponse(ResponseImpl.java:274) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setResponse(ResponseImpl.java:230) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.parseResponse(HttpExchangeBase.java:150) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:48) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:226) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:110) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:613) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:594) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:345) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:305) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:179) ~[vlsi-client.jar:?]

        at com.sun.proxy.$Proxy101.set(Unknown Source) ~[?:?]

        at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore$LsVmomiWrapper$3.execute(LsVmomiSiteStore.java:229) ~[service-cm.jar:?]

        at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore$LsVmomiWrapper$3.execute(LsVmomiSiteStore.java:226) ~[service-cm.jar:?]

        at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore$LsVmomiWrapper.callLs(LsVmomiSiteStore.java:302) ~[service-cm.jar:?]

        at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore$LsVmomiWrapper.set(LsVmomiSiteStore.java:224) ~[service-cm.jar:?]

        at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore.updateService(LsVmomiSiteStore.java:622) ~[service-cm.jar:?]

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_141]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_141]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_141]

        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_141]

        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at com.vmware.cis.services.common.perfmon.PerfmonInterceptor.invoke(PerfmonInterceptor.java:31) ~[service-common.jar:?]

        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at com.sun.proxy.$Proxy67.updateService(Unknown Source) ~[?:?]

        at com.vmware.cis.services.cm.service.ServiceManagerImplTemplate.reRegisterService(ServiceManagerImplTemplate.java:306) [service-cm.jar:?]

        at com.vmware.cis.services.cm.service.ServiceManagerImpl.reRegisterService(ServiceManagerImpl.java:291) [service-cm.jar:?]

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_141]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_141]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_141]

        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_141]

        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at com.vmware.cis.services.common.perfmon.PerfmonInterceptor.invoke(PerfmonInterceptor.java:31) [service-common.jar:?]

        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at com.sun.proxy.$Proxy68.reRegisterService(Unknown Source) [?:?]

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_141]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_141]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_141]

        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_141]

        at com.vmware.vim.vmomi.server.impl.InvocationTask.run(InvocationTask.java:65) [vlsi-server.jar:?]

        at com.vmware.vim.vmomi.server.common.impl.RunnableWrapper$1.run(RunnableWrapper.java:47) [vlsi-server.jar:?]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_141]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_141]

        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_141]

tcpdump on lo gives:

Request

POST /lookupservice/sdk HTTP/1.1

Content-Type: text/xml; charset=utf-8

SOAPAction: urn:lookup/2.0

Content-Length: 21474

Host: https://VCENTER.DoMain.int/lookupservice/sdk

Connection: Keep-Alive

User-Agent: VMware vim-java 1.0

Cookie: vmware_soap_session=a7600162-79b1-4797-9e7f-4b885dde550b

Accept-Encoding: gzip,deflate

X-Forwarded-For: 127.0.0.1

X-Forwarded-Proto: https

....CERT HASH in XML stream.........

Request

HTTP/1.1 500

Set-Cookie: vmware_soap_session=a7600162-79b1-4797-9e7f-4b885dde550b; HttpOnly

Content-Type: text/xml;charset=utf-8

Content-Length: 558

Date: Wed, 10 Oct 2018 01:45:27 GMT

Connection: close

<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soapenv:Fault><faultcode>ServerFaultCode</faultcode><faultstring/><detail><RuntimeFaultFault xsi:type="InvalidArgument" xmlns="urn:lookup"><invalidProperty>Invalid certificate</invalidProperty></RuntimeFaultFault></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>

Hi,

After a crash of an ESX, the vcenter won't restart.

It's look a problem with authentification with SSO.

I try to follow this KB: VMware Knowledge Base

but whith the command : repoint.cmd configure-vc --lookup-server https://ssso121e.xxxx.xxx:7444/sso-adminserver/sdk --user "admin@System-Domain" --password "...xx...x" --openssl-path "C:\Program Files\VMware\Infrastructure\Inventory Service\bin/"

Do you have an idea?

Thanks,

Let's use this thread to upload screenshots for vSphere Client (HTML5) related discussions.

Anyone seen this error when trying to edit a VM?  Happens whether we add a disk, disconnect a NIC.   6.7 Vcenter with 6.0 hosts..

Hi,

I tried install VMware Client Integration Plugin 6.0 for deploy new vCenter Server VA and I received this error:

There is a problem with this Windows Installer package.

A program run as part of the setup did finish as expected.

Contact your support personnel or package vendor.

On the background is a window with status:

Installing certificates and starting services...

In folder %TEMP% is log file vmmsi.log_<date_time>_Failed.log

Key data:

14:24:29:296]: Executing op: ActionStart(Name=CsdServiceInstall,Description=Installing certificates and starting service...,)

Action 14:24:29: CsdServiceInstall. Installing certificates and starting service...

MSI (s) (60:34) [14:24:29:306]: Executing op: CustomActionSchedule(Action=CsdServiceInstall,ActionType=3090,Source=C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\vmware-csd.exe,Target=--install,)

CustomAction CsdServiceInstall returned actual error code 3 (note this may not be 100% accurate if translation happened inside sandbox)

MSI (s) (60:34) [14:24:29:936]: Note: 1: 1722 2: CsdServiceInstall 3: C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\vmware-csd.exe 4: --install

MSI (s) (60:34) [14:24:29:936]: Note: 1: 2205 2:  3: Error

MSI (s) (60:34) [14:24:29:936]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1722

Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action CsdServiceInstall, location: C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\vmware-csd.exe, command: --install

MSI (s) (60:34) [14:24:32:005]: Note: 1: 2205 2:  3: Error

MSI (s) (60:34) [14:24:32:005]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709

MSI (s) (60:34) [14:24:32:005]: Product: VMware Client Integration Plug-in 6.0.0 -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action CsdServiceInstall, location: C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\vmware-csd.exe, command: --install

Unfortunately I couldn't find out the reason of error from this log.

After my extremely long researching I find out

that subprocess vmware-csd (creating keys and certificetes) logs into the folder C:\ProgramData\VMware\CIP\csd\logs

Example of the log file (csd_000x.log) in troublefree installation:

[2015-03-16 16:30:39] [INFO] Certificate registered!!!

[2015-03-16 16:30:39] [INFO] Changes to the hosts file were successful.

[2015-03-16 16:30:39] [INFO] Changes to the hosts file were successful.

[2015-03-16 16:30:39] [INFO] Successful install of CSD protocol handler.

In my case log file ended:

[2015-03-16 16:30:39] [INFO] Certificate registered!!!

There were missing records about some modification of file hosts.

Reason:

Installer will fail, if the file hosts.bak exists there before running installation of VMware Client Integration Plugin 6.0 !

Solution:

Rename or delete file hosts.bak in folder C:\Windows\System32\drivers\etc\

Good Luck.

P.S.

Deacivate any antivirus before starting the installation of VMware Client Integration Plugin 6.0

I think the subject says it all.

For the first time ever, that I can recall, vCenter had an update release that has a unique API version ... 6.7.1.

Over all the updates of 5.1 to 6.5 ... doing an update 1/2/3 didn't change the API version from 6.5.1 to 6.5.2.  And I've been using VMware since vCenter 2.5 ... so this is pretty new to me.

I guess I'm just curious to know why this was done?

Attempting to enable FT on a VM on an NFS mount. All the vm files are on NFS, and thick provisioned Eager.  Getting error

There are fault tolerance compatibility issues, which might prevent you from turning on fault tolerance on the selected virtual. Invalid Virtual Machine Configuration

The same VM with all files on Vsan works fine.

Unfortunately no real other errors to look to.

Hosts and vcenter is 6.5u2 with latest patches

VM is only 4 vcpu

Hi Folks,

I will appreciate your help.

I Could not download vCenter Server from Downloads as Nothing is being shown under Downloads for my Account.

Please Assist.

Many Thanks.