Product:
Cognos Controller 8.5.1532 FAP
Windows 2008
Cognos TM1 9.5.2

Symptom:
During IP for Controller FAP you get a error message that the FAP service can not login to the TM1 application. When you change client id and restart the FAP service, you get not error message, the FAP service is only hanging.
If you reboot the physical server, the FAP service will try to login once, and then fail.
There are no “fatalerror.log” in the FAP service folder on the server.

Background:
You have changed to use CAM ID and SSO to access Cognos Controller.
The servers and the users are in different Windows domains with trust between.

Error message:
Severity: CRITICAL
Description: Could not login to TM1, host: SERVERNAME, server name: TM1 SERVER NAME, user name: admin

If you hold the mouse over the error message in FAP manager, you see the text:
SystemServerNotFound

Cause:
The windows account that run the IBM Cognos Controller FAP server must be a domain account in the same domain that the Cognos BI server authenticate against. You must be able to surf to http://servername/cognos8 from the server logged in as the service account, and SSO should work.

Solution:
Create a new windows service account in the domain that contains the users
Make that new windows service account local admin on the FAP server
Change the windows account that start the FAP service, to use the new service account.

You may need to enter the account with domain\name in the field for name to the FAP service to make it possible for the FAP service to use the account.

Start FAP service again and test if the FAP publish works now.

In FAP Manager for the connection edit, ensure you enter the client name and domain in same capital letters as used for the namespace id in cognos configuration. If the namespace ID is AD then you need to enter AD\username in the FAP manager for the TM1 connection.

Product:
Cognos Controller 10.2.1 Fix Pack 4
Microsoft Windows 2012 R2 server

Symptom:
Error when importing csv file with data, that have worked fine in previous version of Cognos Controller 10.1. The DiscardedRows are the same number as the Rowsread in Log Reports dialog.

Error message:
The value must be numeric.

The data we try to import contain a decimal value; e.g. 000.00

Solution:
Log on to the Cognos Controller server as the service account that run the Cognos Controller services.
Go to controller panel
Go to regional settings
Change to England (UK)
Click tab ‘Location’
Change this to ‘English (United Kingdom)’
Click tab “Administrative”
Click “Change system locale…” and change this to “English (United Kingdom)”:
Click “Copy Settings”
Tick the box “Welcome screen and system accounts”.
Tick the box “New user accounts”:
Click OK
Reboot the Controller application server

I think it is the value of Decimal symbol need to be changed from comma to a period that solves the issue.

The csv file that is imported to controller must be of a specific format.
Text file should use decimal point (not comma) for decimals and semicolon (not comma or
tab) as delimiter between the data fields.

More information:
http://www-01.ibm.com/support/docview.wss?uid=swg21691867

Product:

Cognos Controller 8.5.1

Windows 2008 R2 server

Cognos BI 8.x

Symptom:

When user run a standard report inside Cognos Controller client they get a login dialog from Cognos Connection inside.  Cognos Controller is working in other areas. But when you select “Verify Account Structure” and run the report – you get a login dialog asking for you User ID and Password for the data source: SQLNCLI.1:… instead of the report result in HTML format.

Error message when you test the data source link in Cognos connection:

QE-DEF-0285

OE-DEF-0321

RQP-DEF-0068

UDA-SQL-0031

UDA-SQL-0129

UDA-SQL-0564 [Microsoft OLE DB provider for SQL server] Login failed

for user ‘cognos’ (SQLSTATE=42000, SQLERRORCODE=18456)

Cause:

The REPAIR button has not worked in Cognos Controller Configuration Report Tab. Can be because the user running Controller Configuration program is not system administrator in Cognos Connection. Data source connections have been manually updated in Cognos.

The correct password is not entered in the Cognos Connection data source connections.

Possible Solution:

Manually update the login value in Cognos Connection for the controller database.

Click on Launch – IBM Cognos Administration

Click on Configuration tab

