Product:

Cognos Controller 10.1

Adobe Reader 10

Symptom:

When Cognos Controller user run a standard report, and it show fine in HTML.

Then user change to view it in Adobe Reader PDF format, then they only get a progress bar and the PDF does not show.

Problem:

PDF report does not show – user see a progress bar instead.

Cause:

Adobe Reader 10 is not supported by Cognos Controller 10.1

More information here

http://www-01.ibm.com/support/docview.wss?uid=swg27020782#eft

Solution:

Start Adobe Reader X on the client computer and under menu

edit – preferences

select general dialog

uncheck “Enable Protected Mode at startup”

click OK

Then start Cognos Controller Client, and test a standard report again.

This change is saved per user on the client, so the best is if the IT department can roll out this change of Adobe Reader with a GPO.

Product:

Cognos Controller 10.1

Symptom:

All users have access to all in Cognos Controller even due they should not because the users are entered and the security groups are created and applied inside Cognos Controller.

Problem:

Only the ADM user can inside Cognos Controller active or deactivate the Security System, from inside the dialog Maintain -Rights -users.

Cause:

When Cognos Controller is using Cognos BI authentication, the CAM users, then the first person to login to Cognos Controller at a new installation become the internal ADM user in Cognos Controller.

Other persons you add to Cognos Controller as Group Administrators can change users rights in the system, but not active Cognos Controller to use the Security settings.

Solution:

Log in to Cognos Controller as the ADM user.

This is the person that is shown as ADM user in MAINTAIN – RIGHTS -USERS dialog.

Go to MAINTAIN – RIGHTS -USERS dialog

In the lower left corner mark “Security Systems Enabled”

Click on SAVE icon

Exit Cognos Controller Client.

Recommended to do this the first time you login to Cognos Controller as ADM.

A person in Cognos Controller that is Group Administrator ( and part of the Cognos connection group controller administrators) can do all changes and security changes in the Cognos Controller application except only this on ( mark the “Security Systems Enabled”).

Product:

Cognos Controller 10.1

Windows 2008 server

Symptom:

After change of the database in Cognos Controller solution, the users are not able to run standard reports. They get a error message when the HTML page should show.

Error message:

AAA-AUT-0011

Invalid namespace was selected

(ogiltigt namnutrymme har valts)

Possible Solution:

Restart the Cognos Controller server including the Cognos BI services.

Note: that if you change the name of the database you need to update the Controller Configuration database connections of that change.

Also you must press the REPAIR button in controller configuration at the Report Server tab.

Product:

Cognos Controller 10.1.4801.127

Windows 2008 R2 Server

Symptom:

Error when you surf to cognos controller (cognos connection) website after you have applied Cognos Controller fix pack.

Error message:

HTTP Error 404.0 – Not Found

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable. Detailed Error InformationModule IIS Web Core

Notification MapRequestHandler

Handler StaticFile

Error Code 0x80070002

Requested URL http://servername:80/cgi-bin/cognosisapi.dll?b_action=xts.run&m=portal/main.xts&startwel=yes

Physical Path C:\inetpub\wwwroot\cgi-bin\cognosisapi.dll

Logon Method Anonymous

Logon User Anonymous

Cause:

The content of the file default.htm and index.html in folder D:\Program Files (x86)\ibm\cognos\c10\webcontent are wrong.

Solution:

Open file default.html in notepad

Find section that contains:

function genMainContent()

                                    {

document.body.innerHTML = ‘<div align=”center”><img src=”‘ + splashImg.src + ‘” style=”position:relative; top:80px”></div>’;

window.setTimeout(“window.location.replace(‘../cgi-bin/cognosisapi.dll?b_action=xts.run&m=portal/main.xts&startwel=yes’)”,5);

                                    }

                        </script>

Remove the ../ part in front of cgi-bin so the section looks like this:

function genMainContent()

                                    {

document.body.innerHTML = ‘<div align=”center”><img src=”‘ + splashImg.src + ‘” style=”position:relative; top:80px”></div>’;

window.setTimeout(“window.location.replace(‘cgi-bin/cognosisapi.dll?b_action=xts.run&m=portal/main.xts&startwel=yes’)”,5);

                                    }

                        </script>

Save the file and exit notepad.

Do the same change in file index.html

Restart iis with the dos command iisreset.

Try to surf to the page again.

Product:

Cognos Controller 10.1.405

