Error in services-messages.log after Diagnostic page is hit

  • 7015339
  • 07-Jul-2014
  • 07-Jul-2014

Environment

Novell ZENworks Configuration Management 11.3

Situation

After the zenserver service restart, the first time ZCC is used to view the Diagnostic page, an error is thrown in services-messages.log

ERROR (in services-messages.log)

[TRACE] [07/07/2014 22:34:02.117] [1867] [ZENService] [88] [] [DataModel] [] [Failed to configure caching defined in file: /etc/opt/novell/zenworks/datamodel/caching/default/caching-system-update.xml] [] [] [] [ZENServer]
[TRACE] [07/07/2014 22:34:02.119] [1867] [ZENService] [88] [] [DataModel] [] [org.jdom.JDOMException: Could not load default SAX parser: org.apache.xerces.parsers.SAXParser: SAX2 driver class org.apache.xerces.parsers.SAXParser not found: org.apache.xerces.parsers.SAXParser
at com.novell.zenworks.datamodel.utils.jdom.SAXBuilder.createParser(SAXBuilder.java:588)
at com.novell.zenworks.datamodel.utils.jdom.SAXBuilder.build(SAXBuilder.java:426)
at com.novell.zenworks.datamodel.utils.jdom.SAXBuilder.build(SAXBuilder.java:817)
at com.novell.zenworks.datamodel.utils.jdom.SAXBuilder.build(SAXBuilder.java:796)
at com.novell.zenworks.datamodel.utils.XMLUtil.read(XMLUtil.java:145)
at com.novell.zenworks.datamodel.utils.DataModelCache.configure(DataModelCache.java:431)
at com.novell.zenworks.datamodel.services.DirectServiceStoreImpl.initializeCache(DirectServiceStoreImpl.java:1013)
at com.novell.zenworks.datamodel.services.DirectServiceStoreImpl.loginAsSystem(DirectServiceStoreImpl.java:278)
at com.novell.zenworks.datamodel.services.DirectServiceStoreImpl.loginAsSystem(DirectServiceStoreImpl.java:254)

Resolution

Workaround:  This error can be ignored if it goes away after some time browsing out and back into Diagnostic page (until restart).  It is only cosmetic.  If the error persists, confirm ZENworks Diagnostic Center for proper version of jars present.

Status

Reported to Engineering

Feedback service temporarily unavailable. For content questions or problems, please contact Support.