Hello all,

I am running vCenter 6.7 and I've been getting the following error when trying to log into my vCenter: [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 - null

I've tried restarting the vCenter appliance and one thing I noticed is the vAPI endpoint service was not starting. Looking at the endpoint.log, I see the following error:

2019-08-13T14:58:22.278-04:00 | INFO  | state-manager1            | DefaultStateManager            | Invoking sts-builder

2019-08-13T14:58:22.376-04:00 | ERROR | state-manager1            | SoapBindingImpl                | SOAP fault

com.sun.xml.internal.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: Invalid credentials Please see the server log to find more detail regarding exact cause of the failure.

at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)

at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:116)

at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:259)

at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:289)

at com.vmware.vim.sso.client.impl.SoapBindingImpl.sendMessage(SoapBindingImpl.java:161)

at com.vmware.vim.sso.client.impl.SoapBindingImpl.sendMessage(SoapBindingImpl.java:114)

at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.sendRequest(SecurityTokenServiceImpl.java:927)

at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.executeRoundtrip(SecurityTokenServiceImpl.java:856)

at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl.acquireTokenByCertificate(SecurityTokenServiceImpl.java:477)

at com.vmware.vapi.endpoint.cis.StsBuilder.createToken(StsBuilder.java:179)

at com.vmware.vapi.endpoint.cis.StsBuilder.rebuild(StsBuilder.java:77)

at com.vmware.vapi.endpoint.cis.StsBuilder.buildInitial(StsBuilder.java:54)

at com.vmware.vapi.state.impl.DefaultStateManager.build(DefaultStateManager.java:354)

at com.vmware.vapi.state.impl.DefaultStateManager$1.doInitialConfig(DefaultStateManager.java:168)

at com.vmware.vapi.state.impl.DefaultStateManager$1.run(DefaultStateManager.java:151)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at java.lang.Thread.run(Thread.java:748)

2019-08-13T14:58:22.376-04:00 | ERROR | state-manager1            | StsBuilder                     | Failed to acquire token for the solution user.

com.vmware.vim.sso.client.exception.AuthenticationFailedException: Provided credentials are not valid.

at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.handleFaultCondition(SecurityTokenServiceImpl.java:996)

at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.sendRequest(SecurityTokenServiceImpl.java:932)

at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.executeRoundtrip(SecurityTokenServiceImpl.java:856)

at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl.acquireTokenByCertificate(SecurityTokenServiceImpl.java:477)

at com.vmware.vapi.endpoint.cis.StsBuilder.createToken(StsBuilder.java:179)

at com.vmware.vapi.endpoint.cis.StsBuilder.rebuild(StsBuilder.java:77)

at com.vmware.vapi.endpoint.cis.StsBuilder.buildInitial(StsBuilder.java:54)

at com.vmware.vapi.state.impl.DefaultStateManager.build(DefaultStateManager.java:354)

at com.vmware.vapi.state.impl.DefaultStateManager$1.doInitialConfig(DefaultStateManager.java:168)

at com.vmware.vapi.state.impl.DefaultStateManager$1.run(DefaultStateManager.java:151)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at java.lang.Thread.run(Thread.java:748)

This line caught my attention: com.sun.xml.internal.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: Invalid credentials Please see the server log to find more detail regarding exact cause of the failure.

I am not sure what credentials vAPI is attempting to use but I don't see anything in the logs that points to what credentials are being tried.

Would anyone have any insight into this problem? I've been working on this for a few days with no success.

Many thanks

vCenter version 6.0.0, build 3634794.

srm version: 6.1.0

I have a protected site, and a recovery site.  Running `connect-viserver -alllinked:$true -server protected.domain.com` works just fine, and I can see all the linked servers in $global:DefaultVIServers

PS > $global:DefaultVIServers

Name                           Port  User

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

recovery.domain.com  443   DOMAIN\timkennedy

protected.domain.com 443   DOMAIN\timkennedy

When I go to connect to the SRM server(s), I can log into each one individually, but I can't authenticate a single session to both servers using the -RemoteCredential option or the -RemoteUser & -RemotePassword options.

First, building a credential known to work at both sides (AD SSO):

PS > $credential = Get-Credential -Message 'Enter Password:' -UserName 'DOMAIN\timkennedy'

Using -RemoteCredential or passing -RemoteUser with -RemotePassword:

PS > Connect-SrmServer -IgnoreCertificateErrors -Server protected.domain.com -RemoteCredential $credential -Credential $credential

