ERROR CODE: ERROR = 40
ERROR CODE: PPX_ERROR_PATCH_MORE_THAN_MAXAPPLICABLE SIGS = 45
ERROR CODE: PPX_ERROR_ARCHIVE_EXTRACT = 2
Make sure that CABARC runs on the end point where the error message appears.
Check the available disk space on the end point.
Re-cache the patch to the ZCM Server.
If the issue persists, contact Micro Focus Support.
ERROR CODE: PPX_ERROR_PACKAGE_ARCHIVE_INITIALIZE = 8
ERROR CODE: PPX_ERROR_EXTRACT_FILE = 20
ERROR CODE: PPX_ERROR_PACKAGE_REIMPORT = 40
ERROR CODE: PPX_ERROR_EXPIRED_LICENSE_KEY = 27
ERROR CODE: PPX_ERROR_VARIABLE_CACHE_EXHAUSTED = 1
ERROR CODE: PPX_ERROR_PATCH_OPEN_FAILURE = 3
ERROR CODE: PPX_ERROR_PATCH_BAD_GUID = 4
ERROR CODE: PPX_ERROR_PATCH_MANY_APPLICABLE_SIGNATURES = 5
ERROR CODE: PPX_ERROR_PATCH_OPEN_FAILURE = 6
ERROR CODE: PPX_ERROR_PATCH_BAD_GUID = 7
ERROR CODE: PPX_ERROR_PATCH_OPEN_FAILURE = 9
ERROR CODE: PPX_ERROR_PATCH_BAD_GUID = 10
ERROR CODE: PPX_ERROR_PATCH_OPEN_FAILURE = 11
ERROR CODE: PPX_ERROR_PATCH_BAD_GUID = 12
ERROR CODE: PPX_ERROR_SIGNATURE_PREREQ_CACHE_EXHAUSTED = 13
ERROR CODE: PPX_ERROR_PATCH_OPEN_FAILURE = 14
ERROR CODE: PPX_ERROR_PATCH_BAD_GUID = 15
ERROR CODE: PPX_ERROR_FINGERPRINT_EXPRESSION_SYNTAX = 16
ERROR CODE: PPX_ERROR_FINGERPRINT_FILEROOT_UNSUPPORTED = 17
ERROR CODE: PPX_ERROR_FINGERPRINT_TYPE_UNSUPPORTED = 18
ERROR CODE: PPX_ERROR_SCRIPT_BAD_FILEHANDLE = 19
ERROR CODE: PPX_ERROR_WMI_FINGERPRINT_UNSUPPORTED = 22
ERROR CODE: PPX_ERROR_JAVASCRIPT_UNSUPPORTED = 23
ERROR CODE: PPX_ERROR_MISSING_PREREQ_SIGNATURE = 25
ERROR CODE: PPX_ERROR_INVALID_PREREQ_LANGUAGE = 26
ERROR CODE: PPX_ERROR_INVALID_ROOT_HKEY = 21
ERROR CODE: PPX_ERROR_FINGERPRINT_INVALID_SYSINFO = 31
ERROR CODE: PPX_ERROR_FINGERPRINT_EXPRESSION_MISSING_VARIABLE = 32
ERROR CODE: PPX_ERROR_FINGERPRINT_FILESCAN_UNSUPPORTED = 34
ERROR CODE: PPX_ERROR_FINGERPRINT_WMI_ERROR = 35
ERROR CODE: PPX_ERROR_RELEVANCE_SCRIPT_SYNTAX = 36
ERROR CODE: PPX_ERROR_ENTITLED_FILE_INVALID = 41
Check your Internet connection and firewall settings.
Check that the ZCM Server can access a third-party website such as the Microsoft Download Center.
Download patches from the third-party website.
Re-cache the downloaded patches.
ERROR CODE: PPX_ERROR_ENTITLED_FILE_MISSING = 28
ERROR CODE: PPX_ERROR_ENTITLED_FILE_BAD_CHECKSUM = 29
ERROR CODE: PPX_ERROR_ENTITLED_FILE_WRONG_SIZE = 30
ERROR CODE: PPX_ERROR_OUT_OF_MEMORY = 24
ERROR CODE: PPX_ERROR_PACKAGE_MKDIR_FAILURE = 33
ERROR CODE: PPX_ERROR_UNKNOWN
Open a support ticket with Lumension.
Contact Micro Focus Support.
ERROR CODE: 41
ERROR CODE: 142
ERROR CODE: 143
Redeploy the patch.
If the error persists, file an incident report with Micro Focus.
ERROR CODE: 144
ERROR CODE: 145
ERROR MESSAGE: “There is an issue with checksum metadata at CDN”
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
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)]
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,
Assign a baseline in a group.
Refresh the agent to receive the baseline.
Remove the baseline on the server.
Refresh agent again and notice the baseline should remain.
Modify memory in the file "zman-config.properties file."
Refresh the agent again.
OTHER ERROR CODES