After deploying ZCM 11.2.3a MU1, Machine may hang, remains in "Startup Location", Zesservice stops or crashes

  • 7012847
  • 13-Jul-2013
  • 28-Oct-2013

Environment

Novell ZENworks Configuration Management 11.2
Novell ZENworks Endpoint Security Management 11.2

Situation

Device with ZCM 11.2.3a MU1 agent hangs, and after a reboot the Location stays at whatever is set as the Start Location

There are two known causes for this error, check the detailed symptoms below:

CASE 1
To check if the problem is due to this particular issue, open the ZESM about box:
 If ZESM is activated: See Endpoint Security link from ZENworks icon properties.
If ZESM is not activated: go to Start > All Programs > Novell > ZESM About
 
Click Diagnostic > logging > View Service Log
Search for "written with wrong munge buffer, attempting to recover" - if this phrase is not found, then this cause does not apply.

CASE 2
ZES Service will not start; as soon as the device is restarted, the service crashes again, and the symptoms above do not apply. Unregister and re-register does not fix the problem

Resolution

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

Workaround:

CASE 1
  1. In windows explorer navigate to the ZESM Store files:
    e.g., for Windows 7: C:\Program Data\Novell\ZES\Store\Service
  2. The content of the files is encrypted, but the corrupt file in this directory can be determined in the following manner:
    a. Open each file in notepad and observe if the file contains some content, it will be unreadable but it should not be empty (nulls).
    b. If a file is seen to have length (non-zero) but the contents are filled with blanks, this is a corrupt file.
    c. Delete the blank file and reboot.

CASE 2
Unfortunately, the only known fix for this case is to uninstall and re-install the agent

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