Hello,

I tried to install vCenter, but I got an error and logs are:

https://paste.ubuntu.com/p/NhNnWGQTqF/

https://paste.ubuntu.com/p/g4ktRrDHR2/

https://paste.ubuntu.com/p/5hFSHBG8Bm/

How can I solve it?

Thank you.

Hello, trying to take a simple vCenter backup to an HTTP location via the HFS tool but it's giving me the error below. Port 80 on the ESXi firewall is checked and the vCenter has no firewall. Anyone else run into this?

ESXi host firewall that vCenter is on is accepting 80 and 443.

I get a different error based on whether or not I use the root / or the folder path. The folder has everyone full control and the ficticious user account and permissions are set to root/password from HFS.

1. ERROR: Error at process ComponentScriptsBackup; rc:55.

2. ERROR: BackupManager encountered an exception: Hit exception inside process ComponentScriptsBackup

[MainProcess:PID-9280] ERROR: stderr:Failed to dispatch component rbd backup

1. curl: (55) Send failure: Broken pipe

2. curl: (52) Empty reply from server.

ERROR: BackupManager encountered an exception: Failed to send data to the destination server. Please check network connectivity/space available/permissions on the server. For details please check the log file: /var/log/vmware/applmgmt/backup.log.

1. ERROR: BackupManager encountered an exception: Hit exception inside process ComponentScriptsBackup

2. ERROR: BackupManager encountered an exception: Failed to receive data/response from the remote server

Good morning.

I have recently installed a brand new vcenter appliance version 6.7U3b

Then i have replaced the default vcma certificate and solutions certificates with my microsoft ca signed certificates .

Everything works as expected and i can connect to my vcma from my browser as a secure connection.

But when i connect my esxi hosts to this vcma they receive a certificate which belongs to vmvare and when i directly connect to them i received from the browser

the warning that i am connecting to an untrusted site, even when i update and refresh  the certificates from the web client and html5 client.

Is this the right behaviour ? should i take care of replacing by hand every certificate installed in the esxi hosts or is there something i am missing

in the configuration of the vcma ?

Thankyou in advance

Kind regards

Andrea

We have a midsize VMware Vsphere Infrastructure with one vCenter, several clusters with 4 to 6 hosts in two datacenters. Summarizing all togehter not real big environment. In the last week we have decided to migrate our Windows vCenter 6.0 U3 with external windows PSC  to a VCSA 6.7 topology. The first step with migrating the PSC was working allright and we were really happy. In the following we tried to migrate the Windows vCenter VM to the VCSA, but we were struggling with the problem that we could only use x-Large deployment with the GUI installer. Unfortunately we didn´t have enough physical ressources to go on with that sizing and actually it is to big for our environment.

We were searching the internet and google about the issue. We found some articles that we have to do some cleaning with the databases and the inventory, but nothing helped. Then we hav a look about at an article that we should use the cli-based installer with vcsa deploy and use a "prepared migration" template to migrate the vCenter. We did a lot of work about customizing the vCSA Migration template and did a lot of prechecks. All of the prechecks failed with nearly the same error: the "hostname" Value is missing in the "vc_win" variable.

We have checked the file several times, and it seems to work until it reaches the last part were the values for "vc_win" is placed. It looks like it can´t read anymore what is written in there afterwards.

We were using the following template:

...

