vCenter Operations Manger Error when viewing from the webclient Health Tab

[benjo1234]

Has anyone run into this issue on 5.5 when trying to view the Health of a VM from the webclient. Overall the vCOPS works from both the thick and web client but not from the health tab in the web client. The error message states " Cannot connect to the vCenter Operations server. Check your network connection, and the running state of the virtual machines in the vCenter Operations Manager vApp". Both the UI and analytic are running.

Thank you.

[JohannStander]

This problem I normally find when you don't have your permissions setup correctly within vCenter server. Create the role for VCOPS where you have the vCOPS enabled for admin or user access. Global -> vCenter Operations Manager User/Admin) Then verify you have the user/group with newly create VCOPS role assigned under permissions to the following objects in vCenter sever. If you want to provide access to everything in vCenter server for the group then add group/user with role too: Top level vCenter server (inherited) If you only want to provide access to a specific cluster inside a datacenter then add group/user with role too: Top level vCenter server (not inherited) Datacenter (not inherited) Cluster (inherited, depending on how much information you want to see within the datacenter) Hope this helps for future

[jjgunn]

I had this issue. VCOPS 5.8.2 & vCenter 5.5 Update 2b (build 2183111)

After upgrading VM Tools & VM hardware to 10. I simply logged out & back into the vsphere web client.

Health State Tab is now operational again with health, risk & efficiency listed.

Hope this is helpful

[MarkStrong]

jjgunn wrote:

I had this issue. VCOPS 5.8.2 & vCenter 5.5 Update 2b (build 2183111)

After upgrading VM Tools & VM hardware to 10. I simply logged out & back into the vsphere web client.

Health State Tab is now operational again with health, risk & efficiency listed.

Hi jjgunn,

Sorry, what VM/VA did you upgrade the VMware Tools on?

Thank you.

Mark

[MarkStrong]

JohannStander wrote:

This problem I normally find when you don't have your permissions setup correctly within vCenter server. Create the role for VCOPS where you have the vCOPS enabled for admin or user access. Global -> vCenter Operations Manager User/Admin) Then verify you have the user/group with newly create VCOPS role assigned under permissions to the following objects in vCenter sever. If you want to provide access to everything in vCenter server for the group then add group/user with role too: Top level vCenter server (inherited) If you only want to provide access to a specific cluster inside a datacenter then add group/user with role too: Top level vCenter server (not inherited) Datacenter (not inherited) Cluster (inherited, depending on how much information you want to see within the datacenter) Hope this helps for future

Hi Johann,

I am logging in with a user with Administrator role - still cannot get to the Health page.

Regards

Mark

[JohannStander]

Hi Mark

few things you can check.

- under SSO verify that you account is also added to the VCOAdministrators group

                Administrations -> Single Sign-n -> Users and groups -> Groups

                add your domain or vsphere.local to this group

- under administration -> Solutions -> client plug-ins, verify that com.vware.vcops is showing

- Login to vCenter MOB and verify that the server information is correctly configured for vCops.

                https://<vcenter server>/MOB/

                content -> extensionManager -> extensionList["com.vmware.vcops"] -> server

                copy the url and paste in browser and make sure you get a response back for vCenter Operations Manager Plug-in

- Under vCenter Operations manager administration webpage, verify that the account listed for vCenter server registration has the appropriate rights in vCenter server.

[MarkStrong]

Hi Johann,

Everything is in order except of VCOAdministrators group that is missing from SSO -> Administrations -> Single Sign-n -> Users and groups -> Groups

I only see:

- Users

- SolutionUsers

- DCAdmins

- ExternalDPUsers

- Administrators

[JohannStander]

sorry my bad, the VCOadministrator under SSO is for Orchestrator and not VCOPS

the last thing I think of trying to restart your Web client for vCenter server.

After I made my changes with the permissions I had to restart the web client to get the health page to show correctly.

[jjgunn]

firstvm-external & secondvm-external.

I upgraded the VMTools & VM version to 10.