Connect-SrmServer : 8/29/2017 12:51:33 PM       Connect-SrmServer               Cannot complete login due to an incorrect user name or password.

At line:1 char:1

+ Connect-SrmServer -IgnoreCertificateErrors -Server protected.domain. ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Connect-SrmServer], VimException

    + FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VimAutomation.Srm.Commands.Commands.ConnectSrmServer

And:

PS > Connect-SrmServer -IgnoreCertificateErrors -Server protected.domain.com -RemoteUser 'DOMAIN\timkennedy' -RemotePassword 'supersecretpassword' -User 'DOMAIN\timkennedy' -Password 'supersecretpassword'

Connect-SrmServer : 8/29/2017 12:51:33 PM       Connect-SrmServer               Cannot complete login due to an incorrect user name or password.

At line:1 char:1

+ Connect-SrmServer -IgnoreCertificateErrors -Server protected.domain. ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Connect-SrmServer], VimException

    + FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VimAutomation.Srm.Commands.Commands.ConnectSrmServer

And even calling the api directly after logging into a SRM server directly:

PS> $global:DefaultSrmServers[1].ExtensionData.SrmLoginSites('DOMAIN\timkennedy','supersecretpassword','DOMAIN\timkennedy','supersecretpassword')

Exception calling "SrmLoginSites" with "4" argument(s): "Cannot complete login due to an incorrect user name or

password."

At line:1 char:1

