Running VCenter 7.0 and I am trying to add an ESXi-7.0.0-15843807-standard host. I enter all the correct credentials and addition process starts but then abruptly ends with:
A specified parameter was not correct: info.productVersion
Anybody seen this and know why this is occurring and a possible fix?
Hello,
I have problem with VCenter. In UI I have this error:
ESXi Host Certificate Status
When I open settings and certificates I cannot see anything.
But when I open webgui on the host - it is ok.
Steps tried:
Can you help me please?
Pavel
Hello,
I am trying to install vcenter and keep getting this error. I have disabled my firewall and still get the error. Please help!
--
2018-07-03T14:37:44.444Z - info: output:PROGRESS
2018-07-03T14:37:50.279Z - info: output:
2018-07-03T14:37:50.279Z - info: output:
2018-07-03T14:37:50.279Z - info: output:ERROR
+ <Errors>
+ <Error>
+ <Type>ovftool.http.send</Type>
+ <LocalizedMsg>
+ Failed to send http data
+ </LocalizedMsg>
+ </Error>
+ </Errors>
2018-07-03T14:37:52.414Z - info: output:RESULT
+ ERROR
2018-07-03T14:37:52.415Z - info: Xml output from ovftool: <data><ManifestValidate valid="true"/><Errors><Error><Type>ovftool.http.send</Type><LocalizedMsg>Failed to send http data</LocalizedMsg></Error></Errors></data>
2018-07-03T14:37:52.415Z - error: Ovf Service:vmrefFlag: false
2018-07-03T14:37:52.416Z - info: Cancelling timeout due to error from progress callback
2018-07-03T14:37:52.416Z - error: Progress Controller: [VCSA ERROR] - Progress callback error
2018-07-03T14:37:52.416Z - error: Progress Controller: [VCSA ERROR] - Details Failed to send http data
2018-07-03T14:37:52.419Z - info: Cancelling the ping timer for session mgmt
2018-07-03T14:37:52.419Z - info: Cancelling the ping timer for session mgmt
2018-07-03T14:37:52.437Z - info: ovfProcess child process exited with code 1
2018-07-0
Hi,
I get the following Error when i want to log in with AD user
Can anybody help me?
My story is some what similar to this post here
VCenter Appliance - Esx Agent Manager fails to start (vmware.thread 586245)
was getting error 503 when trying to brows to the vCenter ui. Stumbled across this KB article
Discovered that my root passwrd was expired and the Log file was to large. Followed those steps and was able to get vmware-vpostgres to start.
then the Vmware-invsvc now failed to start. searched and found
and was now getting LDAP 49 error and used the steps in this KB article (VMware Knowledge Base )to reset my account credentials.
vmware-invsvc still wouldn't start now because i noticed my SSL cert had expired (yeah.. set it and forget it i know....) so I found this KB article (VMware Knowledge Base )to reset that.
look all I want to do is upgrade to 6.5. I am at my end with this thing. And I don't know what to do. any guidance would be appreciated.
I am attaching some logs if you need more let me know.
Hi, I changed my old AD Server from 2012 to a new MS Server 2019 with a new AD name. After setting Identity Source and Global Permissions it is not possible to login in the vcenter with a MS domain user. In Global Permissions I can see the Domain User with the Role Administrator. What else can I check? In the VCSA:5480 logged in as the root user everything looks good...
Thanks for a good tip
Best regards
werner
We have a vcenter windows server 6.5 that suddenly stopped working and the web client fails with the following error
400] An error occurred while sending an authentication request to the vCenter Single Sign-On server - An error occurred when processing the metadata during vCenter Single Sign-On setup - Cannot connect to the VMware Component Manager https://vcentersvt.company.intranet/cm/sdk?hostid=e58bd8b0-bb2d-11e8-94b4-000c29d9b960.
Rebooting the server didn't help
The CM service does not start but could not identify the cause
any suggestion is appreciated
I just started to learn this and wonder which method is better.
1. Joining vcsa SSO to AD via Active Directory (Integrated Windows Authentication); will require reboot (need to reboot all vcsa in a cluster?), only join to one AD, AD trust to consider, Should join to root of the forest.
2. Join vcsa via AD over LDAP, no reboot, join to multiple AD, any AD trust to consider?... does this mean workstation joined to a Domain can't just use SSO? (like must provide account and password all the time)
Identity Sources for vCenter Server with vCenter Single Sign-On
Extracted from the above link;
"Active Directory over LDAP. vCenter Single Sign-On supports multiple Active Directory over LDAP identity sources. This identity source type is included for compatibility with the vCenter Single Sign-On service included with vSphere 5.1. Shown as Active Directory as an LDAP Server in the vSphere Client."
Does this mean, this is included mainly to be compatible with vCenter SSO vSphere 5.1 and we should use Active Directory (Integrated Windows Authentication) instead if there isn't vSphere 5.1 around.
If so, why? Because it is easier?
Thanks!
Im running VShere 5.5 Essentials. I migrated to VSPhere VCEnter 6.5 on the 5.5 host. I know have my 6.5 host and want to move VCEnter to the 6.5 host. What is the best way to do this? Can I just run the installer and have it migrate from the 5.5 host to 6.5 host. I have migrated my vm's to new 6.5 hosts, no just have vcenter 6.5 running on one old 5.5 host. I guess I could try upgrading vmware on the 5.5 host tp 6.5, but would rather not mess with that.
Any recommendations?
is it possible to set up an alarm that will send an email notification when DRS migrates a virtual machine?
Hi all,
Just started having an issue when trying to access vCenter from the web client. Initially whilst trying to access I received a "root certificate cannot be null" error. I rebooted the appliance. Now when I try and login I am receiving an error that states: "400 An error occured while sending an authentication request to the vCenter Single Sign On server - An error occurred when processing the metadata during vCenter Single Sign-On setup - null" We are running version 6.5.
I did some reading and a few folk found that a time difference between the ESXi host and the appliance caused the issue. I logged onto the host / server appliance, and the time was incorrect on both. I have since changed this so that they both have the same time, however I still get the same error.
Any ideas?
Thankyou,
Paul
VCSA web client down multiple times and high cpu usage after update to 7.0.0d. Can anyone help with this issue ?
Hello,
I have a vcenter appliance version 5.5
I tried to change the SSL certificates. it was a fail and half of the services were not working properly.
So I rollbacked and put back the old certificates.
service vmware-vpxd was still not starting.
I followed many procedures, KB, etc. and I think I accidentally wiped the embedded database. And I have no backup of course !
vcenter:~ # /opt/vmware/vpostgres/9.0/bin/psql -h 127.0.0.1 -p 5432 -d VCDB -U vc
Password for user vc:
psql.bin (9.0.22)
Type "help" for help.
No entry for terminal type "xterm-256color";
using dumb terminal settings.
VCDB=> \dt vpx.*;
VCDB=> SELECT * FROM vpx.vpx_license;
serial_number | serial_key | type
---------------+------------+------
(0 rows)
VCDB=> \l
List of databases
Name | Owner | Encoding | Collation | Ctype | Access privileges
-----------+----------+-----------+-----------+-------+-----------------------
VCDB | vc | SQL_ASCII | C | C | =Tc/vc +
| | | | | vc=CTc/vc
postgres | postgres | SQL_ASCII | C | C |
template0 | postgres | SQL_ASCII | C | C | =c/postgres +
| | | | | postgres=CTc/postgres
template1 | postgres | SQL_ASCII | C | C | =c/postgres +
| | | | | postgres=CTc/postgres
(4 rows)
VCDB=> \dn
List of schemas
Name | Owner
--------------------+----------
information_schema | postgres
pg_catalog | postgres
pg_toast | postgres
pg_toast_temp_1 | postgres
pg_toast_temp_14 | postgres
pg_toast_temp_15 | postgres
pg_toast_temp_2 | postgres
pg_toast_temp_25 | postgres
pg_toast_temp_26 | postgres
public | postgres
vpx | vc
(11 rows)
VCDB=> \dt
List of relations
Schema | Name | Type | Owner
--------+--------------------------------+-------+-------
vpx | vpx_access | table | vc
vpx | vpx_alarm | table | vc
vpx | vpx_alarm_action | table | vc
vpx | vpx_alarm_disabled_actions | table | vc
vpx | vpx_alarm_expr_comp | table | vc
vpx | vpx_alarm_expression | table | vc
vpx | vpx_alarm_repeat_action | table | vc
vpx | vpx_alarm_runtime | table | vc
vpx | vpx_alarm_state | table | vc
vpx | vpx_binary_data | table | vc
vpx | vpx_bulletin_operation | table | vc
[......]
VCDB=> SELECT * FROM vpx.vpx_license;
serial_number | serial_key | type
---------------+------------+------
(0 rows)
VCDB=>
How can I confirm I have wiped the database ?
My main concern is some ESX hosts hve lost root passwords.
To manage them, vcenter was the last way I guess ?!
Thanks
Hi,
We had a vCenter fail that was in ELM with a second VC, it was a very small environment so we just decomed the problematic VC and rebuilt it from scratch. Everything else is working fine but there are now duplicate objects in the licensing section that are not visible in the rest of the VC interface.
Reality:
VC1
Host A
Host B
Host C
VC2
Host 1
Host 2
Host 3
What licensing shows:
VC1
Host A
Host B
Host C
VC2
Host 1
Host 2
Host 3
VC2
Host 1
Host 2
Host 3
Basically we need to find a way to update the licensing database/tables to recognise that 'host 1' is actually the same object as 'host 1', 'VC2 is the same as 'VC2' and merge the into a single entity or allow us to delete the duplicted objects.
I've posted about this before but have since made some changes in anticipation of this part:
So far, I've upgraded the VCSA to 6.7U3 (from 6.5), I've introduced the new management network into the environment (with a vDS port group available for it), I've opened FW rules up from the new IP of the VCSA to all the hosts (any port), and I've reserved the new IP and new DNS name on the new network:
Current Configuration:
VCSA 6.7: myvcsa.old.management.network; Subnet A
ESXi 1/2/3: esxi[1/2/3].old.management.network; Subnet A
Target Configuration:
VCSA 6.7: myNEWvcsa.NEW.manegement.network; Subnet B
ESXi 1/2/3: old.manegement.network; Subnet A
I tried to move the VCSA using the following steps from a post on this page but ran into a few issues...
1) Backup the Vcenter config. You can do that inside the VAMI by connecting to FTP server.
2) Add an extra network adapter to the vcenter applicance
3) go into the VAMI and assign the new ip address to the newly added Adapter.
4) Add new record in the DNS.
5) Log into the vcenter with the new ip
6) Remove the old network adapter and restart the vcenter appliance
7) After restart go to DCUI and change the management network IP for the vcenter appliance .
The pings stopped on the old IP and the new IP picked up, but it was slow to start all services, and eventually, I tied to log in and got an error (Failed to connect to VMware Lookup Service) where it was looking for the old URL:443.
How can successfully I move my VCSA to a new IP, with a new hostname, new domain and new network? What am I missing?
Hello,
First Question:
Our vCenter server has crashed and we're having issues trying to figure out how to restore it from backup. We backup to the cloud and our backup solution authenticates through vCenter to backup/restore VMs....so we're not able to restore without vCenter, it seems. Any ideas?
Second Question:
We have made some VM changes directly on hosts since our vCenter has been lost. If we restore our vCenter will we lose those changes? We haven't made any networking changes, we have simply deleted/added a few VMs for the most part.
Thanks for any help!
Matt
Author : Evgeni Ivanov
Topic Name : Considerations and Limitations for File-Based Backup and Restore
Publication Name : vSphere Installation and Setup
Product/Version : VMware vSphere/6.5
Question :
Please clarify how to do a Filed-Based backup or restore if the vCenter Server has an embedded PSC in a linked mode configuration.
Hello,
After suffering a storage failure on the array running the VCSA and hosts we are unable to connect to the VCSA from the web console to manage the environment. It looks like the VCSA lost its registration with itself. I entered emergency mode and repaired the file system so the VCSA boots now but when logging into the webclient it just display the below message and nothing in the inventory. Any ideas on how to get this VCSA to manage the environment again?
Could not connect to one or more vCenter Server systems:https://xxx.xxx.xxx.xxx:443/sdk
Environment:
1 x VCSA 6.7 with embedded PSC
3 x ESXi 6.5 hosts
1 x HP array
Thanks.
I have had my vCenter install fail three times with this message. When I check the error.log it says
cmd "/usr/bin/python /usr/lib/vmware-lookupsvc/tools/lstool.py list --url http://localhost:7090/lookupservice/sdk" timed out after 60 seconds due to lack of progress in last 30 seconds (0 bytes read)
No file found matching /etc/vmware-vpx/vc-extn-cisreg.prop
I have the full log bundle if anyone needs it, but it is too large to attach. I am not sure what to do.
Does anyone have suggestions? They would be most appreciated.
Thanks,
Michael
Good afternoon,
I have been managing our company's vCenter Server Virtual Appliance (v6.0) and recently - in the last 3 weeks - I am unable to log into the servers main web portal using the configured administrator account. I am able to see that the server is running via a vSphere Client to the ESXi host it is installed on, can SSH to it and can log in as the root user under the 5480 port. I initially was seeing the login page but the user account would not login but now, after an initial restart of the appliance, I am receiving the following error :
I am unable to find any references to this specific error on the web although there are a number of posts regarding the 503 error pointing to primarily a database issue.
I have verified the available space on the drives and did a cleanup of the database to clean up any "bloated" tables but still receive the error.
Are there any other suggestions as to the cause and solution to this error? Do I simply need to "bite the bullet" and re-install the vCenter Server?
Thank you, in advance, for any replies.
GregM