A.3 Error Codes

ERROR CODE: ERROR = 40

Source: ZENworks 2017; Patch Management.
Possible Cause: The patch file cached to the ZCM Server is corrupt.
Action: Try re-caching the patch to the ZCM Server.

ERROR CODE: PPX_ERROR_PATCH_MORE_THAN_MAXAPPLICABLE SIGS = 45

Source: ZENworks 2017; Patch Management.
Possible Cause: The patch file contains more than the maximum applicable signatures.
Action: Notify Micro Focus Support of the error. We will fix the problem with the patch and notify you when it is fixed.

ERROR CODE: PPX_ERROR_ARCHIVE_EXTRACT = 2

Source: ZENworks 2017; Patch Management.
Possible Cause: Extraction of the .cab file or its contents fails.
Action: Follow the steps below:

  1. Make sure that CABARC runs on the end point where the error message appears.

  2. Check the available disk space on the end point.

  3. Re-cache the patch to the ZCM Server.

  4. If the issue persists, contact Micro Focus Support.

ERROR CODE: PPX_ERROR_PACKAGE_ARCHIVE_INITIALIZE = 8

Source: See ERROR CODE: PPX_ERROR_ARCHIVE_EXTRACT = 2.

ERROR CODE: PPX_ERROR_EXTRACT_FILE = 20

Source: See ERROR CODE: PPX_ERROR_ARCHIVE_EXTRACT = 2.

ERROR CODE: PPX_ERROR_PACKAGE_REIMPORT = 40

Source: See ERROR CODE: PPX_ERROR_ARCHIVE_EXTRACT = 2.

ERROR CODE: PPX_ERROR_EXPIRED_LICENSE_KEY = 27

Source: ZENworks 2017; Patch Management.
Possible Cause: The .plk license file you are using is outdated or has expired. This error code might also appear if the license file is erased or did not get decrypted properly.
Action: Ensure that you have the latest System Update installed.

ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1

Source: ZENworks 2017; Patch Management.
Possible Cause: You might encounter any of these error codes if a patch has bad metadata.
Action: Contact Technical Support.

ERROR CODE: PPX_ERROR_PATCH_OPEN_FAILURE = 3

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_PATCH_BAD_GUID = 4

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_PATCH_MANY_APPLICABLE_SIGNATURES = 5

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_PATCH_OPEN_FAILURE = 6

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_PATCH_BAD_GUID = 7

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_PATCH_OPEN_FAILURE = 9

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_PATCH_BAD_GUID = 10

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_PATCH_OPEN_FAILURE = 11

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_PATCH_BAD_GUID = 12

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_SIGNATURE_PREREQ_CACHE_EXHAUSTED = 13

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_PATCH_OPEN_FAILURE = 14

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_PATCH_BAD_GUID = 15

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_FINGERPRINT_EXPRESSION_SYNTAX = 16

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_FINGERPRINT_FILEROOT_UNSUPPORTED = 17

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_FINGERPRINT_TYPE_UNSUPPORTED = 18

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_SCRIPT_BAD_FILEHANDLE = 19

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_WMI_FINGERPRINT_UNSUPPORTED = 22

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_JAVASCRIPT_UNSUPPORTED = 23

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_MISSING_PREREQ_SIGNATURE = 25

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_INVALID_PREREQ_LANGUAGE = 26

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_INVALID_ROOT_HKEY = 21

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_FINGERPRINT_INVALID_SYSINFO = 31

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_FINGERPRINT_EXPRESSION_MISSING_VARIABLE = 32

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_FINGERPRINT_FILESCAN_UNSUPPORTED = 34

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_FINGERPRINT_WMI_ERROR = 35

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_RELEVANCE_SCRIPT_SYNTAX = 36

Source: See ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1.

ERROR CODE: PPX_ERROR_ENTITLED_FILE_INVALID = 41

Source: ZENworks 2017; Patch Management.
Possible Cause: These error codes indicate possible problems in bundle distribution. The ZCM server might not be able to access a third-party website where bundles are located.
Action: Follow the steps below:

  1. Check your Internet connection and firewall settings.

  2. Check that the ZCM Server can access a third-party website such as the Microsoft Download Center.

  3. Download patches from the third-party website.

  4. Re-cache the downloaded patches.

ERROR CODE: PPX_ERROR_ENTITLED_FILE_MISSING = 28

Source: See ERROR CODE: PPX_ERROR_ENTITLED_FILE_INVALID = 41.

ERROR CODE: PPX_ERROR_ENTITLED_FILE_BAD_CHECKSUM = 29

Source: See ERROR CODE: PPX_ERROR_ENTITLED_FILE_INVALID = 41.

ERROR CODE: PPX_ERROR_ENTITLED_FILE_WRONG_SIZE = 30

Source: See ERROR CODE: PPX_ERROR_ENTITLED_FILE_INVALID = 41.

ERROR CODE: PPX_ERROR_OUT_OF_MEMORY = 24

