Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

OWA meeting request address is not valid for POP3 clients


View products that this article applies to.

This article was previously published under Q329266
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 (http://support.microsoft.com/kb/256986/EN-US/ ) Description of the Microsoft Windows Registry

↑ Back to the top


Symptoms

If you send a meeting request from Microsoft Outlook Web Access (OWA) to a POP3 client, the meeting request has http://exbe/exchange/alias/meeting.eml as the path to the meeting. The Hosted Messaging and Collaboration solution disables this Web page and uses an individual virtual directory for each company.

↑ Back to the top


Resolution

Cumulative Patch Information

To resolve this problem, obtain the March 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
813840� XGEN: March 2003 Exchange 2000 Server Post-Service Pack 3 Rollup

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. Component: OWA

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version      Size       File name
   -------------------------------------------------------
   16-Sep-2002  17:21  6.0.6325.0     90,112   Eximap4.dll
   16-Sep-2002  17:22  6.0.6325.0     32,768   Expop3.dll
   16-Sep-2002  17:22  6.0.6325.0     32,768   Exproto.dll
   16-Sep-2002  16:34  6.0.6325.0     40,960   Febecfg.dll
   16-Sep-2002  17:21  6.0.6325.0     32,768   Iisif.dll
   16-Sep-2002  17:23  6.0.6325.0    131,072   Iisproto.dll
   16-Sep-2002  17:23  6.0.6325.0     61,440   Imap4be.dll
   16-Sep-2002  16:38  6.0.6325.0    319,488   Imap4evt.dll
   16-Sep-2002  16:35  6.0.6325.0    131,072   Imap4fe.dll
   16-Sep-2002  17:22  6.0.6325.0    126,976   Imap4svc.dll
   16-Sep-2002  17:22  6.0.6325.0     36,864   Pop3be.dll
   16-Sep-2002  16:38  6.0.6325.0    303,104   Pop3evt.dll
   16-Sep-2002  16:36  6.0.6325.0     24,576   Pop3fe.dll
   16-Sep-2002  17:20  6.0.6325.0     73,728   Pop3svc.dll
   16-Sep-2002  16:38  6.0.6325.0    163,840   Protomsg.dll
				
NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
301378� How to Obtain the Latest Exchange 2000 Server Service Pack
After you apply this hotfix, you must enable it through Registry Editor. To do so, follow these steps.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
  1. Start Registry Editor (Regedt32.exe).
  2. Locate and then click the following key in the registry:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\SYSTEM\CurrentControlSet\POP3SVC\Parameters
  3. On the Edit menu, click Add Value, and then add the following registry value: Value name: UseSmtpProxyFQDNForOWAUrl
    Data type: REG_DWORD
    Data: 0x1

  4. Quit Registry Editor.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

↑ Back to the top


Keywords: KB329266, kbfix, kbexchange2000presp4fix, kbbug, kbqfe, kbqfe, kbhotfixserver, kbautohotfix

↑ Back to the top

Article Info
Article ID : 329266
Revision : 10
Created on : 2/21/2007
Published on : 2/21/2007
Exists online : False
Views : 264