VMware Solutions Discussions

Vcenter 5.5 update 3 VSC 6.2 web client blank/empty shows no data.

waynesilvia
5,143 Views

Have a weird issue that just appeared.... VSC was working fine then all of a sudden VSC was "blank", Click on the VSC icon and nothing shows up....the pull down that shows what Vcenter you are connected to is blank (see screenshot and attachment), the backup jobs 0, Hosts 0, Storage systems 0.... 

The scheduled backup jobs continue to run fine,  if you stop and restart the VSC services you can see it discovering hosts etc...

 

A reboot of Vcenter fixed it once....but has sinced happened again and rebooting vcenter and or VSC server (seperate windows server) has not resolved the issue.

I have an open case with Vmware and Netapp and tried many steps to try to resolve it...

 

1) register VSC (always reregisters fine)

2) upgrade VSC to 6.2p1

3) remove the netapp plugin via vcenter mob (using KB article) https://kb.netapp.com/support/index?page=content&id=1015437

4) remove the netapp via mob and uninstall/resinstall the vsphere web client (vmware recommendation)

 

If anyone as experienced this issue please chime in....

 

The vsphere_client_virgo.log show this...

[2016-08-09 14:18:17.537] [INFO ] http-bio-9443-exec-12        70000700 100002 200004 com.netapp.vsc.util.VscDataAdapter                                getData called with 1 queries.

[2016-08-09 14:18:17.537] [INFO ] http-bio-9443-exec-12        70000700 100002 200004 com.netapp.vsc.util.VscDataAdapter                                Start- processQuery() - Query Spec: dam-auto-generated: AggregateRelatedItemsCount:dr-33

[2016-08-09 14:18:17.537] [INFO ] http-bio-9443-exec-12        70000700 100002 200004 com.netapp.vsc.util.VscDataAdapter                                Start - processConstraint(): com.vmware.vise.data.Constraint, Target type: vsc:All

[2016-08-09 14:18:17.537] [INFO ] http-bio-9443-exec-12        70000700 100002 200004 com.netapp.vsc.storagesystem.service.StorageSystemDataAdapter     Start - processSimpleConstraint() for: vsc:All

[2016-08-09 14:18:17.571] [INFO ] http-bio-9443-exec-12        70000700 100002 200004 com.netapp.vsc.storagesystem.service.StorageSystemDataAdapter     Controller list is: []

[2016-08-09 14:18:17.571] [INFO ] http-bio-9443-exec-12        70000700 100002 200004 com.netapp.vsc.storagesystem.service.StorageSystemDataAdapter     End - processSimpleConstraint() - returning [0] objects.

[2016-08-09 14:18:17.571] [INFO ] http-bio-9443-exec-12        70000700 100002 200004 com.netapp.vsc.util.VscDataAdapter                                processConstraint() for: vsc:All - No objects selected, nothing to return...

[2016-08-09 14:18:17.571] [INFO ] http-bio-9443-exec-12        70000700 100002 200004 com.netapp.vsc.util.VscDataAdapter                                End - processConstraint() - found [0] objects.

[2016-08-09 14:18:17.571] [INFO ] http-bio-9443-exec-12        70000700 100002 200004 com.netapp.vsc.util.VscDataAdapter                                End - processQuery() - Result Set contains [0] items.

 

 

VSC-Blank.JPG

 

 

4 REPLIES 4

asulliva
4,923 Views

Hello @waynesilvia,

 

Have you opened a support case for ths?  They will be able to assist with troubleshooting and, if needed, raising a bug with engineering.

 

Andrew

If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

waynesilvia
4,910 Views

As my post said...I already have open cases with netapp and vmware...both seemed to be stumped....figured I would try the community.... hoping someone might have had the same issue at the very least.... misery loves company. 

 

 

ptravis
4,831 Views

I have a similar issue.  Removing and reinstalling addressed it initially.  However, the issue returns and I've found restarting the VSC service works.  My issue however is no matter what I try, since upgrading to 6.2P2, none of my backup jobs will run manually or scheduled as I receive a message that the datastores cannot be found.  I have a case opened with netapp but having only sent over logs so far.

scathomas
4,698 Views

Did you get a solution for this issue? I see same behave.

Public