Product:
Cognos Controller 10.3
Microsoft Windows 2012 R2 Server
Microsoft SQL 2014 server

Problem:
Surf to controller web give blank page. If you try to surf to http://localhost:9080/fcm.web/login instead of http://servername:9080/fcm.web/login it works fine.

Solution:
Ensure you surf to FQDN and that is in your Trusted Zone in IE. Local intranet zone is not good enough. You must surf to http://servername.domain.com:9080/fcm.web/

How to install Controller web:
During installation on your Cognos Controller server select to install the controller web parts.
This will create the folder C:\Program Files\IBM\cognos\ccr_64\fcmweb

Locate the file server.env in the C:\Program Files\IBM\cognos\ccr_64\fcmweb\wlp\etc\ folder.
Open the file server.env and set the JAVA_HOME installation directory to JAVA_HOME=C:/Program Files/IBM/cognos/ccr_64/fcmweb/jre/jre.
To synchronize Controller Web with Uniform Data Language (UDL) files defined for databases used by Controller, run SyncDBConf.bat as an administrator from the command prompt.

SyncDBConf.bat takes two parameters:
The UDL files folder: the path to the folder containing UDL files (specifying database connections) defined for Cognos Controller.
The datasource folder: the output path for the folder that shall contain the data sources generated from the UDL files.
For example:
C:/Program Files/IBM/cognos/ccr_64/fcmweb/SyncDBConf.bat       ..\Data     wlp\usr\shared\config\datasources

Locate the file com.ibm.cognos.fcm.web.properties in the C:\Program Files\IBM\cognos\ccr_64\fcmweb\wlp\usr\servers\fcm.web folder.
Open the file com.ibm.cognos.fcm.web.properties and set the login mode to loginMode=NATIVE.

Optionally you can change the available memory.
Locate the file jvm.options in the C:\Program Files\IBM\cognos\ccr_64\fcmweb\wlp\etc\ folder.
This is part of that file;

# Java Heap size.
# In production, setting min and max to same value can provide the best performance by avoiding heap expansion and contraction.
# But high min value increases startup time, which may be undesired in a dev environment.
-Xms2g
-Xmx4g

Create a Microsoft Windows service by running the file install_service.bat in the folder C:\Program Files\IBM\cognos\ccr_64\fcmweb\install_service.bat.
In the Windows Services console find IBM Cognos Controller Web and start the service.
Log in to Controller Web via your browser using the following url: http://[servername.domain.com]:9080/fcm.web/login.

The Controller web server name must be in TRUSTED ZONE in internet explorer.
Go to the Control panel on your workstation – click on internet options.
Click on Security tab
Mark Trusted sites and click on Sites button.
Enter the name of your Controller web server and click add. You may need to untick the “require server verification for all sites in this zone”.

You must surf to http://servername.domain.com:9080/fcm.web/

If you surf to http://servername.domain.com:9080/FCM.WEB/ you get a message like this

IBM WebSphere Application Server
Context Root Not Found

Close IE and try again with correct address.

If you surf to http://servername.domain.com:9080/ you get a message like this
Update Available. Click to download WebSphere Application Server Liberty Runtime

Do not update – close IE and try again with correct address.

If you change the Cognos controller databases, after the initial configuration of IBM Controller Web, then you need to stop the Controller Web Windows service, before you run SyncDBConf.bat again to collect the new database definitions.

To make Controller WEB work with CAM (Cognos Access Manager) :

You must configure IBM Cognos BI to not allow for anonymous authentication. You must also specify the Controller Web settings as below.

In the Cognos BI installation folder, /templates/ps/portal/, create a file with the name variables_CCRWeb.xml.
The content of the file variables_CCRWeb.xml must be as follows:

<CRNenv c_cmd=”http://controllerservername:9080/fcm.web/cam_login”>

<cookies>

<param name=”cam_passport”/>

</cookies>

</CRNenv>

Locate the file com.ibm.cognos.fcm.web.properties in the C:\Program Files\IBM\cognos\ccr_64\fcmweb\wlp\usr\servers\fcm.web folder.
Open the file com.ibm.cognos.fcm.web.properties and set the following properties:

biUrl: the URL that the user must go to when CAM authentication is needed. This property is only valid for CAM login mode.
biDispatchEndpoint: the endpoint to which Controller Web connects to validate CAM users and CAM passports. This property is only valid for CAM login mode.
loginMode: the authentication type. The accepted values are: CAM and NATIVE.

