jueves, 27 de enero de 2011 14:29
we´ve a dedicated W2K8 R2 server with the latest Forefront Protection Server Management Console 2010 installed. We´ve setup a new redistribution job for signatures. After starting this job with "run now" we receive a couple of minutes later the error message (Notification log): Download of engine x,y,z failed. Root element is missing.
The event log shows following error message:
2011-01-27 06:00:35.294 [pid:3184] [tid:1] Microsoft.FFSMC.Services.RedistributionManagement - Root element is missing.-Forefront Protection Server Management Console failed to retrieve valid engine version information. Root element is missing. in module System.Xml
The job is defined to download all available engines. We´ve changed it to download only one engine -> same result.
Internet access is working without any problems.
Todas las respuestas
viernes, 28 de enero de 2011 6:28Moderador
Thank you for the post.
The issue may related to the timeout of engine downloading. Please navigator to the following register:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\wow6432node\Forefront Server Security\Server Management]
And then change that key to at least 1200 (Decimal) and see if it works.
Nick Gu - MSFT
- Marcado como respuesta Nick Gu - MSFTMicrosoft Contingent Staff, Moderator martes, 01 de febrero de 2011 2:31
lunes, 21 de febrero de 2011 11:46
I'm current experiencing the same problem and the above mentioned registry does not exist on my Forefront Protection Server Management Console Box.
Any idea on how to resolve this.
Microsoft South Africa.
martes, 20 de marzo de 2012 14:11
Was this issue ever resolved? I am getting the same error as the OP and there seems to be no updates anywhere on Technet or anywhere else. Can you please let us know how you resolved the issue? The registry key referenced above to modify the timeout does not exist on the server as specified. Instead the regkey "DownloadEngineTimeout" exists in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Forefront Server Security\Server Management.
I've updated that value to 9600 and it still timesout at around 10 minutes. Thank you for any information to help in resolving this matter.
martes, 20 de marzo de 2012 20:52
yes, it´s working now! We´ve changed the timeoouot settings on the Exchange servers. This means we´ve "delegated" the download engine task to the exchange servers itself:
HKEY_LOCAL_MASCHINE/Software/Wow6432Node/Microsoft/Forefront Server Security/Exchange Server
EngineDownloadTimeout = dword 600000