Highlighted
EvgeniyStruts
1 Nickel

VSI plugin doesn't work properly for some users

I've been able to register SIS and a couple of Storage systems for me and for a couple other users in vSphere Web client but it doesn't work for some users at all.

It gives me Flash error with code 1009 which is generic Flash error when I am adding Storage Systems.Untitled.png

I also noticed if you go to Solutions Integration Service in Web Client you will see that the Name and the Version have never showed up.

It seems the plugin works improperly for those users for some reason.

I tried to add those users manually on VSI appliance side and give them permissions to the storage systems but they don't appear in vSphere Web Client as well.

I also tried this KB  VMware Knowledge Base  but it didn't work for me.

We are running on vSphere 6.5 U1 and VSI 7.2.

Does anybody have any ideas how to fix it?

Labels (2)
Tags (2)
0 Kudos
1 Reply
EvgeniyStruts
1 Nickel

Re: VSI plugin doesn't work properly for some users

NoNameNoVersion_v1.png

There is a symptom, if VSI name and its version doesn't show up you will get Flash error

I also tried to use VSI 7.1 with the same result

Found some errors in virgo log file:

[2017-12-19T17:21:56.741Z] [INFO ] http-bio-9090-exec-16     c.e.v.p.storageaccess.StorageAccessProviderRepositoryCache    Start to update cache Stor

ageAccessProvider , The register details: StorageAccessProvider[name=<null>,status=Online,ip=<VSI hostname was deleted>,version=<null>,userId=<Username was deleted>,password=<the password was deleted>,userAuthenticationType=BEARER_TOKEN,registeredvCenters=vCenter01:1.1.1.1]

[2017-12-19T17:21:57.094Z] [INFO ] http-bio-9090-exec-33    70001015 100231 200207 com.emc.vsi.services.HttpsClientService                       user

@localdomain.com : Request URI : https://VSI.localdomain.com:8443/vsi_usm/api/types/storageSystem/instances

[2017-12-19T17:21:57.094Z] [INFO ] http-bio-9090-exec-33    70001015 100231 200207 com.emc.vsi.services.HttpsClientService                       user

@localdomain.com : Request Header info : GET https://VSI.loacldomain.com:8443/vsi_usm/api/types/storageSystem/instances HTTP/1.1

[2017-12-19T17:21:57.094Z] [INFO ] http-bio-9090-exec-33    70001015 100231 200207 com.emc.vsi.services.HttpsClientService                       user

@localdomain.com : Request Body : null

[2017-12-19T17:21:57.180Z] [INFO ] http-bio-9090-exec-33    70001015 100231 200207 com.emc.vsi.services.HttpsClientService                       HTTP

/1.1 400 Bad Request

[2017-12-19T17:21:57.180Z] [INFO ] http-bio-9090-exec-33    70001015 100231 200207 com.emc.vsi.services.HttpsClientService                       user

@localdomain : Response status : 400

[2017-12-19T17:21:57.180Z] [INFO ] http-bio-9090-exec-33    70001015 100231 200207 com.emc.vsi.services.HttpsClientService                       user

@localdomain : Response body :

[2017-12-19T17:21:57.180Z] [INFO ] http-bio-9090-exec-33    70001015 100231 200207 com.emc.vsi.services.HttpsClientService                       user

@localdomain.com : VSI call to Solutions Integration Service : End

[2017-12-19T17:21:57.180Z] [ERROR] http-bio-9090-exec-33    70001015 100231 200207 com.emc.vsi.providers.storagesystems.StorageSystemInfoRetriever   Erro

r response from hercules

[2017-12-19T17:21:57.180Z] [ERROR] http-bio-9090-exec-33    70001015 100231 200207 com.emc.vsi.providers.storagesystems.StorageSystemInfoRetriever   Thro

ws error info to be caught in response.error to be sent to Flex : java.lang.Exception:

0 Kudos