This is how it can be in the file;

# IBM SOURCE CODE HEADER START
# =====================================================================
# OCO Source Materials
#
# BI and PM: ccr
#
# (C) Copyright IBM Corp. 2004, 2009. All Rights Reserved
#
# 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.
# =====================================================================
# IBM SOURCE CODE HEADER END

### SYSTEM RUNTIME SETTINGS ####
# See com.ibm.cognos.fcm.web.ui.infrastructure.SingletonSystemContext for current details

# global grace period before revalidating cache (milliseconds). Default: 6000 ms (if not defined)
# cache.validation.graceperiod=6000

### REALTIME EVENTS ###
# Examples:
# applicationID=fcm.web
# realtime=true
# jms=false

### CLASSIC and BI SERVER ###

# @TOKEN@ elements below must be transformed during deployment to match actual installation.
# Login mode can be set to NATIVE or CAM.
# Examples:
ccrwsUrl=http://controllerservername.domain.com/ibmcognos/controllerserver/ccrws.asmx
biUrl=http://biservername.domain.com /ibmcognos/cgi-bin/cognosisapi.dll
biDispatchEndpoint=http://biservername.domain.com:9300/p2pd/servlet/dispatch
loginMode=CAM
# loginMode=NATIVE

# eof

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

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

Product:
Cognos Controller 10.3
Microsoft Windows 2012 R2 Server Standard
Microsoft SQL 2016 database server

Problem:
How copy a controller database to test database?

Solution:
Take a backup of your existing controller prod database in Microsoft SQL.
You can export the backup by use of Microsoft SQL Server Management Studio or from a command line on the SQL Express server with this command:

SqlCmd -U admin -P cognos123 -S .\SQLEXPRESS -Q “BACKUP DATABASE [ControllerLive] TO DISK=’C:\backup\ControllerLive.bak’ “

Above is if you use SQL login admin with password cognos123, and the database name to take backup of is named ControllerLive. Enter the command in Notepad++ and save as a ANSI cmd file – that you then run from an administrative command prompt on the SQL server.

SqlCmd -E -S .\SQLEXPRESS -Q “BACKUP DATABASE [ControllerLive] TO DISK=’C:\backup\databases\ControllerLive.bak’ “

Above is when you use Windows authentication and the logged in Windows user on the SQL server is executing the SQL backup. You need to update the path to reflect your environment.
This BAK file is then copied to the server where you have your test environment.

Best is to restore the BAK file with use of Microsoft SQL Server Management Studio. But if you know the logical name of the database you can use a script like this:
SqlCmd -E -S .\SQLEXPRESS -Q “RESTORE DATABASE [ControllerTEST] FROM DISK=’C:\backup\databases\ControllerLive.bak’ WITH RECOVERY, MOVE ‘ControllerLive’ TO ‘C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\DATA\ControllerTest.mdf’, MOVE ‘ControllerLive_Log’ TO ‘C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\DATA\ControllerTest.ldf’ “

You need to update the path to the correct ones for your environment.

After the Controller Database is restored you in most cases need to connect the SQL login with this SQL query that you run in Microsoft SQL Server Management Studio:
Sp_change_users_login ‘update_one’,’frango’,’frango’
Replace frango with the login name you use for your controller database.

Now the controller database is setup as ControllerTest, you need to go to the Cognos Controller server and add this database to Controller.
Inside IBM Cognos Controller Configuration mark the Database Connections tab and click on the NEW icon.
Enter database type to SQL Server.
Enter name to ControllerTest (or what you find most useful for the user to see)
Enter Provider to SQLNCLI11.1
Enter User ID to frango (or the SQL name to login to the database)
Enter Password to xxxxx (the password you have set on the SQL login)
Enter Initial catalog to ControllerTest (the name of the database in SQL)
Enter Data source to servername of the SQL server (and do not use FQDN)
Click on save.
Click on Check.
Click on Run, to start the DBCONV program.

Click on Connect to see version of the database.
If the Current version and upgrade to version number is not the same for Controller DB, then click on upgrade button.
Click on Close.

Go to Report Server and click on the green Check icon.
Then Controller will check if the new database exists in Cognos Connection.
If not, a REPAIR button will appear inside Cognos Controller Configuration.
Click on the REPAIR button (this will only work if the Windows user that is logged into the controller server is system admin inside Cognos Connection).
Report server connections have been created successfully.

