1 2 3 4 Previous Next 35 Replies Latest reply on Feb 26, 2009 3:24 PM by jeet.sharma

    Pull tasks for the 5529 DATs fail in ePolicy Orchestrator

      hello guys,
      we currently have a problem with our test epo 4.x server installation.

      yesterday we installed a server and all updates from update.nai.com looks fine.
      today all updates failed (since 08:00 am (GMT))!

      we got the following error:

      mcafee http 2009-02-18 14:38:28.5 error
      fehler beim herunterladen der datei "Current\VSCANDAT1000\DAT\0000\55285529.upd" von der site "update.nai.com:80". fehlercode: 0

      can everyone verify this problem? same problem also with ftp...

      thx
      christian
        • 1. RE: Pull tasks for the 5529 DATs fail in ePolicy Orchestrator
          I have the same problem...

          Current\VSCANDAT1000\DAT\0000\55285529.upd del sitio update.nai.com:80, código de error 10060 ( A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. )

          any idea whats hapening?
          • 2. RE: Pull tasks for the 5529 DATs fail in ePolicy Orchestrator
            twenden
            McAfee has just posted a knowledge base article to address this issue:

            Corporate KnowledgeBase
            Pull tasks for the 5529 DATs fail in ePolicy Orchestrator

            Corporate KnowledgeBase ID: KB60644
            Published: February 18, 2009

            Environment
            Microsoft Windows (All supported versions. See KB51109)
            Microsoft Exchange 2000/2003
            Microsoft SharePoint PortalServer
            Microsoft Windows ISA Server
            IBM Lotus Domino
            Novell NetWare
            Linux
            Mac OS X
            Summary
            The majority of customers using McAfee ePolicy Orchestrator (ePO) will encounter an error during a pull task of the 5529 DATs from McAfee.

            This is due to a problem with the V1 5529 incremental update file, which has now been removed from all McAfee download sites. As a result, yesterday's DAT update is not available to the majority of customers and the error detailed in the following problem sections will be seen.

            NOTE: Customers who have successfully pulled the 5529 DAT package prior to removal of the UPD will experience increased network usage during replication to distributed repositories and to V1 clients performing updates.
            Video Tutorial

            Problem 1

            In the ePO 4 server task log, the pull task will fail with a status of Failed. If the log entry is clicked to see further details, a Failed to download file error is visible.

            On examining the ePOApSvr.log, messages similar to the following are visible:

            I #4256 SIM_InetMgr Download file 55285529.upd failed in session 1, nainet ret=0
            e #4256 SiteMgr CheckInMirrorPackage: Download file 55285529.upd from site McAfeeHttp::Current\VSCANDAT1000\DAT\0000 failed, hr=-2147467259
            Problem 2

            In the ePO 3.6.1 server task log, the pull task will fail with a status of Failed. If the log entry is expanded to see further details, the following error is visible: Failed to download file Current\VSCANDAT1000\DAT\0000\55285529.upd from site update.nai.com.

            On examining the ePOApSvr.log, messages similar to the following are visible:

            I #4256 SIM_InetMgr Download file 55285529.upd failed in session 1, nainet ret=0
            e #4256 SiteMgr CheckInMirrorPackage: Download file 55285529.upd from site McAfeeHttp::Current\VSCANDAT1000\DAT\0000 failed, hr=-2147467259
            System Change

            Cause
            The V1 5529 incremental (55285529.upd) is of an excessive (61MB) size and has been removed from the download sites. As the file has been removed, the pull task will fail.
            Solution
            The problematic file has been removed from the McAfee download sites.
            Workaround
            To prevent experiencing excessive network usage on account of the 5529 DATs, disable the replication tasks. If replication to clients is occurring then in ePO 4.0 terminate the task or in ePO 3.6 the ePO Application Server Service has to be stopped. If you want to prevent v1 clients from updating, delete the 5529 DAT package. (This prevents all v1 and v2 clients from updating.)
            Related Information

            Customers updating directly from McAfee will successfully update, but for the following products excessive bandwidth usage may be seen as the update will be pulling the complete 5529 zip file. This is currently a 75 MB file:
            VirusScan API 1.0
            VS Online/Retail 10.0
            VSC 4.5.1sp1
            VirusScan Enterprise 8.0i
            VirusScan Enterprise 7.1 for NetApp
            GroupShield for Exchange 6.02
            GroupShield for Exchange 6.03
            GroupShield for Domino for NT 5.2.1
            GroupShield for Domino for NT 5.3
            GroupShield for Domino for AIX 5.2.1
            GroupShield for Domino for SOL 5.2.1
            PortalShield Version 1.0.1
            LinuxShield Version 1.3 32-bit
            LinuxShield Version 1.3 64-bit
            LinuxShield Version 1.4 32-bit
            LinuxShield Version 1.4 64-bit
            MAS 1.5
            Netware 4.6.3 Novell 6.5 SP4
            WebShield Appliance Version 3
            WebShield Appliance Version 4
            Blade 4.6
            SecurityShield Version 1.0
            Virex 7.7
            VirusScan for Mac 8.5
            WebShield SMTP Version MR2

            Consumer products impacted by this incremental are the following. These products are getting the incremental file.
            VSO AOL
            Freeescan 2.2
            Mailscan 1.0.0.6

            NOTE: This KnowledgeBase article will be updated when further information is available.
            • 3. RE: Pull tasks for the 5529 DATs fail in ePolicy Orchestrator
              Hi,

              Having the exact same problems since this morning, I've tracked the error down to (atleast I think) a Mcafee problem. checking the update site, the specific file mentioned in the error (the first file that EPO will try to download) is currently not accessible. Trying to directly download it results in "Access denied".

              I get the error on our EPO 3.6 server.

              Seems the FTP update is also not functioning atm. This has happend once before as I recall, it was fixed within a day.

              /P
              • 4. RE: Pull tasks for the 5529 DATs fail in ePolicy Orchestrator
                Hah, well that explains it, and the 60MB file i suppose :)

                /P
                • 5. RE: Pull tasks for the 5529 DATs fail in ePolicy Orchestrator
                  Edit...

                  sorry i just read the post, well downlading dat-5529.zip :)

                  thx for the answer master.
                  • 6. RE: Pull tasks for the 5529 DATs fail in ePolicy Orchestrator
                    61mb incremental update - ouch!! Then again it matches their dat-xxx.zip file sizes.
                    • 7. RE: Pull tasks for the 5529 DATs fail in ePolicy Orchestrator
                      ok, when we try to update, we get the error:

                      McAfeeHttp 2009-02-18 15:11:01.357 ERROR Fehler beim Herunterladen der Datei "Current\VSCANDAT1000\DAT\0000\55285529.upd" von der Site "update.nai.com:80". Fehlercode: 0

                      -

                      how we can fix this issue on the epo server?
                      or repair mcafee this problem, that we can update "normally" the epo tomorrow?
                      • 8. RE: Pull tasks for the 5529 DATs fail in ePolicy Orchestrator
                        tonyb99



                        read the article that twenden posted earlier on this thread.

                        they screwed up the upd, it will be fixed tomorrow. in the meantime switch off the pull.
                        • 9. RE: Pull tasks for the 5529 DATs fail in ePolicy Orchestrator
                          nothing you can do about it Magnoc, this should be fixed by McAfee shortly. If not today, by tomorrow with the incrimental update that will get distrobuted then.

                          Atleast, that's my guess.

                          /P
                          1 2 3 4 Previous Next