+ $global:DefaultSrmServers[1].ExtensionData.SrmLoginSites('DOMAIN\timk ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException

    + FullyQualifiedErrorId : VimException

The same behavior is seen, even if I change the target server to be recovery.domain.com.

Without specifying any -Remote options, I can log into both SRM servers successfully using either username and password, or credential, however this prevents being able to do things like configure protection on an array based protection group, because the single session isn't authenticated to both SRM servers.

PS > Connect-SrmServer -Credential $cred -Server protected.domain.com

ServiceUri    : https://192.168.1.101:9086/vcdr/extapi/sdk

SessionSecret : "10334eb7e60c9bb1cb23c4fdce6a8c1c525423af"

User          : DOMAIN\timkennedy

IsConnected   : True

Port          : 9086

Version       : 6.1.0

Build         : 3037005

ProductLine   : srm

InstanceUuid  : 459474ca-50ad-41de-8d3f-a21cdbb0027c

RefCount      : 1

ExtensionData : VMware.VimAutomation.Srm.Views.SrmServiceInstance

Uid           : /SrmServer=domain\timkennedy@192.168.1.101:9086/

Id            : /SrmServer=domain\timkennedy@192.168.1.101:9086/

Name          : 192.168.1.101

IsInUse       : True

PS > Connect-SrmServer -Server recovery.domain.com -Username 'DOMAIN\timkennedy' -Password 'supersecretpassword'

ServiceUri    : https://172.16.1.101:9086/vcdr/extapi/sdk

SessionSecret : "e58247793dcda1e31182388d1856dd2be40457e7"

User          : DOMAIN\timkennedy

IsConnected   : True

Port          : 9086

Version       : 6.1.0

Build         : 3037005

ProductLine   : srm

InstanceUuid  : cf5269b3-237b-4d6a-b6a7-f5632e015c90

RefCount      : 1

ExtensionData : VMware.VimAutomation.Srm.Views.SrmServiceInstance

Uid           : /SrmServer=domain\timkennedy@172.16.1.101:9086/

Id            : /SrmServer=domain\timkennedy@172.16.1.101:9086/

Name          : 172.16.1.101

IsInUse       : True

I this scenario, if I configure a new protection group, via the api at $global:DefaultSrmServers[1].ExtensionData.Protection something like:

$pgroup = $srmapi.Protection.ListProtectionGroups()[-1]

$pspec = New-Object VMware.VimAutomation.Srm.Views.SrmProtectionGroupVmProtectionSpec

$pspec.Vm = (Get-Vm test-vm).ExtensionData.MoRef
$ptask = $pgroup.ProtectVms($pspec)

Here is the error:

PS > $ptask.GetResult().Error

Fault                  LocalizedMessage

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

VMware.Vim.MethodFault Not authenticated into SRM server 'Recovery'.

I should note, that logging in to the same vcenter server as the same user, and using the GUI to configure protection on the protection group does work.  So I'm not sure what I'm missing.

Greetings all!  Hoping for some guidance on this? We noticed "gaps" in our LogInsight data from our VCSA appliances and seems it has at-least something to do with which protocol we selected (TLS, TCP, UDP, RELP) in the VAMI setup.  Curious on which one (and port) we should be using to send syslog data from VCSA/PSCs to loginsight?  I understand, generically, the differences between TCP/TLS/UDP/RELP-- I'm just curious what folks are using when considering it's a fairly large environment (1000+ hosts)

Also, in digging in further, we see there's two different syslog options in vCenter itself.  Can someone tell us the difference?

Just curious what the difference here is and if both should be checked/enabled/true?

Thanks in advance!

Hi,

I am creating Automation scripts for our SRA. I am trying to do with Power CLI commands, using trying to manage SRM. Installed vCenter Power CLI 11.2. using powerCLI,

i am able to connect SRM servers, but discoverdevices() is failing. as per syntax arguments are not required. but the command failed as expecting some arguments.

below are process steps followed.

Appreciate your help to resolve

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

PS C:\Users\Administrator> Connect-VIServer -server xxxx1202.sss.ccc.com -username Administrator@vsphere.local -password xxxxxxxx12#

Name Port User ---- ---- ---- xxxx1202.sss.ccc.com 443 VSPHERE.LOCAL\Administrator

PS C:\Users\Administrator> $srmConn=Connect-SrmServer -user Administrator@vsphere.local -password xxxxxxxx12# -RemoteUser Administrator@vsphere.local -RemotePassword xxxxxxxx12# -IgnoreCertificateErrors

PS C:\Users\Administrator> $srmapi=$srmConn.ExtensionData

PS C:\Users\Administrator> $srmapi.Storage.DiscoverDevices()

Exception calling "DiscoverDevices" with "0" argument(s): "The request refers to an unexpected or unknown type."

At line:1 char:1 + $srmapi.Storage.DiscoverDevices() + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [], MethodInvocationException + FullyQualifiedErrorId : VimException

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

Thanks

Noorullah

Hi,

When we declare DR in SRM we understand that primary storage will not replicate data to secondary storage.

Question 1:

But in a NOT DR scenario, a synchronously synchronized storage, can I use the SRM (Test) option without having to disable storage synchronization?

Question 2:

I want to simulate a DR scenario in real practice.

Knowing this is not a true DR, as I will actually simulate the production VM shutdown before declaring DR in SRM, do I have to disable or pause synchronous synchronization?

Thank you.

Hi, I'm was wandering whether it is possible to enable a menu bar option that allows me to easily access running VM's rather than having to keep going back to the main Virtual Machine Library.

I've seen this on numerous videos but that has been using VMWare Workstation rather than Fusion

Virtual machines aren't shown in the dock along with other running applications, so if there was an option to access each VM from the main (top) menu bar or dock then that would be really useful

I'm currently running Mac OS X 10.14.6.

By the way I'm using VMWare Fusion 10.1.6 Professional

Thanks in advance

I need to install VMServer 2.02-293138 onto another Windows 7 64bit PC...I cannot get past the Error "Setup failed to generate the SSL keys necessary to run VMware Server" ... I do not even need/want the SSL connection to the management console...I only connect to the VMware Server console on the PC that is running the software.  I have tried the suggestions that i hove found doing Google searches including remove all files from Windows\Temp, verified that there were no other copies of openssl.exe on the PC, removed Windows Security Essentials, turned off the Windows Firewall for Private and Public, logging onto Windows as Administrator...

Are there any logs that can be examined to see why it is failing?

Can VMware Server be installed without needing the SSL key installed?

Hi,

I did the SRM training, but it does not show the configuration and failback steps.

I researched and found some blog and managed to do the setup.

However, I'm stuck in the step-by-step to make a correct failback in a (primary) drop-off scenario.

I simulated the (Vphere, Vcsa, Srm and Storage) shutdown of the primary site and run the recovery plan on the DR site successfully.

I noted: LUNS appear with a SNAP nomenclature, with says in training. But when I do the failback, it will be strange.

Now I want to connect the servers (Vphere, Vcsa, Srm and Storage) of the primary site again, to do the reprotection.

In this scenario I think it would be a basic procedure, the steps below:

1 - Remove (Rescan) Vsphere LUNs from the primary site;

2 - Remove VMs from Vsphere inventory;

3 - Failback of storage LUNs;

In SRM I would have to reconfigure the direction of (Save> Master).

But the plan is with DR running, can I use it by the protection group to enable reprotection?

Or is it better to create a new protection plan?

Thank you.

Is it a ok to have Multiple VM's with the same hard drive ID as the Host?  I have software that binds itself to the Host Hard Drive ID and want to utilize the same license on my VM's.

Hi,

I am trying the new app remote collector in vROps 7.5. Installation and connection to vCenter is fine. Unable to install CentOs7 agent or Windows 2016 agent from the remote agent console. Both have VM Tools 10.2 installed (replaced open source version on CentOS). Since they both failed i thought it was the old vCenter issue with symbols in passwd, so I changed linux root user to other passwd. Still fails. I get:

com.vmware.adapter3.applicationdiscovery.AppOSAdapter.logAdapterActionResult - [2019-04-17 13:07:37.417000 UTC]Task with operation install failed at 1555506457417 with reason Failed to connect to vCenter. Please check the credentials. Unable to acquire token

[654] 2019-04-17 15:07:57,322 ERROR [pool-1-thread-8] (74) com.vmware.adapter3.applicationdiscovery.actions.dispatch.UCPActionExecutor.checkActionStatus - Could not fetch auth token from UCP API. Unable to fetch the status from doc link. Hence trying from file...

Any ideas ? Anyone tried this yet?

We have a few hundred persistent full VMs in our Horizon View environment.  These are updated via SCCM as they are full persistent VMs.  Occasionally a few of them will get their updates, restart and then go agent unreachable.  The only way to get them back is to remove them from the desktop pool and re-add them to the pool then shut them down and let Horizon View configure them and then start them up.  Does anyone have any idea why this would happen?  Horizon View 7.8

Trying to update a physical 5.5 instance to VCSA 6.5 with the migration assistant and I'm receiving the following error:

Running Prechecks...

Prechecks reported the following errors/warnings:

Error: Unable to fetch or parse VC URL from vCenter ServiceInstance!

Resolution: VC URL in vCenter ServiceInstance is unreadable. The vCenter Service may not be reachable. Please contact customer support and submit

a support bundle.

Looking in the generated support bundle/logs I'm seeing the following (hostname's redacted):