Now you should restart the Windows server where Cognos controller are to ensure that the batch routine recognize the new database.

Then when this is done the super user of Cognos Controller should start their Controller client and login to see that the new database is working.

More information:
http://www-01.ibm.com/support/docview.wss?uid=swg22001683
https://www.howtogeek.com/50295/backup-your-sql-server-database-from-the-command-line/
http://www-01.ibm.com/support/docview.wss?uid=swg21347969&aid=5

Product:
Cognos TM1 10.2.2 (works also in PA 2.0 Local)
Microsoft Windows 2012 R2 server

Problem:
Setup logging of TI processes execution to a Tm1 cube.

Solution:
Create two dimensions and build a cube of them.
Then add an EPILOG script to all TI process that should log information in that cube.

Go into your application – in our text we use planning sample.
In Tm1 Architect select Dimensions – Create New Dimension
Select Insert Element from Edit menu
Enter the following as Element Name
Time
User
Comment
Click OK
Select save from dimension menu and name the dimension to be Sys.Event

In Tm1 Architect select Dimensions – Create New Dimension
Select Insert Element from Edit menu
Enter the following as Element Name
Temp
Click OK
Select save from dimension menu and name the dimension to be Sys.Log

Right click on cubes and select Create new cube
Mark the two dimensions and click on the arrow icon to move them over to the cube.
Enter Cube name to Sys.Log
Click on Create Cube button.

Now you have a cube to view the logging in.

Then you need to paste below code in EPILOG in all TM1 TI process that you need logging in.
It is important you update the sStatusText line in each TI process to explain what has happen.

#—————————————————————————–
# Logging
#
# set sStatusText to information on what file create or values updated
# if the TI process is run by a Chore then the TM1 user is R*+chore name
# otherwise set the sUserText to the user running the chore
# dimensionelementinsertdirect will add the TI process to the dim if it does not exist
# timSt(now, ‘\Y-\m-\d \h:\i’) will create the time in format 2017-05-16 12:43
#—————————————————————————–

sStatusText = ‘ This the comment written to log ‘;
sCubeName = ‘Sys.Log’;

if(SUBST(TM1User(),1,2) @= ‘R*’);
sUserText = ‘Scheduled’;
else;
sUserText = attrs(‘}clients’, TM1User(), ‘}TM1_DefaultDisplayValue’);
If (sUserText @= ”);
sUserText = TM1User();
endif;
endif;

dimensionelementinsertdirect( sCubeName , ”, getProcessName(),’S’);
cellputs(timSt(now, ‘\Y-\m-\d \h:\i’), sCubeName ,’Time’, getProcessName());
cellputs(sUserText , sCubeName ,’User’, getProcessName());
cellputs(sStatusText, sCubeName ,’Comment’, getProcessName());

To test the TI process, you can enter following code in PROLOG tab.
#—————————————————–
# DEBUG LINE ONLY
#——————————————————
V1 = TM1User();
ASCIIOutput(‘c:\temp\tm1logging.txt’, V1, ‘ this is a variable result’ ) ;

Please note that TI process that is run from a scheduled core in TM1 is executed as a special user that have admin rights and is not listed in the Security dialog. If you run same TI process from TM1 Architect – it is processed as the user who logged in to TM1 Architect.

## The below is the smart code that will take the user name and show the Friendly name of it instead of the CAMID(“AD:u:6f2c060820fb2341bbcfd6”)

sUserText = attrs(‘}clients’, TM1User(), ‘}TM1_DefaultDisplayValue’);

## This extra test if it is blank, is for the case there is not a DisplayValue (alias).

If (sUserText @= ”);
sUserText = TM1User();
endif;

Ensure the ‘ character is correct in your code.

More information:
https://www.ibm.com/support/knowledgecenter/en/SS9RXT_9.5.0/com.ibm.swg.im.cognos.tm1_ref.9.5.2.doc/tm1_ref_id13786tifun_asciioutput.html

Product:
Cognos TM1 10.2.2
Microsoft Windows 2008 R2 Server

Symptom:
[ ERROR ] The cryptography information was not generated – error when you try to save changes in Cognos Configuration for TM1.

