ZPM 0x0000190C error when running DAU

  • 3280189
  • 29-Jun-2007
  • 30-Apr-2012

Environment

Novell ZENworks Patch Management 6.3 - ZPM6.3
Novell ZENworks Patch Management 6.4 - ZPM6.4

Situation

Discover Applicable Updates (DAU) does not run successfully after an upgrade of the agent, and fails with error 0x0000190C (190C)

Resolution

The most common failure, this error indicates the Update Agent encountered a problem executing the script associated with the deployment or the Windows Installer returned a generic 1603 installation failure.

The most common reason for a script failure is the operating system has not registered the wshom.ocx or vbscript components. Re-registering wshom.ocx on the machine in question will typically solve this, typed from a Run or CMD prompt or deployed through a Custom Package (use the -s switch in the command line of a Custom package to hide the notification message from the End-User):

    regsvr32 wshom.ocx

If the preceding registration does not solve the behavior, you may also re-register vbscript:

    regsvr32 vbscript

If a generic Windows Installer 1603 error is encountered during script execution, you may also receive a 190C. This may be caused by lack of available disk space, permissions issues, missing files, missing prerequisites, or other OS-related issues. To determine root cause, attempt the Manual Deployment method explained below.

Manual Deployment (-pldo)

To determine the reason for a Windows Installer failure, deploying the package using the -pldo option within ZPM Update is a solution that will yield more detail. To deploy with -pldo, click the Edit icon in the Package Deployment Order and Behavior page of the Deployment Wizard and replace the Optional Flags with:

    -pldo

Once deployed, this option will leave the package in the %TEMP% location (e.g., C:\WINDOWS\TEMP) where you may then execute the package manually. In most cases, the error encountered will explain in detail the reason for the MSI failure, allowing you to correct the OS or Program-related issue.

An alternative to deploying the package through ZPM Update is to visit the Microsoft KB article associated with the vulnerability in question, downloading, and then executing the patch on the end-point.

See
PatchLink KB article 591 for more information on 190 errors.

Change Log

14-Oct-2009  tgordon  updated the resolution section and updated the link to the Patchlink Knowledgebase article.

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