Authentication and FTS Exporter errors

Use the following tips to help you troubleshoot authentication and FTS Exporter-related errors.

Authentication errors

If you encounter any errors about authentication in the FTS Exporter trace, the FTS Server log, or message 439 in the Content Manager OnDemand system log with the following message text, the wrong authentication token might be in use:

FTS Error: IQQD0040E The client specified the wrong authentication token. --
File=arsfti.cpp, Line=394

The default authentication token of fIqBxTQ= can change because of a reinstallation of the FTS Server or other severe incidents. You can discover the current authentication token by running the configTool of the FTS Server with the printToken parameter as shown in the following example:

# /opt/ibm/odfts/V9.0/bin/configTool.sh printToken
The authentication token is printed below. This token is used to communicate
with the server. Store the token if applicable.
fIqBxTQ=

You can configure the authentication token that is used by Content Manager OnDemand through a configuration setting in the ARS.CFG file of your instance:

ARS_FULL_TEXT_INDEX_TOKEN=fIqBxTQ=

Note: If you are documenting the default token (for example, as a parameter of the FTS Exporter), be aware that the second character of the token value is an uppercase letter I, as in IBM.

If you receive this token error and are using multiple FTS servers, then you should use the -ftiTokDef parameter and the additional ARS.CFG parameters described previously.

FTS Exporter errors

If you encounter issues with the FTS Exporter, increase the trace level as described in FTS Exporter trace. Also ensure that you review the configuration file by opening it in a text editor. Check whether all settings are correct.

If you encounter errors about ars3wapi in the FTS Exporter output or trace, the FTS Exporter cannot find the native library reference to the ODWEK system libraries. To see how to use the -D parameter of Java to include the native library path at application start, see Running the FTS Exporter.

If the error relates to a java.lang.UnsatisfiedLinkError error that does not find the ars3wapi32, you are running on a 32-bit JVM. The Java classes of the FTS Exporter try to load the libars3wapi64, which is in the lib64 subdirectory of your Content Manager OnDemand installation. If they cannot load the libars3wapi64, a 32-bit version is searched (which is not present in the lib64 folder). If both attempts fail, they fail with the related error message.

Important: Ensure that you run the FTS Exporter with a 64-bit JVM that can load the 64-bit share library libars3wapi64.

For more information, see Configuring the FTS Exporter.

Note: Ensure that you apply the latest Content Manager OnDemand version and fix pack to the Content Manager OnDemand server and the FTS Server component before you use FTS.