FileNet Connector Troubleshooting

Web Service error while establishing connection to SQL Server

WebserviceError:
- A network-related, or instance-specific, error that occurred while establishing a connection Connection defines the how Connectivity Hub connects to your Source System (which contains your documents, graphics, etc.,). Your Connection includes identifying elements such as: URL of the BA Insight web service connector you are using, (File Share connector, SharePoint Online connector, etc.), Authentication mode, User Accounts and Credentials, Database information (for database connectors) to SQL Server.
- The server was not found or was not accessible.
- Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40: Could not open a connection to SQL Server).

Possible Cause

Invalid connection string is specified to establish the connection to the target A Target is a "pointer" to a specific instance of a search application, such as Elasticsearch. - (A Search application instance has one or more indexes) database.
To fix, specify a valid connection string for the Object Store Database Connection.

WebServiceError: Keyword not supported: …

Possible Cause/Solution

An invalid connection string format is specified to establish a connection to the target database
See examples for Object Store Database Connection and fix.

WebserviceError: Cannot open database … requested by the login. The login failed.

Possible Cause/Solution

Incorrect credentials are specified in the connection string.
This applies if the target SQL server uses the SQL Server Authentication mode:
- See examples for Object Store Database Connection and fix.

WebserviceError: Invalid FPOS connection parameters

Possible Cause(s)

An invalid connection string is specified for the target database connection.

Solution

Go to Connection Info tab and specify valid a connection string to File Plan Object Store Database Connection (Records Manager).

Webservice call:crawl: The remote name could not be resolved: …

Possible Cause/Solution

Invalid IP/host name is specified in the WebService parameter:
- Validate correct value(s).

MSSQL Database – WebserviceError: Impersonation failed to login with user

WebserviceError: Impersonation failed to login with user: svc_filenet domain:<domain name> check if it is a valid user and you entered the correct password; details: error code:1326 error message:System.ComponentModel.Win32Exception: Logon failure: unknown user name or bad password.

Possible Cause/Solution

Invalid credentials specified in the Impersonalization Account: To fix, enter valid parameters.

Oracle DB – Exception during retrieving DataStoreTypes

Exception retrieving DataStoreTypes:ORA-00257: archiver error. Connect internal only, until freed. Last Executed SQL.

Possible Cause/Solution

Out of free space on hard disk with Oracle data base: To fix, clear any empty space.

Syntax error using ROWLIMIT custom filter

On using custom filter for content FOLDER=/New Folder/Security/inherited security/*|ROWLIMIT=A see an error:

There was a syntax error in a SQL query or filter expression at line 1, position 12. Saw A but expected <UINT_LITERAL>.
The original text was: 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.

Possible Cause

Improper character is specified for the item count that should be retrieved (ROWLIMIT filter)

Solution

The 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 used

Possible Causes

Problem in generating SQL commands. Internal connector error.

Solution

Probably an invalid SQL.
Try another filtering option or contact bainsight-support@uplandsoftware.com.

Content of items is not retrieved and the user cannot search items by content

Possible Causes

The content of items that are stored on the file system and corresponding connection parameter is not specified/specified incorrectly.
The content size of the items is greater than specified in the Max File Size parameter on the Content page.

Solution for the first cause

Go to Connection Info page and check the value of Crawler/FileNet Share.

Solution for second cause

Check the Max File Size parameter on the Content page and increase the value as required.

Exception:WebserviceError: The type initializer for Devart.Data.Oracle.an threw an exception

Possible Cause

An issue with the initialization of Devart library used for establishing connection to databases.

Solution

This is temporary solution because the underlying problem has not been completely investigated:

Navigate to the Connector installation directory. Find and open the bin folder.
Find the Devart.Data.Oracle.dll and move this file out of the Connector directory.
Open the Connection page of the FileNet Connector. Click Refresh or Update WebService.
Navigate to the test bench and click Run.

You should see the error shown above in the test bench.

Move the Devart.Data.Oracle.dll back to the bin folder
Open the Connection page of the FileNet Connector. Click the Refresh or Update WebService link.
Repeat steps 3 and 4 above.

Marking Set security did not process, or processed incorrectly

Possible Causes

The Marking Sets security was not validly set up to allow this processing
Marking Set was renamed/removed in the source system Your Source System is the repository where your data is stored (data to be indexed). This repository is managed by applications such as: - SharePoint O365 - SharePoint 2013/16/19 - Documentum - File Share - OpenText - Lotus Notes - etc. Your Source System repository can also be a database such as SQL or Oracle. after the last full crawl
Items that had more than the maximum allowed security previously now have the allowed security level.

Solution for the first cause

Specify multi-level security and install and configure the Federator with the Advanced Security Module.

Solution for the second cause

Execute a full crawl for the content.

Solution for the third cause

Clear all data in tables SIDMappingLevels and SIDMapping from cache_db database and execute a full crawl on the content.

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

Possible Cause

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

Solution

Open the Connection page of the Connector and check the value of the WorkplaceXT URL field.
Try to open the URL in the web browser. You should see login page of Workplace. If not, edit the URL and save the changes.
(Required) Execute a full crawl.
Try searching and reopening the URL.

In the Test Bench/Search page all items are marked improperly as public (allowed for everyone)

Possible Cause

Enabled Disable security mode

Solution

Go to Disable security and make sure that this option is not selected.
Run a full crawl.

TestBench/Search displays more than only the current version of one item

Possible Cause/Solution

Index every version of a Document is enabled.
Disable this setting to fix this issue.

Items with hidden classes are displayed in the test bench or available for search

Possible Cause/Solution

Include hidden document classes is enabled
Disable to fix.

Custom filters are not working properly

Possible Cause/Solution

Incorrect syntax/format is used for specifying filters in the Custom Filters
To fix, specify the correct syntax/format.

Unfiled Items (without parent folders) are not present in the crawl result

Possible Cause/Solution

Include Unfiled Items is disabled:
To fix, enable Include Unfiled Items.

Running search/test bench returns no results/missing expected results

Possible Cause/Solution

The Crawl Start Point parameter in the Content page contains a date that is beyond the modified date of the items in the source system.
To fix, enter the correct date.

Items of some classes are not displayed in Test Bench or in Search results

Possible Cause/Solution

The Object Classes filter is enabled to crawl items of some specified classes and corresponding classes that are not in a list.
To fix, verify these settings.

No Record metadata properties exist in Item metadata list

Possible Causes

File Plan Object Store Connection String parameter is not specified or specified incorrectly.
Items Handling is incorrectly configured

Solution for first cause

Go to the Connection Info tab and specify valid connection string to File Plan Object Store Database Connection (Records Manager).

Solution for second cause

Check your settings Items Handling.
For example, If you click All items, you can search by any documents in the source system.