Product : SharePointConnector 1.0.SP3 on Win32
Category : Recommended fix
Date released : 12-Jun-12
This patch fixes various issues reported by customers on service pack 3 and above.
Build version: null
Service Pack 3 or above.
Why would you apply this fix
This patch resolves number of issues related to incremental and restart mode of the connector and/or if you are experiencing any of the issues listed in this readme.
Known impacts of applying this fix
o No known side-effects.
o Back up the existing connector by making a copy of the installation folder. If you have done a default installation, the path to the installation folder is typically c:\Program Files (x86)\FAST\FAST SharePoint Connector 1.0
o Unzip the file sharepointconnector.1.0.SP3.complete.patch05.Win32.zip on top of the existing installation (If you have done a default installation, the path you should unzip it in is typically c:\Program Files (x86)\FAST\FAST SharePoint Connector 1.0\). This will replace all the binary files inside the bin folder as well as some files below the ssl and etc folder. Also there are two new database scripts (sql_db_31128.sql and oracle_db_31128.sql) inside the etc folder. It will not replace any configuration files, so you can reuse your configuration files after applying the patch.
This release does not require a full re-crawl to be operational but it’s highly recommended.
To trigger a full crawl with this release using your existing configuration, you need to either delete and re-create your state database or, if you're not worried about space in your state database, set the configuration parameter Database/TableNamePrefix to a new unique value. This will cause a whole new set of tables to be created.
If you want to not perform a full crawl but instead go directly to incremental, you will need to migrate your state database. This version makes use of one new table and updates few existing stored procedures.
If you are using SQL Server, follow below instructions.
o Connect to the current existing state tracker database by using SQL Server Management Studio.
o Open the script “sql_db_31128.sql”
o If the connector is configured to use a table name prefix (Database/TableNamePrefix)
replace the literal <UNIQUE_PREFIX> in the migration script with the table name prefix else replace this literal with empty string.
o Execute the script. The status line in SQL Server Manager should read "Query executed successfully".
To migrate your state database for Oracle, please replace the literal <UNIQUE_PREFIX> in the migration script(oracle_db_31128.sql) with the table name prefix else replace this literal with empty string and Execute the script.
This is a fix for issues
o 854329 : Changes happened between the initial crawl and recovery-mode crawl are not detected properly
o 854627 : Folder view is not well support in incremental mode
o 855497 : Duplicating ACL information when ExpandSharepointGroups = true
Folder view is not well support in incremental mode
Create a folder in a sharepoint list and create an item inside the folder. Set IndexFolderView to true in connector configuration file. Delete/rename the item. Do an incremental crawl. Search for the deleted item or for renamed items search by the older name.
The folder view should get updated. Should get zero hits.
The folder view is not updated. Get hits for folder view, as if the older values still exist.
Duplicating ACL information when ExpandSharepointGroups = true
Set ExpandSharepointGroups = true in configuration file for SharePoint connector. Run connector against SharePoint site with users belonging to multiple user groups. Check the docacl fields in fastxml.
The "docacl" element should not contain duplicates for the users in multiple user groups.
The "docacl" element contains duplicate user names.
Stopping SharePoint Connector during full/incremental crawl affects Restart mode and changes are not detected properly
Create a document library in SharePoint with some documents. Start initial crawl, when the publishers are initialized or just as the connection to the collection is established, stop the connector by hitting Ctrl + C .
Go to SharePoint and remove the above document library.
Should crawl the site collection with all the changes.
Connector throws an exception
If you do not have access to MSConnect and will be downloading software for your organization, please submit a request to firstname.lastname@example.org. Please be sure to include the complete contact details and the contract identifier.
Article ID: 2745538 - Last Review: 6 Sep 2012 - Revision: 1