ZENworks Agent Status in ZCC not displaying

  • 7003014
  • 05-Apr-2012
  • 05-Jul-2012

Environment

Novell ZENworks Configuration Management 11 ZENworks Control Center - ZCC
Novell ZENworks Configuration Management 11.1 ZENworks Control Center - ZCC
Novell ZENworks Configuration Management 11.2 ZENworks Control Center - ZCC

Situation

The 'ZENworks Agent Status' in the ZCC is not displaying for any device.  Instead of showing a green sphere there is constant 'bouncing ball'.
Port 7628 is open.

Seen in the zcc.log:

java.lang.NullPointerException
at com.novell.zenworks.admin.extensions.ajax.DeviceHealthDescriptionAJAX.service(DeviceHealthDescriptionAJAX.java:72)
at com.novell.web.ajax.AJAXDataHandler.service(AJAXDataHandler.java:40)
at com.novell.web.AjaxServlet.serviceImpl(AjaxServlet.java:95)
at com.novell.web.AjaxServlet.service(AjaxServlet.java:70)
at com.novell.zenworks.fw.web.internal.ZENworksAjaxServlet.service(ZENworksAjaxServlet.java:47)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

Resolution

This is fixed in version 11.2.1 - see KB 7010042 "ZENworks Configuration Management 11.21 - update information and list of fixes" which can be found at https://support.microfocus.com/kb/doc.php?id=7010042

For ZCM 11.0: A fix for this issue is intended to be included in a future update to the product: however, in the interim, Novell has made a Patch available for testing, in the form of a Field Test File (FTF): it can be obtained at https://download.novell.com/Download?buildid=pssJ40mAV2I~ as "ZCM 11.0 fix for ZENworks Agent Status in ZCC not displaying - see TID 7003014". This Patch should only be applied if the symptoms above are being experienced, and are causing problems.

This Patch has had limited testing, and should not be used in a production system without first being checked in a test environment. Some Patches have specific requirements for deployment, it is very important to follow any instructions in the readme at the download site. Please report any problems encountered when using this Patch, by using the feedback link on this TID.