Product:

Cognos Tm1 10.2.2 fix pack 7

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

Cognos BI 10.2.2 fix pack 8

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

Microsoft Windows 2012 R2 server

Microsoft SQL server 2014

Symptom:

Cannot login to TM1 application web when surf to http://tm1test:9510/pmpsvc

Error message

“The planning service parameter was not specified or is not one of the configured locations”

Cause:

The value you use in fpmsvc_config.xml file for <external uri=”http://tm1test:9510″/>

Must exist in file E:\Program Files\ibm\cognos\c10_64\webcontent\planning.html

At

// Update the following to point to the location of the planning service(s)

var planningServices = [“http://tm1test:9510″,”http://tm1serversnames:9510”];

Below from other website;

Solution, the steps to setup cam authentication:

To configure TM1 Web and Performance Modeller / Planning Service to use CAM Authentication and Single Signon.

Configuring TM1 Web

By default the URL for TM1Web is http://mytm1server:9510/tm1web.

This works by default with the default installation, however, if your TM1 Server is configured to use CAM Security (IntegratedSecurityMode 5) rather than Native (IntegratedSecurityMode 1) then you will hit issues trying to access it.

To configure TM1Web to use CAM Secured Servers do the following:

STEP 1 – Create the variables_tm1.xml file

This file links BI to the TM1Web Interface using CAM Authentication. Simply make a copy of the file variables_tm1.xml.sample in the BI Server installation directory …\templates\ps\portal and call it variables_tm1.xml. Edit the file to include your tm1server. The file can contain a NETBIOS and FQDN value to ensure it works in all circumstances.

<?xml version=”1.0″ encoding=”UTF-8″?>

<!–

IBM Confidential

 

OCO Source Materials

 

BI and PM: tm1fragments

 

(C) Copyright IBM Corp. 2008, 2017

 

The source code for this program is not published or otherwise

divested of its trade secrets, irrespective of what has been

deposited with the U.S. Copyright Office.

–>

<!–

This file is referenced by the tm1s.cfg file when using CAM authentication.  The “localhost” string should be replaced with the name of the server running TM1Web. For java tm1web, the tm1web.html is accessed when the standalone tm1web uses cam authentication.

–>

 

<CRNenv>

<urls>

<url is-regex=”true”>http://tm1test/TM1Web(/\([aAsS]\([A-Za-z0-9]+\)\))?/TM1WebLogin.aspx</url>

<url is-regex=”true”>http://tm1test/TM1Web(/\([aAsS]\([A-Za-z0-9]+\)\))?/TM1WebLoginHandler.aspx</url>

<url is-regex=”true”>http://tm1test/TM1Web(/\([aAsS]\([A-Za-z0-9]+\)\))?/TM1WebMain.aspx</url>

<url is-regex=”true”>http://tm1test:9510/TM1Web(/\([aAsS]\([A-Za-z0-9]+\)\))?/UrlApi.jsp(\?.*)?(#.*)?</url>

 

<url>../tm1/web/tm1web.html</url>

</urls>

<cookies>

<param name=”cam_passport”/>

</cookies>

</CRNenv>

 

STEP 2 – Add CAMPortalVariableFile to tm1s.cfg

Next you need to add the reference to the variables_tm1.xml file into your TM1 Server and connect BI authentication if it is is not already in place.

Open your TM1 Servers tm1s.cfg file and add/amend the following lines to it.

IntegratedSecurityMode=5

ServerCAMURI=http://mybiserver:9300/p2pd/servlet/dispatch

ClientCAMURI=http://mybiserver/ibmcognos/cgi-bin/cognosisapi.dll

ClientPingCAMPassport=900

CAMPortalVariableFile=portal\variables_TM1.xml

Remember, if your BI Gateway is using CGI and not ISAPI then use cognos.cgi not cognosisapi.dll.

STEP 3 – Configuring TM1Web Main Page

The next step is to configure TM1Web and to avoid service errors when accessing TM1Web. To do this you edit the tm1web.html file in the BI Install Location\webcontent\tm1\web directory.

Open file E:\Program Files\ibm\cognos\c10_64\webcontent\tm1\web\tm1web.html in notepad.

The following change need to be made:

Change the var tm1webServices variable to use references to your TM1 Server as below.

// Update the following to point to the location of the TM1Web service(s)

var tm1webServices = [“http://tm1test:9510”];

STEP 4 – Modify the TM1Web Configuration to choose Admin Server

To modify the TM1Web front page to automatically select an admin server and TM1 Server modify the file tm1web_config.xml in directory

TM1 install location\webapps\tm1web\WEB-INF\configuration.

Change the following arguments to select defaults:

<!– If set, users will not be asked to enter Admin Host during login. –>

<add key=”AdminHostName” value=”mytm1server” />

and optionally

<!– If set, users will not be asked to select a TM1 Server to connect to during login. –>

<add key=”TM1ServerName” value=”GO_New_Stores” />

When complete, save the file and restart the ‘TM1 Application Server’ windows service for the changes to take effect.

Testing TM1Web

To test TM1Web simply go to http://mytm1server:9510/tm1web and you should be prompted to select from a list of available TM1 Servers. Once you have selected the TM1 Server you will be prompted for appropriate Native or CAM Security before being presented with the TM1 Cube View screen.

TM1 Architect

Before you start TM1 Architect the first time adjust this file E:\Program Files\ibm\cognos\tm1_64\bin64\tm1p.ini to have values for CAM.

[TM1]

DataBaseDirectory = ..\samples\tm1\PData

AdminHost =

ConnectLocalAtStartup = F

LocalServerNetworkProtocol = tcp

IntegratedLogin = F

AdvancedRulesEditor = F

AllowImportCAMClients = T

CognosGatewayURI = http://myBIserver/ibmcognos/cgi-bin/cognosisapi.dll

Language=eng

This file is copied to your windows user’s profile when you start TM1 architect the first time – the file cannot be changed in the user profile when the TM1 Architect program is running.

C:\Users\%username%\AppData\Roaming\Applix\TM1\

Steps to configure TM1 Performance Modeller

In order to configure Performance Modeller to function correctly with CAM secured TM1 Servers we need to perform some configuration work.

The steps required are as follows:

STEP 1 – Add required parameters to support Performance Modeller models.

These parameters and settings need to be added or modified in the TM1 Server tm1s.cfg file and the TM1 Server windows service restarted.

ServerCAMURI=http://mybiserver:9300/p2pd/servlet/dispatch

ClientCAMURI=http://mubiserver/ibmcognos/cgi-bin/cognosisapi.dll

ClientPingCAMPassport=900

CAMPortalVariableFile=portal\variables_TM1.xml

DistributedPlanningOutputDir=tunit

ForceReevaluationOfFeedersForFedCellsOnDataChange=T

AllowSeparateNandCRules=T

Some of the above will already have been added to the configuration file if you have previous configured TM1Web.

STEP 2 – Modify the Service Configuration file

Modify the fpm_svc.config file on the TM1 Server. The file resides in the TM1 installation location webapps\pmpsvc\WEB-INF\configuration directory. Stop the TM1 Application server service BEFORE editing this file.

Only the marked arguments need to be completed / corrected:

<?xml version=”1.0″ encoding=”UTF-8″?><fpm_config xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xsi:noNamespaceSchemaLocation=”fpmsvc_config.xsd”>

<service forceQualifiedPaths=”true”>

<businessViewpoint enabled=”false” uri=”http://localhost:9655/bv/main.jsp”/>

<scorecarding enabled=”true”/>

 

<provisioning allowInstalls=”true” allowUpdates=”true” uri=””/>

<resource path=””/>

<users path=””/>

<external uri=”http://tm1test:9510″/>

<session timeout=”60″/>

</service>

<tm1>

<gateway uri=”http://mybiserver/ibmcognos/cgi-bin/cognosisapi.dll”/>

<alternate_gateway_uris>

<alternate_gateway uri=”*”/>

</alternate_gateway_uris>

<dispatcher uri=”http://mybiserver:9300/p2pd/servlet/dispatch”/>

<admin_host name=”mytm1server”>

<servers>

<server name=”proven_techniques”/>

</servers>

</admin_host>

</tm1>

<!–

The Cognos Insight publish feature enforces a set of minimum system requirements that are required to perform a publish. These are requirements on the system running the TM1 Applications service where the new TM1 servers will be created. To change these system requirement settings add the <insight_publish> element.

maximumCDDDataMB – The maximum amount of TM1 data that can be sent in a publish request

maximumTM1ServersAllowed – The maximum number of servers that can run on this machine. This is the maximum number of servers that are registered with the tm1Admin service.

minimumFreeDiskSpaceMbRequired – The amount of disk space that must be available on the drive where the Tm1 data is published.

minimumFreeDiskSpaceMbRequired – The amount of free memory that must be available on the publish server.

–>

<!–

<insight_publish enabled=”true” maximumCDDDataMB=”100″>

<system_requirements maximumTM1ServersAllowed=”10″ minimumFreeDiskSpaceMbRequired=”5000″ minimumFreeMemoryMbRequired=”500″/>

</insight_publish>

–>

<!– If low on disk space you can set a different drive for the published TM1 server data as an alternative to reducing minimumFreeDiskSpaceMbRequired –>

<!–

<insight_publish enabled=”true” maximumCDDDataMB=”100″>

<tm1Data path=”E:\PublishedServers”/>

<system_requirements maximumTM1ServersAllowed=”10″ minimumFreeDiskSpaceMbRequired=”5000″ minimumFreeMemoryMbRequired=”500″/>

</insight_publish>

–>

 

 

<insight pmpsvcPingTime=”30″/>

<insight_publish enabled=”true”/>

</fpm_config>

 

By default, they will be pointing to localhost, you can also change these in Cognos Configuration IF you have NEVER configured TM1 Application Server to run with a Native secured TM1 Server.  Inside Cognos Configuration at TM1 Applications Server at Component Properties you find the External Server URI to change.

By checking this file and adding your Gateway and Dispatcher URI’s you will guarantee the correct settings are in place.

Changes in Cognos Configuration can overwrite any manual updates to the config file.

 

STEP 3 – Install and modify the BI Interoperability software

You have a single ZIP file called bi_interop.zip that resides in a bi_interop directory of the TM1 installation directory (E:\Program Files\ibm\cognos\tm1_64\bi_interop).

Copy this file and expand it into the BI installation directory. This places files in the following directories within the BI installation:

  • Variables_plan.xml in \templates\ps\portal
  • Planning.html in webcontent
  • Pmhub.html in webcontent
  • Icon_active_application.gif in webcontent\icd\feeds\images
  • Icon_active_application.gif in webcontent\ps\portal\images

STEP 4 – Modify the BI Interoperability HTML Files

The two html files extracted into the Webcontent directory need to be modified as follows:

Change in E:\Program Files\ibm\cognos\c10_64\webcontent\planning.html

// Update the following to point to the location of the planning service(s)

var planningServices = [“http://mytm1server.domain.com:9510″,”http://tm1test:9510”];

 

Change in E:\Program Files\ibm\cognos\c10_64\webcontent\pmhub.html

// Update the following to point to the location of the pmhub service(s)

var pmhubURLs = [“http://tm1test:9510″,”http://mytm1server.domain.com:9510”];

Testing Performance Modeller

Now the configuration is complete, restart the TM1 application server service to read all the new parameters and test access to the application through the URL http://mytm1server:9510/pmpsvc

If successful your browser will return a blank applications window.

Click the Open Performance Modeller button on the toolbar. This can take some time to open first time, PM will look for TM1 Servers that have the correct security and parameters. If more than one are found you will be prompted to choose and then Performance Modeller opens.

 

Firewall

In some cases, you need to open following ports in the local Windows Firewall on the server to make it Cognos Tm1 work:

80,9300,9510,5495,5498,12345,12346

Plus ports for your TM1 applications instances.

Memory

In Cognos BI Configuration it is recommended to adjust the memory for java to the function of the BI server

Maximum memory for WebSphere Liberty Profile in MB 1024 change to 4096.

Cognos Configuration TM1 Applications server – component properties – Maximum memory in MB 768 change to 4096.

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

https://www.ibm.com/support/knowledgecenter/SSEP7J_10.2.2/com.ibm.swg.ba.cognos.c8pp_inst.10.2.2.doc/c_installs_verify_ram.html

 

The values depend on your server hardware and what the users will do and how many they are.

Timeout

When using IBM® Cognos® TM1® Applications with IBM Cognos Business Intelligence security, set the pmpsvc session timeout to a value higher than the CAM session timeout to ensure the proper timeout detection. If the Cognos TM1 Applications (pmpsvc) session timeout is set to a value lower than the Cognos BI security (CAM) session timeout, then Cognos TM1 Applications will not properly detect a CAM session termination and will not timeout.

The timeout for TM1 default is 60 minutes in Cognos Configuration – TM1 Applications server – components properties at session timeout (min). Set to a good value calculated to fulfill the requirements.

Can also be changed in the file, Navigate to the fpmsvc_config.xml file in the following location: TM1_install_location\webapps\pmpsvc\WEB-INF\configuration.

Update the default value to a desired time, default is, <session timeout=”60″/>.

Inside tm1s.cfg you can adjust the value of ClientPingCAMPassport, default is

ClientPingCAMPassport=900. Change ClientPingCAMPassport to a good value.

On your Cognos BI system, configure the CAM session timeout using IBM Cognos Configuration.

Enter a value in the Inactivity timeout in seconds’ field in the Security/Authentication section of Cognos Configuration. Set to 10800 seconds to get 3 hours or other good value.

Click BI Configuration > Servlet Gateway > IBM Cognos Servlet Gateway.

Notice the Ping timeout in seconds value. Default 240 seconds is 4 minutes.

Verify that the Ping timeout in seconds and Inactivity timeout in seconds settings in BI Configuration are set the same, and that they are lower than the session timeout setting in the fpmsvc_config.xml file and twice as much as the ClientPingCAMPassport value in the tm1s.cfg file.

Adjust the IIS to have the same value in all timeout positions.

I am Not sure if above is correct about timeout values – please test in your dev Cognos environment first.

Cognos BI DUMP files

If you prefer you can disable the creation of these files by amending a configuration file as below:

  1. On the server where IBM Cognos BI is installed, open the cclWinSEHConfig.xml file from the c10_location\configuration directory.
  2. In the configuration element, change the value of the environment variable setting to 0 (zero) so that it reads <env_var name=”CCL_HWE_ABORT” value=”0″/>

III. Save the file.

  1. Repeat the above steps for any other server(s) that could potentially run reports.

 

Text copied from this sites:

https://allthingscognos.wordpress.com/

https://www.ibm.com/support/knowledgecenter/en/SSMR4U_10.2.2/com.ibm.swg.ba.cognos.express_migration.10.2.2.doc/c_express_inst_mig_trouble_tm1_timeout.html

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

Product:
Cognos Controller 10.3 fix pack 1 =
(IBM Cognos Controller Version 10.3.1.43
Integration Version 10.3.1.19
Install/Updater Kit Version 10.3.1.29)
Microsoft Windows 2012 R2 server
Microsoft SQL 2014 database

Problem:
After upgrade to new version of Cognos Controller 10.3 when you go into the new IBM Cognos Controller Financial Analytics Publisher client (FAP) and click edit on a Source that have log level “detailed” you get a error message.

Other controller database “sources” that are listed work fine to be open by EDIT button in FAP client.

Error message:

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

 

************** Exception Text **************

System.ArgumentOutOfRangeException: InvalidArgument=Value of ‘3’ is not valid for ‘SelectedIndex’.

Parameter name: SelectedIndex

at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)

at FAPClient.frmEditSource.frmEditSource_Load(Object sender, EventArgs e)

at System.Windows.Forms.Form.OnLoad(EventArgs e)

at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)

at System.Windows.Forms.Control.CreateControl()

at System.Windows.Forms.Control.WmShowWindow(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.Form.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

 

************** Loaded Assemblies **************

mscorlib

Assembly Version: 4.0.0.0

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll

—————————————-

FAPClient

Assembly Version: 10.3.1.19

Win32 Version: 10.3.1.19

CodeBase: file:///E:/Program%20Files/ibm/cognos/ccr_64/webcontent/ccr/FAPClient.exe

—————————————-

Microsoft.VisualBasic

Assembly Version: 10.0.0.0

Win32 Version: 12.0.20806.33440 built by: FX45W81RTMREL

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll

—————————————-

System

Assembly Version: 4.0.0.0

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

—————————————-

System.Core

Assembly Version: 4.0.0.0

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

—————————————-

System.Windows.Forms

Assembly Version: 4.0.0.0

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

—————————————-

System.Drawing

Assembly Version: 4.0.0.0

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

—————————————-

System.Runtime.Remoting

Assembly Version: 4.0.0.0

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll

—————————————-

C1.Win.C1FlexGrid.4

Assembly Version: 4.0.20153.110

Win32 Version: 4.0.20153.110

CodeBase: file:///E:/Program%20Files/ibm/cognos/ccr_64/webcontent/ccr/C1.Win.C1FlexGrid.4.DLL

—————————————-

System.Xml

Assembly Version: 4.0.0.0

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

—————————————-

System.Configuration

Assembly Version: 4.0.0.0

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

—————————————-

System.Data

Assembly Version: 4.0.0.0

Win32 Version: 4.0.30319.36372 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll

—————————————-

System.Numerics

Assembly Version: 4.0.0.0

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll

—————————————-

System.Transactions

Assembly Version: 4.0.0.0

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll

—————————————-

System.EnterpriseServices

Assembly Version: 4.0.0.0

Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll

—————————————-

Microsoft.GeneratedCode

Assembly Version: 1.0.0.0

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

—————————————-

 

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

 

For example:

 

<configuration>

<system.windows.forms jitDebugging=”true” />

</configuration>

 

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

Possible workaround:
Looks like the new version of FAP does not support detail logging.
In old version of Controller FAP this setting would show DEBUG log level. Please ensure you take a backup of the SQL database before you do any changes in it. If this does not work, you can restore the Controller FAP database.
So go into Microsoft SQL Server Management Studio.
Connect to the database server there you have your controllerfap database.
Select you ControllerFap database and on table dbo.NRTR_SOURCE right click and select Edit Top 200 Rows.
Far to the right you have column “LogLevel” – here there is a value of 40, change that to 30, for the source you get the error.
Exit out and check that your update is there with SQL command:

SELECT TOP 100 [Name]
,[Status]
,[Type]
,[UserName]
,[Password]
,[NRTRPurgeDate]
,[NRTRPurgeSecNum]
,[NRTRPurgeTextSecNum]
,[CCRMoveIndex]
,[CCRTextMoveIndex]
,[CCRDBUrl]
,[LogLevel]
,[Info]
,[Interval]
,[IntervalCounter]
FROM [ControllerFAP].[dbo].[NRTR_SOURCE]

Now go into your FAP client and on the source tab
mark the name of the data source who have detailed loglevel and click on Edit button.
You should now get into the edit dialog without errors.

The loglevel in “edit source..” show High, instead of Detail as listed.
You can update the server value.
The port number is missing do, so you may need to add it 1433.
Click on Test Connection to see that it works.
Click Save.

You have now updated the FAP to work with the new ControllerFAP database on the new SQL server.

Product:
Cognos Tm1 10.2.2
Microsoft Windows 2012 R2 server

Problem:
Can not connect to TM1 server from other computer, but it works fine direct on the TM1 server to connect from TM1 architect.

Possible Solution:
The Windows firewall is blocking the connection.
This looks like TM1 architect is not responding for a long time and then you are not seeing a list of TM1 applications.

You need port 5498 open to get contact with the TM1 admin service from the TM1 architect client.
You need the TM1 applications port (e.g. 12345) to connect to the application from TM1 architect client.

Go to control panel on the TM1 windows server
Click on Windows firewall
Click on Advance settings
Select inbound rules and click on New Rule on the left
Select Port and click next
Enter list of ports at Specific local ports
(e.g. 80,9300,9080,9510,5495,5498,12345,12346)
ensure you use comma between the port numbers.
click Next
Select Allow the connection and click next
Keep all marked for where the rule apply and click next
Set a name (e.g. cognos) and click finish

Now test again from you remote computer where TM1 architect are installed.

Cognos Controller 10.3 need this ports;
80,9300,9080
Cognos BI 10.2.2 need this ports;
80,9300,9362 ,25,389,1433
Cognos Tm1 10.2.2 need this ports;
80,9510,9513,5495,5498,12345,12346 + your TM1 applications ports.

If you have all products, then you need to open all this ports between the Cognos Servers.
You need also open port for database connections, like 1433 for Microsoft SQL server and 389 for Active Directory contact.
Port 25 is used for sending mail from Cognos BI.

No port over 65535 is allowed to be configured in Windows firewall.
TM1 sample application Proven_techniques uses port 83333 as default and need therefor to be changed to port 13333.
PortNumber=12345 is for planning sample application.
PortNumber=12346 is for SDATA app, that you use for opsconsole as default login.
PortNumber=9510 is used by CAFE and PM.

You can in TM1S.CFG set a client port number for each tm1 application. Should be used if you have firewalls between server and client computer, or client is a citrix server. This number need also to be open in the firewall.
# Note: Be sure to assign unique port numbers for the server and client message ports. If you have two servers running on the same machine with the same port number, the message activity may cause a system failure.
ClientMessagePortNumber=32345

Best is if you keep a notepad txt file on your server where you enter each TM1 PortNumber and ClientMessagePortNumber, so you easy can see that you not by mistake reuse the same number.

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

Product:
Cognos Controller 10.3
Microsoft Windows 2012 R2 server

Problem:
When starting the Cognos Controller client for the first time in a new installation, you get a error like this:
An error occurred while trying to access the server.
Details give:
The request failed with HTTP status 405: Method Not Allowed.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Cognos.Controller.ControllerSoapHttpClientProtocol.Invoke(String methodname, Object[] parameters)
at Cognos.Controller.Proxy.Light.WSLight.CheckServerConnection(String sGuid, String sUser)
at Cognos.Controller.Direct.ServerInfoD.CheckServerConnection()
at CCR.AppContext.CheckConnectionToServer()

If you start Internet explorer and surf to
http://APPSERVER:80/ibmcognos/controllerServer/ccrws.asmx
you get a HTTP error 404

Solution:
Ensure that on the Cognos Controller server you have installed windows roles for .NET extensibility 4.5 and ASP.NET 3.5 and ASP.NET 4.5 under Application Development for IIS server role.

This show some of what need to be in the Windows server to make Cognos Controller work:
http://www-01.ibm.com/support/docview.wss?uid=swg21986254

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

Product:
Cognos BI 10.2.2
Microsoft Windows 2012 R2 server

Problem:
When starting the Cognos BI service, it takes long time and we get a error.
[Start Service]
[ ERROR ] CFG-ERR-0106 IBM Cognos Configuration did not receive a response from the IBM Cognos service in the time allotted.
Check that IBM Cognos service is available and properly configured.

In this cbs_start_WebSphereLiberty.logfile the text is:
Wed Apr 26 15:13:27 2017 ERROR t[1a08] CBSSocketCommand failed to connect, CAM error: -12CAM-CRP-0026 The underlying socket: ‘10.151.38.35:9300’ returned an error.10061Could not connect the socket, errno: 0x274d(10061)
Wed Apr 26 15:13:29 2017 INFO t[1a08] CBSBootstrapService testReadyByPingingWin – child processes are not ready, stop trying.

Solution:
The windows service account that run the IBM Cognos service does not have enough rights in the Windows box. IT department have a process that every night they remove accounts direct from the local administrator group. This service account was in there the other day when system was installed. But as of removing it then the Cognos BI process not successfully started.

Ensure that the Cognos BI service account has needed rights on the server.

Other causes:
http://www-01.ibm.com/support/docview.wss?uid=swg21646350

Product:
Cognos TM1 architect 10.2.2
Microsoft Windows 2012 R2 standard server

Problem:
Login dialog when you start TM1 architect, and you have configured it to be SSO to the Cognos BI Cognos Connection.
If you surf to http://cognosBIserver.domain.com/ibmcognos you are automatically logged in.

Login dialog titled : Windows Security

tm1a.exe connecting to biservername.domain.com

User name

Password

Solution:
On the computer where you start TM1 architect, go to control panel and internet options.
Go to Security tab.
Select Local Intranet and click on sites button.
Click on advance button.
Enter the URL to the Cognos BI server;
http://biservername.domain.com
Click on Add button.
Click Close.
Click OK.

Restart TM1 architect, and see if the SSO are working.

For SSO to work with TM1 clients and Cognos BI the CAM authentication Bi server must be in local intranet or trusted intranet zone of Internet Explorer on client computer.

Product:
Cognos TM1 10.2.2
Microsoft Windows 2012 R2 standard server

Problem:
When inside TM1 architect try to add a new user (clients – add new client) you get a error message about the CAM. The dialog will not show up.

Possible solution:
The value in the file tm1p.ini for that user is not updated with a URL to the cognos bi server.

You update the TM1S.CFG file for the TM1 server – but this change is not copied to the TM1 architect users.

IntegratedSecurityMode=2
ServerCAMURI=http://biservername:9300/p2pd/servlet/dispatch
ClientCAMURI=http://biservername.domain.com:80/ibmcognos/cgi-bin/cognosisapi.dll
ClientPingCAMPassport=900
CAMPortalVariableFile=portal\variables_TM1.xml

Only new TM1 architect users will get value from file E:\Program Files\ibm\cognos\tm1_64\bin64\tm1p.ini.

You need to close TM1 architect and update this file
C:\Users\%username%\AppData\Roaming\Applix\TM1\tm1p.ini in notepad.

Add values for
AllowImportCAMClients = T
CognosGatewayURI = http://biservername.domain.com:80/ibmcognos/cgi-bin/cognosisapi.dll

save the tm1p.ini file and start the TM1 architect program again.

Product:
Cognos Controller 10.3
Oracle 12c database
Microsoft Windows 2008 R2 Server

Problem:
Standard Error generated when running Multi Period Locking report, and you have not selected a “Use Filter”.

Error message:
“Number: 5
Source: FrangoDirect.PerLockHandler.SelectMultiPerLocks#System.Web.Services
Description: System.Web.Services.Protocols.SoapException:
Server was unable to process request. —> System.InvalidCastException:
Conversion from type ‘DBNull’ to type ‘Date’ is not valid……..”

Possible Solution:
Set a Selected filter when using “Multi Period Locking” and run the report for a specific period.

This is different behavior since Controller version 10.1.1 where this did not give a error.

Other workaround is to enter a date in the column for date in the “Define Submission” dialog in Cognos Controller for all rows.

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

Product:
Cognos Controller 10.3
Oracle 12c database
Microsoft Windows 2008 R2 server

Problem:
Got error in Cognos Controller client when doing a database optimization or run a Reconcile – Intercompany Balances.

Error message:
An unexpected error has occurred

System.ArgumentException: System.Web.Services.Protocols.SoapException: Server was unable to process request. —> System.Exception: fgsql c:\program files\ibm\cognos\ccr_64\server\progs\fgsql.prg Error in line 324 Connection handle is invalid. 1466……

Solution:
Only the 64 bit oracle drivers are installed. Install the 32 bit oracle drivers on the Cognos Controller server.
The small calculations component is still 32 bit in the 64 bit version of Cognos Controller. Therefor you must have both 64 bit and 32 bit database drivers installed on the Controller servers.

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

Product:
Cognos Controller 10.3
Microsoft Windows 2012 server

Problem:
At start of cognos controller client, from a new installation, you get a error message.

Error message:
An error occurred while trying to access the server.
http://localhost/ibmcognos/controllerserver

The request failed with HTTP status 404: Not Found.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Cognos.Controller.ControllerSoapHttpClientProtocol.Invoke(String methodname, Object[] parameters)
at Cognos.Controller.Proxy.Light.WSLight.CheckServerConnection(String sGuid, String sUser)
at Cognos.Controller.Direct.ServerInfoD.CheckServerConnection()
at CCR.AppContext.CheckConnectionToServer()

Solution:
The app folder in IIS for controllerserver was misspelled, recreate the application controllerserver in IIS manager.