System Update error building packages

  • 7003541
  • 15-Jun-2009
  • 05-Apr-2016


Novell ZENworks 10 Configuration Management with Support Pack 2 - 10.2
Novell ZENworks Configuration Management 11.2


ERROR (on ZCC system update):
"This device was unable to rebuild the deployment packages. Check the loader-messages.log on the device for more details."
ERROR (example from loader-messages.log):
[DEBUG] [6/12/09 12:01:16 PM] [] [Loader.SystemUpdateModule] [] [FINE: Unable to extract content] [com.novell.zenworks.systemupdate.exceptions.SystemUpdateException: There was an error getting the content from the content system.  The specified content is not available on this server
[DEBUG] [6/12/09 12:01:16 PM] [] [Loader.SystemUpdateModule] [] [FINE: Unable to extract update content.] [ Unable to extract content: sybase-asa-10.0.1-3870.i586.rpm


Check the loader-messages.log for the error.  In the example from Situation above, the content referred to is sybase-asa-10.0.1-3870.i586.rpm and is expected to be in content-repo/system-update/ guid where guid is the guid of the system update.

Assuming that the error has been corrected (missing content is now availaible for example) and that the system-update.log shows that the server had been updated sucessfully aside from the package rebuild, then run ZCC on the server that failed to rebuild the packages, select the Clear error and continue option on the main system update page or Redeploy update option on the device status list page to restart the package rebuild option.  This will cause the update to be marked successful.

Alternatively, running zman surp "<UpdateName>" will update the device's update status.

Additional Information

In one case although the actual file was available, it did not show in the database. 
This was after several failed download attempts. 
Deleting the System update with ZCC and redownloading from manual zip corrected the missing content error.
The content guid for any system update content is static (unlike most content) and is listed in the system update xml. 
For example for System Update 10.2 see and note that each msi, rpm etc has an associated uid.