none
Forefront Protection 2010 for Exchange - Download of Wormlist failed.

    Question

  • Starting this morning we started getting failures downloading the Wormlist engine updates.  We also get an error across all our transport servers that try to redistribute the update: Microsoft Forefront Protection encountered an error while performing a scan engine update.

    I know this engine hasn't been updated since 8/10/2012, but these errors are new.  I remember something like this happening about a year ago when Microsoft's update servers had an issue and it cleared up on its own.  Is anyone else seeing this?

    Thanks,
    Bryan

    Saturday, September 14, 2013 10:42 PM

Answers

  • Hi All,

    The next attempt for a Wormlist update should address this issue.  This update attempt can be done manually or you can wait until the next scheduled Wormlist update attempt.  This was only a cosmetic error as there were no new updates for the Wormlist over the past few days. 

    Sorry for the inconvenience and churn on errors/notifications regarding this.

    Thanks,

    -Ryan

    Monday, September 16, 2013 5:02 PM

All replies

  • Yes, we're getting the same errors every hour on both of our HUB servers.  Manual update of the wormlist engine fails and going to the http://forefrontdl.microsoft.com/server/scanengineupdate site gives a 403 error.

    Sunday, September 15, 2013 1:15 AM
  • Hello!

    We have been getting the same since 4am (+4 GMT) today.

    Subject: Microsoft Forefront Protection for Exchange Server failed to update the WormList scan engine on server xxx

    Microsoft Forefront Protection encountered an error while performing a scan engine update.

       Scan Engine: WormList

       Update Path: http://forefrontdl.microsoft.com/server/scanengineupdate

    Microsoft Forefront Protection encountered an error while performing a scan engine update.
       Scan Engine: WormList
       Update Path: http://forefrontdl.microsoft.com/server/scanengineupdate
       Error Detail: An error occurred while processing the universal manifest.

    Sunday, September 15, 2013 5:08 AM
  • Hello,

    We have been getting the same since yesterday

    Microsoft Forefront Protection encountered an error while performing a scan engine update.

       Scan Engine: WormList

       Update Path: http://forefrontdl.microsoft.com/server/scanengineupdate

    Please help !!
    Sunday, September 15, 2013 8:44 AM
  • We have been getting the same:

    Sent: 14 september 2013 02:02 (UTC+01:00)
    Subject: Microsoft Forefront Protection for Exchange Server failed to update the WormList scan engine on server xx

    Microsoft Forefront Protection encountered an error while performing a scan engine update.

       Scan Engine: WormList

       Update Path: http://forefrontdl.microsoft.com/server/scanengineupdate

    Regards

    Linda

    Sunday, September 15, 2013 12:31 PM
  • Same error here since 9/13/2013 8pm ET. Problem still unsolved 9/15/2013 10:40am ET.
    Sunday, September 15, 2013 2:40 PM
  • Same here started 09-13-2013 at 8PM ET (7PM was fine).

    Sunday, September 15, 2013 5:36 PM
  • same here across all of my Exchange Servers. Something broke on MS side.
    Monday, September 16, 2013 3:29 AM
  • Hello,

    I have the same issue that it starts from 14.09.2013 2.06 AM.

    I found an Hot Fix that he tells about this issue.

    Hot Fix was last reviewed at May 11, 2011 but maybe MS change some on it servers and now we have problems.

    Hot Fix link: http://support.microsoft.com/kb/2538719/pl

    If anybody install it and it will work please wrote to me.

    Regards

    Krzysztof. 

    Monday, September 16, 2013 5:37 AM
  • I'm also experiencing the same problem.  Never had the errors before just a little bit ago. 

    Thanks for starting the topic as I was wondering if anyone else had the issue.

    Monday, September 16, 2013 5:46 AM
  • We are experiencing the same error regarding the Wormlist on all of our Exchange servers.

    Problem started 2013-09-14 02:05.

    //Markus

    Monday, September 16, 2013 6:56 AM
  • Yep, I'm also seeing this error with exactly the same symptoms.

    Issue still going on as of 16/09/13 08:21 GMT.


    Darren

    Monday, September 16, 2013 7:12 AM
  • Same here on both HUB's & EDGE's...
    Monday, September 16, 2013 8:08 AM
  • I've just checked my hub transport and I'm getting this worm list update error as well.

    Simon

    Monday, September 16, 2013 8:30 AM
  • Same issue here, started Sep 14, 3:00pm (UTC+01:00).

    Is Microsoft aware of this?

    Regards,

    Marco

    Monday, September 16, 2013 8:50 AM
  • yes we are facing same problem with WORMLIST

    Anthony Y

    Monday, September 16, 2013 10:50 AM
  • Same problem here starting on 9/13. Where's MS at?
    Monday, September 16, 2013 11:39 AM
  • Anyone have a fix form MS on this yet?  All my systems are reporting this since 9/13.
    Monday, September 16, 2013 12:16 PM
  • Yes, have the same problem here.  Obviously a problem on the MS side.
    Monday, September 16, 2013 12:23 PM
  • Has anyone on this tread contacted MS support on the issue?
    Monday, September 16, 2013 1:18 PM
  • Hi, we are seeing Microsoft Forefront Protection for Exchange is alerting saying the below;

    Microsoft Forefront Protection encountered an error while performing a scan engine update.

       Scan Engine: WormList

       Update Path: http://forefrontdl.microsoft.com/server/scanengineupdate

    Checked the event logs and found event 6020 getting logged with the below details;

    Log Name:      Application
    Source:        GetEngineFiles
    Date:          9/16/2013 6:36:32 PM
    Event ID:      6020
    Task Category: Engine Error
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Exchange CAS and HUB server name FQDN
    Description:
    Microsoft Forefront Protection encountered an error while performing a scan engine update.
       Scan Engine: WormList
       Update Path: http://forefrontdl.microsoft.com/server/scanengineupdate
       Error Detail: An error occurred while processing the universal manifest.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="GetEngineFiles" />
        <EventID Qualifiers="49152">6020</EventID>
        <Level>2</Level>
        <Task>6</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-09-16T13:06:32.000000000Z" />
        <EventRecordID>3663730</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Exchange CAS and HUB server name FQDN</Computer>
        <Security />
      </System>
      <EventData>
        <Data>WormList</Data>
        <Data>http://forefrontdl.microsoft.com/server/scanengineupdate</Data>
        <Data>An error occurred while processing the universal manifest.</Data>
      </EventData>
    </Event>

    Please let us know whether anybody else also facing this problem which we can suspect a problem at the Microsoft-end as happened before. Also searched the net and found none has reported this problem recently. This problem started from Saturday 14th September 2013 5:30 PM IST.

    This failure is happening in all our Forefront running servers across different locations.

    Rgds, Guru.

    Monday, September 16, 2013 1:20 PM
  • We are also facing this problem.  The problem was first noticed at 9/13/2013 7:23 PM CDT and is occurring on each of our Forefront installations every hour.

    Monday, September 16, 2013 2:06 PM
  • We are also having the same problem updating the WormList across the board.  Searching for a solution...

    Adam

    Monday, September 16, 2013 2:19 PM
  • Same Problem here:

    I have setup some additional Exchange 2010 servers (SP3-RU2), but Forefront is not able to update WormList

    Microsoft Forefront Protection encountered an error while performing a scan engine update.

       Scan Engine: WormList
       Update Path: http://forefrontdl.microsoft.com/server/scanengineupdate
       Error Detail: An error occurred while processing the universal manifest.

    As my older Exchange 2010 servers are showing the same results


    Michel

    Monday, September 16, 2013 2:20 PM
  • My experience in the past has been the first thing they want is a Credit Card number (even though they won't charge you if it turns out to be a bug, or something wrong on their end).  I have not been successful in getting my employer to give me access to a credit card, even if I try to promise them we won't be charged cause I am sure it's a bug.  So, I cannot call.  I really wish they had a way of logging issues for things like this without asking for a credit card number.

    • Edited by LE2Strat Monday, September 16, 2013 2:26 PM
    Monday, September 16, 2013 2:24 PM
  • We're seeing this as well on our HUB servers.

    Orange County District Attorney

    Monday, September 16, 2013 2:26 PM
  • Same here:

    Microsoft Forefront Protection encountered an error while performing a scan engine update.

       Scan Engine: WormList

       Update Path: http://forefrontdl.microsoft.com/server/scanengineupdate

    Hopefully MS is monitoring this forum and will respond.


    Dave Zuver Davis Wright Tremaine Seattle, WA

    Monday, September 16, 2013 2:54 PM
  • ok, just submitted a level B support case on our premier support site.  Let's see if they can find the developers for this product, since they are kicking to the curb.
    Monday, September 16, 2013 3:04 PM
  • So I just received a call back on the support ticket and was told that MS is aware of the issue and is working to correct the problem.  I was told the ETA is a day or two.  Not a very acceptible ETA, in my opinion.  This engine has not been updated in some time so not a big lose, just sucks on the constaint error e-mails I get for update failures.  They tole me to disable the download if I wanted to stop the messages, but do not feel like doing that on all of my systems. My case is still open so he is suppose to update me when there is a fix.

    Monday, September 16, 2013 3:31 PM
  • exactly same issue here since Firday (13th September 2013) any News about this ?
    Monday, September 16, 2013 3:33 PM
  • We are having the same issue with the scan engine for WormList.  I am getting a 403 - forbidden: access is denied when going directly here: http://forefrontdl.microsoft.com/server/scanengineupdate/.

    Anybody else?

    Monday, September 16, 2013 3:53 PM
  • Same exact issue here.

    Anyone from Microsoft watching this?

    Monday, September 16, 2013 4:03 PM
  • Same issue here as well.  Very annoying.  Exchange 2010 with Forefront for Exchange on two CAS servers.
    Monday, September 16, 2013 4:32 PM
  • Hi All,

    The next attempt for a Wormlist update should address this issue.  This update attempt can be done manually or you can wait until the next scheduled Wormlist update attempt.  This was only a cosmetic error as there were no new updates for the Wormlist over the past few days. 

    Sorry for the inconvenience and churn on errors/notifications regarding this.

    Thanks,

    -Ryan

    Monday, September 16, 2013 5:02 PM
  • Works like a charm again, thanks for fixing!
    Monday, September 16, 2013 5:07 PM
  • Same here.  I'm using a SBS 2011, which is using Exchange 2010.

    I do remember that in the past that one of the sub-list that Forefront used went "Out of business" and you would get an error when it fried to update.

    Not sure if this might be the same issue.  Maybe the subscription partner that Forefront uses for the "WORM LIST" went under.

    The solution before was to change the setting from AUTO to MANUALLY and uncheck the unsupported list.

    But I can not confirm that this is the issue this time with the WORM LIST.

    Monday, September 16, 2013 5:17 PM
  • It is back up. Thanks for fixing the issue.

    Monday, September 16, 2013 5:19 PM
  • MICROSOFT must answer, please.
    Monday, September 16, 2013 6:10 PM
  • Same here.
    Monday, September 16, 2013 6:59 PM
  • it is working again, since 2,5 hours ago it was updates again...

    Michel

    Monday, September 16, 2013 8:30 PM
  • Started working. Had even tried manually but failed. Seems temporary issue but shouldn't be for so long, 3 days.

    Thanks and Rgds,

    Guru.

    Tuesday, September 17, 2013 6:26 AM