none
Error ID 6027 - MS Filtering Engine Update process was unsuccessful in contacting the Primary Update Path. Update Path: http://forefrontdl.microsoft.com/server/scanengineupdate

    Question

  • Hello. 

    I have an installation of Exchange 2013 SP1, and since a few days I continually receive this error message.

    MS Filtering Engine Update process was unsuccessful in contacting the Primary Update Path. Update Path: http://forefrontdl.microsoft.com/server/scanengineupdate

    Any solution?

    Thanks.


    MCSA: Windows Server 2008

    Wednesday, May 21, 2014 5:21 AM

Answers

  • The problem was caused by permissions "network services". My installation of exchange is in a separate hard drive (drive E :). I checked in the event viewer the error was associated with the "user" "network service". 

    I have found that adding "network service" to local Administrators group solves the problem after rebooting. 

    It seems it was a problem of access permissions to an executable file or folder. Now I would like to define the necessary permissions to remove the administrator group user "network service". 

    Greetings and thanks for the help.

    MCSA: Windows Server 2008

    • Marked as answer by Cimmerio Friday, May 23, 2014 9:52 AM
    Friday, May 23, 2014 9:52 AM

All replies

  • HI 

    That is the anti-malware update, and it cannot connect to the server to download the files. A proxy or other firewall restriction are the usual cause.

    Disable the  firewall and see if the updates are successful

    Try downloading manually the updates

    http://technet.microsoft.com/en-us/library/jj657471(v=exchg.150).aspx


    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

    Wednesday, May 21, 2014 7:10 AM
  • Hello. 

    I disabled the windows's firewall and I forced the download. The system returned the same error.

    I tried to enter here "http://forefrontdl.microsoft.com/server/scanengineupdate/x86/microsoft/package/manifest.cab" from my exchange server and i can download the file without problems.

    Any idea?


    MCSA: Windows Server 2008


    • Edited by Cimmerio Wednesday, May 21, 2014 7:42 AM Edit url
    Wednesday, May 21, 2014 7:23 AM
  • Up Up!

    MCSA: Windows Server 2008

    Thursday, May 22, 2014 9:49 PM
  • Hi,

    The cause can be the proxy server not being specified for the updates.

    Try:

    Netsh winhttp set proxy proxy-server="http=%ProxyServer%;https=sproxy:88" bypass-list="*.contoso.com"

    Thanks,


    Simon Wu
    TechNet Community Support

    Friday, May 23, 2014 8:42 AM
  • The problem was caused by permissions "network services". My installation of exchange is in a separate hard drive (drive E :). I checked in the event viewer the error was associated with the "user" "network service". 

    I have found that adding "network service" to local Administrators group solves the problem after rebooting. 

    It seems it was a problem of access permissions to an executable file or folder. Now I would like to define the necessary permissions to remove the administrator group user "network service". 

    Greetings and thanks for the help.

    MCSA: Windows Server 2008

    • Marked as answer by Cimmerio Friday, May 23, 2014 9:52 AM
    Friday, May 23, 2014 9:52 AM
  • Thanks Cimmerio for this, this also fixed it for me as I have Exchange 2013 installed on the D Drive as part of our Exchange 2013 Cu7 build process

    Indeed adding the local computer 'Network Service' to the local admin group does solve the issue and I have network service already in the full path too so it must be somewhere else.

    Hope Microsoft look to fix this bug in CU8

    Andy

    Saturday, January 3, 2015 1:26 PM
  • Hi!

    The solution from Cemmerio doesn't help me. Any other ideas?

    Tuesday, February 3, 2015 4:32 PM
  • The problem was caused by permissions "network services". My installation of exchange is in a separate hard drive (drive E :). I checked in the event viewer the error was associated with the "user" "network service". 

    I have found that adding "network service" to local Administrators group solves the problem after rebooting. 

    It seems it was a problem of access permissions to an executable file or folder. Now I would like to define the necessary permissions to remove the administrator group user "network service". 

    Greetings and thanks for the help.

    MCSA: Windows Server 2008

    I would not do this.  Adding Network Service to the local administrators group could be a big security concern.  There is a reason why network service is a separate account outside of administrators.

    I found the following article which helped me:

    http://blogs.technet.com/b/ehlro/archive/2014/08/20/exchange-2013-malware-engine-updates-troubleshooting.aspx

    I tried pretty much everything on there with no success until I read this one line:

    "Make sure "NT AUTHROITY\Network Service" has full access for the folder Program Files\Microsoft\Exchange\V15\FIP-FS\Data\ in case you have installed exchange in different drive, you need to add "NT AUTHROITY\Network Service" on the drive itself."

    I do have my exchange install on a different drive than "C:" (come on Microsoft... who the hell does that?) so I added full control to network service on the above directory and suddenly it's all working.

    Do not add full control at the volume level.  Just the Data folder under FIP-FS.

    I have found that Exchange 2013 is seemingly a very rushed and buggy app.  you would think after a year or so they would have worked all this crap out.


    • Edited by BrettDioson Sunday, May 17, 2015 3:24 PM updated clarification
    • Proposed as answer by BrettDioson Sunday, May 17, 2015 3:24 PM
    Sunday, May 17, 2015 3:16 PM
  • Thanks!  This solved my issue!

    JT

    Wednesday, January 6, 2016 2:56 PM
  • This worked on 2016 also,Thanks!
    Monday, July 23, 2018 4:42 PM
  • In my case issue the same. Anti-malware engine  cannot undate yourself because network restrictions.
    Wednesday, March 27, 2019 7:28 AM