Tip

IIS 6 file corruption flaw impairs OWA

Internet Information Services (IIS) 6.0 running on Windows Server 2003 (pre-SP1) can throw errors when attempting to load Outlook Web Access (OWA) because of file corruption in the compressed files directory.

When file corruption occurs, IIS may generate the error: "The HTTP verb used to access this page is now allowed." Other errors can happen as well, including arbitrary script crashes that don't seem to relate to a specific issue. Pages returned to the client won't render correctly, will hang in the middle of loading, or just won't load at all.

    Requires Free Membership to View

More Outlook Web Access administration resources:

Configuring IIS to authenticate OWA users

OWA 'Loading' problems with Internet Explorer security zones

OWA Administration Guide

Outlook Web Access FAQs

The problem has already been tagged by Microsoft as a known issue, and the next service pack for Windows Server 2003 should address it.

In the meantime, there's a Microsoft hotfix already available for it that patches the W3core.dll component to revision 6.0.3790.99 (10/29/2003).

While waiting for the next Windows Server 2003 service pack, there are two other possible interim workarounds:

  1. Pause IIS and delete the files in the IIS Temporary Compressed Files folder whenever the problem crops up -- or on a regular basis via a script to keep the problem from becoming chronic. If you elect to do this automatically, bear in mind that you'll want to do it at a time when traffic is low (4 a.m., for instance) to avoid disrupting employee productivity.

  2. Disable compressed files in IIS. This isn't always an option though. It's not possible to selectively disable content compression on only one site in IIS; and compressing (and caching) static content provides a bit of a savings on bandwidth and processing speed.

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.

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 thank-you gift only an IT geek could love.

This was first published in May 2007

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

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.