Windows 2008 R2 server

Symptom:

Consolidation in Cognos controller does not work after update.

If you look in the help – system info dialog inside Cognos controller client you see version number:

IBM Cognos Controller version: 10.1.405

Integration version: 0.0.0

Cause:

When integration version is showing zeros, then some part of the Cognos Controller has not been installed correct.

Correct value for integration version should be: 10.1.416.

Possible Solution:

On the Cognos Controller Windows server:

Launch a command prompt by clicking “Start” – “Run” and then typing in “CMD” <Enter>
Change directory using: cd C:\Windows\SysWOW64\common

Here is the file xceedzip, that maybe is not correct installed.

Register the file using: regsvr32.exe xceedzip.dll

Restart then the server.

Cognos Controller client version must be the same as the Cognos Controller version installed on the Application server.

More Information:

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

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

If you still have problems, remove the frangovfp com+ components and add them again.

Product:

Cognos Controller 10.1.405

Tm1 9.5.2

Windows 2008 R2 server

Symptom:

When doing a initial publish in Financial Analytics Publisher you get a error message that it can not login to the TM1 server cube.

This happen after you have upgrade Cognos Controller with a Fix Pack.

Error Message:

FAP Service Scheduler CRITICAL

Could not login to TM1, host: sr01639, server name: tm1fap, user name:  AD\username

If you keep the mouse over the error message you will see this message:

com/cognos/ccf/c8itk/ITKProxyJNI.jnIsLoggedOn(J)Z

Cause:

When using Cognos Controller with Cognos BI CAM security to TM1 version 9.5.2 you need to use the correct c8itk4j.jar file.

Solution:

Stop the Cognos FAP service.

Go to folder D:\Program Files (x86)\ibm\cognos\c10\server\FAP\lib

Rename the file c8itk4j.jar to c8itk4j.jar.old

Copy the c8itk4j.jar file from folder D:\Program Files (x86)\ibm\cognos\c10\server\FAP\lib\TM1_9.5_CAM_compatibility

You should now have c8itk4j.jar filesize to be 22 KB.

Start the Cognos FAP service.

Go the the datamarts tab in Financial Analytics Publisher and click start to test again.

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:
IBM Cognos Controller 10.2.1 FAP
C8BISRVR_UPDATE_version=C8BISRVR-AW64-ML-RTM-10.2.5002.78-0
C8BISRVR_UPDATE_name=IBM Cognos Business Intelligence Server Update
CONTRL_UPDATE_version=CCR-AW64-ML-RTM-10.2.5003.68-0
CONTRL_UPDATE_name=IBM Cognos Controller Update
Microsoft Windows 2008 R2 Server

Problem:
After update of certificate on TM1 server, the FAP will not work.

Error message:
2016-10-15 13:36:58,382 [schedulerThread] INFO Scheduler – FAP service started
2016-10-15 13:37:31,251 [schedulerThread] ERROR Scheduler – Could not logon to TM1
com.ibm.cognos.tm1.TM1Exception: SystemServerNotFound
at com.ibm.cognos.tm1.API.getServerSecurityMode(Native Method)
at com.ibm.cognos.fap.common.persistence.tm1.TM1Context.preLoginCheckIfCAM(TM1Context.java:62)
at com.ibm.cognos.fap.service.schedule.Scheduler.updateDatamarts(Scheduler.java:454)
at com.ibm.cognos.fap.service.schedule.Scheduler.run(Scheduler.java:230)
at com.ibm.cognos.fap.service.schedule.Scheduler$1.run(Scheduler.java:144)
at java.lang.Thread.run(Thread.java:781)

Solution:
You have the FAP service installed on the Cognos Controller server, and not the TM1 10.2.2 server.
Then there is a TM1 client installed on the Cognos Controller server that also need to have the certifikate updated.

Stop the Cognos services.
Backup the folder D:\Program Files\ibm\cognos\tm1_64\bin64\ssl and D:\Program Files\ibm\cognos\tm1_64\bin\ssl

Download the updated TM1 SSL Certificates from the following location: http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCognos+TM1&fixids=BA-CTM1-SSL-ZIP-IF001

Extract the downloaded file/archive and extract it to any directory. For the purpose of this document, our files will be extracted in to <tm1_client_install_dir>\tm1_64\NewSSLCerts\