2019-06-18T17:28:51.407Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.153Z INFOservice_manager Executing command '['%VMWARE_CIS_HOME%\\bin\\service-control.bat', '--list']'

2019-06-18T17:28:51.407Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.177Z WARNING transport.localBAD REQUEST: Cannot execute ['%VMWARE_CIS_HOME%\\bin\\service-control.bat', '--list']. Error: [Error 2] The system cannot find the file specified

2019-06-18T17:28:51.407Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.177Z ERROR service_manager VMware services could not be extracted as the service-control is not present.

2019-06-18T17:28:51.408Z INFO upgrade.states.component_states vco:CollectRequirements: Traceback (most recent call last):

2019-06-18T17:28:51.408Z INFO upgrade.states.component_states vco:CollectRequirements:   File "C:\migFAB6.tmp\PFiles\VMware\CIS\cis_upgrade_runner\libs\sdk\service_manager.py", line 500, in _getVMwareServices

2019-06-18T17:28:51.408Z INFO upgrade.states.component_states vco:CollectRequirements:     result = _execCommand(compAssist, command)

2019-06-18T17:28:51.410Z INFO upgrade.states.component_states vco:CollectRequirements:   File "C:\migFAB6.tmp\PFiles\VMware\CIS\cis_upgrade_runner\libs\sdk\service_manager.py", line 451, in _execCommand

2019-06-18T17:28:51.410Z INFO upgrade.states.component_states vco:CollectRequirements:     localStderr=stderrFilename)

2019-06-18T17:28:51.411Z INFO upgrade.states.component_states vco:CollectRequirements:   File "C:\migFAB6.tmp\PFiles\VMware\CIS\cis_upgrade_runner\libs\sdk\component_assistant.py", line 299, in execCommand

2019-06-18T17:28:51.411Z INFO upgrade.states.component_states vco:CollectRequirements:     raise _convertToComponentAssistantError(e)

2019-06-18T17:28:51.411Z INFO upgrade.states.component_states vco:CollectRequirements: ComponentAssistantError

2019-06-18T17:28:51.411Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.213Z INFO __main__ Context file C:\migFAB6.tmp\PFiles\VMware\CIS\cis_upgrade_runner\upgrade_working_directory\system-data\upgrade-com.vmware.vco-upgradeContext does not exist. Use default context

