Troubleshooting Patch management Remediation Problems on managed agent
This document (7001089) is provided subject to the disclaimer at the end of this document.
wmic qfe list full >updateslist.txt
Bad plp file.
Bad pls file.
Bad or out of date remediate.exe file.
Compare to known good the three files above to see if there are differences in checksums. If the plp is bad, recache the patch. If the pls file is bad do "update now" of zpm to bring down proper pls files to agents. If remediate.exe is bad, verify the patch agent files bundle. If necessary follow TID https://www.novell.com/support/search.do?usemicrosite=true&searchString=7011751to bring down the patch agent files again.
|Error|| Error Code
|PPX_ERROR_VARIABLE_CACHE_EXHAUSTED||1||Patch signature expression was too complex to be evaluated|
|PPX_ERROR_ARCHIVE_EXTRACT||2||Patch .PLS / .PLP file could not be extracted|
|PPX_ERROR_PATCH_OPEN_FAILURE||3||Unable to open patch definition data|
|PPX_ERROR_PATCH_BAD_GUID||4||Patch signature data was corrupt within the .PLS file|
|PPX_ERROR_PATCH_MANY_APPLICABLE_SIGNATURES||5||Patch signature has more than one applicable signature|
|PPX_ERROR_PACKAGE_OPEN_FAILURE||6||Unable to open package definition data|
|PPX_ERROR_PACKAGE_BAD_GUID||7||Package data was corrupt within the .PLS file|
|PPX_ERROR_PACKAGE_ARCHIVE_INITIALIZE||8||Package file could not be used, may be corrupt or missing|
|PPX_ERROR_FILEINFO_OPEN_FAILURE||9||Unable to open file information definition data|
|PPX_ERROR_FILEINFO_BAD_GUID||10||File information data was corrupt within the .PLS file|
|PPX_ERROR_SIGNATURE_OPEN_FAILURE||11||Unable to open signature definition data|
|PPX_ERROR_SIGNATURE_BAD_GUID||12||Signature definition data was corrupt within the .PLS file|
|PPX_ERROR_SIGNATURE_PREREQ_CACHE_EXHAUSTED||13||Patch prerequisites were too complex to be evaluated|
|PPX_ERROR_FINGERPRINT_OPEN_FAILURE||14||Unable to open fingerprint definition data|
|PPX_ERROR_FINGERPRINT_BAD_GUID||15||Fingerprint definition data was corrupt within the .PLS file|
|PPX_ERROR_FINGERPRINT_EXPRESSION_SYNTAX||16||Expression fingerprint type contains a syntax error|
|PPX_ERROR_FINGERPRINT_FILEROOT_UNSUPPORTED||17||File fingerprint type does not support the <root> syntax|
|PPX_ERROR_FINGERPRINT_TYPE_UNSUPPORTED||18||Fingerprint type is not supported on this platform|
|PPX_ERROR_SCRIPT_BAD_FILEHANDLE||19||Patch installation script could not be run|
|PPX_ERROR_EXTRACT_FILE||20||Unable to extract package file(s)|
|PPX_ERROR_INVALID_ROOT_HKEY||21||The <root> key specified was invalid|
|PPX_ERROR_WMI_FINGERPRINT_UNSUPPORTED||22||WMI fingerprint type is not supported|
|PPX_ERROR_OUT_OF_MEMORY||24||Out of memory|
|PPX_ERROR_EXPIRED_LICENSE_KEY||27||(Note the most likely cause for this is a missing or invalid, .PLK file)|
|PPX_ERROR_ENTITLED_FILE_MISSING||28||"Entitled" patch files were not provided to the Deploy method|
|PPX_ERROR_ENTITLED_FILE_BAD_CHECKSUM||29||"Entitled" files were not correct, may have been corrupted|
|PPX_ERROR_PACKAGE_REIMPORT||40||This means that cabarc could not unpackage the file - make sure cabarc is accessible|
||remediate.exe is attempting to run a script from a deployed patch bundle and failing, or from an action inside the patch bundle that is running a script and failing. The error should be printed in the corresponding .txt file associated with this patch and in the Windows Application event logs. Also if present look for system temp folder patch-player* logs.|
|145||same as error 144 except that it failed to open the registry to print the script error to the .txt file.|
|200||another instance of remediate is running|
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7001089
- Creation Date:04-AUG-08
- Modified Date:09-NOV-17
- NovellZENworks Configuration ManagementZENworks Patch Management
Did this document solve your problem? Provide Feedback