Microsoft KB Archive/929074

= The scan engines are not updated when you schedule a scan engine update in Forefront Server Security, and an error message occurs: &quot;ERROR: Unable to load manifest&quot; =

Article ID: 929074

Article Last Modified on 11/7/2007

-

APPLIES TO


 * Microsoft Forefront Security for Exchange Server
 * Microsoft Forefront Security for SharePoint

-



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows XP and Windows Vista



SYMPTOMS
When you schedule a scan engine update in Microsoft Forefront Server Security for SharePoint or in Microsoft Forefront Server Security for Exchange, the scan engines are not updated. Additionally, the following error is logged in the :\Program Files\Microsoft Forefront Security\SharePoint\ProgramLog.txt file:

ERROR: Unable to load manifest from: http://forefrontdl.microsoft.com/server/scanengineupdate/x86/Microsoft/Package/manifest.cab : (0x00002ee7) The server name or address could not be resolved. WinHttpClient failed while sending a request.

Additionally, the following error is logged in the Application log:

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

Note This problem may also occur when you try to manually update a scan engine.



CAUSE
This problem occurs if the Forefront Server Security server cannot reach the Microsoft engine download site.



RESOLUTION
To resolve this problem, follow these steps.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.  Confirm that you can reach the Microsoft engine download site. To do this, verify the following items:  The proxy and firewall settings on the proxy or firewall and in Forefront The bandwidth Other network issues  If you cannot reach the download site, determine the version of the scan engine. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> Download the latest Manifest.cab file from a URL that resembles the following URL:

http://forefrontdl.microsoft.com/server/scanengineupdate/x86/ /Package/manifest.cab

Note In this URL,  represents the name of the scan engine.

To download the latest Manifest.cab file for the latest version of the Microsoft scan engine, visit the following Microsoft Web site:

http://forefrontdl.microsoft.com/server/scanengineupdate/x86/Microsoft/Package/manifest.cab

</li> Extract the Manifest.xml file from the Manifest.cab file.</li> Use Microsoft Internet Explorer to open the Manifest.xml file, and then examine the package version number. For example, the package version number may be 0612030005.

If the package version number is the same as the version number of the scan engine that is currently installed, do not update the scan engine.

If the package version number is an earlier version of the scan engine that is currently installed, replace the download URL with the secondary network update path. Then, repeat step 1.

You can use the secondary network update path in Forefront Server Security Administrator. If the secondary network update path is not specified, do not update the scan engine.</li></ol> </li> Download the latest scan engine. To do this, download the _fullpkg.cab file from a URL that resembles the following URL:

http://forefrontdl.microsoft.com/server/scanengineupdate/x86/ /Package/ / _fullpkg.cab

Note In this URL,  represents the package version number that you noted in step 1c.</li> Create the folder structure for the updated scan engine. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> Create a folder that is named &quot;Staging&quot; in the current scan engine package folder.</li> Copy the contents of the current scan engine package folder to the Staging folder.</li> Extract the contents of the _fullpkg.cab file to the Staging folder. When you do this, the files in the Staging folder will be updated.</li></ol> </li> Test the updated files in the Staging folder. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> In Forefront Server Security Administrator, disable the current version of the scan engine that you are using.</li> Copy the Bin folder of the current scan engine installation to the BinLKG folder.</li> Copy the files in the Staging folder to the Bin folder.</li> Enable diagnostic logging for the GetEngineFiles program. To do this, set the following registry value to 1 :

(on 64-bit systems)

(on 64-bit systems)

Note If the GetEngineFilesDiagnostics registry value is not present, create the registry value by using the following parameters:

Value name: GetEngineFilesDiagnostics

Value type: REG_DWORD

Value data: 1 (Hexadecimal)

If you enable diagnostic logging for the GetEngineFiles program, you can determine whether the new scan engine version successfully loads and passes a self-test.</li> Click Start, click Run, type cmd, and then click OK.</li> At the command prompt, move to the folder in which Forefront Security is installed.</li> Type scanenginetest.exe –e, and then press ENTER.

Note You will not receive any command results. The command initializes the scan engine and then tests whether the scan engine works.</li> <li>View the ProgramLog.txt file to see whether the scan engine test finished successfully.</li></ol>

Note If any of the substeps in step 4 fail, follow the procedure in the &quot;Rollback procedure&quot; section at the end of the article. Otherwise, go to step 5.</li> <li>Commit the updated scan engine files. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>Delete the BinLKG folder and the Staging folder.</li> <li>Copy the Manifest.cab file to the Bin folder.</li> <li>Set the  registry value to 0 .</li> <li>Re-enable the scan engine.</li></ol> </li></ol>

Rollback procedure

 * 1) If the BinLKG folder is present, delete the Bin folder. Rename the BinLKG folder to &quot;Bin.&quot;
 * 2) Delete the Staging folder.
 * 3) If the   registry value is present, set this registry value to 0.
 * 4) Re-enable the scan engine by using Forefront Server Security Administrator.

Keywords: kbtshoot kbexpertiseadvanced KB929074

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.