2019-06-18T17:28:51.411Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.214Z INFO extensions Found upgrade phase <module 'vco' from 'C:\migFAB6.tmp\PFiles\VMware\CIS\cis_upgrade_runner\payload\component-scripts\vco\__init__.py'>:CollectRequirements'

2019-06-18T17:28:51.413Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.214Z INFO extensions Executing upgrade phase '<module 'vco' from 'C:\migFAB6.tmp\PFiles\VMware\CIS\cis_upgrade_runner\payload\component-scripts\vco\__init__.py'>:CollectRequirements' with context {u'resourceDir': u'C:\\migFAB6.tmp\\PFiles\\VMware\\CIS\\cis_upgrade_runner\\upgrade_working_directory', u'sourceSsoPassword': 'CENSORED', u'locale': u'en', u'destinationPlatform': u'Linux', u'destinationVcVersion': u'6.1', u'systemExportDir': u'C:\\migFAB6.tmp\\PFiles\\VMware\\CIS\\cis_upgrade_runner\\upgrade_working_directory\\system-data', u'sourcePlatform': u'Windows', 'logDir': u'C:\\Users\\DHancock\\AppData\\Local\\Temp\\vcsMigration', u'sourceVcVersion': u'5.5', u'sourceSsoVersion': u'5.5', u'vcdb.migrateSet': u'all', u'destinationSsoVersion': u'6.1', u'sourceSsoUsername': None}.

2019-06-18T17:28:51.413Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.216Z INFO vco Source vCO found at C:\Program Files\VMware\Infrastructure\Orchestrator with version 5.5.3.2945834

2019-06-18T17:28:51.414Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.216Z INFO vco Collect size of installed plugins in C:\Program Files\VMware\Infrastructure\Orchestrator\app-server\plugins

2019-06-18T17:28:51.414Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.219Z INFO vco o11nplugin-ad.dar: 396.49 KB

2019-06-18T17:28:51.414Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.219Z INFO vco o11nplugin-amqp.dar: 4097.81 KB

2019-06-18T17:28:51.414Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.220Z INFO vco o11nplugin-configurator.dar: 4318.07 KB

2019-06-18T17:28:51.414Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.220Z INFO vco o11nplugin-database.dar: 588.46 KB

2019-06-18T17:28:51.415Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.220Z INFO vco o11nplugin-dynamictypes.dar: 136.82 KB

2019-06-18T17:28:51.415Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.220Z INFO vco o11nplugin-enums.dar: 8.11 KB

2019-06-18T17:28:51.417Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.220Z INFO vco o11nplugin-jakartacommonsnet.dar: 267.87 KB

2019-06-18T17:28:51.417Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.220Z INFO vco o11nplugin-library.dar: 1945.06 KB

2019-06-18T17:28:51.417Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.220Z INFO vco o11nplugin-mail.dar: 1147.94 KB

2019-06-18T17:28:51.417Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.220Z INFO vco o11nplugin-multi-node.dar: 4412.77 KB

2019-06-18T17:28:51.417Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.220Z INFO vco o11nplugin-powershell.dar: 2727.74 KB

2019-06-18T17:28:51.418Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.221Z INFO vco o11nplugin-rest.dar: 20370.95 KB

2019-06-18T17:28:51.418Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.221Z INFO vco o11nplugin-snmp.dar: 4571.71 KB

2019-06-18T17:28:51.418Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.221Z INFO vco o11nplugin-soap.dar: 7837.48 KB

2019-06-18T17:28:51.420Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.221Z INFO vco o11nplugin-ssh.dar: 12283.87 KB

2019-06-18T17:28:51.420Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.221Z INFO vco o11nplugin-vsphere.dar: 34195.58 KB

2019-06-18T17:28:51.420Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.223Z INFO vco o11nplugin-weboperator.dar: 106.01 KB

2019-06-18T17:28:51.420Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.223Z INFO vco o11nplugin-wfdocs.dar: 1994.46 KB

2019-06-18T17:28:51.420Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.223Z INFO vco o11nplugin-xml.dar: 34.94 KB

2019-06-18T17:28:51.421Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.223Z INFO vco Total size of the installed plugins 99.06 MB

2019-06-18T17:28:51.421Z INFO upgrade.states.component_states vco:CollectRequirements: 2019-06-18T17:28:49.223Z INFO extensions The component script returned '<component_requirements.UpgradeRequirementsSpec object at 0x0000000003250588>'

2019-06-18T17:28:51.421Z INFO upgrade.states.component_states vco:CollectRequirements: Script completed for 3.41899991035 secs with return-code='0', and executionId=8510fa35-99ef-490b-8c5a-aa66ce2340c6

