FileNet Connector API Troubleshooting

Content is not retrieved

  • The test bench contains the following message (with Include Trace enabled): API: Content retrieving failed. Possible cause: Access denied for view/read content for user: [user name]

Solution

Item security is not retrieved

  • The test bench contains the following message (with Include Trace enabled): API: Processing permissions failed. Possible cause: Access denied for view permission model for user: [user name]

Solution

  • Check the account specified for the connection to FileNet in Administrator Account for Content Engine on the Connection page. The account should have full read access to the Object Stores that are specified in the Repository tab.

Test Bench displays User is not authenticated exception

Cause

  • Invalid credentials/incorrect format are/is specified

Solution

  • Specify proper credentials (with full read access to FileNet instance) in the same format as used for Workplace XT/Workplace or the FileNet Enterprise manager.

Empty results when using custom filters, but other Workplace filters are working properly

Cause

  • Data for the custom filter is specified from the wrong FileNet instance.

Solution

Open the Connection page of the Connector and click FileNet Content Engine WebService URL. This parameter must contain the correct URL to the corresponding FileNet instance.To validate the URL, use the following steps:

  1. Execute test bench without any Custom Filters.
  2. Locate an item in the trace result.
  3. Find an ID property of the item.
  4. Specify the ID in the Custom Filters.
    1. For example, specify: ITEMID=CD21356C-4BAB-4E5E-A679-8D975A5918D3
      where CD21356C-4BAB-4E5E-A679-8D975A5918D3 is an ID of any item from the test bench.
  5. The test bench displays only item(s) with specified ID(s).
  6. Open the Workplace XT (Workplace).
  7. Locate any items with the same ID in the WorkplaceXT (Workplace).
    1. If you are unable to locate the items, the FileNet instance specified for the Connector and used in the Workplace XT are different.
    2. Change the value in WorkplaceXT URL on the Connection form.
  8. Save: Click Save.

Unable to open the document in the search results by the referenced URL

Cause

  • An incorrect URL specified for the WorkplaceXT on the Connection page.

Solution

  1. Go to the Connection page of the Connector and check the value of field WorkplaceXT URL.
  2. Open the URL in the web browser. You should see login page of the Workplace. If not, edit the URL and save the changes.
  3. Run a full crawl. Required.
  4. Try searching and opening the URL again.

In the test bench/search page, all items are improperly marked as public (allowed for everyone)

Cause

  • Disable security is enabled

Solution

  1. Go to the Connection page and make sure that Disable security is not selected.
  2. Run a full crawl. Required.
  3. Search and open the URL.

Custom filters not working properly

Cause

  • Incorrect syntax/format is specified

Solution

Network error when processing a Web Service Request

  • The test bench displays this error: "A network error occurred when processing a Web service request or response.". See the nested exception for specific details.

Cause

  • An incorrect URL is specified for the FileNet Content Engine WebService.

Solution

  1. Go to the Connection page > FileNet Content Engine WebService URL.
  2. Open the URL in your Web browser.
  3. See the proper XML response.

WebService Response Example

Example
Copy 
<!-- 
====== Copyright (c) 2006 FileNet Corporation. All rights reserved. =====*
Description:
FileNet P8 Content Engine Web Service Definition
 =======================================================================
--><definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:mdef="http://www.filenet.com/ns/fnce/2006/11/ws/MTOM/wsdl"xmlns:cdef="http://www.filenet.com/ns/fnce/2006/11/ws/wsdl" xmlns:ctyp="http://www.filenet.com/ns/fnce/2006/11/ws/schema" name="FNCEWS40MTOM" targetNamespace="http://www.filenet.com/ns/fnce/2006/11/ws/MTOM/wsdl"><import location="http://192.168.4.93:9080/wsi/FNCEWS40MTOM/FNCEWS40.wsdl" namespace="http://www.filenet.com/ns/fnce/2006/11/ws/wsdl"/><binding name="FNCEWS40MTOMBinding" type="cdef:FNCEWS40PortType">…
Specify correct url or fix network related issues.
FileNet Content Engine Web Service should be available for connector.

Syntax Error Using the ROWLIMIT Custom Filter

  • There was a syntax error in a SQL query or filter expression at line 1, position 12. Saw A but expected &lt;UINT_LITERAL>. The original text was:

Copy 
SELECT TOP A ID, DATELASTMODIFIED , MIMETYPE,CONTENTELEMENTS,VERSIONSERIES FROM DOCUMENT DOCUMENT WHERE ISCURRENTVERSION = TRUE AND DateLastModified > 20120101T000000Z AND (DOCUMENT.This INSUBFOLDER '/New Folder/Security/inherited security/' ) ORDER BY DateLastModified.

Cause

  • Improper character is specified for the count of items that should be retrieved (ROWLIMIT filter)

Solution

ROWLIMIT filter: Must be a positive number. For example: ROWLIMIT=10.

Syntax error in a SQL Query or Filter Expression at Line 1, Position 12. …

Note: No custom filters are specified.

Cause

  • Issue generating SQL commands. Internal connector error.

Solution

Wrong values for item ACLs Appear in the Test Bench Output

Examples of error types:

  • Local Everyone group is displayed in the items ACLs for items where the ALL Authenticated group is assigned.
  • Some groups of users are displayed in the items ACLs where the ALL Authenticated group is assigned.
  • The test bench contains #WRONG_SECURITY_PRINCIPAL: (SID or Name) in the ACL items

Cause/Solution

Content of All/Some of the Items is Not Retrieved and the User Cannot Search Items by Content

Cause

  • The size of the items is greater than specified in Max File Size on the Content page. To fix this, increase the value as required.