Knowledge Center

Unable to find a valid repository (when downloading SiteStat.xml)
Technical Articles ID:   KB54474
Last Modified:  4/7/2017


McAfee VirusScan Enterprise (VSE) 8.x


The ePO scheduled update task, or local VSE 8.x update, fails and you see the following entries in the agent_<computer_name>.log file:

Unable to find a valid repository


The VSE 8.x AutoUpdate action fails to initiate an update session with a repository.


Updates or deployments fail and you see the following entries in the agent_<computer_name>.log file:
Error occurred while downloading the file SiteStat.xml
Error downloading the file CommonUpdater/SiteStat.xml, nainet GetLastError() = 4


SiteStat.xml is the first file the update process looks for. SiteStat.xml is used to validate the repository is correct and updated. Although there might be several causes for this error, most often there is some type of connectivity issue between the client and the repository it is attempting to access.


Troubleshooting a connection with a proxy server
Proxy servers such as Microsoft ISA Server often require authentication. By default, VSE attempts to use Internet Explorer proxy settings. However, this is sometimes insufficient.

To establish if a proxy server is in use
  1. Launch Internet Explorer.
  2. Click Tools, Internet Options.
  3. Select Connections, LAN Settings.

If any details are present in the proxy section, make a note of these.

To manually configure proxy settings and authentication for VSE

  1. Open the VSE 8.x console:

    For VSE 8.x, click Start, Programs, McAfee, VirusScan Console
  2. Select ToolsEdit AutoUpdate Repository List.
  3. Select the Proxy settings tab in the Repository List menu.
  4. Select Manually configure the proxy settings.
  5. Do the following to configure the settings for each required protocol (HTTP and FTP):
    1. Type the IP Address (or the host name) of the proxy server and press TAB.
    2. Type the Port number that the proxy server listens on.
    3. Select Use authentication.
    4. Type the user name in the following format:


      (where DomainName is the domain where the user account resides)
    5. Type the password and press TAB.
    6. To confirm, type the password again, then click OK.


Troubleshooting issues with a UNC repository
  1. Click Start, Run, type the full UNC path in the following format and press ENTER.

  2. Confirm the following files are present:
    • SiteStat.xml
    • catalog.z
    • Current (folder)
NOTE: If the folder opens but these files are missing, the issue lies with the process or application that is responsible for populating this repository. If the folder does not open, the repository might not exist or the logged on user might not have the correct read permissions to access the share.
To set the permissions:
  1. Open the VSE 8.x console:

    For VSE 8.x, click Start, Programs, McAfee, VirusScan Console

    Select Tools, Edit AutoUpdate Repository List.
  1. Select the appropriate repository from the list, then click Edit.
  2. Ensure that the UNC path is correct.
  3. You can select the Use logged-on user option if the update will take place when a user is logged on to the computer and the user has the correct permissions.

    If reliance on a logged on user is not appropriate, then deselect this option and type a user account with the correct permissions.


A verbose log file is available to assist troubleshooting.
Default location:  C:\Documents and Settings\All Users\Application Data\Network Associates\Common Framework\Db
Filename: agent_<computer_name>.log
  (where <computer_name> is the hostname of the computer where the update is being initiated)
The log has a time-date stamp on the left. If an update has recently been attempted, this is recorded in the last 20 to 100 lines of the log.


The content of this article originated in English. If there are differences between the English content and its translation, the English content is always the most accurate. Some of this content has been provided using Machine Translation translated by Microsoft.

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.