2019-06-18T17:28:51.426Z INFO upgrade.states.component_states vco:CollectRequirements: Remote Command Returned: <component_requirements.UpgradeRequirementsSpec object at 0x000000000816A710>

2019-06-18T17:28:51.426Z INFO upgrade.states.component_states vco:CollectRequirements: Completed successfully.

2019-06-18T17:28:51.447Z INFO wf.wf_processor State CollectRequirements com.vmware.vco has succeeded.

2019-06-18T17:28:51.453Z INFO upgrade.states.component_states vpxd:CollectRequirements:

2019-06-18T17:28:51.453Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:49.244Z INFO __main__ Context file C:\migFAB6.tmp\PFiles\VMware\CIS\cis_upgrade_runner\upgrade_working_directory\system-data\upgrade-com.vmware.vpxd-upgradeContext does not exist. Use default context

2019-06-18T17:28:51.453Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:49.244Z INFO extensions Found upgrade phase <module 'vpxd' from 'C:\migFAB6.tmp\PFiles\VMware\CIS\cis_upgrade_runner\payload\component-scripts\vpxd\__init__.py'>:CollectRequirements'

2019-06-18T17:28:51.454Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:49.246Z INFO extensions Executing upgrade phase '<module 'vpxd' from 'C:\migFAB6.tmp\PFiles\VMware\CIS\cis_upgrade_runner\payload\component-scripts\vpxd\__init__.py'>:CollectRequirements' with context {u'resourceDir': u'C:\\migFAB6.tmp\\PFiles\\VMware\\CIS\\cis_upgrade_runner\\upgrade_working_directory', u'sourceSsoPassword': 'CENSORED', u'locale': u'en', u'destinationPlatform': u'Linux', u'destinationVcVersion': u'6.1', u'systemExportDir': u'C:\\migFAB6.tmp\\PFiles\\VMware\\CIS\\cis_upgrade_runner\\upgrade_working_directory\\system-data', u'sourcePlatform': u'Windows', 'logDir': u'C:\\Users\\DHancock\\AppData\\Local\\Temp\\vcsMigration', u'sourceVcVersion': u'5.5', u'sourceSsoVersion': u'5.5', u'vcdb.migrateSet': u'all', u'destinationSsoVersion': u'6.1', u'sourceSsoUsername': None}.

2019-06-18T17:28:51.454Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.372Z INFO vpxd_export Got 'Version' Value: 3

2019-06-18T17:28:51.456Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.378Z INFO vpxd_export Got 'Issuer' Value: O=VMware, Inc., OU=VMware, Inc., CN=vcenter.domain.local/emailAddress=support@vmware.com

2019-06-18T17:28:51.456Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.378Z INFO vpxd_export Got 'Not After' Value: Apr  7 20:29:45 2022 GMT

2019-06-18T17:28:51.457Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.378Z INFO vpxd_export Got 'Subject' Value: O=VMware, Inc., OU=VMware, Inc., CN=vcenter.domain.local/emailAddress=support@vmware.com

2019-06-18T17:28:51.457Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.378Z INFO vpxd_export Got 'Public Key' Value: 2048

2019-06-18T17:28:51.457Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.378Z INFO vpxd_export Got 'CA' Value: FALSE

2019-06-18T17:28:51.457Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.378Z INFO vpxd_export Patched End Date: Apr 07 20:29:45 2022 GMT

2019-06-18T17:28:51.457Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.380Z INFO vpxd_export Returning Cert X509 version is not 3 - False for version 3

2019-06-18T17:28:51.459Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.380Z INFO vpxd_export Need to Preserve CACert - False

2019-06-18T17:28:51.459Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.380Z INFO vpxd_export Returning Cert is Self Signed: True for Issuer O=VMware, Inc., OU=VMware, Inc., CN=vcenter.domain.local/emailAddress=support@vmware.com and Subject O=VMware, Inc., OU=VMware, Inc., CN=vcenter.domain.local/emailAddress=support@vmware.com and CA - false

2019-06-18T17:28:51.460Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.417Z INFO vpxd_export Returning Cert Expired False for End Date: Apr 07 20:29:45 2022 GMT

2019-06-18T17:28:51.460Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.417Z INFO vpxd_export Returning Cert Key length not 2048 False with key length: 2048

2019-06-18T17:28:51.460Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.417Z INFO vpxd_export Got 'CN' Value: vcenter.domain.local