Cause:
When you first save Cognos Configuration for TM1, after a new installation of TM1, the crypto keys are generated. If you at that time have the values for Content Manager URIs set to localhost, then the keys will be created with use of the Cognos TM1 services.
If you later change this value, IBM Cognos Configuration, Environment – Gateway URI or Content Manager URI, to a Cognos BI server host – then when you try to save the configuration it will contact that server to check the crypto files – because they are not generated from that BI server, the process will fail.

If you have set the values to localhost in Environment – the recommendation is to keep them that way later too. Then there is not a crypto demand with Cognos BI at this point.

If you have set the values to a Cognos BI server the first time, then you need to ensure the Cognos BI server is up, and that you can reach it from the TM1 server when you make the “save” in Cognos configuration.

Test by copy the URL from Gateway URI and paste it into Internet Explorer on your TM1 server – to see if you have network connection to that services.

If Cognos BI is stopped before the save – in TM1 Cognos configuration – then the save should work – because the local certificates should be used. But this is not always the case.

If you are going to use a BI services on the same Windows server as you have Cognos TM1 installed, then you must install the Cognos BI service first. Because if you use localhost and there is a Cognos BI service on the localhost server it (Cognos BI) will be used for the keys.

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

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

Product:

Cognos BI 10.2.2

Microsoft Windows 2012 R2 server

Microsoft SQL 2014 database

Symptom:

On a new installed Cognos BI 10.2.2 where you have upgraded an old Content store from Cognos BI 10.1.1 you get an error message when you in Cognos connection go to Administer IBM Cognos content and look at Current Activities.

Error message:

SOAPFaultException

CNC-MON-0024 Monitor Service paging error: Invalid column name ‘TENANT_ID’.

com.cognos.portal.fragment.server.SOAPFaultException: CNC-MON-0024 Monitor Service paging error: Invalid column name ‘TENANT_ID’.

at com.cognos.portal.fragment.service.ServiceEnvironment.getBiBusTargetStream(ServiceEnvironment.java:543)

at com.cognos.portal.fragment.service.ServiceEnvironment.getLocalTargetStream(ServiceEnvironment.java:330)

at com.cognos.portal.fragment.Environment.getTargetStream(Environment.java:624)

at com.cognos.portal.fragment.SynchronizedEnvironment.getTargetStream(SynchronizedEnvironment.java:265)

at com.cognos.portal.fragment.SynchronizedEnvironment.getTargetStream(SynchronizedEnvironment.java:265)

at com.cognos.portal.fragment.server.document.DocumentFactoryImpl.createDocument(DocumentFactoryImpl.java:132)

at com.cognos.portal.fragment.server.document.DocumentRequest.runImpl(DocumentRequest.java:80)

at com.cognos.portal.fragment.server.document.RequestExecutor$Request.run(RequestExecutor.java:58)

at com.cognos.portal.thread.DefaultRerunnable.run(DefaultRerunnable.java:65)

at com.cognos.portal.thread.RerunnableThread.run(RerunnableThread.java:109)

<SOAP-ENV:Fault xmlns:SOAP-ENV=”http://schemas.xmlsoap.org/soap/envelope/”><faultcode xmlns=””>soapenv:Server</faultcode><faultstring>CNC-BAL-0503 The Server has failed.</faultstring><detail><detail><ns1:exception xmlns:ns1=”http://developer.cognos.com/schemas/bibus/3/”><ns1:severity>error</ns1:severity><ns1:errorCode>CNC-BAL-0502 Error Number: MSG_MS_PAGING_ERROR

</ns1:errorCode><ns1:message><ns1:messageString>CNC-MON-0024 Monitor Service paging error: Invalid column name ‘TENANT_ID’.</ns1:messageString><ns1:nestingLevel>0</ns1:nestingLevel></ns1:message></ns1:exception></detail></detail></SOAP-ENV:Fault>

at com.cognos.portal.soap.impl.SOAPConnectionImpl.handleFault(SOAPConnectionImpl.java:307)

at com.cognos.portal.soap.impl.SOAPConnectionImpl.readResponse(SOAPConnectionImpl.java:251)

at com.cognos.portal.soap.impl.SOAPConnectionImpl.processResponse(SOAPConnectionImpl.java:210)

at com.cognos.portal.soap.impl.BusConnectionImpl.execute(BusConnectionImpl.java:144)

at com.cognos.portal.fragment.service.ServiceEnvironment.getBiBusTargetStream(ServiceEnvironment.java:515)

