Last Modified: October 8, 2003
This Readme contains important, late breaking information about the beta release of Microsoft® Content Management Server (MCMS) 2002 Connector for SharePoint™ Technologies. It is strongly recommended you review this Readme before installing MCMS Connector for SharePoint Technologies.
Note After you install the product, you can find the MCMS Connector for SharePoint Technologies Help file at: <install dir>:\Program Files\MCMS Connector for SharePoint Technologies\Docs.
For the beta release you can only install MCMS Connector for SharePoint Technologies on a computer where the following are all installed on the same computer:
Note This beta release only supports the English edition of the software listed below.
In addition, you must install MCMS 2002 SP1, SharePoint Portal Server 2003, and/or Windows SharePoint Services 2.0 in Internet Information Services (IIS) 6.0 on the Default Web Site virtual Web server.
This section contains known issues in MCMS Connector for SharePoint Technologies.
This section contains:
When you are installing MCMS Connector for SharePoint Technologies you may get the following error message if you do not have Visual Studio .NET 2003 installed on your computer: "Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run." To resolve this issue, you must install Visual Studio .NET 2003.
To change the SharePoint Portal Server search server URL, search query user name, or password, you must uninstall and reinstall MCMS Connector for SharePoint Technologies.
If you add a new page to any Woodgrove Sample site, the SharePoint Portal Server search engine will not index that page unless there is a hyperlink to the new page in another pre-existing searchable Woodgrove page. This is because the Woodgrove site navigation control is generated with script and the SharePoint Portal Server search index crawler ignores script.
When you do a search query that displays more than one page of results and you then do a subsequent query, the results from the originally query may still appear. To resolve this, do another search query by leaving the search query text box blank, and then clicking Go. You can now do a subsequent search.
If you accept the default MCMS site URL (http://localhost/channels) during the MCMS 2002 Connector for SharePoint Technologies installation and you specify a search crawl account that is different from the configured SharePoint Portal Server default search account then SharePoint Portal Server does not index your entire MCMS site. To resolve this issue you must create additional content sources and/or site path rules in SharePoint Portal Server. For more information on this issue see the section "Creating Additional Content Sources" and "Creating Additional Site Path Rules" in "Installing Content Management Server 2002 Connector for SharePoint Technologies" located on Microsoft BetaPlace.
The MCMS Web Parts may appear minimized on the SharePoint Portal site, but the Restore option is not available on the Web Part menu. This usually happens when you are editing the Web Part custom properties. To resolve this, click Refresh on your Web Browser toolbar. You may have to click Refresh more than once.
If you minimize a MCMS Web Part and then modify the properties of another Web Part, when you select Restore on the MCMS Web Part it does not restore. To resolve this, click Refresh on your Web Browser toolbar.
If you sort the MCMS Page Listing Web Part by Last Modified Date the pages do sort, but the "x" icon does not appear on the drop-down menu to indicate how the pages are sorted.
In the Placeholder Properties window of the SharePoint Document Placeholder the Site drop-down list contains all sub-sites (Windows SharePoint Services sites) and sub-areas (SharePoint Portal Server sites). Duplicate names can appear in this list. It is also possible that you may not see all sub-sites or sub-areas.
If you cannot find the sub-site or sub-area you are looking for you can find the library you need by doing the following:
Note You must use the URL of the site that displays the library. Do not use the URL of the library page by clicking the library hyperlink.
If you attach a Word ML file containing an embedded image, or an attachment to another file, to the SharePoint document placeholder, and then select the word ML inline rendering template, the SharePoint document placeholder does not display the embedded image or the attachment in line.
If you edit an MCMS page that has a SharePoint document placeholder and the attachment in the placeholder no longer exists in the Windows SharePoint Services library, when you try to save the page you may get the following error message: "Save Placeholder Failed Error Details: SPListItem not initialized." To resolve this, delete or replace the attachment from the SharePoint document placeholder.
If you use common words such as "this" or "is" on the SharePoint document placeholder properties window in the Search Site for text-box, and then click Go, no results are returned. To resolve this, do not use common words in your key word search.
In Visual Studio .NET, when you open the intranet sample data that has the SharePoint Portal Server look and feel, the SharePoint Portal controls show the following error message: "Error Creating Control." This error message is displayed because SharePoint Portal Server controls do not support design time behavior in Visual Studio .NET. You can ignore this error message and edit the page as normal.
If you reinstall without first uninstalling MCMS Connector for SharePoint Technologies an error may appear that says you must be a local machine administrator and an MCMS administrator in order to install MCMS 2002 Connector for SharePoint Technologies. This message appears even if you are already a local and MCMS administrator. To resolve this, you must uninstall MCMS Connector for SharePoint Technologies before reinstalling it.
-----------------------------------------------
This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2003 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, SharePoint, Visual Studio, Windows, Windows NT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.