Click on the data source connection you want to edit, starts mostly with SQLNCLI.1

Click on more time on the SQLNCLI name to go into the login object.

then click on the “SET PROPERTIES” icon on the right side of the login object.

Click on Signon tab

Click on Edit the signon… link

Here you can enter the correct password for the controller data source.

Click OK

Click OK

Click on the SQLNCLI link in the top next to the cognos link, so you are back on the data source connection and not in the signon object.

Click on the “Test the connection” icon at the right side of the data source.

Click the TEST button

If it display “Succeeded” then you are good to go.

Click Close

Click Close

Leave Cognos connection and start Cognos controller client and test the report again.

Product:

Cognos Controller 10.1 FAP

Symptom:

I do not see the trickle of data in the FAP log dialog.

Problem:

Correct log level, not set at startup of FAP process.

Solution:

When you setup the Controller FAP process, you must active HIGH logging level to allow the trickling steps to be written to log table.

Go into Cognos Controller FAP Manager.

Edit the source (the controller database) you are using

Set the Log Level to High.

Click Save.

Edit the data mart  (the tm1 connection) you are using.

Set the Log Level to High.

Click Save.

You need to stop the Data marts

You need to stop the Source

Then you need to start the Source

and start the Data mart again

to active your change in logging.

(this will make a intial publish – who may take long time)

Then you will see a line like;

-Start trickling data

-Finished trickling data.

Then you should be able to see when the trickling is done.

Product:

Cognos Controller 10.1.395   (integration version 10.1.408)

IBM Cognos Controller Financial Analytics Publisher

TM1 10.1

Windows 2008 R2 (64 bits)

Symptom:

In FAP logs show error after the New Active source detected and added to scheduling: controller.

Error message:

Could not login to TM1, host: tm1servername, server name:  tm1servicename, user name: AD\service_account

Background information:

All windows server is in one domain called SRV

All users accounts are in one domain called EU

On TM1 server have only installed Cognos TM1 version 10.1 64 bit.

All tm1 service use the a service account in the EU domain.

The FAP service use a service account in the EU domain.

CCR_JAVA_HOME is set to \program files (x86)\ibm\java60\jre, where you have unpacked the jre.zip file that comes with the Cognos Controller media.

A 32 bit ODBC connection called FAP is created to the Controller FAP SQL database.

The Cognos Controller Batch service and COM service use a service account in the SRV domain.

Cognos Configuration for BI have namespace advanced properties set to:

singleSignOnOption      IdentityMapping

multiDomainTrees         True

Solution:

Restart of the Cognos BI service and change of the DC server that Cognos BI authenticate against.

From a DC server for the SRV domain, change to a DC server in the EU domain.

This is made inside Cognos Configuration under the namespace settings.

Host and port:  DC2EU.corp.company.com:389

The FAP service need to use a service account in a domain that Cognos BI service is authentication against.

Other possible solutions:

Install of TM1 32 bit client on the server where the FAP service is installed.

Update the PATH with the folder to the 32 bit TM1 client.

Erase the TM1 cube used for FAP, and start over. It can have become corrupted so the FAP service can not update it.

Product:

IBM Cognos Controller 10.1

Windows 2008 server/Citrix Server for Controller Client

Microsoft Excel 2007

Symptom:

When user inside Cognos Controller click on Reports – Run, Microsoft Excel pop’s up and placed Excel spreadsheet in front of Cognos Controller.

This is irritating in a Citrix session, because it is difficult to switch back to Controller window.

Solution:

On the Citrix Server (Windows 2008 server) for the Cognos Controller client, you need to look into registry value below and change values for Excel to change this behavior.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Microsoft\Office\12.0\Excel

If possible copy the registry values from a working Citrix server to yours server.

Product:

Cognos Controller 10.1

Windows 2008 R2

Symptom:

Get error when select maintain – manage active users from inside Cognos Controller client.

After we have changed the controller database.

Error message:

