Skip to content

Latest commit

 

History

History

Q215474

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
layout title permalink
page
Q215474: XFOR: Missing SP2 README.RTF from Exchsrvr\Connect\Exchconn
/kb/215/Q215474/

Q215474: XFOR: Missing SP2 README.RTF from Exchsrvr\Connect\Exchconn

{% raw %}

Article: Q215474
Product(s): Microsoft Exchange
Version(s): winnt:5.5
Operating System(s): 
Keyword(s): 
Last Modified: 13-APR-2000

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Exchange Server, version 5.5 
-------------------------------------------------------------------------------


SYMPTOMS
========

The readme.rtf file is not found in the expected loacation,
Exchsrvr\Connect\Exchconn directory after you install the Microsoft connectors
for SNADS, OfficeVision, or PROFS.

This article explains the cause of this problem and offers a workaround.

CAUSE
=====

This is the result of a problem in the Setup program introduced after the
shipping of Web 2.

RESOLUTION
==========


The Readme.rtf file will be available in the next Exchange Service Pack (SP3).

STATUS
======

Microsoft has confirmed this to be a problem in Exchange Server version 5.5.


MORE INFORMATION
================

Connector Feature Enhancements
------------------------------

For information on feature enhancements made to the Microsoft Exchange Connector
for Lotus Notes, the Microsoft Exchange Connector for SNADS, and Microsoft
Exchange Connector for IBM OfficeVision/VM (PROFS), see the Readme.rtf file that
is located in the Exchsrvr\Connect\Exchconn directory after you install the
connectors.

However, this file is not copied anywhere when you install any of the noted
connectors.

Additional query words: readme.rtf, missing

======================================================================
Keywords          :  
Technology        : kbExchangeSearch kbExchange550 kbZNotKeyword2
Version           : winnt:5.5
Issue type        : kbbug
Solution Type     : kbnofix

=============================================================================

{% endraw %}