2019-06-18T17:28:51.460Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.417Z INFO vpxd_export Got Subject CN vcenter.domain.local

2019-06-18T17:28:51.460Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.502Z INFO vpxd_export Subject CN vcenter.domain.local is a valid DNS entry with IP  

2019-06-18T17:28:51.460Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.503Z INFO vpxd_export Got 'Subject Alternative Name' Value:

2019-06-18T17:28:51.460Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.503Z INFO vpxd_export Got Line 'DNS:vcenter.domain.local'

2019-06-18T17:28:51.461Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.503Z INFO vpxd_export Got 'DNS' Value: vcenter.domain.local

2019-06-18T17:28:51.461Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.503Z INFO vpxd_export Returning Cert Host DNS: vcenter.domain.local

2019-06-18T17:28:51.463Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.503Z INFO vpxd_export Cert has no Host IPv4 entries

2019-06-18T17:28:51.463Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.503Z WARNING vpxd_export VPXD Certificate is invalid and will be replaced.

2019-06-18T17:28:51.463Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.503Z WARNING vpxd_export Certificate Req Mismatch Errors or Warnings present.

2019-06-18T17:28:51.463Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.503Z INFO vpxd_export Heartbeat port from registry is 902

2019-06-18T17:28:51.464Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.503Z INFO vpxd_export Http and Https port from registry are 80, 443

2019-06-18T17:28:51.464Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.503Z INFO vpxd_export Found SDK Node with port 8085

2019-06-18T17:28:51.464Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.503Z INFO vpxd_export Found SDKTunnel Node with port 8089

2019-06-18T17:28:51.466Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.505Z INFO vpxd_export VPXD Source ports are: ['8085', '8089', u'80', u'443', '389', '636', u'902']

2019-06-18T17:28:51.466Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.505Z INFO vpxd_export VPXD Destination Ports are: ['8085', '8089', u'80', u'443'], 902

2019-06-18T17:28:51.467Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.505Z INFO vpxd_export SSO Admin Uri: https://vcenter.domain.local:7444/sso-adminserver/sdk/vsphere.local

2019-06-18T17:28:51.467Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.505Z INFO vpxd_export SSO Extra Arguments are {'vpxd.sso.port': '7444', 'vpxd.sso.host': 'vcenter.domain.local', 'vpxd.sso.admin.url': 'https://vcenter.domain.local:7444/sso-adminserver/sdk/vsphere.local', 'vpxd.sso.sts.url': 'https://vcenter.domain.local:7444/sts/STSService/vsphere.local', 'vpxd.sso.group.url': 'https://vcenter.domain.local:7444/sso-adminserver/sdk/vsphere.local'}

2019-06-18T17:28:51.467Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.506Z INFO vpxd_export Using 5.5.0.15337 WebClient registry path

2019-06-18T17:28:51.467Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.506Z INFO vpxd_export WebClient Https port from registry: 9443

2019-06-18T17:28:51.467Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.506Z INFO vpxd_export Using 5.5 WebClient config path

2019-06-18T17:28:51.469Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.506Z INFO vpxd_export Using WebClient config path C:\Program Files\VMware\Infrastructure\vSphereWebClient\server\configuration\tomcat-server.xml

2019-06-18T17:28:51.469Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.506Z INFO vpxd_export WebClient Https port from config file: 9443

2019-06-18T17:28:51.470Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.506Z INFO vpxd_export Webclient Https port: 9443

2019-06-18T17:28:51.470Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.506Z INFO vpxd_export WebClient Source ports are: [u'9443']

2019-06-18T17:28:51.470Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.509Z INFO vc_connector Proxy http port is configured to: 80

2019-06-18T17:28:51.470Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.509Z INFO vc_connector Proxy https port is configured to: 443

2019-06-18T17:28:51.470Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.940Z ERROR vpxd_export Exception: 302 Moved Temporarily. Unable to fetch or parse VCenter URL from Services List.

2019-06-18T17:28:51.471Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.940Z ERROR vpxd_export VC Hostname Req Mismatch Error Spec present.

2019-06-18T17:28:51.471Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.941Z INFO vc_connector Proxy http port is configured to: 80

2019-06-18T17:28:51.473Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:50.941Z INFO vc_connector Proxy https port is configured to: 443

2019-06-18T17:28:51.473Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:51.371Z ERROR vpxd_export Exception 302 Moved Temporarily getting Extension information

2019-06-18T17:28:51.473Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:51.371Z INFO vpxd_export No external extensions found.