System.Web.service.Protocols.SoapException: Server was unable to process request. –>

System.Runtime.InteropService.COMException (0x80070070):

Method ‘~’ of object ‘~’ failed

at FrUserValidator.ValidatorClass.IsMenuItemAllowed(String sMenuIDs, String sMode, String sWebServiceAction)

at….

Possible Solution (workaround):

Restart the physical server.

Restart of the Cognos Controller services in Windows 2008 Server did not help.

This error is from the Component Services COM+ Applications.

Product:

Cognos Controller 10.1

Windows 2008 R2

Symptom:

When going into Cognos Controller Configuration and select Report server tab then the Controller Configuration program hang.

Cause:

During the upgrade with a interim fix for Cognos controller the web.config file in c:\Program Files (x86)\ibm\cognos\c10\ControllerProxyServer have been changed. The server name have been changed with local host values.

The report server value is stored in both web.config and registry on HKLM\Software\Wow6432Node\VB and VBA Program Settings\FrangoController\Shares\CRNPath

Problem arise when the values does not match.

Solution:

Open c:\Program Files (x86)\ibm\cognos\c10\ControllerProxyServer web.config in notepad

Change lines

<add key=”crnServer” value=”http://localhost/ibmcognos/cgi-bin/cognos.cgi”/>

<add key=”crnDisp” value=”http://localhost:9300/p2pd/servlet/dispatch”/>

to lines with correct server name

<add key=”crnServer” value=”http://servername.domain.com/ibmcognos/cgi-bin/cognosisapi.dll”/>

<add key=”crnDisp” value=”http:// servername.domain.com:9300/p2pd/servlet/dispatch”/>

Save the file

Open Windows task manager

Mark IBM Cognos Controller Configuration in Applications tab

Right click and select End Task

Start Cognos Controller Configuration program again.

Product:

Cognos Controller 10.1 RTM

Windows 2008 R2 server

Symptom:

When start Cognos Controller client for the first time, it stop at the WSSurl value.

To try to troubleshoot you surf to http://servername/ibmcognos/controllerserver/ccrws.asmx.

Error Message:

Server Error in ‘/ibmcognos/controllerserver’ Application.

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Could not load file or assembly ‘stdole, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. The system cannot find the file specified.

Source Error:

Line 36:         <add assembly=”ADODB, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A” />

Line 37:         <add assembly=”MSDATASRC, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A” />

Line 38:         <add assembly=”stdole, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A” />

Line 39:         <add assembly=”Microsoft.StdFormat, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A” />

Line 40:       </assemblies>

Source File: E:\Program Files (x86)\ibm\cognos\c10\ControllerProxyServer\web.config Line: 38

Assembly Load Trace: The following information can be helpful to determine why the assembly ‘stdole, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ could not be loaded.

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Version Information: Microsoft .NET Framework Version:2.0.50727.5448; ASP.NET Version:2.0.50727.5456

Cause:

Missing file “stdole.dll” on application server

Solution:

Install SQL 2005 32 client on Controller Applications server, including Workstation components, Books Online and development tools.

Or upgrade to latest version of Cognos Controller

More Information:

https://www-304.ibm.com/support/docview.wss?uid=swg21509303

Product:

IBM Cognos Controller 10.1

Windows 7

Symptom:

When you start Cognos Controller Client (ccr.exe) you get a error message.

Error Message:

Invalid database version

This version of Controller requires database version: 851

Cause:

You have upgrade the Cognos Controller software on the server to a later version of Cognos Controller but have not upgrade the local ccr.exe client

Cognos Controller client software can work with different versions of Cognos Controller server software as long as they use the same database version.

Solution:

Uninstall the local Cognos Controller Client

Install the new Cognos Controller Client from the ccrlocalclient.msi file found on the Cognos Controller server in folder c:\Program Files (x86)\ibm\cognos\c10\webcontent\ccr

More Information:

http://www-01.ibm.com/support/docview.wss?uid=swg21367448