{

    "__version": "2.13.0",

    "__comments": "Sample template to migrate a Windows installation of vCenter Server 6.0 with an external Platform Services Controller to a vCenter Server Appliance 6.7 with an external Platform Services Controller on a vCenter Server instance.",

    "new_vcsa": {

        "vc": {

            "__comments": [

                "'datacenter' must end with a datacenter name, and only with a datacenter name. ",

                "'target' must end with an ESXi hostname, a cluster name, or a resource pool name. ",

                "The item 'Resources' must precede the resource pool name. ",

                "All names are case-sensitive. ",

                "For details and examples, refer to template help, i.e. vcsa-deploy {install|upgrade|migrate} --template-help"

            ],

            "hostname": "<FQDN or IP address of the vCenter Server instance>",

            "username": "<The user name of a user with administrative privileges or the Single Sign-On administrator on vCenter.>",

            "password": "<The password of a user with administrative privileges or the Single Sign-On administrator on vCenter. If left blank, or omitted, you will be prompted to enter it at the command console during template verification.>",

            "deployment_network": "VM Network",

            "datacenter": [

                "Folder 1 (parent of Folder 2)",

                "Folder 2 (parent of Your Datacenter)",

                "Your Datacenter"

            ],

            "datastore": "<A specific datastore accessible to the ESXi host or DRS cluster in the 'target' path.>",

            "target": [

                "Folder A (parent of Folder B)",

                "Folder B (parent of Your ESXi Host, or Cluster)",

                "Your ESXi Host, or Cluster"

            ]

        },

        "appliance": {

            "__comments": [

                "You must provide the 'deployment_option' key with a value, which will affect the VCSA's configuration parameters, such as the VCSA's number of vCPUs, the memory size, the storage size, and the maximum numbers of ESXi hosts and VMs which can be managed. For a list of acceptable values, run the supported deployment sizes help, i.e. vcsa-deploy --supported-deployment-sizes"

            ],

            "thin_disk_mode": true,

            "deployment_option": "management-small",

            "name": "vCenter-Server-Appliance"

        },

        "os": {

            "password": "<Appliance root password; refer to --template-help for password policy. If left blank, or omitted, you will be prompted to enter it at the command console during template verification.>",

            "ssh_enable": false

        },

        "temporary_network": {

            "ip_family": "<ipv4 or ipv6>",

            "mode": "static",

            "ip": "<Static IP address. Remove this if using dhcp.>",

            "dns_servers": [

                "<DNS Server IP Address. Remove this if using dhcp.>"

            ],

            "prefix": "<Network prefix length. Use only when the mode is 'static'. Remove if the mode is 'dhcp'. This is the number of bits set in the subnet mask; for instance, if the subnet mask is 255.255.255.0, there are 24 bits in the binary version of the subnet mask, so the prefix length is 24. If used, the values must be in the inclusive range of 0 to 32 for IPv4 and 0 to 128 for IPv6.>",

            "gateway": "<Gateway IP address. Remove this if using dhcp.>"

        },

        "user_options": {

            "vcdb_migrateSet": "<Set the data migration option. Available options are 'core', 'all', 'core_events_tasks', 'transfer_events_tasks_after_upgrade', and  'transfer_stats_events_tasks_after_upgrade'. Note that the last two options, 'transfer_events_tasks_after_upgrade', and 'transfer_stats_events_tasks_after_upgrade', are available only if the database for the source VCSA (the VCSA to be upgraded) is external.>"

        }

    },

    "source_vc": {

        "description": {

            "__comments": [

                "This section describes the source Windows vCenter that you want to migrate.",

                "For vCenter running on a virtual machine, you can automate the installation and launching of",

                "the Migration Assistant by including the 'run_migration_assistant' section.",

                "For vCenter running on a physical machine, or if you are running Migration Assistant manually",

                "on the Windows vCenter, copy and paste the thumbprint value from the Migration Assistant",

                "console output on the source vCenter to the 'migration_ssl_thumbprint' key in the 'vc_win'",

                "section, and remove the 'run_migration_assistant' section. You can read more about",

                "'migration_ssl_thumbprint' in template help, i.e. vcsa-deploy migrate --template-help"

            ]

        },

        "vc_win": {

            "hostname": "<FQDN or IP address of the source vCenter Server instance>",

            "username": "administrator@<SSO domain name>",

            "password": "<vCenter Single Sign-On administrator password. If left blank, or omitted, you will be prompted to enter it at the command console during template verification.>",

            "active_directory_domain": "<The name of the Active Directory domain to which the source Windows installation is joined. Remove this if your Windows is not in a domain.>",

            "active_directory_username": "<Administrator user name of the Active Directory domain to which the source Windows installation is joined. Remove this if your Windows is not in a domain.>",

            "active_directory_password": "<Administrator password of the Active Directory domain to which the source Windows installation is joined. Remove this if your Windows is not in a domain. If left blank, or omitted, you will be prompted to enter it at the command console during template verification.>"

        },

        "run_migration_assistant": {

            "__comments": [

                "Remove this section and provide the value for 'migration_ssl_thumbprint'",

                "in the 'vc_win' section if the Windows vCenter/PSC is running on a physical machine, or if you want to run Migration Assistant manually. Read more about the other 'run_migraton_assistant' template keys, or about 'migration_ssl_thumbprint' in template help, i.e. vcsa-deploy migrate --template-help"

            ],

            "esxi_hostname": "<FQDN or IP address of ESXi on which source vCenter Server Appliance resides.>",

            "esxi_username": "<Username of a user with administrative privileges on the ESXi host.>",

            "esxi_password": "<The password of the ESXi host user. If left blank, or omitted, you will be prompted to enter it at the command console during template verification.>",

            "esxi_port": "<The port number of the ESXi host. The default value is 443.>",

            "os_username": "<Administrator username for the source Windows operating system, e.g. 'administrator@example.com' or 'DOMAIN_NAME\\Administrator'>",

            "os_password": "<Administrator user password for the source Windows operating system. If left blank, or omitted, you will be prompted to enter it at the command console during template verification.>",

            "migration_port": "<Migration Assistant port number. The default value is 9123, e.g. \"migration_port\": 9123>",

            "sa_password": "<vCenter Server service account user password. This option is only required if the vCenter Server service is running under a non LocalSystem account. If left blank, or omitted, you will be prompted to enter it at the command console during template verification.>"

        }

    }

}