at com.cognos.portal.fragment.service.ServiceEnvironment.getLocalTargetStream(ServiceEnvironment.java:330)

at com.cognos.portal.fragment.Environment.getTargetStream(Environment.java:624)

at com.cognos.portal.fragment.SynchronizedEnvironment.getTargetStream(SynchronizedEnvironment.java:265)

at com.cognos.portal.fragment.SynchronizedEnvironment.getTargetStream(SynchronizedEnvironment.java:265)

at com.cognos.portal.fragment.server.document.DocumentFactoryImpl.createDocument(DocumentFactoryImpl.java:132)

at com.cognos.portal.fragment.server.document.DocumentRequest.runImpl(DocumentRequest.java:80)

at com.cognos.portal.fragment.server.document.RequestExecutor$Request.run(RequestExecutor.java:58)

at com.cognos.portal.thread.DefaultRerunnable.run(DefaultRerunnable.java:65)

at com.cognos.portal.thread.RerunnableThread.run(RerunnableThread.java:109)

 

Root Cause:

<SOAP-ENV:Fault xmlns:SOAP-ENV=”http://schemas.xmlsoap.org/soap/envelope/”><faultcode xmlns=””>soapenv:Server</faultcode><faultstring>CNC-BAL-0503 The Server has failed.</faultstring><detail><detail><ns1:exception xmlns:ns1=”http://developer.cognos.com/schemas/bibus/3/”><ns1:severity>error</ns1:severity><ns1:errorCode>CNC-BAL-0502 Error Number: MSG_MS_PAGING_ERROR

</ns1:errorCode><ns1:message><ns1:messageString>CNC-MON-0024 Monitor Service paging error: Invalid column name ‘TENANT_ID’.</ns1:messageString><ns1:nestingLevel>0</ns1:nestingLevel></ns1:message></ns1:exception></detail></detail></SOAP-ENV:Fault>

at com.cognos.portal.soap.impl.SOAPConnectionImpl.handleFault(SOAPConnectionImpl.java:307)

at com.cognos.portal.soap.impl.SOAPConnectionImpl.readResponse(SOAPConnectionImpl.java:251)

at com.cognos.portal.soap.impl.SOAPConnectionImpl.processResponse(SOAPConnectionImpl.java:210)

at com.cognos.portal.soap.impl.BusConnectionImpl.execute(BusConnectionImpl.java:144)

at com.cognos.portal.fragment.service.ServiceEnvironment.getBiBusTargetStream(ServiceEnvironment.java:515)

at com.cognos.portal.fragment.service.ServiceEnvironment.getLocalTargetStream(ServiceEnvironment.java:330)

at com.cognos.portal.fragment.Environment.getTargetStream(Environment.java:624)

at com.cognos.portal.fragment.SynchronizedEnvironment.getTargetStream(SynchronizedEnvironment.java:265)

at com.cognos.portal.fragment.SynchronizedEnvironment.getTargetStream(SynchronizedEnvironment.java:265)

at com.cognos.portal.fragment.server.document.DocumentFactoryImpl.createDocument(DocumentFactoryImpl.java:132)

at com.cognos.portal.fragment.server.document.DocumentRequest.runImpl(DocumentRequest.java:80)

at com.cognos.portal.fragment.server.document.RequestExecutor$Request.run(RequestExecutor.java:58)

at com.cognos.portal.thread.DefaultRerunnable.run(DefaultRerunnable.java:65)

at com.cognos.portal.thread.RerunnableThread.run(RerunnableThread.java:109)

 

Possible Solution:

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

 

The tables in Content store can be corrupt.

Take a backup of the Database before doing any changes.

Stop the Cognos BI service.

Get the drop table SQL script from folder E:\Program Files\ibm\cognos\c10_64\configuration\schemas\delivery\sqlserver\NC_DROP_MS.sql

Looks like this:

—    Licensed Materials – Property of IBM

—    BI and PM: JSM

—    (c) Copyright IBM Corp. 2003, 2015.

—    US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

 

 

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

— NC_DROP_MS.sql         *  DO NOT EDIT  *          Data Store Version: 1032

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

 

ALTER TABLE NC_JOBQUEUE

DROP CONSTRAINT PN_JOBQUEUE

 

 

ALTER TABLE NC_MESSAGELINE

