Administration Guide › Subscription › Self-Monitoring Events for Subscription › Subscription Event Failures and Warnings › Update File for component – <CompName> not found in the Proxy Server. Hence it is not downloaded to the Client for installation !!!

Previous Topic: The capacity of the disk space in the <temp download path> path - <pathName> has exceeded the limit of 90 %. Please free up some disk space. Hence the updates could not be downloaded from Proxy to client !!!

Next Topic: Updates for Component – <CompName> is applicable for versions higher than or equal to <CompVersionApplicableTo>. Current version of the component on the client is <CurrentVersion>. Hence this update is not applicable

Update File for component – <CompName> not found in the Proxy Server. Hence it is not downloaded to the Client for installation !!!

Reason:

The subscription client cannot download the update file for the component named in the message because it is not available from the configured subscription proxy server. This can occur when the update file has been manually deleted or the file has exceeded the age in days configured for "Cleanup updates older than."

Note: Be sure that this subscription client has a configured update schedule and is left running so that no updates are missed. The proxy retains updates only for the number of days configured for "Cleanup updates older than", a global subscription setting.

Action:

Identify a subscription proxy that still has the module containing the needed component, CompName. Copy the subscription directories from this proxy to this client's subscription proxy. Use the procedure described for updating an offline proxy from an online proxy as a guide.

Note: It is important to copy the directories recursively because CompName is composed of multiple files and this process ensures that all required files are available.