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’.

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:

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.

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.

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.

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.

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.

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.

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.

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.

Solution:
Install Cognos Analytics 11 on the windows server.
Install DB2 11 on the database server, ensure the local administrator is administrator on the db2 database to.

From the DB2 server copy the jar files needed from folder
C:\Program Files\IBM\SQLLIB\java. Place the two filesd2jcc_license_cu.jar db2jcc4.jar
in folder c:\program files\ibm\cognos\analytics\drivers on the Cognos BI server.

Start Cognos Configuration and setup up the values for the environment.
On the Content Store tab enter the values for the DB2:
database server and port number: Enter ipadress:50000
User id and password: Enter the namn and password you want the schema to have.
Database name: Enter the name of the database you want it to have.

Click save.
Right click on Content store and select “Generate DDL”.
This will create a SQL script you should run on the DB2 server to create the needed database.
Copy the file C:/Program Files/ibm/cognos/analytics/configuration/schemas/content/db2/createDb.sql to the DB2 server.
Place the file in folder c:\install.

When the database is finish created in DB2 server, then go to the Cognos Analytics 11 server and from inside Cognos Configuration click on START. This will start the Cognos BI service, and connect it to the database and create the tables needed.

The Cognos status will show this for a successful start;
[Launching a JVM using ‘Maximum memory in MB’]
Successfully launched a test JVM with the memory setting of ‘4096’. Note that this does not guarantee that the IBM Cognos service will start and run successfully.

To see which JVM options are based on this setting, view ibmcognos_location/bin64/bootstrap_wlp_.xml and see your JVM documentation for an explanation of those options.

[Archive Local File System Root]
Since the value is empty, the feature is disabled. There is nothing to test.