2019-06-18T17:28:51.473Z INFO upgrade.states.component_states vpxd:CollectRequirements: 2019-06-18T17:28:51.371Z INFO vpxd_export Checking for Host Profiles.

HTTP/HTTPS proxy ports are default 80/443 and the web client is reachable @ https://vcenter.domain.local:9443/vpshere-webclient/. I can hit the above listed ports locally (127.0.0.1) and the network IP with no issues and firewall has been disabled. Not sure where the 'vpxd_export Exception 302 Moved ..." error is coming from.

Trying to understand the error(s) and how to resolve this issue. Any insight would be greatly appreciated!

Recently replaced my smart card with a NIST SP 800-73 smart card. The new card reads on the host, but times out in my Windows 10 VM guest. I am using VMware Workstation 15.1.0 build-13591040.

I've tried forcing passthrough with the following 2 ilnes in my vmx file, but the smart card still times out:

usb.generic.allowCCID = "TRUE"

usb.ccid.disable = "TRUE"

The reader is recognized in the vmware.log as:

vmx| I125: USB: Found device [name:Realtek\ USB2.0-CRW vid:0bda pid:0169 path:1/0/0/12 speed:high family:storage,storage-bulk,smart-card virtPath:ehci:0 instanceId:USB\\VID_0BDA&PID_0169\\20070818000000000 serialnum:20070818000000000 arbRuntimeKey:15 ownerdisplay:Windows\ 10\ Pro version:3], connected to ehci port 0.

The Windows drivers for both the reader and the card are the same in the host and guest, but Windows event viewer shows the following errors when reading the card in the vm:

Error WudfUsbccidDrv Event ID 1

A Request has returned failure.

MsgType: 0x80

ICCStatus: 0x0

CmdStatus: 0x1

Error: 0xFE

SW1: 0x0

SW2: 0x0

Error WudfUsbccidDrv Event ID 11

An operation has failed (0x3, 0x3, 0x40, 0xFE).

ScCardPowerColdReset: IccPowerOnStatusError

HResult: {Device Timeout}

The specified I/O operation on %hs was not completed before the time-out period expired.

Any ideas for troubleshooting?

Guest identifies both reader and smart card

Hi,

Do I need license for VMware Identity Manager. The aim for using VIDM is RBAC for NSX-T ?

I have esxi 6.7 running on HPE blades. /var is full. I found 2 log files, /var/log/tallylog (32064) and /var/run/SDRR_LOCAL (16384) bytes in size of the total 49152byte size of /var. Which are these are safe to zero out (cat /dev/null > tallylog, and SDRR_LOCAL) during running?

Author : jacquiew

URL : http:////docs.vmware.com/en/VMware-Horizon-Client-for-Windows/4.10/horizon-client-windows-user/GUID-427B0E44-2089-426D-84A1-AD0181D997D1.html

Topic Name : VMware Horizon Client for Windows User Guide

Publication Name : VMware Horizon Client for Windows User Guide

Product/Version : VMware Horizon Client for Windows/4.10

Question :

I'm trying to download and install VMware Horizon Client - 5.1.0 - build 14045148. It clocks for a few minutes and then displays message "Download VMware Horizon Client failed. When I try to connect to my workstation without this update, I can log in, then the connection closes right away.

ESXi 6.7.0u2 crashes with the following pink screen. Started after the upgrade from 6.5 to 6.7u2.

Is this a known issue or someone here with PowerEdge R630 experiencing this?

What are the official limitations including commercial use for the free ESXi Hypervisor?

I'm developing a custom workflows for creating Services and Services group in one or more NSX because workflows for this are missing in the NSX plugin and I had to use HTTP-REST plugin.

What I achieved at the moment is:

• Create a Service
• Create a Service group

Now I want to add Services to a Service Group, so I need to call another REST Operation, and I would like to populate the input form elements with the already existing services and service groups, in this way I can show to the user a dual list element where the user can select the services from.

I'm not able to find a specific documentation for this as the docs found in VMWare portal are just showing very basic stuff.

Is it possible to populate form element values with the result of a REST call?

Thanks in advance.

I installed a windows server 2016 on ESXi 6.7U2 using most of the defaults, including Secure boot with the intention of installing View Composer 7.9.  In order to complete the install I had to turn off Secure Boot, install and then turn it back on.  during a composer operation, I get Disk Fault errors.  After looking at the UFA log and seeing issues with the creation of the disk, spindle.... I made a guess that it was related to secure boot.  Turned it off on the composer server and everything works properly.