Exchange Server 2003 uses virtual directories in Internet Information Services (IIS) for a number of Microsoft...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Exchange services -- mainly, Outlook Web Access (OWA), Outlook Mobile Access (OMA) and Exchange ActiveSync:
IIS virtual directories can get damaged or changed inappropriately. For instance, an inexperienced Exchange Server administrator may try changing them directly in the IIS administration console, when they actually must be changed in Exchange System Manager.
IIS virtual directories are not recreated automatically if they are damaged, so you need to know how to recreate them. They can be remade in a "semi-automatic" way, but Exchange Server has to be specifically commanded to do so; it doesn't "sense" that the directories are damaged or missing.
Microsoft Knowledge Base article 883380 walks through three possible ways to recreate IIS virtual directories for Outlook Web Access, Outlook Mobile Access and Exchange ActiveSync:
- Use the Metabase Explorer utility (available as part of the IIS 6 Resource Kit Tools) to remove the metabase entries for the IIS virtual directories. If you don't already have the Metabase Explorer installed or don't know how to use it, this is probably not the best way to go.
- Use the ADSUTIL.VBS script. This is probably the easiest method, because you can simply delete the IIS virtual directories from IIS Manager, use the script to purge the metabase (rather than trying to do that by hand), and then have Exchange Server recreate the directories. It's pretty foolproof, since you only need to know how to use the IIS Manager and run a .VBS script from a command line.
- Edit the Metabase.xml file by hand. This is probably the most dangerous and difficult way to do it, and is recommended only for experts who really know what they're doing.
In some cases the directories may take up to 15 minutes to automatically recreate; if that doesn't happen, the Exchange server and IIS server machines should both be restarted (IIS first, then Exchange Server).
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.
Do you have comments on this tip? Let us know.
Related information from SearchExchange.com:
Please let others know how useful this tip was via the rating scale below. Do you have a useful Exchange Server or Microsoft Outlook tip, timesaver or workaround to share? Submit it to SearchExchange.com. If we publish it, we'll send you a nifty thank-you gift.