Loading...

Knowledge Center


Updates were not applied because packages were not in the repository
Technical Articles ID:  KB55713
Last Modified:  8/2/2012
Rated:


Environment

McAfee VirusScan Enterprise 8.x
 

Problem 1

Message: These updates will be applied if they are in the repository

Problem 2

Message: Updates were not applied because packages were not in the repository

Cause

These messages are the result of the AutoUpdate configuration. In the VirusScan Enterprise (VSE) AutoUpdate configuration under Update Options. You can select which updates you want to check for:

VSE 8.8 and later
Get newer detection definition files if available
Get newer detection engine and dats if available
Get other available updates (service packs, upgrades, etc.)


VSE 8.7i and earlier

Get newer detection definition files if available.
Get newer detection engines if available.
Get other available updates (service packs, upgrade, etc.)


The default configuration has ALL items are selected. If one of these selections is removed, the above messages are shown, indicating exactly what the update process is looking for during update and what it fails to apply because the updates were not available in repository - it will list these components at the end of the message.

Example:
First Message: These updates will be applied if they are in the repository:  DAT, Engine, EXTRADAT1000, ENTVRULE1000.
 
The Engine and DAT application/verification will take place at this point
 
Second Message: Updates were not applied because packages were not in the repository:  EXTRADAT1000, ENTVRULE1000.


This means that the AutoUpdate process looked for updates for DAT, Engine, EXTRADAT1000, ENTVRULE1000 but could only find DAT and Engine update in the repository, it then reports that it did not apply EXTRDAT1000 or ENTVRULE1000 updates because they were not available. 

Solution

This is not an error message. The AutoUpdate process displays messages to record exactly what is occurring during the update session according to its configuration.

Previous Document ID

KB39149

Rate this document

Did this article resolve your issue?

Please provide any comments below

Beta Translate with

Select a desired language below to translate this page.

Glossary of Technical Terms


Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.