From vcenter 6.0 4541947 vCenter Server 6.0 Update 2a

To vcenter 6.0 7037394 vCenter Server 6.0 Update 3c

uninstall.log

2017-02-18 02:23:30,903: CM search failed. ProductId=com.vmware.cis, TypeId=cs.identity

2017-02-18 02:23:30,903: Error connecting to CM: {

    "resolution": {

        "id": "install.default.failure.resolution", 

        "localized": "This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request.", 

        "translatable": "This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request."

    }, 

    "detail": [

        {

            "args": [

                "CM search failed. ProductId=com.vmware.cis, TypeId=cs.identity:503 Service Unavailable (Failed to connect to endpoint: [class Vmacore::Http::NamedPipeServiceSpec:00000000018056F0] _serverNamespace = / _isRedirect = false _pipeName =\\\\.\\pipe\\vmware-vpxd-webserver-pipe)"

            ], 

            "id": "install.ciscommon.internal.error", 

            "localized": "Encountered an internal error.\n\nCM search failed. ProductId=com.vmware.cis, TypeId=cs.identity:503 Service Unavailable (Failed to connect to endpoint: [class Vmacore::Http::NamedPipeServiceSpec:00000000018056F0] _serverNamespace = / _isRedirect = false _pipeName =\\\\.\\pipe\\vmware-vpxd-webserver-pipe)", 

            "translatable": "Encountered an internal error.\n\n%(0)s"

        }

    ], 

    "componentKey": null, 

    "problemId": null

}

