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.