IBM Support

** Troubleshooting ** "Could not login to TM1" errors when using FAP Client

Troubleshooting


Problem

User launches "IBM Cognos FAP" from the start menu. The Controller "Financial Analytics Publisher" (FAP) Window appears. User starts a publish. User clicks the 'logs' tab. After a few seconds, an error appears.

Symptom

The error message will vary slightly, but it will be similar to the following:

Could not login to TM1

TIP: If the user hovers their mouse over the error, then more information (on the cause) is shown.

Cause

There are many potential causes for this issue:

  • Scenario #1 - the installed TM1 client does not match the TM1 server version
  • Scenario #2 - Connectivity issue between Controller/FAP server and the server hosting the TM1 Data Mart
  • Scenario #3 - Invalid password, potentially caused by corrupt data mart definition
  • Scenario #4 - TM1 Server has been restarted. This has caused the FAP<->TM1 communication to become invalid.
  • Scenario #5 - In Controller 10.1 IF6 (10.1.384) or earlier, the "c8itk.jar" file being used by Controller is incompatible with TM1 10.1.
  • Scenario #6 - Controller's FAP Service cannot find the required shared DLL file ("C8ITKShared.dll") necessary to allow CAM authentication to work.
  • Scenario #7 - Invalid value for username
  • Scenario #8 - Incorrect syntax used for Data Mart definition
  • Scenario #9 - Misconfigured FAP Data Mart settings, relating to CAM authentication/logon.
  • Scenario #10 - User has configured FAP to use a TM1 database user (for example "admin"), but has not configured the TM1 server to accept TM1 database user logins
  • Scenario #11 - More than one FAP service using the same FAP database
  • Scenario #12 - SSL certificate problem (with either the TM1 server, client or both)
  • Scenario #13 - Misconfigured FAP Data Mart settings, relating to TM1 application server name and TM1 cube name

Diagnosing The Problem

To narrow down which scenario you are suffering from, hover your mouse over the error message. A 'popup' new message will appear.

Below are some examples of what you may see:

  • SystemServerConnectionInvalid - See scenario #1
  • SystemServerNotFound - Scenario #2, #4, #11, #12 & #13
  • SystemServerClientPasswordInvalid - Scenario #3
  • com/cognos/ccf/c8itk/ITKProxyJNI.jniIsLoggedOn(I)Z - Scenario #5
  • C8ITKShared (Not found in java.library.path) - Scenario #6
  • SystemValueInvalid - Scenario #7
  • Array index out of range: 1 - Scenario #8
  • SystemServerClientNotFound - Scenario #9
  • Could not logon with to CAM with user: <username> to ClientCAMURI http://servername/cognos8/cgi-bin/cognosisapi.dll - Scenario #9
  • The TM1Server <TM1 server name> is neither in BASIC or CAM mode - Scenario #10

Resolving The Problem

The solution depends on the scenario:


Scenario #1 - The installed TM1 client does not match the TM1 server version
Ensure that the version of the TM1 client (running on the 'FAP service' server) matches the TM1 server.

  • For more details, see separate IBM Technote #1663481.


Scenario #2 - Connectivity issue
Correct network communication between servers (the Controller/FAP server and the server hosting the TM1 Data Mart).

  • For more details, see separate IBM Technote #1657213.


Scenario #3 - Invalid password, potentially caused by corrupt data mart definition
Recreate data mart correctly.

  • For more details, see separate IBM Technote #1472624.


Scenario #4 - TM1 server has recently been rebooted/restarted
If servers/services are restarted (or server machines rebooted) you have to restart servers/services it in a specific order (to keep the FAP-TM1 communication in valid state).

  • For more details, see separate IBM Technote #1599573.


Scenario #5 - "c8itk.jar" file being used by Controller is incompatible with TM1 10.1

Replace the file "c8itk.jar" on the Controller application server with a version that is compatible with TM1 10.1.

  • For more details, see separate IBM Technote #1593674.


Scenario #6 - Controller's FAP Service cannot find the required file ("C8ITKShared.dll")

  • For more details, see separate IBM Technote #1450399.


Scenario #7 - Invalid value for username

  • For more details, see separate IBM Technote #1449708.


Scenario #8 - Incorrect syntax used for Data Mart definition

  • For more details, see separate IBM Technote #1449708.


Scenario #9 - Misconfigured FAP Data Mart settings, relating to CAM authentication/logon

  • For more details, see separate IBM Technote #1449704.


Scenario #10 - User has configured FAP to use a TM1 database user (for example "admin"), but has not configured the TM1 server to accept TM1 database user logins

  • For more details, see separate IBM Technote #1449701.


Scenario #11 - More than one FAP service using the same FAP database

  • For more details, see separate IBM Technote #1693576.


Scenario #12 - SSL certificate problem (with either the TM1 server, client or both)
Either:

  • (a) the TM1 server's SSL certificate has expired
    or (b) the TM1 client (installed on the Controller application server's FAP service server) SSL certificate has expired
    or (c) the TM1 client's certificate does not match the exact same one that is used by the TM1 server. For example, the TM1 server's certificate has been updated, but the TM1 client (installed on the Controller server) has not.

For more details, see separate IBM Technote #1693576.

Scenario #13 - Misconfigured FAP Data Mart settings, relating to TM1 application server name and TM1 cube name
Edit the data mart, and ensure that the settings are correct.

  • Admin Host = The Windows hostname (for example NetBIOS or FQDN) of the application server, where the TM1 server has been installed
  • Server = The name of the TM1 instance (sometimes referred to as the 'TM1 server') which is being used (running on the 'admin host'  machine/device)

For more details, see separate IBM Technote #2004808.

[{"Product":{"code":"SS9S6B","label":"Cognos Controller"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Controller","Platform":[{"code":"PF033","label":"Windows"}],"Version":"10.2.1;10.2.0;10.1.1;10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
09 July 2019

UID

swg21664572