Patch Deployments fail with 190D

Description

Applies To: Prism Patch Manager version 6.4.

Symptom

Deployments fail with 190D.

Cause

This is caused by a reset of the UpdateStorage location in the registry of the Prism Patch Manager Server using the LOCAL_DNS_HOSTNAME stored in the PLUS database during the upgrade process. If the LOCAL_DNS_HOSTNAME is a location unreachable by the agents in the environment or a location that causes a PatchLink Update Web Site SSL certificate to mismatch, agents will be unable to download packages stored in the UpdateStorage directory.

Resolution

1. On the Prism Patch Manager Server, open the registry and go to the following key:
   HKEY_LOCAL_MACHINE\SOFTWARE\PatchLink.com\Update\ISAPI\STORAGE1
    
2. Within this key, an entry will be listed for "Server" that points the agent to the UpdateStorage directory. Change this registry value to match your SSL certificate. Example:
   https://PLUSNAME.DOMAIN.COM/UpdateStorage/%A%/%P%/
   where PLUS.DOMAIN.COM is the name of the Update Server specified in the SSL certificate.
    
3. Restart IIS by opening a CMD Prompt and running IISRESET.

Note: If you are using Distribution Points for the caching of packages in your environment, it is recommended that http:// is used within the UpdateStorage string instead of https://. By design, caching proxies are unable to cache encrypted content, thus binaries downloaded via HTTPS will be ignored instead of cached. Also note this will only work if port 80 traffic is not blocked in your secure environment.