2017-02-18 02:23:30,903: Failed to unregister node from CM. Error {

    "resolution": {

        "id": "install.default.failure.resolution", 

        "localized": "This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request.", 

        "translatable": "This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request."

    }, 

    "detail": [

        {

============================================================================================

soluser_firstboot.py_9276

2018-05-19T05:17:43.701Z   Invoked command: ['C:\\Program Files\\VMware\\vCenter Server\\vmafdd\\vecs-cli.exe', 'store', 'list']

2018-05-19T05:17:43.701Z   RC = 1021

Stdout = 

Stderr = vecs-cli failed. Error 1021: Cannot connect to vmafd service. 

2018-05-19T05:17:43.701Z   Error deleting solution user machine. Error {

    "resolution": null, 

    "detail": [

        {

            "args": [

                "Command: ['C:\\\\Program Files\\\\VMware\\\\vCenter Server\\\\vmafdd\\\\vecs-cli.exe', 'store', 'list']\nStderr: vecs-cli failed. Error 1021: Cannot connect to vmafd service. \r\n"

            ], 

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

            "localized": "An error occurred while invoking external command : 'Command: ['C:\\\\Program Files\\\\VMware\\\\vCenter Server\\\\vmafdd\\\\vecs-cli.exe', 'store', 'list']\nStderr: vecs-cli failed. Error 1021: Cannot connect to vmafd service. \r\n'", 

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

        }, 

        {

            "id": "install.ciscommon.vecs.list.stores", 

            "localized": "Error in generating list of VECS store instances.", 

            "translatable": "Error in generating list of VECS store instances."

        }

    ], 

    "componentKey": null, 

    "problemId": null

=============================================================================================    

vmafd-firstboot.py_9276_stderr.log

2018-05-19T05:18:31.873Z   WARNING Value for install-parameter vmdir.password is empty

2018-05-19T05:18:31.873Z   WARNING Value for install-parameter machine.cert.dir is empty

2018-05-19T05:18:31.873Z   WARNING Value for install-parameter upgrade.import.directory is empty

2018-05-19T05:18:31.873Z   WARNING Value for install-parameter upgrade.source.platform is empty

2018-05-19T05:18:31.873Z   WARNING Value for install-parameter upgrade.import.directory is empty

2018-05-19T05:18:31.873Z   WARNING Value for install-parameter vmdir.password is empty

2018-05-19T05:18:31.889Z   WARNING Value for install-parameter vmdir.password is empty

2018-05-19T05:18:31.889Z   Exception: Traceback (most recent call last):

  File "C:\Program Files\VMware\vCenter Server\firstboot\vmafd-firstboot.py", line 121, in main

    controller.uninstall()

  File "C:\Program Files\VMware\vCenter Server\firstboot\vmafd-firstboot.py", line 71, in uninstall

    service.uninstall()

  File "C:\Program Files\VMware\vCenter Server\firstboot\identityinstall\vmcaInstall.py", line 191, in uninstall

    self.utils.stop_service(self.__VMCA_SERVICE_NAME, self.__VMCA_COMPONENT_NAME)

  File "C:\Program Files\VMware\vCenter Server\firstboot\identityinstall\WindowsUtils.py", line 92, in stop_service

    raise ServiceStopException(serviceName)

ServiceStopException: {

    "resolution": null, 

    "detail": [

        {

            "args": [

                "VMWareCertificateService"

            ], 

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

            "localized": "An error occurred while stopping service 'VMWareCertificateService'", 

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

        }

    ], 

    "componentKey": null, 

    "problemId": null

}

vminst.log           

2018-05-18 23:17:31.236-06:00| vcsInstUtil-7037391| I: ParseStatusFile: STATUS: 87%: "Stopping VMware Single Sign-On User Creation..."

2018-05-18 23:17:31.236-06:00| vcsInstUtil-7037391| I: ParseStatusFile: Calling callback with 83 -> 87 "Stopping VMware Single Sign-On User Creation..."

2018-05-18 23:17:31.236-06:00| vcsInstUtil-7037391| I: Entering function: UpdatePkgMgrProgressFromStatusFile

2018-05-18 23:17:31.236-06:00| vcsInstUtil-7037391| I: ProcessMsiMsg: ACTIONDATA reporting "Stopping VMware Single Sign-On User Creation..."

2018-05-18 23:17:31.252-06:00| vcsInstUtil-7037391| I: Leaving function: UpdatePkgMgrProgressFromStatusFile

2018-05-18 23:17:31.252-06:00| vcsInstUtil-7037391| I: Leaving function: ParseStatusFile

2018-05-18 23:18:31.343-06:00| vcsInstUtil-7037391| I: Entering function: ParseStatusFile

2018-05-18 23:18:31.343-06:00| vcsInstUtil-7037391| I: ParseStatusFile: STATUS: 91%: "Stopping VMware Authentication Framework..."

2018-05-18 23:18:31.343-06:00| vcsInstUtil-7037391| I: ParseStatusFile: Calling callback with 87 -> 91 "Stopping VMware Authentication Framework..."

2018-05-18 23:18:31.343-06:00| vcsInstUtil-7037391| I: Entering function: UpdatePkgMgrProgressFromStatusFile

2018-05-18 23:18:31.343-06:00| vcsInstUtil-7037391| I: ProcessMsiMsg: ACTIONDATA reporting "Stopping VMware Authentication Framework..."

2018-05-18 23:18:31.359-06:00| vcsInstUtil-7037391| I: Leaving function: UpdatePkgMgrProgressFromStatusFile

2018-05-18 23:18:31.359-06:00| vcsInstUtil-7037391| I: Leaving function: ParseStatusFile

2018-05-18 23:18:31.998-06:00| vcsInstUtil-7037391| I: Entering function: ParseStatusFile

2018-05-18 23:18:32.014-06:00| vcsInstUtil-7037391| I: ParseStatusFile: curr error msg: "An error occurred while stopping service 'VMWareCertificateService'"

2018-05-18 23:18:32.014-06:00| vcsInstUtil-7037391| E: ParseStatusFile: Displaying error message for " ": "An error occurred while stopping service 'VMWareCertificateService'"

2018-05-18 23:18:49.408-06:00| vcsInstUtil-7037391| I: Entering function: ShowMessageQueue

2018-05-18 23:18:49.408-06:00| vcsInstUtil-7037391| I: Leaving function: ShowMessageQueue

2018-05-18 23:18:49.408-06:00| vcsInstUtil-7037391| I: Entering function: ShowMessageQueue

2018-05-18 23:18:49.408-06:00| vcsInstUtil-7037391| I: Leaving function: ShowMessageQueue

2018-05-18 23:18:49.408-06:00| vcsInstUtil-7037391| I: ParseStatusFile: got error or success

2018-05-18 23:18:49.423-06:00| vcsInstUtil-7037391| I: ParseStatusFile: keeping completed status file: C:\ProgramData\VMware\vCenterServer\logs\uninstall\fbInstall.json

2018-05-18 23:18:49.423-06:00| vcsInstUtil-7037391| I: Leaving function: ParseStatusFile

2018-05-18 23:18:49.423-06:00| vcsInstUtil-7037391| I: MonitorStatusFile: Parse callback gave final result: 0

2018-05-18 23:18:49.423-06:00| vcsInstUtil-7037391| I: MonitorStatusFile: called parse callback 10 times

2018-05-18 23:18:49.423-06:00| vcsInstUtil-7037391| I: MonitorStatusFile: Process still hasn't terminated, waiting

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| I: MonitorStatusFile: Wait on process has completed: 0

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| I: MonitorStatusFile: Process's job tree still hasn't terminated, waiting

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| I: MonitorStatusFile: Wait on process's job tree has completed: 0

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| I: Leaving function: MonitorStatusFile

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| E: LaunchProcAndMonitorStatus: Failure detected while monitoring status file

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| E: LaunchProcAndMonitorStatus: Job still alive, terminating

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| I: Leaving function: LaunchProcAndMonitorStatus

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| I: Leaving function: LaunchProcAndMonitorCommonStatusFile

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| E: RunFirstLastUpdateboot: Failed to run boot script: "C:\Windows\system32\cmd.exe /S /C ""C:\Program Files\VMware\vCenter Server\bin\run-uninstall-scripts.bat" --operation ROLLBACK""

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| I: Leaving function: VM_RunLastBoot

2018-05-18 23:42:03.520-06:00| vcsInstUtil-7037391| E: wWinMain: MSI result of install of "Z:\vCenter-Server\Packages\vcsservicemanager.msi" may have failed: 1603 (0x00000643)

2018-05-18 23:42:03.520-06:00| vcsInstUtil-7037391| E: LaunchPkgMgr: Operation on vcsservicemanager.msi appears to have failed: 1603 (0x00000643)

2018-05-18 23:42:03.520-06:00| vcsInstUtil-7037391| I: PitCA_MessageBox: Displaying message: "Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details."

2018-05-18 23:42:20.306-06:00| vcsInstUtil-7037391| I: LaunchPkgMgr: Telling child to revert transaction

2018-05-18 23:42:20.306-06:00| vcsInstUtil-7037391| I: InstallStatus_SetStage: install stage: install-packages / revert-transaction

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: EndTransaction: Chain transaction 1 rollback result 3010

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: wWinMain: We've been told our work is done, terminating

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: wWinMain: Releasing install mutex

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: Leaving function: wWinMain

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: LaunchPkgMgr: DLL got exe done: 3010

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: LaunchPkgMgr: disconnected pipe

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: LaunchPkgMgr: Starting services on update rollback.

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: Entering function: VM_StartVcsServices

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: PitCA_RefreshVMEnvironmentVars: Updating PATH environment variable.

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: PitCA_RefreshVMEnvironmentVars: Var: Path, Val: C:\Program Files (x86)\Java\jre7\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\MIT\Kerberos\bin;D:\Program Files\VMware\vCenter Server\openSSL;C:\Program Files\VMware\vCenter Server\openSSL

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: StartStopVCSServices: Running command '"C:\Windows\system32\cmd.exe" /S /C ""C:\Program Files\VMware\vCenter Server\bin\service-control.bat"" --start --all'...

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: StartStopVCSServices: Waiting for VC services to start...

2018-05-18 23:46:09.002-06:00| vcsInstUtil-7037391| E: StartStopVCSServices: Unable to start VC services

2018-05-18 23:46:09.002-06:00| vcsInstUtil-7037391| I: Leaving function: VM_StartVcsServices

2018-05-18 23:46:09.049-06:00| vcsInstUtil-7037391| E: LaunchPkgMgr: Overall operation has failed

Hello

I have vCenter 6.5 with six ESXI 6.5 Hosts

Two Hosts have 4 plus network adapters installed.

I run Windows 2012 R2 and Windows 2016 Cluster Servers using iSCSI from my NAS Device which has iSCSI support al working well

I am trying to set up MPIO on the Windows server I run SQL Cluster servers.

I installed the iSCSI Software Adapter on Both Host 1 and Host 3

On Host 1 and Host 3 I created two VMKernel's  VMkernal-iSCSI-1 and VMKernal-iSCSI-2  they both have one network adapter assigned.

After creating the VMkernels I went to the storage adapters hit the green + sign and added the two VMKernels.

Selected the target tab and entered the ip address on my NAS device

On the iSCSI Software Adapter I saw 24 Targets 0 Devices and 0 Paths

on the Network Port Binding tab the Path Status in NOT USED all others look good.

I tried to do a Dynamic Discovery on the ip address 10.x.x.x:3260 I saw nothing when I do a Static Discovery I see all my targets.

This is the same on both Host 1 and Host 2

Any ideas what I might be missing here?

Thank you,

Tom

Hi,

What I will gain if I used Content Library for my template insteadoff NFS  shared storage ?

Hi,

I recently updated my ESXi 6 and VCenter 6 Server environment to 6.5 This worked fine, with me upgrading VCenter Server and VCenter PSC in the right order.

Later, I patched my ESXi server to 6.5. Now, with all my VMs turned on, if I go to VCenter Server and then web client, I get the error page can't be displayed.

Everything in the network is working, DNS, no firewall rules blocking traffic, etc.

EDIT: Ok so the web client has come up but I get the error:

Could not connect to one or more vCenter Server systems:

Looking on vmware kb it states there may be a duplicate certificate but I cannot see how when the certificate configuration has not changed?

Any help much appreciated!

Thanks

Hello.

We have 2 vCenters with VUM.

vCenter 01 can dowload patches from internet, but vCenter 02 - not.

I want to export patches from vCenter 01 to shared repository and vCenter 02 point to it.

How can I do it ?

Hello,

Can I use the HA fonctionality of vCenter with 1 bay HPE MSA2050 SAS and 2 ESXi on HP DL360 attached on ?

Thanks for the help,

What the f@ck with vCenter Appliance?! Till the last 7 years every installation of vCenter Appliance is f@cking magic... What the problem with the heart of every modern IT infrastructure - virtualization and DNS? How did it happen that the most critical component of IT infrastructure(virtualization) so depends on DNS which may exist inside VMs.

Hi,

If I understood that right vCenter Converter Standalone is cloning the source VM  for instance VMs running on Xen server to the destination ESXI. In this case there will be a dublicate IP address if I powered on the destination VM on ESXI ? Do I need to powered off the source VM before power on the new VM on destination. If is that the solution there will be a down time between powering off the old vm and powering on the new VM?

Thanks

Hello world!

I am new in this forum and before to write my problem and start the post, I encountered many posts with similar problems. But no one exactly matches with my problem.

The problem that I have is when trying to do a full image backup from a VM in my vCSA, managed by VDP. vCSA = vCenter Server Appliance 6.5 and VDP = vSphere Data Protection 6.14.

In order to make a backup from a VM (for example, a Domain Controller with many disks with data), it takes a long time (normal, there is a lot of data) but backup speed is too slow (not greater than 100 Mbit/s). VDP, vCSA and FreeNAS (physical server with a NFS datastore) are using Gigabit interfaces to link between them. The Gigabit interfaces are tested and working OK. By the other hand, a restoration from a VM it takes a normal speed (about 500-600 Mbit/s).

Any idea what happens? Is there some any restriction in order to upload data from VDP to FreeNAS?

Thank you very much. Regards,

So my client has VCenter v5.0 and has 2 hosts running on this VCenter.  There is 1 VDR backup appliance running on 1 of the hosts and doing around 20 backups nightly combined for both hosts.  It appears there are some network dropouts from time to time from some of the vm's around the same time the backups are running. 

To lessen the load on the 1 VDR, I want to know if it's recommended or possible to have multiple VDRs on 1 VCenter e.g. 1 VDR appliance per host? If yes, is there a recommended procedure for cloning the current VDR and then reconfiguring it for the second host?

TiA

Good morning folks,

first of all please my apologies if this discussion does not belong here (perhaps in section vSAN), but I think that here (vCenter) would probably arrive to more people.

Let's start: I have a solution deployed like this:

- 1 vCSA managing a CLUSTER with 3 ESXi hosts (6.5 compilation 5705665). The storage is vSAN.

- This last weekend one of the VMs hosted in one esxi host got problems. Review the logs, the VM powered off automatically with error: Fatal error from VMware ESX: (vcpu-4) MXUserAllocSerialNumber: too many locks!.

- After, with vSphere HA, the VM automatically started in other esxi host, all OK.

From now, I migrated the VM to the first esxi host and works OK. Now, my question is try to solve the problem of "...too many locks".

I searched information about this error and I found several info from VMware, explaining the problem and explaining the solution (mainly I found KB 2149941). But I did not find when this error happened in a vSAN storage. As you can see in the permanent link from KB 2149941, it explains that it is necessary to modify the .vmx file from the VM. My question if I modify this file in the VM, for the solution explained, would it be propagate to the rest of configuration in vSAN for this VM?.

I make the question in other way: if I modify .vmx file in the main folder from this VM, the other folders that are synchronized with vSAN that stores this VM in the other esxi host, would the changes propagate and make effective? For this question, I found this two links:

KB 1714

KB 1026043

But it not says anithing if the storage is vSAN (assumes that you have a storage where VM is stored 1 time). First of making the changes recommended by these last KBs, I want confirm if anyone knows how to exactly modifiy the files without any affectation or problem in the future.

Apreciating your attention. Regards,

Hi all!

Recently in a VM I increased space in a disk for a VM. VM (a Windows Server) shows the unallocated space and I am able to use as a separate partition or having the posibility to merge the partition with the rest of the disk.

But now, I must return to the original space of disk in VM. Is there a way to return the original size? When I try from VM configuration it only permits to add more space, not delete.

I checked with VMware tools but it is not posible (I have already VMware tools installed but I have installed only Monitor Resources installed, not more components).

Any idea? One thig that I am wondering is to create another disk with the size that I need and then, copy the data from the older disk to the new and finally, delete the older disk by VM configuration and assign the drive letter from the older to the new disk in Disk Management from Windows.

Any help would be apreciated. Regards,

Hello,

Recently, one of my host lost access to 1 of the 10 datastores. That one datastore was accessible by other hosts in the cluster.

I am have been trying to figure out a way to fetch any "inaccessible" datastore from an ESXi host so that I can work on to fix it. Wish there was an alarm definition to get it for alert as well.

Any help on the same will be greatly appreciated!!

Thanks!!

Hi Gurus

I Have a vcenter 5.0 and I have created a VC6.5 , I would like to move all my VMs from the old VC to the new VC. I know there is the OVA option but if there is an easy way to connecting the two VC and then migrate/move the vms between them or something like that.

still learning vmware so any help would be cool.

Thanks a bunch

Dear all,

We are having an issue in configuring properly a vDS in vSphere / vCenter Server 6.5 with regards to network failover in case of network loss for the VM.

Our environment:

• Two ESXi 6.5 hosts and a shared NAS.
• Hosts configured in a cluster with HA enabled.
• There is a vDS that uses two physical NICs (uplinks), one from each of the hosts. Both physical NICs are connected to the same switch. Teaming is configured on this vDS and groupport.
• The VM is using this groupport.
• The VM has a static IPv4 address
• Management network, vMotion network etc. are using other vSwitch and NICs.

The HA feature works properly:

• If one host is lost, the VM restarts on the other host (and is fully reachable through the network);
• If network path to NAS is down on one host, the VM restarts on the other host (and is fully reachable through the network);
• If we manually vMotion the VM from one host to another host, same, it is all good.

What is not working is when the VM is running on one host, and we disconnect the network cable on that host for the particular NIC used in the vDS. What we expect is that the inbound/outbound network traffic will continue to flow transparently (flowing through the NIC of the other host which is part of the vDS). But here, when this happens, we cannot ping anymore the VM, and the VM cannot ping anymore the outside world.

Do you have any idea on how to fix this?

Is vDS the appropriate feature to handle this type of error (we assume that purpose of teaming on a vDS is to have traffic routed somehow from the other NICs still up in the vDS)?

Thank you very much.

Regards.

I updated 3 instance in my lab without issue, kudos to the install/upgrade team!

so long as the environement is healthy and configured correctly, the upgrade is painless...

Just be sure your environment is healthy and configured correctly and that you know all the passwords/ip's/ds's/esxi/fqdn/etc before starting the upgrade...  and BACKUP! BACKUP!! BACKUP!!!  you should always make a backup before you do any work!!! (or snapshot)

Hi!

Is there always a Cold Clone CD for convert physical machine to VM? Where can i download it? Found only Converter Standalone...

Thx

Tomber

Hi, I was having problems with mi linux machines, whenever I modifie some setting it lost the network connection, but then I realized that it happens in all my linux VM's including my vCenter, looking on the web i find that the VMWaretools should fix this issue, but I wonder if it's recommended to install VMWtools on Vcenter or not, any tip will be appreciated, thank you.

How do I change the built-in alerts so the subject line of the email it sends me isn't so long? I'd like to go from this:

[VMware vCenter - Alarm alarm.vsan.health.test.physicaldisks.physdiskcongestion] Virtual SAN Health Test 'Congestion' status changed from 'yellow' to 'red'

to this:

Virtual SAN Health Test 'Congestion' status changed from 'yellow' to 'red'

I'm running vmware-vdiskmanager -R against a VMDK file that produces "the virtual disk is invalid or needs to be repaired" errors in VCenter Converter.  vmware-vdiskmanager does NOT report anything; it just silently returns to the command prompt after a second or two and does not fix the problem.

vdisk-vdiskmanager -e reports: Disk chain is consistent.

Now what?  What to do when vmware-vdiskmanager -R does not fix the problem?