I am noticing a failure in Cloudmark engine update in Forefront Protection 2010 for Exchange Server from last saturday, 7th August 2010. Nothing has been changed in my environment. Engine summary shows that Cloudmark engine update has failed.
Event viewer has an entry with the following error message.
Microsoft Forefront Protection encountered an error while performing a scan engine update.
Scan Engine: Cloudmark
Update Path: http://forefrontdl.microsoft.com/server/scanengineupdate
Error Detail: An error occurred while processing the universal manifest.
But, the “definition version” column shows the last update with the most recent time.
I am a bit confused as to whether the update is actually happening, as the definition version is up-to-date with a failure in engine summary and event viewer.
Anyone else has the same issue? I will update the post once I have more information.
Update
Microsoft has fixed whatever the issue was and my cloudmark engine is up-to-date again.
All green in the console as well.
Hi Anonymous,
It should be ok now. Are you still having the issue?
Hi,
I am having the same problem what you mentioned. all the engines are not updated and no response from Microsoft. i had installed exchange server with TMG for Exchange with two NIC in workgroup environment. please help me in this.
Thanks Kostas. The issue is now fixed, so you should have all green!
Same here. Seems like MS has problems updating cloudmark engine databases again. It is not a problem on your Exchange.
Hi Anonymous,
Check my previous article http://www.theucguy.net/2010/08/cloudmark-antispam-engine-not-updating.html
Hi
I had configured TMG for Exchange when i update all the engine updates are failed. please help me
I agree Anonymous. There was no response on the Technet forums.
Same problem here. Incredibly frustrating given I only installed it the previous day, so didn't bode well for us..
Posted on the technet forums without little response.
Suspected it was a dodgy file so checked for RSS or blog posts at Cloudmark or MS – found nothing..
Surely someone knew what the issue was early on and could have posted a quick update somewhere to save us admins wasting a weekend troubleshooting. :((
Thanks Anonymous. I have updated the article as well, as it has "magically" started working.
Had the same problem. Check again this morning and all was green. Assume an issue with MS site which is hosting these updates. Would be nice to be able to individually verify or create repository locations without using FPE.
Joy, glad to know that I am NOT alone!
This post has been removed by the author.
Yes – this started 8/6 in our environment – had run Windows Updated 8/5 – not sure if any correlation.