Outlook Web Access logon issues can occur for several reasons, including IIS metabase corruption. In this tip,...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Microsoft Exchange Server expert Brien Posey explains how OWA uses the IIS metabase and outlines the steps to fix an IIS metabase corruption that's causing OWA login problems.
OWA depends on the Internet Information Server, which uses the IIS metabase as an internal database. IIS metabase corruption can also cause OWA logon issues; however, it can be difficult to troubleshoot since symptoms vary depending on the nature and extent of the corruption. Metabase corruption, for instance, can cause simple logon failures to a total breakdown of hosted sites on the server. In one situation, IIS metabase corruption prevented any of OWA's image files from displaying correctly.
Whether you're trying to access OWA from inside or outside your network perimeter, IIS metabase corruption problems manifest themselves in the same way. The method to fix the problem, however, varies, depending on which versions of IIS and Exchange you're using. No matter what, you want to back up your OWA server before you attempting any of the following methods.
If you're using IIS 6 and Exchange 2003, shut down all Exchange-related services on the OWA server. Next, open the IIS Manager and delete the following directories:
- Public virtual directories
Now it's time to fix the IIS metabase. To do so, follow these steps.
- Download the IIS Resource Kit and open the IIS Metabase Explorer tool.
- When Metabase Explorer opens, navigate through the console tree to your server | LM | DS2MB.
- Right-click on the DS2MB folder and select the Delete command from the menu. Then close Metabase Explorer.
- Reboot Exchange Server. When you do, the System Attendant Service will automatically regenerate the Exchange virtual directories that you deleted earlier.
- Verify that the proper authentication types have been set on the ExchWeb virtual directory by opening IIS Manager and navigating through the console tree to Web Sites | Default Web Site | ExchWeb. Right-click on the ExchWeb virtual directory and select the Directory Security tab from the properties sheet.
Note: In some cases, the SSL certificate may need to be reassigned to the Default Web Site.
- You'll have to enable anonymous access and integrated Windows authentication.
About the author: Brien M. Posey, MCSE, is a five-time recipient of Microsoft's Most Valuable Professional (MVP) award for his work with Exchange Server, Windows Server, Internet Information Services (IIS), and File Systems and Storage. Brien has served as CIO for a nationwide chain of hospitals and was once responsible for the Department of Information Management at Fort Knox. As a freelance technical writer, Brien has written for Microsoft, TechTarget, CNET, ZDNet, MSD2D, Relevant Technologies and other technology companies. You can visit Brien's personal website at www.brienposey.com.
Do you have comments on this tip? Let us know.
Please let others know how useful this tip was via the rating scale below. Do you know a helpful Exchange Server, Microsoft Outlook or SharePoint tip, timesaver or workaround? Email the editors to talk about writing for SearchExchange.com.
Dig Deeper on Outlook Web Access