Outlook Web Access template file mismatch

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2005-11-18

The Microsoft® Exchange Server Analyzer Tool queries the CIM_Datafile Microsoft Windows® Management Instrumentation (WMI) class to determine the version number of the Wmtemplates.dll file. The Exchange Server Analyzer then compares the version number of Wmtemplates.dll on all servers in the administration group. If the Exchange Server Analyzer finds that the version number of Wmtemplates.dll does not match between front-end and back-end Exchange servers, the Exchange Server Analyzer displays a Best Practice message.

The Wmtemplates.dll file is used by Microsoft Office Outlook® Web Access controls. Mismatched versions of Wmtemplates.dll on the front-end and back-end Exchange servers may cause 400-level errors when users try to log on to Outlook Web Access by accessing the front-end Exchange server.

There have been two recent updates released by Microsoft that update Wmtemplates.dll:

If you have recently installed either of these updates, the following conditions might be true:

  • The updates were not installed in the correct order.

  • The update was not installed on both the front-end and back-end servers.

When you install updates for Outlook Web Access, you should install the update on the front-end server, restart the server, and then install the update on the back-end server.

If you have not installed either of these updates, make sure that all servers are running the latest Exchange Server service packs and updates.

For information about the latest Exchange Server service packs and updates, visit the following Web sites: