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
Windows 2008 R2 Server
Cognos TM1 10.2.2
Oracle database

Issue:
In a multi server setup, when you try to connect to the TM1 server from a terminal server where Cognos TM1 Architect is installed, you get the list of TM1 servers, but when you click on ONE TM1 server ( for example the one called FAP ) then there is no login. Only a not responding message for some time, and then you are back inside TM1 Architect.
If you use TM1 Architect on the same server as where TM1 is installed, then it works fine.

Possible Solution:
There are two networks cards in the TM1 server machine. One network card for access by clients, and the other network card for the company backup routines.
TM1 server will bind and only use the first network card found on the Microsoft Windows 2008 server. And if that is not the card used by clients, you will get this issue.
Go to Control Panel
Go to Network and Sharing Center
Click Change adapter settings
Press the ALT key to get menus on top in the dialog
Select Advance – advance settings from the menu
In adaptor and bindings dialog for connections you see two networks listed
Mark the one that belongs to the client network ( it may start with ip 10 ) and click on the up arrow icon on the right.
Click OK
Close the dialog.
Restart the TM1 services, and test again from TM1 Architect on the Terminal server or client computer.

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 TM1 10.2.2
Windows 2008 R2 Server

Issue:
How do I copy a cube from on TM1 server to another TM1 server in a different environment? The 2 TM1 servers are part of two different BI installations, they use the same Active Directory for authentication, and there are no firewall issues between the servers.

Possible Solution:
Use a ODBO connection in Cognos TM1 Architect to create the copy.
Start TM1 Architect and log in to the receiving TM1 server.
Right click and select to create a new process.
Select Datasource type: ODBO – cube.
In connection you need to enter this information:
ODBO Provider: IBM Cognos TM1 OLE DB MD Provider
ODBO Location: servername.domain.com (servername of the windows host that have TM1 admin service)
ODBO Datasource: FAP (name of the TM1 server where you want to get data from)
ODBO Catalog:
ODBO UserID: username (name of the admin user in TM1 application)
ODBO Password: password
Additional Connection Parameters: Provider String=”CAMNamespace=CDS”
The additional Connection Parameters is only if you have a TM1 application that use CAM/BI authentication – enter the name of the Cognos BI namespace, in our example CDS.
Click on CONNECT button – if no errors then you wrote the correct values above.
Go to Load ODBO Cube dialog tab
Select ODBO Cube to load from: FAPMonthlyCompanyDetails (or any other cube you want to import)
Select TM1 Cube to load to: FAPMonth (or any other name you have for it)
Cube Type: Physical Cube
TM1 Cube Action: Create Cube
Data Action: Store Values
Click on Cube Dimensions dialog tab
Here you can change what dimensions the values should connect to, or let the import create the new dimensions in your TM1 receiving server.
Click on MDX Query tab
Here you should be possible to adjust the MDX if you need to.
Click SAVE icon to save the process, give it a name like: FAP import from external server
Run the process.
Depending on the size of the TM1 Cube this can take some time.
When done you should have a copy of the cube and the dimensions.

More Information:
http://blog.tm1tutorials.com/2012/07/27/automating-data-transfers-between-tm1-servers/
http://blog.tm1tutorials.com/tag/odbo/

Product:
Cognos Planning 10.1.1
Windows 2008 R2 Server
Oracle database

Problem:
When a user inside Cognos Planning Administration Console ( CAC ) click on the Monitoring Console tab he get a error message and when he click OK the CAC program exits (crash).

Error message:
Run time error 13 – type mismatch

Solution:
Truncate two tables inside the Cognos Planning Store.

p_pnrequestprogress
and p_pnrequest

Start SQL developer
Login to the database as COGPLAN (the schema that have access as the planning and planning store databases)
Enter;

truncate p_pnrequestprogress
truncate p_pnrequest

Commit
And test again from inside Cognos Planning Administrator to click on Monitoring Console.

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 = ‘ ‘;

Product:
Cognos BI 10.2.1
Windows 2008 R2 server

Problem:
When run a report and then click on link to drill down to other report (or same report with other parameters) you get an error message.
Error Message:
DPR-ERR-2014
Unable to load balance the request because no nodes in the cluster are available, or no nodes are configured for the service: reportService.

Possible solution:
Check the report in Report studio.
The link is pointing to a report that does not exist, probably have you changed the name of the report, and not updated the links inside the report to this new name.
The error is misleading that there is a platform issue, first check that the report exist with the name that is requested.

Product:
IBM Cognos Planning 10.1.1 Fix Pack 3
Microsoft Windows 2008 R2 server
Oracle Database

Symptom:
When user in CAC (Cognos Planning Administration Console) click on Monitoring Console tab to Monitor a Deployment they get a error message. When they click OK on error message the CAC is closed down.

Error message:
‘Runtime Error 13’
‘Type Mismatch’

Solution:
Stop the Cognos BI and Cognos Planning services in Windows on all Planning servers.
Log into the Planning Store database with SQL developer ( or TOAD ).
Ensure you have a backup of the oracle database.
Run this commands to truncate the two tables:

truncate table p_pnrequestprogress;
truncate table p_pnrequest;

Start Cognos Configuration for the server that contain Content Manager first.
Start the Cognos services here first – both BI and Cognos Planning.
After they are up, then go to next server – the Cognos Planning Job server.
Start Cognos Configuration for the Planning Job server and start that as second.
When all the Planning services are up, go into CAC and test again.

The start order of the Cognos BI and Planning servers are important.

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

Product:
Cognos BI 10.2.1 Cognos Connection

Problem:
User cannot replace a report in a folder with a different report he copied from a different folder. This is because the report to be pasted has different security settings for the user than the report in the target.
In the source folder you only have read, this means you can see reports and use them in report studio.
In the target folder you also have write access, this means you can create folders and paste reports there. But you cannot replace a report with a identical report from the source folder, because there the report is set with only READ access and not READ/WRITE.

Solution:
In the target folder you must have SET POLICY to be able to paste a report with other rights that the report you try to replace.
Workaround is to erase the report first, and then paste a new report into the folder. A new report does not change policy, and therefore can you save a report in a folder where you have write access.
If you only add new object to the target folder in Cognos Connection, you can manage with WRITE rights.
To work with a report or package you need to have READ, EXECUTE and TRAVERSE rights. If you only have EXECUTE and TRAVERSE you can run the report, or use the FM package in a report, but you cannot edit it in a Report Studio.

Product:
Cognos BI 10.2.1
Windows 2008 R2 server

Problem:
How to move reports and keep reference link intact?

Solution:
Drill through reports are linked with path and report ID, which gives this effect when you adjust the report.

Rename
When renamed a report, all involved links will be changed accordingly.

Copy and paste to new folder
All involved links will be changed accordingly.

Cut and paste both source and target report to new folder
All involved links will be changed accordingly.

Cut and paste target report to new folder
All involved links will be changed accordingly.

Move target report to new folder (found under More actions)
All involved links will be changed accordingly.

Open it and save as same name
All involved links will be broken, including drill through, portal page and Job

Open report A
Copy report to clipboard,
Change XML,
Open report from clipboard
Save as report A

Copy to another folder, then change it, then copy back
All involved links won’t be impacted

Copy report A to My folder
Open report A from My Folder
Change report A from My Folder , add color to a column.
Copy report A from My folder to original folder and overwrite old report

Copy to another folder, then copy report to XML, change XML and then save it as same name, then copy back
All involved links won’t be impacted

Copy report A to My folder
Open report A from My Folder
Copy report to clipboard from My Folder
Change XML,
Open report from clipboard
Save as report A in My folder and overwrite report A
Copy report A from My folder to original folder and overwrite old report

Copy to another folder, then save any other report as same name, then copy back
All involved links won’t be impacted

Copy report A to My folder
Save any other report as report A in My folder and overwrite report A
Copy report A from My folder to original folder and overwrite old report

Merge two drill through target reports to one
Given Source report A -> Target report A, Source report B -> Target report B,
request to change Source report B ->Target report A

Steps:
Delete Target report A
rename Target report B to Target A

More Information:
http://www-01.ibm.com/support/docview.wss?uid=swg21341623
http://cognosknowhow.blogspot.se/2013/01/how-to-avoid-breaking-report-link-for.html