5 Replies Latest reply on May 18, 2009 3:09 AM by rhythm_methods

    Master Repository is not updating

      Hello,

      we have implemented new mcafee servre ePO4.0 patch 4 and set all configuration in the past 2 days. However the Master Repository status is not updtated ?


      did I miss some configuration? please advice.
        • 1. RE: Master Repository is not updating
          Laszlo G
          Have you created the automated server task to update your master repository daily?
          If so, when you go to the software section and click on extract now does it work?
          • 2. RE: Master Repository is not updating
            On the Automation Tab - Server Tasks - I have Update Master Repository task to run reporsitory pull ever 4 hours.

            then I went to Software - and click on Pull Now- it was completed successfully.

            but still not update on the Master reporitory status.


            it is showing the following;

            Master Repository Status
            No Information Avilable

            The latest MyAvert information was not successfully retrieved from McAfee

            My Repository Latest Available
            DAT: 5617.0000 --
            Engine: 5301.4018 --
            64-Bit DAT 5617.0000 --
            64-Bit Engine 5301.4018 --

            MyAvert Security Threats: 0 unread

            Last check: Unknown
            • 3. RE: Master Repository is not updating
              Hi,

              Don't worry about that.

              Your repository is updating fine, so long as you are seeeing the DAT and Engine numbers.
              Everything will be pulled ok.

              The issue you are actually seeing is only that the MyAvert information is not getting downloaded.
              This is actually a different issue which is not something that will cause any issue for you.
              The updates are still being pulled fine.

              To fix the myavert issue, though it's pretty much a non issue, you may need to change some proxy settings or firewall settings so that you can get to the MyAvert website to get the info.

              The first check is to see if you can get to the myavert website by putting the url in directly to a browser on the server.

              I think this is actually a bug in ePO 4, many people get this, McAfee released an article a while back saying that the issue will be fixed in ePO 4.5

              The main thing is that it doesn't mean anything is wrong with your setup and doesn't stop repository pulls from working (it's actually a different thing altogether) it's just that the MyAvert information is compared with what's in your repository in the same pane of the dashboard.

              oh yea, the URL, see if you can go to http://myavert.avertlabs.com:8801/reportservice.asmx
              That is the first check.

              If you can't get to that website from the server, then that's step one, make sure you can get there.

              If you can get to that website but the info is still not pulled down, then there is more steps you can take to get it to work, though it can get very involved with chaning proxy configs etc and stuff :)

              Just see if you can get to that myavert url to start with anyway, it could be that simple for you,

              This article does not show how to fix this KB53619 but at least shows you that it's a common thing people face, really, it's almost not worth worrying about it too much.


              -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- -----

              Corporate KnowledgeBase ID: KB53619
              Published: April 30, 2009

              Environment
              Microsoft Internet Security and Acceleration (ISA) Server
              Microsoft Windows (All supported versions. See KB51109)
              Problem 1
              The Master Repository Status dashboard displays the DAT and Engine currently in the repository under "My Repository". The section under "Latest Available" contains no data, also MyAvert Security Threats displays 0 unread.

              Correct authentication details to access the proxy was stored in the ePO console under Configuration => Server Settings => MyAvertSecurity Threats

              Accessing the service by copying the URL http://myavert.avertlabs.com:8801/reportservice.asmx?wsdl into a IE browser windows works without problems and also verifies that port 8801 is open which is a requirement for the MyAvert Service to work properly.

              Problem 2
              The Orion.log records the following errors:
              ERROR [pool-5-thread-1] httpclient.HttpMethodDirector - Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernamePasswordCredentials
              org.apache.commons.httpclient.auth.InvalidCredentialsException: Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernamePasswordCredentials

              INFO [pool-5-thread-1] httpclient.HttpMethodDirector - Failure authenticating with NTLM <any realm>@<Proxy IP>:<Proxyport>

              ERROR [pool-5-thread-1] cmd.CommandInvoker - Error invoking command:AvertAlerts.Web.Service
              java.io.IOException: POST Command got unexpected HTTP Status:407

              ERROR [pool-5-thread-1] daemon.AvertService - Exception while executing the AvertAlerts command: POST Command got unexpected HTTP Status:407


              Problem 3
              Web server proxy logs shows anonymous being used and not the Domain\User account credentials:
              cs-username sc-authenticated r-host cs-protocol cs-transport sc-status
              anonymous Commons-HttpClient/3.0.1 N myavert.avertlabs.com http TCP 407
              anonymous Commons-HttpClient/3.0.1 N myavert.avertlabs.com http TCP 407

              Solution
              Due to the complexity of the code change involved, this issue will be addressed in ePO 4.5.

              ePO 4.5 is tentatively scheduled for release by the end of Q2 2009.
              Previous Document ID
              616483
              • 4. RE: Master Repository is not updating
                Thanks a lot happy
                • 5. RE: Master Repository is not updating
                  No problemo happy