ZCM Devices stuck in 'Startup', 'Unknown' or 'Default' locations

  • 7013474
  • 18-Oct-2013
  • 20-Jul-2015

Environment

Novell ZENworks Configuration Management 11.2
Novell ZENworks Asset Management 11.2
Novell ZENworks Patch Management 11.2

Situation

Devices unexpectedly go to the 'Startup', 'Unknown' or 'Default' location, and remain there.

The ZESM service will not stay running.

ERROR (from ZES event viewer logs):

[Fatal     , SYSTEM][11/22/2013 10:34:32.403][][][ 4][][FDE Minimum Component   ][][Failed to read FDE Settings document from store: 0xa00e0142
Logged at:
    1: ZES.Log.LogEventArgs::RecordStack - file: ZESBase.dll
[Warning   , SYSTEM][11/22/2013 10:30:17.661][][][ 4][][ZES Component Manager   ][][Load of engine components failed, stage: Base Load (All), Version: 11.2.3.385
Logged at:
    1: ZES.Log.LogEventArgs::RecordStack - file: ZESBase.dll

Resolution

This is fixed in version 11.3 - see KB 7014213 "ZENworks Configuration Management 11.3 - update information and list of fixes" which can be found at https://support.microfocus.com/kb/doc.php?id=7014213
 
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, as part of a Monthly patch update: it can be obtained at https://download.novell.com/Download?buildid=Rbs5fYlojj0~ as "ZCM 11.2.4 Monthly Update 1 - see TID 7014163". This update should only be applied if the symptoms above are being experienced, and are causing problems.

Please report any problems encountered when using this Patch, by using the feedback link on this TID.

Cause

Corrupt ZES/FDE core files.

Additional Information

As a work-around: Delete the files located in %zenworks_home%\cache\zmd\zencache\metadata, then force a refresh of the device.
If that does not work, delete all of the contents of %zenworks_home%\cache, but not the cache folder itself, and restart the ZCM Agent Service or Device.