Q. What causes the Microsoft Outlook Web Access (OWA) errors I receive when I try to connect through OWA to a Windows Server 2003 host?

A. The errors you report are caused by a problem with the Microsoft Internet Information Services (IIS) 6.0 compression. The problem causes static files to become corrupted and incorrect information to be rendered to the requesting client. A typical error is

Line: 15
Char: 30
Error: object expected
Code: 0
URL: https://domainname/exchange/user/Inbox/?Cmd=contents

You can download a fix for the problem at http://www.microsoft.com/downloads/details.aspx?amp;amp;displaylang=en&familyid=0bc9b5bc-a094-49bf-89a5-c8a2d32345a2&displaylang=en. You must apply this fix before you can upgrade to Microsoft Exchange Server 2003 Service Pack 1 (SP1).

Please or Register to post comments.

IT/Dev Connections Exchange Server

Las Vegas
September 30th - October 4th

Paul ThurottYou'll have the opportunity to experience:
• Future Deopyments
and Integrations
• Hybrid Deployments
• Exchange Online
• Windows 8 Deployment
and much more!

Come See Tony Redmond & Mark Minasi in Person!

Early Registration Now Open

Current Issue

May 2013 - The NameTranslate object is useful when you need to translate Active Directory object names between different formats, but it's awkward to use from PowerShell. Here's a PowerShell script that eliminates the awkwardness.

CURRENT ISSUE / ARCHIVE / SUBSCRIBE

Windows Forums

Get answers to questions, share tips, and engage with the Windows Community in our Forums.