DROP CONSTRAINT F1N_MESSAGELINE

 

 

ALTER TABLE NC_MESSAGELINE_ELEMENT

DROP CONSTRAINT F1N_MESSAGELINE_EL

 

 

ALTER TABLE R_MESSAGESTRUCT_TASK

DROP CONSTRAINT F2R_MESSAGESTRUCT_

 

 

ALTER TABLE R_MESSAGESTRUCT_TASK

DROP CONSTRAINT F1R_MESSAGESTRUCT_

 

 

ALTER TABLE NC_METRICS

DROP CONSTRAINT PN_METRICS

 

 

ALTER TABLE R_MSGSTRUCT_RECIPIENT_DELIVINF

DROP CONSTRAINT F3R_MSGSTRUCT_RECI

 

 

ALTER TABLE R_MSGSTRUCT_RECIPIENT_DELIVINF

DROP CONSTRAINT F1R_MSGSTRUCT_RECI

 

 

ALTER TABLE NC_SDS_INSTANCE

DROP CONSTRAINT PN_SDS_INSTANCE

 

 

ALTER TABLE NC_TASKSCHEDULE

DROP CONSTRAINT F1N_TASKSCHEDULE

 

 

ALTER TABLE R_TASKSCHEDULE_SCHEDULE

DROP CONSTRAINT F2R_TASKSCHEDULE_S

 

 

ALTER TABLE R_TASKSCHEDULE_SCHEDULE

DROP CONSTRAINT F1R_TASKSCHEDULE_S

 

 

DROP TABLE NC_CONFIGURATION

 

 

DROP TABLE NC_CTMAP

 

 

DROP TABLE NC_DB_VERSION

 

 

DROP TABLE NC_DELIVERYADDRESS

 

 

DROP TABLE NC_EVENTSTATUS

 

 

DROP TABLE NC_JMSQUEUE

 

 

DROP TABLE NC_JOBQUEUE

 

 

DROP TABLE NC_MESSAGELINE

 

 

DROP TABLE NC_MESSAGELINE_ELEMENT

 

 

DROP TABLE NC_MESSAGESTRUCT

 

 

DROP TABLE NC_METRICS

 

 

DROP TABLE NC_OBJECTCATALOGUE

 

 

DROP TABLE NC_OBJECTID

 

 

DROP TABLE NC_PERMISSION

 

 

DROP TABLE NC_RECIPIENT

 

 

DROP TABLE NC_SCHEDULE

 

 

DROP TABLE NC_SCHEDULE_QUEUE

 

 

DROP TABLE NC_SDS_INSTANCE

 

 

DROP TABLE NC_TASK

 

 

DROP TABLE NC_TASKSCHEDULE

 

 

DROP TABLE NC_SCHEDULED_EVENT_OVERRIDE

 

 

DROP TABLE NC_TASK_HISTORY_DETAIL

 

 

DROP TABLE NC_TASK_HISTORY_SUB_INDEX

 

 

DROP TABLE NC_TASK_PROPERTY

 

 

DROP TABLE NC_TASK_QUEUE

 

 

DROP TABLE NC_TSE_STATE_MAP

 

 

DROP TABLE NC_TASK_ANCESTOR_STOREIDS

 

 

DROP TABLE R_MESSAGESTRUCT_TASK

 

 

DROP TABLE R_MSGSTRUCT_RECIPIENT_DELIVINF

 

 

DROP TABLE R_NEWSITEMS_NCOBJECTS

 

 

DROP TABLE R_TASKSCHEDULE_SCHEDULE

 

 

DROP TABLE NC_RESOURCE_LOCK

 

 

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

—         END NC_DROP_MS.sql        *  DO NOT EDIT  *

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

 

Go to the SQL server and login to Microsoft SQL Server Management Studio.

Paste above script in the Query window.

Execute it on the Content Store database.

This will erase the NC tables and any data therein.

 

Start the Cognos BI service from Cognos Configuration to recreate the tables.

Test to surf to Cognos Connection.

If this does not help, then create a empty database and setup Cognos BI against that empty content store. Then after you have to export a deployment of all content from Old Cognos BI and import it into the new Cognos BI environment. But you will not get the “my folders” content with  you in this deployment case. Then you have to use other methods to move the content.

More information:

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

Pricing

https://www.motio.com/products.do

http://www.reportfellow.com/en/home.html

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