Copy the contents of the folder you extracted earlier <tm1_client_install_dir>\tm1_64\NewSSLCerts\ , and place them inside of the 2 directories listed above in Step 4. During this process, you will be required to REPLACE all conflicting files as we must replace the old certificate files with new ones.

After all files have been copied successfully, navigate to <tm1_client_install_dir>\tm1_64\bin\ssl\

Execute the uninstallSSL.bat file, to uninstall old keys from the Windows Keystore

If uninstallSSL.bat does not exist, run importsslcert.exe -remove from Command Line

Execute the importsslcert.exe file, to install the new keys in to the Windows Keystore
Start the Cognos services.

Start IBM Cognos FAP service.

Login to IBM Cognos Controller Financial Analytics Publisher and do a initial publish by click on START in the Data Marts tab.

If it works, then the certificate it replaced good.

Product:
Cognos Controller FAP 10.1.1
Cognos TM1 10.2.2
Windows 2008 R2 Server

Problem:
When starting the FAP service, where we use Cognos BI CAM authentication, we get a error in the logs that say:
“Could not login to TM1, host: , server name: , user name: <namespace\username>”
C8ITKShared (C:\Program Files\IBM\cognos\TM1_64\bin64\ C8ITKShared.dll is not a valid Win32 application.)

Background:
TM1 10.2.2 64 bit server installed to same Windows server as the Controller FAP Service.
The Windows FAP Service are 32 bit and uses 32 bit dll.
The new FAP client is 64 bit and uses the 64 bit dll and database drivers.
Default install of TM1 10.2.2 only install 64 bit dll files for TM1.

Solution:
Install TM1 Architect in 32 bit version to the server.
Add the path to the C8ITKShared.dll to the system path e.g. C:\Program Files (x86)\IBM\cognos\TM1\bin.
Right click on My Computer and select properties
Click on Advance System Settings
Click Environment Variables
Select PATH and click Edit
Update the path and save.
Click OK to exit dialog.
Restart the Server.

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

Product:
Cognos Controller FAP 10.1.1
Cognos TM1 10.2.2
Windows 2008 R2
Oracle Database
Problem:
FAP process stops when it founds a user in Controller that does not exist in CAM source (LDAP or AD)
Error in FAP log:
2015-01-07 12:36:03,673 [IP:FAP] ERROR RetryInterceptor – Trial 3 failed for method addCAMUser
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
at com.ibm.cognos.fap.common.persistence.retry.RetryInterceptor.intercept(RetryInterceptor.java:43)
at com.ibm.cognos.fap.service.persistence.tm1.SecurityTM1$$EnhancerByCGLIB$$3867900c.addCAMUser()
at com.ibm.cognos.fap.service.security.User.createUsers(User.java:87)
at com.ibm.cognos.fap.service.security.Security.publish(Security.java:64)
at com.ibm.cognos.fap.service.schedule.DatamartTimerTask.initialPublish(DatamartTimerTask.java:501)
at com.ibm.cognos.fap.service.schedule.DatamartTimerTask.access$300(DatamartTimerTask.java:80)
at com.ibm.cognos.fap.service.schedule.DatamartTimerTask$1.run(DatamartTimerTask.java:367)
at java.lang.Thread.run(Thread.java:736)
Caused by:
com.ibm.cognos.fap.common.exception.LoggedException: Could not add CAM user AD\username1 with CAMID
at com.ibm.cognos.fap.service.persistence.tm1.SecurityTM1.addCAMUser(SecurityTM1.java:320)
… 12 more
Caused by:
com.ibm.cognos.tm1.TM1Exception: ObjectRegistrationFailed
at com.ibm.cognos.fap.service.persistence.tm1.SecurityTM1.addCAMUser(SecurityTM1.java:314)
… 12 more

Possible Solution:
Go into the Cognos Controller client, and erase all users that should not be there. That has left the company and does not exist in the Active Directory.
http://www-01.ibm.com/support/docview.wss?uid=swg21632436
Different solution is to run SQL script to erase all users that have no CAMID in the table XCAMUSER inside the Cognos Controller database.
Start SQL developer and connect to the Cognos Controller database
Enter below to list the free rows:
Select * from frango.xcamuser where camid = ‘ ‘;
Enter below to make a copy of the table before deleting its contents:
create table xcamuser_backup as select * from xcamuser;
Enter below to delete the empty rows:
Delete from frango.xcamuser where camid = ‘ ‘;