Be careful when editing the Exchange IMF custom configuration XML file

The Exchange Intelligent Message Filter (version 2) uses an XML file called MSExchange.UceContentFilter.xml for custom configuration, particularly for the custom weighting feature. If that XML file isn't saved in the proper Unicode format, Exchange IMF will not work correctly.

Many Exchange Server administrators edit their XML files in Notepad. That's fine, but you must be careful, because Notepad provides three different ways to save a file as Unicode:

If you look at the XML leader on your Exchange IMF's MSExchange.UceContentFilter.xml file, you'll see the following line:

<xml version="1.0" encoding="UTF-16">

If you mistakenly saved the XML file as plain ANSI text or as a variant of Unicode other than UTF-16, the Exchange Intelligent Message Filter will stop working and will typically log error 7514, with this explanatory text:

An error occurred while loading Microsoft Exchange Intelligent Message Filter. The error code is 0x80004005.

One quick way to verify if the XML file is "munged" is to try loading it in Internet Explorer. If you get an err

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Antispam Software and Spam Filtering Problems with email spoofing on SBS 2003 Exchange Insider e-zine Securing your Exchange Server 2007 journaling archives Microsoft Exchange Server security dos and don'ts Troubleshooting Microsoft Exchange Server Event ID error 6009 How can I configure Exchange IMF to allow an IP address or DNS? Tool helps identify inbound Exchange Server email flow issues Configure SMTP relay restrictions in Exchange Server 2003 to stop spam Exchange email sent to a domain using SPF authentication is returned Secure Edge Transport servers using the Security Configuration Wizard Antispam Software and Spam Filtering Research Microsoft Exchange Server Administration Tools Microsoft Exchange Server 2007 performance tutorial How to custom-configure a Microsoft Outlook 2007 install using OCT Top Exchange Server performance monitoring and troubleshooting tools Search and index Microsoft Outlook 2007 public folders Executing an .MSP customization file in Microsoft Outlook 2007 Using the NTBackup tool for Exchange Server backup and recovery Tools to bulk modify Active Directory users in Exchange Server 2003 Free tools keep Microsoft Outlook visible in Windows Vista Setting up email disclaimers and signatures in Exchange Server Tool deploys customized Microsoft Outlook 2007 configurations Microsoft Exchange Server Administration Tools Research Exchange Security Tips How file-level antivirus software can harm your Exchange Server Understanding Exchange Server 2007 SP1 mobile security settings Which ActiveSync authentication method is best for your mobile device? Why you should secure Exchange 2007 using administrative policies Microsoft Exchange Server security dos and don'ts Create a journal rule in Exchange 2007 to secure journaling mailboxes How to protect an Exchange journaling mailbox from email spoofing Lock down Microsoft Outlook 2007 to prevent .PST file access Using Exchange Server journaling as an email-archiving solution Use the OWA Admin tool to 'segment' Outlook Web Access 2003 features

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary greylist  (SearchExchange.com) hash buster  (SearchExchange.com) image spam  (SearchExchange.com) KnujOn  (SearchExchange.com) Sender ID  (SearchExchange.com) spam confidence level  (SearchExchange.com) spamblock  (SearchExchange.com) spim  (SearchExchange.com) tarpitting  (SearchExchange.com) teergrube  (SearchExchange.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

or that says "Cannot view XML input using style sheet," then it was probably saved in the wrong format.

If you still get error 7514, try deleting the XML file entirely. If the error still occurs, something else may be wrong -- for instance, the IMF .DLLs may not be registered correctly.

About the author: Serdar Yegulalp is editor of Windows Insight, a newsletter devoted to hints, tips, tricks, news and goodies for all flavors of Windows users.

MEMBER FEEDBACK TO THIS EXCHANGE SECURITY TIP

I am still getting the same error:

Invalid at the top level of the document. Error processing
resource 'file:///C:/rror.xml'. Line 1, Position 40

<?xml version="1.0" encoding="utf-8"?>

Do you have any suggestions?
—Prameela D.

******************************************

I confess I'm a bit stumped on this one. The only thing I can think of is that the encoding of the document is wrong.
—Serdar Yegulalp, tip author

Do you have comments on this tip? Let us know.

Rate this Tip To rate tips, you must be a member of SearchExchange.com. Register now to start rating these tips. Log in if you are already a member. DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.