....

As you can see the last section is vc_win. As deployment option we have been using "management-medium" and "management-small", but we always get the same error.

Did anyone of the community get the same errors then we have. How can we achieve a migration in reasonable sizing?

Hello All,

We experienced an interesting anomaly today where all users/admins lost their vCenter access. We currently have 4 ESXi servers (HP DL 380's) and HP MSA storage device rack mounted in our server room with UPS support. We believe we may have experienced a power spike due to a storm that rolled through.

The oddity here is that all the Roles/Permissions that I manually created and assigned to vCenter, Datacenter, Cluster, Datastore and Distributed Switch Port groups all got deleted.

This is definitely not a good thing! Any idea as to why this may have happened? The only thing I can identify by looking through the logs is that the 4 ESXi hosts started experincing sync errors around the time the storm rolled through, though we were already out of the office on a Friday and did not encounter the issue until this Monday morning. I was able to login with the administrator@vsphere.local account but then became unresponsive and I had to reboot all 4 servers.

Any thoughts? Solutions to prevent this in the future?..........our racks are also grounded.

when adding one of the hosts to vcenter

A general system error occurred: Unable to get signed certificate forhost name '192.168.0.88' ip '192.168.0.88': Error: Operation failed with error = ERROR_NOT_ENOUGH_MEMORY (8) (8)

what should I do?

Hello All,

Thank you for taking the time to read this.  I've been tasked with making my first nested lab.  Currently the root vcenter is 6.5 with std switches.

I've been asked to and created 2 nested ESXi hosts and created a 2nd non-nested vcenter with embeded  PSC, a vum and db servers to add the hosts

into.

The company does not want to use a DVSwitch only Std.   I have created the nested hosts with no problem and assigned them to vlan 4095.   With this

dns resolves and I can ping vcenters, gateway, etc with no problems.

When I attempt to connect the nested hosts to this newly created vCenter, I am not able to.  Both the nested ESXi hosts and the new vCenter are on the

same Datastore.

I'm scratching my heading trying to get this to work as I'm pretty sure it will not work without a dvs...

Will this configuration work with nested hosts and non nested vcenter, vum and db?

Any assistance and feedback is very much appreciated. 

Thanks in advance!

Hi,

I can't Open virtual Machine folder from <vCenter-Address>/Folder  url. actually it returns 500 error. My vCenter appliance version is 6.7 with build number 15129973.

Based on screenshot that I attached, I can just forward to this step, thus when I open VM folder, faced with 500 Error.

Note: It's worked on vCenter 6.5 and we can see all contents in virtual machine's folder such as *.nvram , *.vmdk , *.vmx and etc.

Also you can see error log as below:

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2020-01-13T13:11:19.811+03:30 info vpxd[04730] [Originator@6876 sub=HTTP server /folder req=00007f29304b6520 user="username"] Got HTTP GET request for /folder/VM?dcPath=Cloud01&dsName=STOR01

2020-01-13T13:11:19.811+03:30 info vpxd[06403] [Originator@6876 sub=vpxLro opID=req=00007f29304b6520-72] [VpxLRO] -- BEGIN lro-3515974 -- SearchIndex -- vim.SearchIndex.findByInventoryPath -- 52cfad26-7ad3-4e5b-2043-1624611f432f(52710809-3213-0d6c-0b4c-972d37b06d37)

2020-01-13T13:11:19.811+03:30 info vpxd[06403] [Originator@6876 sub=vpxLro opID=req=00007f29304b6520-72] [VpxLRO] -- FINISH lro-3515974

2020-01-13T13:11:19.814+03:30 info vpxd[05837] [Originator@6876 sub=vpxLro opID=req=00007f29304b6520-78] [VpxLRO] -- BEGIN lro-3515977 -- ServiceInstance -- vim.ServiceInstance.retrieveContent -- 52cfad26-7ad3-4e5b-2043-1624611f432f(52710809-3213-0d6c-0b4c-972d37b06d37)

2020-01-13T13:11:19.814+03:30 info vpxd[05837] [Originator@6876 sub=vpxLro opID=req=00007f29304b6520-78] [VpxLRO] -- FINISH lro-3515977

2020-01-13T13:11:19.814+03:30 info vpxd[04769] [Originator@6876 sub=vpxLro opID=req=00007f29304b6520-10] [VpxLRO] -- BEGIN session[52cfad26-7ad3-4e5b-2043-1624611f432f]521e6dcc-4dc6-303e-a3d1-0433918449b8 -- datastoreBrowser-datastore-4981 -- vim.host.DatastoreBrowser.search -- 52cfad26-7ad3-4e5b-2043-1624611f432f(52710809-3213-0d6c-0b4c-972d37b06d37)

2020-01-13T13:11:19.950+03:30 info vpxd[04769] [Originator@6876 sub=vpxLro opID=req=00007f29304b6520-10] [VpxLRO] -- FINISH session[52cfad26-7ad3-4e5b-2043-1624611f432f]521e6dcc-4dc6-303e-a3d1-0433918449b8

2020-01-13T13:11:19.954+03:30 info vpxd[04805] [Originator@6876 sub=vpxLro opID=2a15e0ea] [VpxLRO] -- BEGIN lro-3515982 -- nfcService -- vim.NfcService.fileManagement -- 52cfad26-7ad3-4e5b-2043-1624611f432f(52710809-3213-0d6c-0b4c-972d37b06d37)

2020-01-13T13:11:19.960+03:30 info vpxd[04805] [Originator@6876 sub=vpxLro opID=2a15e0ea] [VpxLRO] -- FINISH lro-3515982

2020-01-13T13:11:20.363+03:30 info vpxd[04832] [Originator@6876 sub=vpxLro opID=261383c] [VpxLRO] -- BEGIN lro-3515983 -- ServiceInstance -- vim.ServiceInstance.retrieveContent -- 52c73ce5-b7e7-aa11-0597-256845c498b3(52505850-89cb-d5d4-5992-573892659c55)

2020-01-13T13:11:20.364+03:30 info vpxd[04832] [Originator@6876 sub=vpxLro opID=261383c] [VpxLRO] -- FINISH lro-3515983

2020-01-13T13:11:20.364+03:30 warning vpxd[04807] [Originator@6876 sub=Default] [NFC ERROR] Received fileIO error 2 from server: A file error was encountered -- NfcFssrvrRead: failed to read 73728 bytes @ 0 : Error

-->

2020-01-13T13:11:20.364+03:30 error vpxd[04807] [Originator@6876 sub=HTTP server /folder] NfcFssrvr_IO returned 4, fileIOErr: 2

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Actually it should open vm folder and show some thinng like thise :

Whould you please help me in this regard?

Thank you in Advance

Author :

URL : http:////docs.vmware.com/tw/VMware-vSphere/6.7/com.vmware.vcenter.install.doc/GUID-D6C0F17B-6E2C-4E2A-A90F-94057F964619.html

Topic Name : 在 Windows 上安裝含內嵌式 Platform Services Controller 的 vCenter Server

Publication Name : vCenter Server 安裝和設定

Product/Version : VMware vSphere/6.7

Question :

Hi, i have Windows Server 2019 STD for install vCenter, but when i click start to install. the installation will stop on VCSServiceManger. and popup The installation of vCenter Server failed due to an internal error

I need some help with my installation and setup of vCenter 6.7 in ESXi 6.7. I worked through Stage 1 and need to begin Stage 2. How do I access vCenter to continue? Do I use the internet on my workstation or do I use a workstation from within ESXi, a VM?

I'm trying to create a gold template for provisioning guests from using current version of CentOS 8, however, VMware Customzation Specification seems to be just completely broken for it. I have the latest version of open-vm-tools and perl packages installed. If I try to customize the OS and give it the network configuration, the VM starts up without hostname being changed (to the VM name) and the NIC has no IP at all. What am I missing? I'm also using EFI boot, which is recommended for CentOS 8.

Here are the environment information:

- ESXi 6.7u3

- vCenter 6.7u3

- CentOS 8.0.1905

- open-vm-tools 10.3.0-2.el8

- perl 5.26.3-416.el8

I entered a value in a global custom attribute in the HTML5 client (6.7U3) . When I had to clear the value (not delete the custom attribute), the value would not clear. After deleting the text and clicking OK, the text would remain.

When I tried in the flash client everything worked as expected and my text was deleted without issue.

Can anyone reproduce this issue or is it just me?

Hi,

I'm trying to create an environment where end users can deploy their own test VMs.

I do not what them changing the VM hardware configuration when they deploy from a template.

So far I have been able to prevent this, However an issue comes up when they check the box to "Customize this virtual machine's hardware"

in the new VM wizard.

all 3 boxes are present in the wizard on the select clone options page:

Customize the operating system

Customize this virtual machine's hardware

Power on virtual machine after creation

when they select "Customize the operating system" and click next they get a nice error message saying they can't do that.

the wizard stays active and they can uncheck the box and proceed

This is good.

however when they select "Customize this virtual machine's hardware" and click next they are permitted to proceed to customize hardware screen

They are allowed to create a new HDD and add a new HDD. ( these permissions are needed to clone a VM / template )

the error comes up when they then proceed to the end of the wizard.

the wizard closes with out an error, then the user gets this message.

"Permission to perform this operation was denied.

NoPermission.message.format"

What the ideal solution would be is to prevent the "Select Clone Options" page from even showing up.

I don't mind them powering on the VM when the close is done but I do not want them to customize the OS or hardware from the template.

A better error message would work in the wizard, similar to the use case of checking Customize the operating system.

also, after the user gets the error I can't find the failed task in the events or tasks view.

I'm running vCenter 6.7

Any help would be greatly appreciated.

Thanks for your time

We plan to deploy a new vCenter appliance as an initial step to executing embedded linked mode between the new appliance and the existing one.

This will be followed by moving some of the hosts with their VMs from the original vCenter to the new vCenter. Running VMs must not be impacted and VMs across the two vCenters are reachable to each other the same before they moved out.

still determining the approach to achieve this, the considered steps

Deploy new appliance

Join to existing SSO

Create identical VLAN/Port Groups in new vCenter

(This host which planned to be moved later to new vCenter)

Create a new empty host cluster in new vCenter

Evacuate target host and move it from source vCenter to new vCenter under new host cluster

Mount a new datastore to the moved host

SVmotion VMs to new datastore and moved host

Repeat the same for the second host.

Not sure if this plan is doable or missing pieces or order is not quite right, I am open to any idea or recommendations for achieving this task. Thanks

I have vcenter server 6 database on a standalone sql server and would like to move it to a sql cluster that has always on group. But could not find any documentation as to whether always on is supported or what needs to be done to migrate it. Since one will be a principal database and the other secondary (non-readable), how does sql server agent job play out in such scenario?

I have two Vcenters  both are setup with HA so I have three VCSA running      Primary  Peer Witness

The are working fine.

I am unable to ssh into them

I am using Cygwin  to ssh

I can ssh into the ESXI hosts with no problem

I keep getting

Permission denied, please try again.

I can logon using the web interface

SSH is enabled

Any ideas?

hi,

in order to monitor the VMs ans ESXi, vcenter uses the monitor port from every esxi and those ports form a vlan?

Hia

I'm trying to create a local account on the VCSA that is able to run 'service-control --status' in the bash shell. While trying to do this I've come accross a few things I cant really explain.

1. I can create users without any problem using "localaccounts.user.add --username x --role y -- password" but I cant edit or delete them without getting an error that the user is not recognized.

     - localaccounts.user.list only lists the root user. Didn't change after setting the bash shell as default for my custom user.

     - I can see all the users I created in my VCSA Web Interface, but I cant edit or delete useres here.

2. None of the given roles, even superAdmin, seems to have the permissions to run service-control. Do I need a root shell to run those commands?

I'm clearly missing something, overread something.. hoping you can point me in the right direction. I'm running a VCSA V6.7 U3 Build 14367737.

Regards

David

I found this > Configure vCenter Server Appliance for SNMP v3

And now stuck at configure SNMP users when run "snmp.hash --auth_hash secret1 --priv_hash secret2"

I input plain text for <secret1> and <secret2>. This works when execute this in the shell of ESXi. But in the shell of vCSA. It shows

Error in method: Invalid path to secret file. The file must be a plain text

file containing the secret to use to generate hash. (code

com.vmware.applmgmt.err_snmp_bad_path)

The guide did mentioned the prerequisites include "store these passwords in files on the host system".

But what kinds of file (format) should I create? Input the plain text password in those 2 files? Where should I place those files in the "host system"?

Hi!

I have VC 6.0 on windows server..

Today i reboot my VC,

Now the service starts, runs for a while, then goes into a panic.

In windows logs i see this:

The VMware VirtualCenter Server service terminated unexpectedly.  It has done this 4 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.

In VPXD log i see this:

2020-01-19T23:06:13.716+03:00 warning vpxd[14044] [Originator@6876 sub=Default opID=9678F612-0000003A-73] [VdbStatement] SQL execution took too long: SELECT EVENT_ID, CHAIN_ID, EVENT_TYPE, EXTENDED_CLASS, CREATE_TIME, USERNAME, CATEGORY, VM_ID, VM_NAME, HOST_ID, HOST_NAME, COMPUTERESOURCE_ID, COMPUTERESOURCE_TYPE, COMPUTERESOURCE_NAME, DATACENTER_ID, DATACENTER_NAME, DATASTORE_ID, DATASTORE_NAME, NETWORK_ID, NETWORK_NAME, NETWORK_TYPE, DVS_ID, DVS_NAME, STORAGEPOD_ID, STORAGEPOD_NAME, CHANGE_TAG_ID FROM VPX_EVENT WHERE HOST_ID=? AND VM_ID IS NULL AND (EVENT_TYPE IN (?,?,?)) AND EVENT_ID<? ORDER BY EVENT_ID DESC

2020-01-19T23:06:13.716+03:00 warning vpxd[14044] [Originator@6876 sub=Default opID=9678F612-0000003A-73] [VdbStatement] Execution elapsed time: 17690 ms

2020-01-19T23:06:50.739+03:00 warning vpxd[16252] [Originator@6876 sub=VpxProfiler opID=ProcessPerfResults-5ca58d21] ProcessPerfResults [TotalTime] took 105288 ms

Any ideas on how to make VC work more stable?