OL2000: You Receive an Error Message If You Open a Public Folder That Has an OWA Page As the Default Home Page

View products that this article applies to.

This article was previously published under Q318927

Expand all | Collapse all

SYMPTOMS

If you configure an Outlook Web Access (OWA) page as the default home page for any public folder in Outlook 2000, you may receive the following error message from Microsoft Internet Explorer when you open that public folder:

An Error has occurred in the script on this page.

Line: 1028
Char: 2
Error: Unable to perform a security operation on this script code in this style sheet.
Code: 0
URL: https://Exchange Server Name/exchweb/controls/ctrl_View20.htc

Back to the top

CAUSE

This problem occurs because of an issue with Outlook 2000 using Microsoft Internet Explorer Version 6.0. There is a malfunction in the Outlook 2000 authorization function when a Uniform Resource Locator (URL) page that includes script code is accessed.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Office 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

276367 (http://support.microsoft.com/kb/276367/EN-US/ ) OFF2000: How to Obtain the Latest Office 2000 Service Pack

The English-language version of this fix should have the following file attributes or later:

   Date         Size       File name     
   --------------------------------------------
   19-Mar-2002  7,758,336  Outlook_admin.msp
   19-Mar-2002  2,721,280  Outlook.msp

After the fix is installed, the following files will have the listed attributes or later:

   Date           Size    Version      File name     
   -------------------------------------------------------
   06-Oct-2000     41,472    1.0.3.27  Bjablr32.dll
   15-Jun-2000     61,952    3.2.0.27  Bjlog32.dll
   27-Jun-2001     98,304    1.0.3.28  Bjsrch32.dll
   20-Jun-2000    805,648 5.5.2652.65  Cdo.dll
   16-Nov-2000    131,122  9.0.0.4715  Contab32.dll
   15-Jun-2000    183,808    1.0.3.27  Emablt32.dll
   06-Sep-2000    154,112  5.5.3142.0  Emsabp32.dll
   20-Nov-2001    594,192  5.5.3165.0  Emsmdb32.dll
   27-Jun-2001    131,344  5.5.3159.0  Emsui32.dll
   03-Jun-2000     86,067  9.0.0.4201  Envelope.dll
   27-Jun-2001    540,944  5.5.3156.0  Exsec32.dll
   06-Apr-2000    192,561  9.0.0.4005  Mimedir.dll
   27-Jun-2001    792,576  5.5.3157.0  Msmapi32.dll
   04-Aug-2000    602,384  5.5.3138.0  Mspst32.dll
   01-Feb-2000    196,661  9.0.0.3731  Oladd.fae
   02-Jun-2000    254,827           -  Olexchng.aw
   13-Jun-2000     27,421           -  Olsec9.chm
   02-Jun-2000    174,439           -  Olxchng9.chm
   27-Jun-2001    454,144  5.5.3153.0  Omi9.dll
   27-Jun-2001    548,352  5.5.3153.0  Omint.dll
   07-Jun-2001    129,024           -  Out2ksec.mst
   27-Jun-2001    782,608 8.30.3157.0  Outex.dll
   03-Jun-2000    891,656           -  Outlhlp.aw
   16-Mar-2002  5,337,138  9.0.0.6314  Outllib.dll
   15-Jun-2001  1,695,794  9.0.0.5414  Outllibr.dll
   25-May-2001    348,210  9.0.5324.0  Pstprx32.dll
   08-Jul-2000     73,772  9.0.0.4307  Rm.dll

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Microsoft Office 2000 Service Pack 3 (SP-3).

Back to the top