After un-installing vcenter server, renaming all of the vCenter folders that remained (except for the VMware tools folder), did the trick for me. This was not before wasting over a week dealing with VMware support.
↧
Re: Installation of component VCSServiceManager failed for vCenter 6.0
↧
Alarm email address delimiter in VCSA 6.5
Hello,
we are using VCSA 6.5d (6.5.0.5500) and try to set alarm email responses to multiple recipients via PowerCLI (6.5 and 6.5.1).
However, multiple email addresses are seperated via semicolon by PowerCLI in vCenter that does not work: Emails are not delivered. The error message is:
The original message was received at Fri, 28 Apr 2017 09:52:54 +0200 from root@localhost
----- The following addresses had permanent fatal errors ----- email1@ourdomain.tld;email2@ourdomain.tld
----- Transcript of session follows -----
553 5.1.3 email1@ourdomain.tld;email2@ourdomain.tld... Invalid route address
Email alarm notifications are working when I set the delimiter to a comma in vCenter alarms configuration manually (i.e. email1@ourdomain.tld,email2@ourdomain.tld).
This is the original PowerCLI script used for setting up a notification for a single alarm:
$vCenterServer="ourvCenterServer"
Connect-VIServer -Server $vCenterServer -Protocol https -WarningAction SilentlyContinue | Out-Null
$sessionManager = Get-View -Id $global:DefaultVIServer.ExtensionData.Content.SessionManager
$sessionManager.SetLocale("en-US")
Get-AlarmDefinition -Name "Storage DRS recommendation" | New-AlarmAction -Email -To @('email1@ourdomain.tld','email2@ourdomain.tld')
For debugging reasons, I cut it down to:
$vCenterServer="ourvCenterServer"
Connect-VIServer -Server $vCenterServer
Get-AlarmDefinition -Name "Storage DRS recommendation" | New-AlarmAction -Email -To @('email1@ourdomain.tld','email2@ourdomain.tld')
But this did not help either.
I also executed that script with different region settings: German as my personal user is set to, and English region settings of another user under another Windows machine installed with English Windows version.
Please note that semicolon worked as delimiter for our previous vSphere 6.0 Windows(!) installation. Now we moved on to 6.5 vCenter appliance and it seems that it requires commas. That's fine, if it would work via PowerCLI.
So where is the problem here? How can we set up our alarms with PowerCLI (it would be too much effort to set them all manually).
Is this a PowerCLI bug? A vCenter bug? Isn't it a bug at all? Rather a settings issue?
↧
↧
Re: vCenter 6.0 update 2 to update 3 failed with errors 3010 , 1603
Did you get chance to look at the following thread and KB?
↧
vCenter 6.0 update 2 to update 3 failed with errors 3010 , 1603
Trying to upgrade windows vCenter 6.0 update 2 to update 3 ( embedded PSC ) but failed with error code 3010 and error code 1603.
Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details.Installation of component VMware vCenter Server failed with error code '3010'. Check the logs for more details.
- Updated all the pending windows updates on the VC server
- killed any process holding vmeventmsg.dll , also renamed the dll and created the copy of original file
- Rebooted server after updates or any changes done. still the upgrade is not successful.
- Ensured the ipv4 stack is installed
Any suggestions please ?
↧
Re: vCenter 6.0 update 2 to update 3 failed with errors 3010 , 1603
Yeah, I tried those suggestions but still no go...
↧
↧
Re: Upgrade vCenter (windows) with external PSC from 6.0 Update 1b to 6.0 Update 3b
Thanks for the Help.
My vCenter is a Windows, I understand that after to do the upgrade of PSC I have to go to Windows and burn the ISO and to do a upgrade.
↧
vdswitch 6.5 error
Hello
Recently i've upgraded my vsphere 6 to 6.5 sucessfully, than i tried to add a new vsphere 6.5 host to my distributed switch (that was in the v 5.1), and i've received the error bellow and the host wasn't added to it. Now i've upgraded the vds to 6.5 too, and i have the same error and i cannot add any other host to it. This is the error:
[HostCapsule::AddJoinedDvs] Host [rammstein] joined the DVS [fc 46 2a 50 ab a0 b7 10-99 a6 aa 10 d4 44 16 39].
2017-04-26T14:55:53.559-03:00 info vpxd[7F62837EF700] [Originator@6876 sub=vpxLro opID=acaa5943-ff6c-42c7-a3c2-ce8985d981aa-42987-ngc-ae] [VpxLRO] -- FINISH lro-290778
2017-04-26T14:55:53.559-03:00 info vpxd[7F6283F7E700] [Originator@6876 sub=vpxLro opID=acaa5943-ff6c-42c7-a3c2-ce8985d981aa-42986-ngc-c3] [VpxLRO] -- FINISH lro-290777
2017-04-26T14:55:53.559-03:00 info vpxd[7F6353BF7700] [Originator@6876 sub=vpxLro opID=acaa5943-ff6c-42c7-a3c2-ce8985d981aa-42985-ngc-2d] [VpxLRO] -- FINISH lro-290779
2017-04-26T14:55:53.559-03:00 info vpxd[7F63820F8700] [Originator@6876 sub=vpxLro opID=acaa5943-ff6c-42c7-a3c2-ce8985d981aa-42984-ngc-9] [VpxLRO] -- FINISH lro-290776
2017-04-26T14:55:53.678-03:00 info vpxd[7F6381451700] [Originator@6876 sub=License:NsxClient opID=DvsAddHostWizard-apply-42990-ngc-e4-304b7bae] NSX: nsx-netsec is not licensed with: vxlan when check for hostInstanceId: host-226634 feature: dvs
2017-04-26T14:55:53.713-03:00 info vpxd[7F6353870700] [Originator@6876 sub=vpxLro opID=DvsAddHostWizard-apply-42990-ngc-e4] [VpxLRO] -- FINISH task-1344163
2017-04-26T14:55:53.967-03:00 info vpxd[7F638114B700] [Originator@6876 sub=vpxLro opID=216b991e] [VpxLRO] -- BEGIN lro-290783 -- SessionManager -- vim.SessionManager.sessionIsActive -- 52d1858f-d5e7-a874-840b-688b4919f329(52f92cfa-366f-450d-3488-174ab81ef06c)
2017-04-26T14:55:53.967-03:00 info vpxd[7F638114B700] [Originator@6876 sub=vpxLro opID=216b991e] [VpxLRO] -- FINISH lro-290783
BEGIN lro-290786 -- dvs-42 -- vim.DistributedVirtualSwitch.fetchPorts -- 52915e0d-8f7d-880e-1dff-f3c59f088d8c(52a7eb00-ec51-02a4-85de-4daf49d7ccfc)
2017-04-26T14:55:54.300-03:00 error vpxd[7F63812CE700] [Originator@6876 sub=MoDVSwitch opID=DvsAddHostWizard-apply-42996-ngc-c0] [MoDVS::GetPortInt] Can't find port with empty key in [dvSwitch-5]
2017-04-26T14:55:54.300-03:00 error vpxd[7F63812CE700] [Originator@6876 sub=SoapAdapter opID=DvsAddHostWizard-apply-42996-ngc-c0] Method vim.DistributedVirtualSwitch.fetchPorts threw undeclared fault of type vim.fault.NotFound
2017-04-26T14:55:54.301-03:00 info vpxd[7F63812CE700] [Originator@6876 sub=vpxLro opID=DvsAddHostWizard-apply-42996-ngc-c0] [VpxLRO] -- FINISH lro-290786
2017-04-26T14:55:54.301-03:00 info vpxd[7F63812CE700] [Originator@6876 sub=Default opID=DvsAddHostWizard-apply-42996-ngc-c0] [VpxLRO] -- ERROR lro-290786 -- dvs-42 -- vim.DistributedVirtualSwitch.fetchPorts: vim.fault.NotFound:
--> Result:
--> (vim.fault.NotFound) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = (vmodl.LocalizableMessage) [
--> (vmodl.LocalizableMessage) {
--> key = "com.vmware.vim.vpxd.dvs.portNotFound.label",
--> arg = (vmodl.KeyAnyValue) [
--> (vmodl.KeyAnyValue) {
--> key = "port",
--> value = ""
--> }
--> ],
--> message = <unset>
--> }
--> ]
--> msg = ""
--> }
--> Args:
-->
--> Arg criteria:
--> (vim.dvs.PortCriteria) {
--> dynamicProperty = <unset>,
--> connected = <unset>,
--> active = <unset>,
--> uplinkPort = true,
--> scope = <unset>,
--> portgroupKey = <unset>,
--> inside = <unset>,
--> portKey = <unset>,
--> host = <unset>
--> }
↧
Re: Not enough memory?
I got around this by using the deploy ovf template option in vSphere fat client. Then pointing to the ova file located in vCSA iso.
↧
share vmdk
i have vcenter 5.5 u2 and esxi 5.5 u2 cluster. now i want to create shared disk vmdk bettween two redhat enterprise 7.0 linux. not redhat cluster.
is it possible and vmotion is working?
↧
↧
vcenter u3b upgrade from u3a
I tried to upgrade from vcenter 6.0 u3a to u3b on windows platform. it was straight forward upgrade on the psc.
but when i tried upgrading vcenter, it prompted me to unisntall vcenter completely instead of an upgrade. why is that?
↧
Re: share vmdk
you can do the vmotion.
Migrating virtual machines with Raw Device Mappings (RDMs) (1005241) | VMware KB
↧
Re: vCenter 6.0 U3/U3a installation fails with Failed to initialize VMware Certificate Authority - Error 100004
Seeing a similar issue with our Windows vCenter 5.5 to 6.0 U3a upgrade.
C:\Program Files\VMware\vCenter Server\vmafdd>vmafd-cli.exe join-vmdir --server-name ExternalPscFqdn --user-name administrator --password password --machine-name vCenterServerFqdn --domain-name dc=vsphere,dc=local
Error 100004: Problem reading password file.
Verify contents of password file.
vmafdd.log shows:
2017-04-30T17:22:04.832Z:t@8008:INFO: VmAfSrvJoinVmDir: Failed to join Vmdir. Error(100004)
2017-04-30T17:22:04.832Z:t@8008:ERROR: ERROR! [VmAfdIpcJoinVmDir] is returning [100004]
vmafdvmdirclient.log shows:
2017-04-30T17:22:04.832Z:t@30980000:ERROR: VmDirCreateBindingHandleUtilityA, ()() failed (100004)
2017-04-30T17:22:04.832Z:t@30980000:ERROR: VmDirGeneratePassword failed (100004)
2017-04-30T17:22:04.832Z:t@30980000:ERROR: VmDirLdapSetupComputerAccount (cn=vCenterServerFqdn,ou=Computers,dc=vsphere,dc=local) failed with error (100004)
2017-04-30T17:22:04.832Z:t@30980000:ERROR: VmDirClientJoin failed. Error(100004)
Thanks for the tip regarding 6.0 U2. I'll try that and report back.
↧
Re: vCenter 6.0 U3/U3a installation fails with Failed to initialize VMware Certificate Authority - Error 100004
A huge thank you for the tip to roll back to 6.0U2 to perform the upgrade. I was able to complete our upgrade with 6.0U2. Now I'm off to see if I can get it patched up to 6.0U3b.
↧
↧
Re: vcenter u3b upgrade from u3a
Sounds quite odd. Have you got some screenshots of what you're seeing and also what is the name of the ISO file you are using?
↧
Re: SNMP agent problem after update to VCSA 6 update 2
When running 6.0, I noticed the snmp daemon was running hot, and given I had already reported it to them, I added a cron job to restart it every 30 minutes. I just managed a successful 6.5 upgrade, so I'll soon see if the same problem persists.
↧
Re: vCenter Distributed Virtual Switch fails on add New Host
i have a similar deployment, and had a similar problem,
one of my esx servers had a management interface attached to the VS that was stopping the deletion, after removing the kernel adapter thing was able to delete the VS
for the connection thing, i had to create a temp network group, configure esx's to have management on the temp network, delete them from vcenter, add vcenter to the temp network, re add esx's configure them with the desired network settings, remove them from v center add them with the new config (it was pain)
hope that helps
↧
Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"
My datastore ran out of space, the vcenter froze, I cleared space on the datastore, resumed the vcsa but it was unresponsive.
Restarted vcenter and got the "Waiting for vpxd to initialize failed".
What solved it was running these instructions I found here:
From: http://www.colabug.com/thread-1093735-1-1.html
To get over this, log on to the VCVA using SSH
Run the command “ /usr/sbin/vpxd_odbcconfig ”
You see output similar to:
VMware vCenter Server Appliance ODBC Configuration
Choose a database to use with VMware vCenter Server
1) oracle
2) embedded
Enter 2 (should the DB be the embedded PostgresSQL
You see output similar to:
Configuring ODBC for embedded
Operation was successful.
Database already populated with version VirtualCenter Database 5.5
Reinitialize database? (WARNING: WILL DELETE ALL RECORDS) [y(es)|N(O)]: OK, preserving the database. (select No to preserve the database)
Restart vCenter Server now to activate the database changes [y/N]:y
Successfully restarted vCenter Server
This should start the vpxd service
Here's my output:
Starting vmware-vpxd: success
Waiting for vpxd to initialize: ............................................................failed
vcsa:~ # /usr/sbin/vpxd_odbcconfig
WARNING - Use of this command is not supported unless you are doing this
with the consultation of VMware Technical Support or a VMware published
technical article.
VMware vCenter Server Appliance ODBC Configuration
Choose a database to use with VMware vCenter Server
1) oracle
2) embedded
#? 2
Configuring ODBC for embedded
Error: VPXD must be stopped to perform this operation.
Database configuration has failed.
Would you like to try again or modify the settings manually?
[A]gain/[m]anually : m
vcsa:~ # service vmware-vpxd stop
Stopping tomcat: success
Stopping vmware-vpxd: success
Shutting down ldap-server..done
vcsa:~ # /usr/sbin/vpxd_odbcconfig
WARNING - Use of this command is not supported unless you are doing this
with the consultation of VMware Technical Support or a VMware published
technical article.
VMware vCenter Server Appliance ODBC Configuration
Choose a database to use with VMware vCenter Server
1) oracle
2) embedded
#? 2
Configuring ODBC for embedded
Operation was successful.
Database already populated with version VirtualCenter Database 5.5
Reinitialize database? (WARNING: WILL DELETE ALL RECORDS) [y(es)|N(O)]: n
OK, preserving the database.
Restart vCenter Server now to activate the database changes [y/N]:y
Successfully restarted vCenter Server
vcsa:~ #
Success!!
↧
↧
Re: [500]SSO error:null Check the vsphere webclient server logs for details. vCenter Server Appliance 6.0 update 2
Hello, I have the same question, I ask you to solve the problem how to solve it
↧
VCenter Server 6.5 Fresh install error, roll back...
New OS
Windows Server 2008 R2 Standard SP1 x64
Dot Net 3.5 feature installed
VCenter Server 6.5 (6.5.0-5318154)
2017-05-03 11:22:50.411-04:00| vcsInstUtil-5318154| I: ParseStatusFile: STATUS: 6%: "Starting VMware Identity Management Service..."
2017-05-03 11:22:50.411-04:00| vcsInstUtil-5318154| I: ParseStatusFile: Calling callback with 3 -> 6 "Starting VMware Identity Management Service..."
2017-05-03 11:22:50.411-04:00| vcsInstUtil-5318154| I: Entering function: UpdatePkgMgrProgressFromStatusFile
2017-05-03 11:22:50.411-04:00| vcsInstUtil-5318154| I: ProcessMsiMsg: ACTIONDATA reporting "Starting VMware Identity Management Service..."
2017-05-03 11:22:50.473-04:00| vcsInstUtil-5318154| I: Leaving function: UpdatePkgMgrProgressFromStatusFile
2017-05-03 11:22:50.473-04:00| vcsInstUtil-5318154| I: Leaving function: ParseStatusFile
2017-05-03 11:22:53.051-04:00| vcsInstUtil-5318154| I: Entering function: ParseStatusFile
2017-05-03 11:22:53.051-04:00| vcsInstUtil-5318154| I: ParseStatusFile: curr error msg: "Encountered an internal error.
Traceback (most recent call last):
File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 2024, in main
vmidentityFB.boot()
File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 348, in boot
self.configureIdentityManager(self.__idmRetryCount, self.__idmRetryInterval)
File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 532, in configureIdentityManager
self.startIDMService()
File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 1257, in startIDMService
returnCode = self.startService(self.__idm_servicename,self.__idmRetryCount * self.__idmRetryInterval)
File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 88, in startService
return service_start(svc_name, wait_time)
File "C:\Program Files\VMware\vCenter Server\python-modules\cis\utils.py", line 784, in service_start
raise ServiceStartException(svc_name)
ServiceStartException: {
"resolution": null,
"detail": [
{
"args": [
"VMwareIdentityMgmtService"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'VMwareIdentityMgmtService'",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
"
2017-05-03 11:22:53.051-04:00| vcsInstUtil-5318154| E: ParseStatusFile: Displaying error message for "VMware vCenter Server": "Encountered an internal error.
Traceback (most recent call last):
File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 2024, in main
vmidentityFB.boot()
File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 348, in boot
self.configureIdentityManager(self.__idmRetryCount, self.__idmRetryInterval)
File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 532, in configureIdentityManager
self.startIDMService()
File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 1257, in startIDMService
returnCode = self.startService(self.__idm_servicename,self.__idmRetryCount * self.__idmRetryInterval)
File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 88, in startService
return service_start(svc_name, wait_time)
File "C:\Program Files\VMware\vCenter Server\python-modules\cis\utils.py", line 784, in service_start
raise ServiceStartException(svc_name)
ServiceStartException: {
"resolution": null,
"detail": [
{
"args": [
"VMwareIdentityMgmtService"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'VMwareIdentityMgmtService'",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
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."
↧
setup new vcenter for horizon view
i am setting up a new vcenter for horizon view. shoudl i setup a new vcenter and point it to the same ps c appliance as the server vcenter or should i setup a new psc and new vcenter but in same sso domain as server vcenter?
↧