Article ID: 183517
Article Last Modified on 9/23/2005
APPLIES TO
- Microsoft Exchange Server 4.0 Standard Edition
- Microsoft Exchange Server 5.0 Standard Edition
- Microsoft Exchange Server 5.5 Standard Edition
- Microsoft Exchange Client 4.0 for Macintosh
- Microsoft Exchange Client 5.0 for Macintosh
- Microsoft Exchange Client 5.5
- Microsoft Exchange Client 5.0
- Microsoft Exchange Client 4.0
- Microsoft Exchange Client 5.0
- Microsoft Outlook 97 Service Pack 1
- Microsoft Outlook 97 Service Pack 1
- Microsoft Outlook 97 Service Pack 1
- Microsoft Outlook 97 Standard Edition
- Microsoft Outlook 98 Standard Edition
This article was previously published under Q183517
SYMPTOMS
When you use an Exchange or Outlook client to view another user's server-
based folders, you may not be able to access the Outlook Calendar folder.
You may receive the following error message:
Unable to display the folder. Outlook could not start because a location
to send and receive mail could not be found. To add a location, such as
a personal folder file, double-click the Mail icon in Windows Control
Panel.
In addition, delegate features may not work or may fail intermittently.
RESOLUTION
To resolve this problem, obtain the latest service pack for Exchange Server
version 5.5. For more information, please see the following article in the
Microsoft Knowledge Base:
191014
XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
STATUS
Microsoft has confirmed this to be a problem in the Microsoft products
listed at the beginning of this article. This problem was first corrected
in Exchange Server 5.5 Service Pack 2.
MORE INFORMATION
This condition may exist after moving user mailboxes from one server in the
site to another using move mailbox. This condition will occur even when the
client permissions are correct. The above problem can also be seen without
using MoveUser. In order to apply this fix, each client computer
experiencing the above problem needs the updated Emsmdb32.dll file.
Additional query words: calender outlook 8.5
Keywords: kbbug kbfix kbqfe kbhotfixserver KB183517