Server out of sync errors since updating to 11.2.2

  • 7011404
  • 20-Nov-2012
  • 11-Apr-2013

Environment

Novell ZENworks Configuration Management 11.2
MSSQL Database

Situation

ERROR (zcc.log):
 
Warning:  Some of the ZENworks features might behave incorrectly because the time of the current Primary Server (some date UTC) and the time of the ZENworks database server (some date UTC) are not in sync.

 



 

Resolution

This is fixed in version 11.2.3a - see KB 7011295 "ZENworks Configuration Management 11.2.3a - update information and list of fixes" which can be found at https://support.microfocus.com/kb/doc.php?id=7011295
 
For ZCM 11.2.2 Monthly Update 2: Workaround: if it is not possible to upgrade to ZCM 11.2.3a at this time, 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=FqytscocWtM~ as "ZCM 11.2.2 MU1/MU2 fix for Server out of Sync errors - see KB 7011404 and ZCC File Upload Remote Code Execution Vulnerability - see TID 7011812". 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.

For ZCM 11.2.2 Monthly Update 1: Workaround: if it is not possible to upgrade to ZCM 11.2.3a at this time, 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=FqytscocWtM~ as "ZCM 11.2.2 MU1/MU2 fix for Server out of Sync errors - see KB 7011404 and ZCC File Upload Remote Code Execution Vulnerability - see TID 7011812". 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.

For ZCM 11.2.2: Workaround: if it is not possible to upgrade to ZCM 11.2.3a at this time, 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=PXticCZ7cLw~ as "ZCM 11.2.2 fix for Server out of Sync errors - see KB 7011404 and ZCC File Upload Remote Code Execution Vulnerability - see TID 7011812". 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.



Confirm that the primary servers and the external database server have times that are in sync.  If this is the case, and the error happens anyway, Workaround:  Restart the ZENworks services or reboot the primary server.

Cause

A bug in the SQL function that was used by ZCM to check time differences meant that the wrong result may be returned when there is a change in the daylight saving status.
 
Also a bug was found for after updating locations, the current time was reset as UTC time on the primary java instance.

Additional Information

Additional keywords for search:
 
11.2.2 Some of the ZENworks features might

zcc saying db not in sync 11.2.2

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