The upgrade solved my issue. Don't forget to logout & login of SSO

vCenter Operations Manager version 5.8.2.0

[MarkStrong]

jjgunn wrote:

firstvm-external & secondvm-external.

I upgraded the VMTools & VM version to 10.

The upgrade solved my issue. Don't forget to logout & login of SSO

vCenter Operations Manager version 5.8.2.0

Thank you for your advise.

Unfortunately, It did help in my environment.  I am using vCenter 5.5 U2b and VCOPs 5.8.4.

[JohannStander]

do you have multiple vcenter in linked mode? this was fixed in 5.8.3 and since you on 5.8.4 should be good but look at this kb 2076938 what errors do you observe in the vcenter log filse?  another issue might be related to timeouts shown in log files.  look at this kb 2071907. If these don't work then I would suggest opening a case with VMware support.

[MarkStrong]

Thank you Johann,

Yes, I had my vCenters 5.5 U2b in Linked Mode and have been running vCOPs 5.8.3 for some time... I then upgraded to 5.8.4 and it worked for some time and then it stopped... I tried redeploying vCOPs 5.8.4 from scratch but it did not help...

I think we are on the right track with KB 2071907.  I opened a case with VMware and they sent me a new, updated 'planning-service-1.0.0.jar' file but it did not help...  Apparently, my case got "attached" to the existing issue that Engineering Team is working on. Will update you as soon as the solution is available.

Regards

Mark

http://www.vStrong.info

JohannStander wrote:

do you have multiple vcenter in linked mode? this was fixed in 5.8.3 and since you on 5.8.4 should be good but look at this kb 2076938 what errors do you observe in the vcenter log filse?  another issue might be related to timeouts shown in log files.  look at this kb 2071907. If these don't work then I would suggest opening a case with VMware support.

[MarkStrong]

Hi Johann,

Finally have an update and the resolution for this issue.

We are hitting an issue where encoding and decoding of the health data between vCenter Server 5.5 and vCenter Operations Manager 5.8.x does not occur quickly enough and leads to a timeout.

To resolve the issue you need to replace planning-service-1.0.0.jar that was provided by VMware.  Since I replaced the jar file (C:/ProgramData/VMware/vSphere Web Client/vc-packages/vsphere-client-serenity/com.vmware.vcops-5.8.4.2199700/plugins/) and restarted the WEB Client service, everything is fine and I can see the Health status in vSphere WEB Client.

Regards

Mark

http://www.vStrong.info

[JohannStander]

Great, thanks for the update on this issue Mark. I guess onwards to vRealize Operations v6 now right 🙂

[Bleeder]

Any word if this will be fixed for vCOps v5.8.x via an actual patch or new installation files versus manually modifying the .jar file?

vRealize Operations v6 is missing several things (TopN views, for example), so I'd rather not go down that road yet.

[Hophophop]

Hi MarkStrong,

Where can I find planning-service-1.0.0.jar file ?

Thanks,

Laurent

[g0rbi]

I'd be interested in this Information, too.

[VIR2AL3X]

Hophophop & g0rbi - please refer to this article in order to edit the .jar file and change the timeout value.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=207190...

Although I had this same problem, this instructions above did not work for me.  What ultimately worked was to log into the vCenter Operations Manager Admin page and unregister vCenter then re-register vCenter.

Once the unregister was complete, I logged into vCenter Web Client to validate and the "Health State" was no longer present.  After re-register of vCenter in the Admin page, logged out of Web-Client and back in..."Health State" was now present again and displaying health info.

Hope this helps!

[germansalazar85]

I replace the file called "planning-service-1.0.0.jar" on the following route - vcenter on Windows: "C:\ProgramData\VMware\vSphere Web Client\vc-packages\vsphere-client-serenity \com. vmware.vcops-5.8.4.2199700\plugins"

and then restart the VMware vShpere web Client service.

download file: planning-service-1.0.0.rar - Google Drive

greeting

Germán.