I had this problem, using Firefox instead of chrome and emptying the cache fixed the problem for me.
Hope it helps
↧
Re: vRO 8.0 Error
↧
Re: errore "Permission to perform this operation was denied"
devi fornire maggiori dettagli sulla tua situazione
qual è il tuo sistema operativo fisico del server?
Il tuo account ha i privilegi di amministratore?
qual è il tuo sistema operativo fisico del server?
Il tuo account ha i privilegi di amministratore?
↧
↧
Re: The Connection to the remote computer ended in Horizon 7
Do you have network access to your assigned Desktop (VM) when you face this error?
what is the status of that VM when it's happened? I mean, is that VM up and run? and can you reconnect to the VM again or not?
You must check the Horizon event logs for more details ...
↧
Re: vCenter registration of the VASA provider failed.
Добрый день, Finikiez
Да, версия плагина имеет совместимость с данной версией vc. Плагин появляется в списке, и часть его работает, то есть саму железку он видит, видит виртуальные машины на нем. Но вот vasa провайдер, так и не хочет регистрироваться, вываливая данное сообщение.
В sps.log записи такого типа, при попытке регистрации плагина:
2019-12-26T16:59:40.963+03:00 [Timer-0] DEBUG opId= com.vmware.vim.sms.health.ServiceHealthPoller - Verifying connectivity with dependent services...
2019-12-26T16:59:40.963+03:00 [Timer-0] DEBUG opId= com.vmware.vim.sms.health.ServiceHealthPoller - Checking VPXD connectivity...
2019-12-26T16:59:41.020+03:00 [Timer-0] INFO opId= com.vmware.vim.storage.common.util.VpxdSSOConnection - Verified that vCenter session is active.
2019-12-26T16:59:41.020+03:00 [Timer-0] DEBUG opId= com.vmware.vim.sms.health.ServiceHealthPoller - VPXD connectivity succeeded!
2019-12-26T16:59:41.020+03:00 [Timer-0] DEBUG opId= com.vmware.vim.sms.health.ServiceHealthPoller - Checking Inventory Service connectivity...
2019-12-26T16:59:41.022+03:00 [Timer-0] DEBUG opId= com.vmware.vim.sms.health.ServiceHealthPoller - Inventory Service connectivity succeeded!
2019-12-26T16:59:41.022+03:00 [Timer-0] DEBUG opId= com.vmware.vim.sms.health.ServiceHealthPoller - Checking VMCA connectivity...
2019-12-26T16:59:41.211+03:00 [Timer-0] DEBUG opId= com.vmware.vim.sms.health.ServiceHealthPoller - VMCA connectivity succeeded!
2019-12-26T16:59:41.211+03:00 [Timer-0] DEBUG opId= com.vmware.vim.sms.health.ServiceHealthPoller - Connectivity with dependent services succeeded!
2019-12-26T16:59:46.298+03:00 [pool-29-thread-4] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session with privilege: StorageViews.ConfigureService
2019-12-26T16:59:46.299+03:00 [pool-29-thread-4] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Found session cookie in request context
2019-12-26T16:59:46.299+03:00 [pool-29-thread-4] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session using session cookie...
2019-12-26T16:59:46.299+03:00 [pool-29-thread-4] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Roles found, not expired.
2019-12-26T16:59:46.299+03:00 [pool-29-thread-4] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Retrieved roles count for user: 1
2019-12-26T16:59:46.299+03:00 [pool-29-thread-4] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Verified privilege: StorageViews.ConfigureService for roleId: -1
2019-12-26T16:59:46.299+03:00 [pool-29-thread-4] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session successfully
2019-12-26T16:59:46.299+03:00 [pool-27-thread-4] DEBUG opId=25bbc20d-8131-4101-a4d5-d7f20e770c08 com.vmware.vim.sms.StorageManagerImpl - Received API Call: registerProvider
2019-12-26T16:59:46.299+03:00 [pool-27-thread-4] DEBUG opId=25bbc20d-8131-4101-a4d5-d7f20e770c08 com.vmware.vim.storage.common.util.SimpleTimeCounter - TIMER STARTED: Task for registerProviderInt
2019-12-26T16:59:46.299+03:00 [pool-27-thread-4] DEBUG opId=25bbc20d-8131-4101-a4d5-d7f20e770c08 com.vmware.vim.sms.task.TaskImpl - Created a task - ManagedObjectReference: type = SmsTask, value = SmsTask-14, serverGuid = eb098996-1af9-4799-8865-9316bd297fa1
2019-12-26T16:59:46.299+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.provider.ProviderFactory - [createVasaProvider] Creating VASA provider with the spec : username - administrator URL - https://192.168.121.126:9083/version.xml certificate - MIIDPTCCAiWgAwIBAgIEX/0AhjANBgkqhkiG9w0BAQsFADAVMRMwEQYDVQQDDApVbmlmaWVkVlND
MB4XDTE5MTIyNTE1MzkzOVoXDTI5MTIyMjE1MzkzOVowFTETMBEGA1UEAwwKVW5pZmllZFZTQzCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKsckWZk0Oul7lp3128k5f7bVcNAo7yGGh1d
7VGE+HF5vUgnS63PI9P92Jq7Q/13s/8CLtObibAgLLAaYo00zToLNBhajL2KJGGfehQ+bUSp9eS7
a9sMuhygJlSJOpDA4vMId7CUFT0P3wiB3swbrCdAITqucbzSEF4CerJ+8BmG29TDvLKCbXplwMAg
XZKTxMGAfRx+SekPh0J8nFGMJbYDZB8nGRga0/YnoYSLHBVJGt8VZP94bjdjUirq4cqpkBDeXg5C
2Cl6IuuybQywwb0ZavggJZQJqrMeZ1iXPexq7PSvadx+jxRd4LhTdjj61/7ocDoGc6PxETrGyNOr
Zi8CAwEAAaOBlDCBkTAdBgNVHQ4EFgQUs7RbtKWqm6w8EJbL4zkGmYHv+RYwHwYDVR0jBBgwFoAU
s7RbtKWqm6w8EJbL4zkGmYHv+RYwDAYDVR0TAQH/BAIwADAOBgNVHQ8BAf8EBAMCBaAwEgYDVR0R
AQH/BAgwBocEwKh5fjAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwDQYJKoZIhvcNAQEL
BQADggEBAJwNNXKdrffod6qXGdfMgz0zm9bcVy7JAVzAwLg9XqOszmSAf1vK6+TZLR/rHwkRPOeu
aJFeOR0/alDWkRQylWyPglX3Qs5kCzoWjfD3Zc2mWziWvUQbEvIOIwvt3Iw4qvak9t0h6LZNLOme
Dgg6dCp05TA0NPCgvg6VwLQGbzvkPR+vYIS8TYh+oE/FekqShtoVhN0BpBK3xdvJhT/RvSfOYByk
oFj/A8Oa9fCrrzIPnqh+4fqSnkaRZ/ufiY9mqOPVxGJ5PJ5VxouBx973ddRoK6kOI1TDdriJOl0X
QKC+5DG40PQ1PBO8KP3+Sg9rCYCiQ+yVo9/VVmve7pyEd3s=
2019-12-26T16:59:46.299+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.provider.ProviderFactory - Validating Provider Spec...
2019-12-26T16:59:46.299+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.provider.ProviderFactory - Validating the provider URL - https://192.168.121.126:9083/version.xml
2019-12-26T16:59:46.310+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.provider.ProviderFactory - provider URL is valid
2019-12-26T16:59:46.311+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.provider.vasa.cert.CertificateManagerImpl - Validating provider certificate
2019-12-26T16:59:46.331+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.provider.vasa.cert.CertificateStore - [addCertificate] Added certificate corresponding to provider URL - https://192.168.121.126:9083/version.xml to sms truststore!
2019-12-26T16:59:46.410+03:00 [pool-29-thread-5] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session with privilege: StorageViews.View
2019-12-26T16:59:46.410+03:00 [pool-29-thread-5] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Found session cookie in request context
2019-12-26T16:59:46.411+03:00 [pool-29-thread-5] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session using session cookie...
2019-12-26T16:59:46.412+03:00 [pool-29-thread-5] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Roles found, not expired.
2019-12-26T16:59:46.412+03:00 [pool-29-thread-5] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Retrieved roles count for user: 1
2019-12-26T16:59:46.412+03:00 [pool-29-thread-5] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Verified privilege: StorageViews.View for roleId: -1
2019-12-26T16:59:46.412+03:00 [pool-29-thread-5] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session successfully
2019-12-26T16:59:46.412+03:00 [pool-27-thread-5] DEBUG opId=ce9559ea-a934-420c-99aa-f9ea1a6e1682 com.vmware.vim.sms.task.TaskImpl - Received API call : queryInfo for task - ManagedObjectReference: type = SmsTask, value = SmsTask-14, serverGuid = eb098996-1af9-4799-8865-9316bd297fa1
2019-12-26T16:59:46.467+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.provider.vasa.cert.CertificateManagerImpl - [trustProviderCertificate] cert for URL - https://192.168.121.126:9083/version.xml is trusted!
2019-12-26T16:59:46.467+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.provider.vasa.VersionHandler - [retrieveProviderVersionInfo] For provider URL - https://192.168.121.126:9083/version.xml
2019-12-26T16:59:46.468+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.provider.vasa.VasaProviderUtils - [createConnection] Using AcceptAllHostnameVerifier...
2019-12-26T16:59:46.501+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.provider.vasa.VersionHandler - [logVersionInfo] VersionInfo for provider with url - https://192.168.121.126:9083/version.xml , maxCommonVASAVersionSupported - version3 , providerServiceLocation - https://192.168.121.126:9083/services/vasa_2_0
2019-12-26T16:59:46.501+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.provider.ProviderFactory - [constructVasaProvider] Constructing VASA provider. Version - version3 incoming providerMoId - null
2019-12-26T16:59:46.501+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.provider.ProviderFactory - [constructVasaProvider] Assigned providerMoId - vasaProvider-9
2019-12-26T16:59:46.501+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.provider.vasa.VasaProviderImpl - [initServices] Initializing services for provider with url -https://192.168.121.126:9083/version.xml
2019-12-26T16:59:46.501+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.storage.common.util.SimpleTimeCounter - TIMER STARTED: VasaClientImpl : Constructor
2019-12-26T16:59:46.518+03:00 [pool-29-thread-6] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session with privilege: StorageViews.View
2019-12-26T16:59:46.518+03:00 [pool-29-thread-6] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Found session cookie in request context
2019-12-26T16:59:46.518+03:00 [pool-29-thread-6] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session using session cookie...
2019-12-26T16:59:46.518+03:00 [pool-29-thread-6] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Roles found, not expired.
2019-12-26T16:59:46.518+03:00 [pool-29-thread-6] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Retrieved roles count for user: 1
2019-12-26T16:59:46.518+03:00 [pool-29-thread-6] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Verified privilege: StorageViews.View for roleId: -1
2019-12-26T16:59:46.518+03:00 [pool-29-thread-6] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session successfully
2019-12-26T16:59:46.519+03:00 [pool-27-thread-6] DEBUG opId=cad80af6-4b52-4933-82e5-200f2ecb312d com.vmware.vim.sms.task.TaskImpl - Received API call : queryInfo for task - ManagedObjectReference: type = SmsTask, value = SmsTask-14, serverGuid = eb098996-1af9-4799-8865-9316bd297fa1
2019-12-26T16:59:46.526+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.storage.common.util.SimpleTimeCounter - TIMER STOPPED: VasaClientImpl : Constructor
2019-12-26T16:59:46.526+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.storage.common.util.SimpleTimeCounter - TIME TAKEN: VasaClientImpl : Constructor: 0.025
2019-12-26T16:59:46.526+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.provider.vasa.VvolProviderImpl - [queryVasaProviderInfo] Invoking registerCACertificatesAndCRLs API on the provider to get VasaProviderInfo for provider -https://192.168.121.126:9083/version.xml
2019-12-26T16:59:46.527+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.provider.vasa.cert.CertificateAuthority - [getRootCert] Querying VECS for root certificates...
2019-12-26T16:59:46.587+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.storage.common.util.SimpleTimeCounter - TIMER STARTED: VasaClientImpl : registerCACertificatesAndCRLs
2019-12-26T16:59:46.627+03:00 [pool-29-thread-7] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session with privilege: StorageViews.View
2019-12-26T16:59:46.627+03:00 [pool-29-thread-7] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Found session cookie in request context
2019-12-26T16:59:46.627+03:00 [pool-29-thread-7] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session using session cookie...
2019-12-26T16:59:46.627+03:00 [pool-29-thread-7] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Roles found, not expired.
2019-12-26T16:59:46.628+03:00 [pool-29-thread-7] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Retrieved roles count for user: 1
2019-12-26T16:59:46.628+03:00 [pool-29-thread-7] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Verified privilege: StorageViews.View for roleId: -1
2019-12-26T16:59:46.628+03:00 [pool-29-thread-7] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session successfully
2019-12-26T16:59:46.628+03:00 [pool-27-thread-7] DEBUG opId=e04dd918-389a-48c7-8975-ca5a08cbe205 com.vmware.vim.sms.task.TaskImpl - Received API call : queryInfo for task - ManagedObjectReference: type = SmsTask, value = SmsTask-14, serverGuid = eb098996-1af9-4799-8865-9316bd297fa1
2019-12-26T16:59:46.740+03:00 [pool-29-thread-8] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session with privilege: StorageViews.View
2019-12-26T16:59:46.740+03:00 [pool-29-thread-8] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Found session cookie in request context
2019-12-26T16:59:46.740+03:00 [pool-29-thread-8] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session using session cookie...
2019-12-26T16:59:46.740+03:00 [pool-29-thread-8] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Roles found, not expired.
2019-12-26T16:59:46.740+03:00 [pool-29-thread-8] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Retrieved roles count for user: 1
2019-12-26T16:59:46.740+03:00 [pool-29-thread-8] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Verified privilege: StorageViews.View for roleId: -1
2019-12-26T16:59:46.740+03:00 [pool-29-thread-8] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session successfully
2019-12-26T16:59:46.740+03:00 [pool-27-thread-8] DEBUG opId=ec4a415d-9af2-4a29-9909-5aa4d2347446 com.vmware.vim.sms.task.TaskImpl - Received API call : queryInfo for task - ManagedObjectReference: type = SmsTask, value = SmsTask-14, serverGuid = eb098996-1af9-4799-8865-9316bd297fa1
2019-12-26T16:59:46.760+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.storage.common.util.SimpleTimeCounter - TIMER STOPPED: VasaClientImpl : registerCACertificatesAndCRLs
2019-12-26T16:59:46.760+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.storage.common.util.SimpleTimeCounter - TIME TAKEN: VasaClientImpl : registerCACertificatesAndCRLs: 0.173
2019-12-26T16:59:46.760+03:00 [pool-14-thread-1] ERROR opId= com.vmware.vim.sms.provider.vasa.VvolProviderImpl - Error in queryVasaProviderInfo
com.vmware.vim.vasa.InvalidCertificate: InvalidCertificate
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at java.lang.Class.newInstance(Class.java:383)
at com.vmware.vim.vasa.VasaServiceStub.registerCACertificatesAndCRLs(Unknown Source)
at com.vmware.vim.sms.client.stub.VasaServiceStubImpl.registerCACertificatesAndCRLs(VasaServiceStubImpl.java:226)
at com.vmware.vim.sms.client.VasaClientImpl.registerCACertificatesAndCRLs(VasaClientImpl.java:728)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.vmware.vim.sms.client.VasaClientHandler.invokeMethod(VasaClientHandler.java:79)
at com.vmware.vim.sms.client.VasaClientHandler.invoke(VasaClientHandler.java:70)
at com.sun.proxy.$Proxy99.registerCACertificatesAndCRLs(Unknown Source)
at com.vmware.vim.sms.provider.vasa.VvolProviderImpl.queryVasaProviderInfo(VvolProviderImpl.java:486)
at com.vmware.vim.sms.provider.vasa.VasaProviderImpl.init(VasaProviderImpl.java:1042)
at com.vmware.vim.sms.provider.ProviderFactory.createVasaProvider(ProviderFactory.java:187)
at com.vmware.vim.sms.provider.ProviderFactory.createProvider(ProviderFactory.java:132)
at com.vmware.vim.sms.StorageManagerImpl.registerProviderInt(StorageManagerImpl.java:454)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.vmware.vim.sms.task.JobHandler.run(JobHandler.java:70)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
at java.lang.Thread.run(Thread.java:745)
2019-12-26T16:59:46.760+03:00 [pool-14-thread-1] ERROR opId= com.vmware.vim.sms.provider.vasa.VasaProviderImpl - [init] Provider creation failed
(vmodl.fault.InvalidArgument) {
faultCause = null,
faultMessage = null,
invalidProperty = certificate
}
at com.vmware.vim.sms.provider.vasa.VvolProviderImpl.queryVasaProviderInfo(VvolProviderImpl.java:497)
at com.vmware.vim.sms.provider.vasa.VasaProviderImpl.init(VasaProviderImpl.java:1042)
at com.vmware.vim.sms.provider.ProviderFactory.createVasaProvider(ProviderFactory.java:187)
at com.vmware.vim.sms.provider.ProviderFactory.createProvider(ProviderFactory.java:132)
at com.vmware.vim.sms.StorageManagerImpl.registerProviderInt(StorageManagerImpl.java:454)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.vmware.vim.sms.task.JobHandler.run(JobHandler.java:70)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
at java.lang.Thread.run(Thread.java:745)
2019-12-26T16:59:46.761+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.provider.vasa.VasaProviderImpl - [rollbackRegistration] Rolling back for provider with url: https://192.168.121.126:9083/version.xml
2019-12-26T16:59:46.761+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.provider.vasa.VasaProviderImpl - Removing Provider Cert from truststore...
2019-12-26T16:59:46.852+03:00 [pool-29-thread-9] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session with privilege: StorageViews.View
2019-12-26T16:59:46.852+03:00 [pool-29-thread-9] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Found session cookie in request context
2019-12-26T16:59:46.852+03:00 [pool-29-thread-9] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session using session cookie...
2019-12-26T16:59:46.852+03:00 [pool-29-thread-9] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Roles found, not expired.
2019-12-26T16:59:46.852+03:00 [pool-29-thread-9] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Retrieved roles count for user: 1
2019-12-26T16:59:46.852+03:00 [pool-29-thread-9] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Verified privilege: StorageViews.View for roleId: -1
2019-12-26T16:59:46.852+03:00 [pool-29-thread-9] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session successfully
2019-12-26T16:59:46.853+03:00 [pool-27-thread-9] DEBUG opId=45fd585a-0283-482d-8402-a4f178eb89b8 com.vmware.vim.sms.task.TaskImpl - Received API call : queryInfo for task - ManagedObjectReference: type = SmsTask, value = SmsTask-14, serverGuid = eb098996-1af9-4799-8865-9316bd297fa1
2019-12-26T16:59:46.959+03:00 [pool-29-thread-10] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session with privilege: StorageViews.View
2019-12-26T16:59:46.959+03:00 [pool-29-thread-10] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Found session cookie in request context
2019-12-26T16:59:46.959+03:00 [pool-29-thread-10] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session using session cookie...
2019-12-26T16:59:46.959+03:00 [pool-29-thread-10] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Roles found, not expired.
2019-12-26T16:59:46.959+03:00 [pool-29-thread-10] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Retrieved roles count for user: 1
2019-12-26T16:59:46.959+03:00 [pool-29-thread-10] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Verified privilege: StorageViews.View for roleId: -1
2019-12-26T16:59:46.959+03:00 [pool-29-thread-10] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session successfully
2019-12-26T16:59:46.959+03:00 [pool-27-thread-10] DEBUG opId=5f9e512e-58fb-4ac6-b458-840f9a385899 com.vmware.vim.sms.task.TaskImpl - Received API call : queryInfo for task - ManagedObjectReference: type = SmsTask, value = SmsTask-14, serverGuid = eb098996-1af9-4799-8865-9316bd297fa1
2019-12-26T16:59:47.037+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.task.TaskManagerImpl - Marked SmsTask-14 as completed
2019-12-26T16:59:47.037+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.storage.common.util.SimpleTimeCounter - TIMER STOPPED: Task for registerProviderInt
2019-12-26T16:59:47.037+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.storage.common.util.SimpleTimeCounter - TIME TAKEN: Task for registerProviderInt: 0.738
2019-12-26T16:59:47.037+03:00 [pool-14-thread-1] DEBUG opId= com.vmware.vim.sms.task.TaskImpl - Task execution failed!ManagedObjectReference: type = SmsTask, value = SmsTask-14, serverGuid = eb098996-1af9-4799-8865-9316bd297fa1
2019-12-26T16:59:47.067+03:00 [pool-29-thread-1] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session with privilege: StorageViews.View
2019-12-26T16:59:47.067+03:00 [pool-29-thread-1] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Found session cookie in request context
2019-12-26T16:59:47.067+03:00 [pool-29-thread-1] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session using session cookie...
2019-12-26T16:59:47.068+03:00 [pool-29-thread-1] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Roles found, not expired.
2019-12-26T16:59:47.068+03:00 [pool-29-thread-1] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Retrieved roles count for user: 1
2019-12-26T16:59:47.068+03:00 [pool-29-thread-1] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Verified privilege: StorageViews.View for roleId: -1
2019-12-26T16:59:47.068+03:00 [pool-29-thread-1] DEBUG opId= com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session successfully
2019-12-26T16:59:47.068+03:00 [pool-27-thread-1] DEBUG opId=d4d5bcd3-2e5f-4ba3-bff8-4c5083ae937b com.vmware.vim.sms.task.TaskImpl - Received API call : queryInfo for task - ManagedObjectReference: type = SmsTask, value = SmsTask-14, serverGuid = eb098996-1af9-4799-8865-9316bd297fa1
2019-12-26T16:59:54.453+03:00 [pool-9-thread-1] DEBUG opId= com.vmware.pbm.qs.PbmQsTagAssociationPoller - Non-null feed received
2019-12-26T16:59:54.454+03:00 [pool-8-thread-1] DEBUG opId= com.vmware.pbm.qs.PbmQsPoller - Non-null feed received
2019-12-26T16:59:54.454+03:00 [pool-8-thread-1] DEBUG opId= com.vmware.pbm.qs.PbmQsPoller - Try to get info change notification for VC provider: 3A36A29B-D65B-4AFA-AAEB-D5EE16B05D4E
Выполнил kb VMware Knowledge Base , переименовав sms.truststore и sms.keystore , и перезапустив службу Profile Driven Storage Service , файлы в каталоге пересоздались.
Попробовал зарешистрировать VASA плагин - неудачно.
Затем выполнил kb VMware Knowledge Base , сертификат так же пересоздался. Попробовал вновь зарегистрировать VASA , и снова вывалилось данное сообщение о ошибке.
Что делать дальше, прошу содействия в вопросе.
Заранее спасибо.
↧
Re: vSphere Upgrade from 6.0 to 6.7
You can migrate the VC and PSC to 6.7U2 appliance and after you use the converge tool to decommission the external PSC.
External Platform Services Controller, A Thing of the Past - VMware vSphere Blog
Upgrading the vCenter Server Appliance and Platform Services Controller Appliance
↧
↧
Re: vcenter6.7 VM migrate failed
Hi
Did you check this VMware Knowledge Base ?
↧
Maximum LUN size. Maximum VMFS volume size.
Hi everyone!
Do you have an example of a LUN bigger than 16TB connected to your vSphere? Maybe 32TB? Do you have a VMFS 5 or 6 volume bigger than 16TB?
According to the information I have found the limitation of VMFS volume is 62TB. Unfortunately I cannot find the confirmation that a storage system can present to vSphere a LUN bigger than 16TB so that I could create the big VMFS volume.
There is a known 16TB LUN size limitation from NetApp. But what about other vendors?
Thanks in advance.
↧
Re: how to boot with USB a vmware virtual machine
Well, I just tested it and it worked. Probably not really oranges to apples but:
(I am not sure that all of is necessary)
I am running WS 14 on Linux Mint.
I created a new VM, minimal disk space, 5 GB
I told it the OS type was Linux 64
I told it I would install the software later.
I told it to use the plop iso for the CDROM, making sure that enable during power on was checked.
I let it complete the VM
I edited the vmx file to add BIOS.bootdelay="5000"
to add 5 seconds delay to let me easily hit esc.
During the boot process, hit esc and got a menu with USB as the only choice.
Edit: make sure the USB stick is in your system and recognized.
Edit 2: Make sure your USB stick is connected. Either VM removable devices or the icon in the lower right. You may have to power on and then connect it.
Messy but worked.
If something like that doesn't work for you, I have no clue.
Lou
--
Give a man a fish; you have fed him for today. Teach a man to use the Internet and he won't bother you for weeks,
or even months unless you give him your email address.
¯\_(ツ)_/¯
↧
Re: Error: Operation failed with error = ERROR_NOT_ENOUGH_MEMORY (8) (8)
hi, can you restart vcenter services and try to add esxi host once?
↧
↧
Re: Not able to ping VM in different host. NSX-V
I didn't quite understand the trace result. Can you send the screenshot?
Regarding VTEP connectivity between hosts, did you validate it with the following command to test both reachability and MTU of 1600?
vmkping ++netstack=vxlan -s 1572 -d x.x.x.x
↧
Re: Edge Nodes with only VLAN Transport Zone
You still need Overlay in that case. The reason for this is that overlay segments are used both for the keepalive mechanism between Edge Nodes in an Edge Cluster and also for communication between T1 SR and T1 DR.
↧
Re: NSX Load balancer Service Certificate
When you import a certificate you have the option of setting this as a certificate to be used for services, for example load balancing, or for the NSX Manager nodes. Since you want to use it for load balancing you have to mark the option named Service Certificate. Did you do this?
Reference: Import a Certificate
↧
Re: Segment MAC learing
MAC learning is not needed in typical scenarios where each vNIC connected to a segment has a single MAC address associated with it. Only in special cases as in nested deployments you need to enable MAC Learning, so this is not enabled by default.
More info here: Understanding MAC Discovery Segment Profile
↧
↧
Re: NSX Intelligence Installation succeeded but admin user cannot see anything
NSX-T 2.5.1 was released last week and includes a workaround for the certificate change issue. Haven't tested it yet, but it should work.
Look at issue 2436302 in the release notes: VMware NSX-T Data Center 2.5.1 Release Notes
↧
Re: vSAN test
By doing this configuration, can we create VM's on top of nested esxi VM's?
Yes, that's what the settings are for. However, don't expect high performance for the nested VMs.
André
↧
Re: how to boot with USB a vmware virtual machine
You are looking at the wrong place top connect the USB device. Look at the screenshot at step 7 of the blog post that youv'e mentioned. Once the VM is powered on, you will see the icons below the guest screen. Click on the USB device that you want to connect to the VM.
You can either follow louyo's hint regarding the boot delay to pause the boot process until you've connected the USB device, or simply warm-boot the VM - pressing CTRL-ALT-INS - after connecting it.
André
↧
Re: Listing all snapshots per vm using get-view
This function works perfectly. On a related subject, we require all scripts to be signed. It seems that a function is basically a script in disguise. Is there a way to require functions to be signed or to restrict their use by the 400 users on our network?
↧
↧
Exposing Configuration in vRO
Is there any way to update configuration elements when required ?
There are lot of team members who want to update Configuration element when required in VRO.
BUT they do not have access of VRO and we can not grant their access.
Kindly share your feedback, What you think about it.
↧
Re: Maximum LUN size. Maximum VMFS volume size.
Unfortunately I cannot find the confirmation that a storage system can present to vSphere a LUN bigger than 16TB ...
There are indeed still storage system with a 16TB maximum LUN size. I assume that Netapp's 16TB maximum is due to a file system limitations on which they store the LUNs.
Anyway, the storage vendors usually have the max. LUN size for supported operating systems in their documentation, and even less expensive systems support LUN sizes with 256TB, or more.
André
↧
Re: vcenter6.7 VM migrate failed
Discussion moved from VMTN Global Forums to vCenter™ Server
↧