FileNet Connector for SharePoint Portal Search 1.0.0
(FNCS Portal Search)

May 19, 2006

 

1. System Requirements for FNCS Portal Search

The system environment must meet the following requirements:

·         Windows 2003 Server installed and configured

·         SharePoint Portal Server 2003 installed and configured

·         .NET Framework 1.1 Service Pack 1

·         Access to FileNet P8 Content Engine version 3.5.1

·         Domain accounts with:

·         Sufficient user access to both SharePoint and FNCS Document Libraries

·         Administrator or power user privileges for accessing and writing to FileNet Object Stores, FileNet Document Classes, and administering SharePoint Document Libraries

·         Optional: Kerberos configured as the authentication method

 

 

2. Known Issues for FNCS Portal Search

The following are known issues associated with FNCS Portal Search 1.0.0.

 

Known Issue: Impersonation Failure Error

An “impersonation failure error” might occur if a user attempts to retrieve a document from the FileNet P8 repository by clicking on a document link on the Search Results page. This error might be the result of the improper configuration of Kerberos.

 

The following Microsoft Knowledge articles explain how to configure Kerberos:

·         Article 810572: “How to configure an ASP.NET Application for a delegation scenario”

http://support.microsoft.com/default.aspx?scid=kb;en-us;810572

·         Article 832769: “How to configure a WSS virtual server to use Kerberos authentication”

http://support.microsoft.com/?id=832769

 

The following MSDN article explains how to implement Kerberos:

·         How to: Implement Kerberos Delegation for Windows 2000

http://msdn.microsoft.com/library/en-us/dnnetsec/html/SecNetHT05.asp?frame=true

 

Known Issue: File Not Found Error in Item Details Page

A “File Not Found” error might occur when a user clicks on a document link on the Item Details page. This error is the result of the document link pointing to the incorrect relative path of the document.

 

Known Issue: “The address could not be found” Error

A user might find the following error in the gatherer log:

 

“The address could not be found, (0x80040204 - An invalid field name was used in a query string ) [7640] CUrlAccessorForDocument::GetSecurityDescriptor: 0x80040204 (FileNet P8 Content Engine DMA Core Library : The supplied identifier does not reference an available class of object. )”

 

This error is the result of an invalid version of the FileNet P8 client connectivity software on the Microsoft SharePoint Server used for indexing. FNCS Portal Search requires the client connectivity software for FileNet P8 3.5.1.

 

Known Issue: FNCS Portal Search cannot be found

Verify FNCS Portal Search was properly installed. A user might encounter this error when SharePoint is running as a Network Service account. This error will not occur if SharePoint is running as a domain user account.

 

Known Issue: SharePoint unable to access registry or instantiate FNCS Portal Search

Verify that the SharePoint Portal Server application pool is configured to run as a domain user account with administrator privileges on the SharePoint server machine.

 

Known Issue: “The Requested Item not found” error

A user will encounter this error if spaces are entered as part of the “Start Address” when defining the Choose Portion of FileNet to Index step of the Create a FileNet Content Source Wizard.

 

Known Issue: Unable to modify FileNet Content Source

Once a content source is created, a user will not be able to modify its settings. The user will need to delete the existing content source, and create a new content source with the appropriate settings using the FileNet Content Source Wizard.

 

Known Issue: Invalid start addresses allowed in FileNet Content Source Wizard

A user can enter an invalid start address when defining the Choose Portion of FileNet to Index step of the FileNet Content Source Wizard. This will not cause an error, and the wizard will continue with the content source creation.

 

Known Issue: Cancelling installation of Browse Only Web Parts does not remove installation files

If a user cancels out of the installation for the Browse Only Web Parts, the files that were installed are not automatically deleted. When the user tries to install the Browse Only Web Parts again, a warning is displayed that files will be overwritten. By allowing the files to be overwritten the installation will proceed normally.