Source: ZENworks 2017; Patch Management.
Possible Cause: This error arises when there is a deficiency in system resources, such as insufficient disk space, low available memory, and so on.
Action: Check the available disk space and memory, then verify that it is sufficient to meet the ZCM Server and Agent requirements.

ERROR CODE: PPX_ERROR_PACKAGE_MKDIR_FAILURE = 33

Source: ZENworks 2017; Patch Management.
Possible Cause: The user has insufficient permissions to carry out the specified action.
Action: Check whether you have appropriate system rights or permissions.

ERROR CODE: PPX_ERROR_UNKNOWN

Source: ZENworks 2017; Patch Management.
Possible Cause: This error is a a general exception. If logging is enabled, the error is recorded in the .log file.
Action: Follow the steps below:

  1. Open a support ticket with Lumension.

  2. Contact Micro Focus Support.

ERROR CODE: 41

Source: ZENworks 2017; Patch Management.
Possible Cause: This error code implies that ZENworks Patch Management was unable to perform patch remediation. This error occurs when deployment of a different version of the same patch is in progress.
Action: Wait for the previous deployment to complete, then deploy the patch again.

ERROR CODE: 142

Source: ZENworks 2017; Patch Management.
Possible Cause: The selected patch requires certain prerequisites before the patch can be deployed. This error can also occur when package files for a patch are unavailable.
Action: Contact Micro Focus Support and report the patch name. This is most likely a bad patch.

ERROR CODE: 143

Source: ZENworks 2017; Patch Management.
Possible Cause: This error is a a general exception. If logging is enabled, the error is recorded in the .log file.
Action: Follow the steps below:

  1. Redeploy the patch.

  2. If the error persists, file an incident report with Micro Focus.

ERROR CODE: 144

Source: ZENworks 2017; Patch Management.
Possible Cause: This error code appears if there are errors in the patch deployment script. If logging is enabled, the error is recorded in the .log file.
Action: File an incident report with Micro Focus.

ERROR CODE: 145

Source: ZENworks 2017; Patch Management.
Possible Cause: The script failed to open the registry. This issue is most probably associated with timing.
Action: Deploy the patch again.

ERROR MESSAGE: “There is an issue with checksum metadata at CDN”

Source: ZENworks 2017; Patch Management.
Possible Cause: There is a problem with not having access to the VEGA content path.
Action: Check the following URL’s and see if you can download them:

http://cache.patchlinksecure.net/PatchComponents/OSPXSet.xml

http://cache.lumension.com/patchcomponents/1f12ad89-5711-41ce-ae84-9df6487153f3/win8x64.ospx

ERROR : zman prb "<baseline_patch_name>" - java.lang.NullPointerException when trying to get the DefaultHibernateSessionManager

Source: ZENworks 2017; Patch Management.
Possible Cause: zman prb "<baseline_patch_name>" is throwing a java.lang.NullPointerException.This is being caused by code returning a null DefaultHibernateSessionManager.

The following error will be seen:.

Code: com.novell.zenworks.zman.commands.PatchHandler.patchRemoveBaseline()Line: 123 DirectServiceStoreImpl dssi = (DirectServiceStoreImpl) store;Line: 124 DefaultHibernateSessionManager dsm =(DefaultHibernateSessionManager) ((HibernateAbstractSession)dssi.getSession()).getSessionManager();Line: 125 session = dsm.openSession();StackTrace:java.lang.NullPointerException (java.lang.StackTraceElement[])[com.novell.zenworks.zman.commands.PatchHandler.patchRemoveBaseline(PatchHandler.java:125),sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method),sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57),sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43),java.lang.reflect.Method.invoke(Method.java:606),com.novell.zenworks.zman.CommandRunner.execute(CommandRunner.java:94),com.novell.zenworks.zman.ZMan.executeRunner(ZMan.java:328),com.novell.zenworks.zman.ZMan.runCommand(ZMan.java:531),com.novell.zenworks.zman.ZMan.main(ZMan.java:465),com.novell.zenworks.zman.ZManExecutor.execute(ZManExecutor.java:101),com.novell.zenworks.zman.ZManExecutor.main(ZManExecutor.java:41),sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method),sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57),sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43),java.lang.reflect.Method.invoke(Method.java:606),com.novell.zenworks.zman.ZManLoader.loadZMan(ZManLoader.java:59),com.novell.zenworks.zman.ZManLoader.main(ZManLoader.java:143)]

Action: Increase memory size as follows:

modify "JVM_STARTUP_OPTIONS=-Xms64m -Xmx128m" to"JVM_STARTUP_OPTIONS=-Xms64m -Xmx1024m" in the zman-config.properties file. The error disappears and indicates the baseline clears successfully.

Then,

  1. Assign a baseline in a group.

  2. Refresh the agent to receive the baseline.

  3. Remove the baseline on the server.

  4. Refresh agent again and notice the baseline should remain.

  5. Modify memory in the file "zman-config.properties file."

  6. Refresh the agent again.

OTHER ERROR CODES

Source: ZENworks 2017; Patch Management.
Action: Contact Micro Focus Support.