Product:
Cognos Business Intelligence

Problem:
How to determine the Service Pack of the Cognos Business Intelligence product installed?

Solution (copied from IBM website before it is removed):
The component list cmplst.txt file displayed a full list of installed components. It is found on any server with a full or partial installation of Cognos Business Intelligence.
The table below maps the various build numbers to their more commonly referenced release names:
The build number indicates the MR (Maintenance Release) version, as per the following table:

IBM Cognos ReportNet
Build 1.1.316.16 is MR1
Build 1.1.413.8 is MR2
Build 1.1.510.0 is MR3
Build 1.1.610 is MR4

IBM Cognos 8 BI 8.1
8.1.108.33 is MR1
8.1.209.25 is MR2

IBM Cognos 8 BI 8.2
8.2.43.128 is the initial release
8.2.44 is SP1
8.2.45 is SP2
8.2.46 is SP3

IBM Cognos 8 BI 8.3
8.3.81.20 is the initial RTM
8.3.82 is SP1
8.3.83 is SP2
8.3.84 is SP3
8.3.85 is FP4
8.3.86 is FP5

IBM Cognos 8 BI 8.4
8.4.27.78 is the RTM or GA
8.4.28.15 is FP1
8.4.29.13 is FP2

IBM Cognos 8 BI 8.4.1
8.4.102.18-0 GA
8.4.103.16-0 FP1
8.4.104.13-0 FP2
8.4.105.14-0 FP3
8.4.106.12 FP4

IBM Cognos 10.1
10.1.4707.544-0 GA
10.1.4801.29-0 FP1

IBM Cognos 10.1.1
10.1.6235.152 – 10.1.1 GA
10.1.6301.14 – 10.1.1 FP1
10.1.6303.12 – 10.1.1 FP2
10.1.6304.10 – 10.1.1 FP3
10.1.6305.14 – 10.1.1 FP4
10.1.6306.40 – 10.1.1 FP5

IBM Cognos 10.2
10.2.1003.159 – 10.2 GA
10.2.1101.19 – 10.2 FP1
10. 2.1102.54 – 10.2 FP2
10. 2.1103.29 – 10.2 FP3
10. 2.1104.98 – 10.2 FP4
10.2.1105.45 – 10.2 FP5

IBM Cognos 10.2.1
10.2.5000.275 – 10.2.1 GA
10.2.5001.156 – 10.2.1 FP1
10.2.5002.78 – 10.2.1 FP2
10.2.5003.113 – 10.2.1 FP3
10.2.5004.54 – 10.2.1 FP4 (build 10.2.5004.53 may be found in versions prior to Aug 15, 2014)
10.2.5005.78 – 10.2.1 FP5
10.2.5006.79 – 10.2.1 FP6
10.2.5007.30 – 10.2.1 FP7
10.2.5008.29 – 10.2.1 FP8
10.2.5009.33 – 10.2.1 FP9
10.2.5010.46 – 10.2.1. FP10 (build 10.2.5004.43 indicates the withdrawn Fix Pack 10)
10.2.5011.54 – 10.2.1 FP11
10.2.5012.26 – 10.2.1 FP12
10.2.5013.81 – 10.2.1 FP13

IBM Cognos 10.2.2
10.2.6100.235 – 10.2.2 GA
10.2.6101.79 – 10.2.2 FP1
10.2.6102.54 – 10.2.2 FP2
10.2.6103.26 – 10.2.2 FP3
10.2.6104.43 – 10.2.2 FP4
10.2.6105.506 – 10.2.2 FP5 (build 10.2.6105.50 indicates the withdrawn Fix Pack 5)
10.2.6106.48 – 10.2.2 FP6
10.2.6107.28 – 10.2.2 FP7
10.2.6108.34 – 10.2.2 FP8
10.2.6109.59 – 10.2.2 FP9

Steps:
Within the Cognos BI install folder, look for a file called cmplst.txt. The default installation location is c:\program files\cognos\
Within this file, look for [Product Update Information]. If this section is missing or blank, then you have the RTM (first release) installed. If the section is populated, reference the table above to determine the service pack installed.

If you do not have access to the component list file (cmplst.txt):
Hit Ctrl-F3 within Cognos Configuration to bring up a Properties menu
On the Installed Components tab, the build numbers will also be displayed

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

For Cognos Analytics
Name                            Release                                  Build Number
Cognos Analytics 11 GA 11.0.0.0                          11.0.0.15121723
Cognos Analytics 11 R1 11.0.1.0                           11.0.1.16031813
Cognos Analytics 11 R2 11.0.2.0                           11.0.2.16042816
Cognos Analytics 11 R3 11.0.3.0                           11.0.3.16062807
Cognos Analytics 11 R4 Initial 11.0.4.0                11.0.4.16090915
Cognos Analytics 11 R4 Refresh 11.0.4.0            11.0.4.16092813
Cognos Analytics R5 11.0.5.0                                11.0.5.16112119
Cognos Analytics R6 11.0.6.0                                11.0.6.17031315
Cognos Analytics R7 11.0.7.0                                11.0.7.17082211
Cognos Analytics R8 11.0.8.0                                11.0.8.17103116

http://www-01.ibm.com/support/docview.wss?uid=swg21990189
and for TM1 you can find the version here
http://www-01.ibm.com/support/docview.wss?uid=swg21964134

Product:
Cognos Business Intelligence (BI) 10.2.2 Fix pack 6
Microsoft Windows 2012 R2 server
Issue:
When adding a new domain to the list of namespaces in Cognos BI, during test or startup it give a error message.
New domain have in our example the name ExtAD
Error message:
[‘ExtAD’]
[ ERROR ] CAM-AAA-0146 The namespace ‘ExtAD’ is not available.
[ ERROR ] CAM-AAA-0064 The function ‘Configure’ failed.
[ ERROR ] CAM-AAA-0089 The provider is not initialized.
[ ERROR ] CAM-AAA-0036 Unable to authenticate because the credentials are invalid.
[ ERROR ] ADSI Error:
8009030C: LdapErr: DSID-0C09053E, comment: AcceptSecurityContext error, data 52e, v1db1
System Error:
The user name or password is incorrect.
Possible Solution:
The user logged into the Windows server where you have Cognos Configuration, does not have a account (or trust) in the new domain, so the test fail and the new Active Directory namespace is not shown.
Start Cognos Configuration and update the new namespace values
Enter a windows service account in the Bindings Credentials row in Cognos Configuration for the new namespace.
Enter in the format: domain.com\username
and the password (because it is a service account the password will never change).
Save the changes and restart the Cognos BI service where the content manager are.
Test to surf to the gateway again.

If Cognos 8 is running on the machine in the same forest as the configured domain/forest, you do not need to specifically set the bind credentials. However, if you run cross forest, then, you must provide the bind credentials

You would also need the binding credentials if AD is not configured to allow anonymous bind

More Information:
If the password is correct:
-2146893044 => 8009030C: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 775, v1db1 (account locked out)

If the pwd is incorrect returns:
-2146893044 => 8009030C: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1 (unknown username or bad password)

https://social.technet.microsoft.com/Forums/lync/en-US/c1d8d706-a506-4973-9542-1e88a2a66ac0/ad-lds-and-locked-out-accounts-response-codes?forum=winserverDS

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

http://www-01.ibm.com/support/docview.wss?uid=swg21335624
https://www.ibm.com/support/knowledgecenter/SSEP7J_10.2.0/com.ibm.swg.ba.cognos.inst_cr_winux.10.2.0.doc/t_ap_active_dir_srvr.html

Product:
Cognos Analytics 11.0.7
Microsoft Windows 2016 Standard server

Problem:
No picture shown in the PDF report, but they show nice in a HTML report.

Solution:
If you have SSO with IIS, then you need to set Anonymous Authentication on the folders where the images are stored.
This can be more than one folder, depending on where you have your company reports pictures stored.
The sample pictures are stored in folder c:\Program Files\ibm\cognos\analytics\webcontent\bi\samples\images

So you need to start IIS Manager
Expand to your IBMCOGNOS folder
Expand down to bi/samples
Mark images folder and click on Authentication icon
Mark Anonymous Authentication and click on Enable text, to change status to Enabled
Exit IIS
Try to run the report as PDF again.

You can also ensure that the account running the Cognos BI services have full rights to the images folder in NTFS file system.

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

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 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 Analytics 11.0.6
Microsoft Windows 2012 server
DB2 11.1.1 database server

Problem:
How create a content store in DB2?

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 files
d2jcc_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.

On the DB2 server login as Windows administrator.
Start a DB2 Command Windows – Administrator.
Enter this command:
db2 -tvf c:\install\createDb.sql

This will run the steps to create the content store database.
Will be similar to this;

CREATE DATABASE cm AUTOMATIC STORAGE YES ALIAS cm USING CODESET UTF-8 TERRITORY
US COLLATE USING SYSTEM PAGESIZE 8192
DB20000I Kommandot CREATE DATABASE har utförts.
CHANGE DATABASE cm COMMENT WITH ‘IBM Cognos Content Store’
DB20000I Kommandot CHANGE DATABASE COMMENT har utförts.
CONNECT TO cm
Information om databasanslutning
Databasserver = DB2/NT64 11.1.1.1
SQL-användar-ID = ADMINIST…
Lokalt databasalias = CM
UPDATE DATABASE CONFIGURATION USING APPLHEAPSZ 1024 DEFERRED
DB20000I Kommandot UPDATE DATABASE CONFIGURATION har utförts.
UPDATE DATABASE CONFIGURATION USING LOCKTIMEOUT 240 DEFERRED
DB20000I Kommandot UPDATE DATABASE CONFIGURATION har utförts.
CONNECT RESET
DB20000I Kommandot SQL har utförts.
CONNECT TO cm
Information om databasanslutning
Databasserver = DB2/NT64 11.1.1.1
SQL-användar-ID = ADMINIST…
Lokalt databasalias = CM
CREATE BUFFERPOOL cm_08KBP IMMEDIATE SIZE 1000 PAGESIZE 8K
DB20000I Kommandot SQL har utförts.
CREATE BUFFERPOOL cm_32KBP IMMEDIATE SIZE 1000 PAGESIZE 32K
DB20000I Kommandot SQL har utförts.
CONNECT RESET
DB20000I Kommandot SQL har utförts.
CONNECT TO cm
Information om databasanslutning
Databasserver = DB2/NT64 11.1.1.1
SQL-användar-ID = ADMINIST…
Lokalt databasalias = CM
CREATE SYSTEM TEMPORARY TABLESPACE TSN_SYS_cm IN DATABASE PARTITION GROUP IBMTEM
PGROUP PAGESIZE 32K BUFFERPOOL cm_32KBP
DB20000I Kommandot SQL har utförts.

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.

[Validate mail server properties.]
[ ERROR ] The mail server cannot be reached.

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

[Start Service]
21:21:53, ‘LogService’, ‘StartService’, ‘Success’.
21:21:54, CAF-WRN-0010 CAF input validation enabled.
21:21:54, CAF-WRN-0021 CAF Third Party XSS checking disabled.
21:22:06, ”, ‘StartService’, ‘Success’.
21:22:08, CM-SYS-2057 Creating content store tables (schema version 7.0045).
21:22:16, CM-SYS-2215 A Content Manager internal PRECACHEINITACTIONS task started.
21:22:16, CM-SYS-2216 A Content Manager internal PRECACHEINITACTIONS task is complete.
21:22:16, CM-SYS-2093 The Content Manager cache initialization is complete. 1 objects loaded in 0,11 seconds.
21:22:17, CM-SYS-2216 A Content Manager internal POSTINITACTIONS task is complete.
21:22:16, CM-SYS-2215 A Content Manager internal POSTINITACTIONS task started.
21:22:39, CM-SYS-5159 Content Manager is running in active mode.
21:22:39, ‘ContentManagerService’, ‘StartService’, ‘Success’.
21:22:39, CM-SYS-2215 A Content Manager internal CMUPGRADESCRIPT task started.
21:22:41, DPR-DPR-1002 Successfully registered the dispatcher http://winca:9300/p2pd in Content Manager.
21:22:43, ‘idVizService’, ‘StartService’, ‘Success’.
21:23:25, ‘SACamService’, ‘StartService’, ‘Success’.
21:23:24, ‘camAsyncService’, ‘StartService’, ‘Success’.
21:23:27, ”, ‘Run’, ‘Run’.
21:23:34, ‘AnnotationService’, ‘StartService’, ‘ANN DB Validation successful.’.
21:23:34, ”, ‘Run’, ‘Run’.
21:23:36, ‘EventService’, ‘StartService’, ‘NC DB Validation successful.’.
21:23:43, ‘HumanTaskService’, ‘StartService’, ‘HTS DB Validation successful.’.
21:23:49, ‘zipiService’, ‘StartService’, ‘Success’.
21:23:49, ‘PDC’, ‘StartService’, ‘Success’.
21:23:50, ‘PresentationService’, ‘StartService’, ‘Success’.
21:23:51, Start a cgsLauncher because the start count 1 is larger than 0.
21:23:51, ‘BUX Service’, ‘StartService’, ‘Success’.
21:24:04, ‘RepositoryService’, ‘StartService’, ‘Success’.
21:24:04, ‘burstDistributionService’, ‘StartService’, ‘Success’.
21:24:04, ‘GraphicsService’, ‘StartService’, ‘Success’.
21:24:41, ‘QueryService’, ‘StartService’, ‘Success’.
21:24:48, ‘QueryService’, ‘StartService’, ‘Success’.
21:24:55,
21:24:55, ‘ReportService’, ‘StartService’, ‘Success’.
21:24:55, ‘visualisationGalleryService’, ‘StartService’, ‘Success’.
21:25:13, ‘camAsyncAA’, ‘StartService’, ‘Success’.
21:25:13, ‘ReportDataService’, ‘StartService’, ‘Success’.
21:25:14, ‘relationalMetadataService’, ‘StartService’, ‘Success’.
21:25:13, ‘Fragment Server Service’, ‘StartService’, ‘Success’.
21:25:14, ‘SACamSrvcInternal’, ‘StartService’, ‘Success’.
21:25:14, ‘QLSService’, ‘StartService’, ‘Success’.
21:25:13, ‘SystemService’, ‘StartService’, ‘Success’.
21:25:14, ‘BatchReportService’, ‘StartService’, ‘Success’.
21:25:13, ‘MobileService’, ‘StartService’, ‘Success’.
21:25:13, ‘ContentManagerCacheService’, ‘StartService’, ‘Success’.
21:25:13, ‘CacheService’, ‘StartService’, ‘Success’.
21:25:14, ‘QLSImportService’, ‘StartService’, ‘Success’.
21:25:14,
21:25:14, ‘SACamSrvc’, ‘StartService’, ‘Success’.
21:25:14, ‘idVizServer’, ‘StartService’, ‘Success’.
21:25:15, ‘MetadataService’, ‘StartService’, ‘Success’.
21:25:14, ‘idVizServer’, ‘StartService’, ‘Success’.
21:25:14, ‘DeliveryService’, ‘StartService’, ‘Success’.
21:25:14, ‘SMDService’, ‘StartService’, ‘Success’.
21:25:14, ‘QLSBIService’, ‘StartService’, ‘Success’.
21:25:14, ‘idVizService’, ‘StartService’, ‘Success’.
21:25:14, ‘idVizService’, ‘StartService’, ‘Success’.
21:25:15, ‘HumanTaskService’, ‘StartService’, ‘Success’.
21:25:15, ‘AnnotationService’, ‘StartService’, ‘Success’.
21:25:15, ‘MonitorService’, ‘StartService’, ‘Success’.
21:25:15, ‘AgentService’, ‘StartService’, ‘Success’.
21:25:15, ‘JobService’, ‘StartService’, ‘Success’.
21:25:15, ‘EventService’, ‘StartService’, ‘Success’.
21:25:25, ‘CPS Producer Registration Service’, ‘StartService’, ‘Success’.
21:25:26, ‘Dispatcher’, ‘Start’, ‘Success’.
21:25:31, ”, ”, ‘Success’.
21:25:56, ”, ‘Run’, ‘Run’.
21:25:56, ”, ‘Run’, ‘Run’.
21:25:56, ”, ‘Run’, ‘Run’.
21:25:56, ”, ‘Run’, ‘Run’.
21:25:56, ”, ‘Run’, ‘Run’.

If a BiBusTKServerMain process terminates unexpectedly, a dump file is created in the ../bin directory.  In order to troubleshoot the termination of these processes, follow the steps below to use the Windows Debug (Windbg) tool available from Microsoft.

Use the Windbg tool to open the dump file to help determine the cause of the BiBusTKServerMain crash.

Steps:
Download and Install Windbg from Microsoft here

1. From the Start menu, launch Windbg.
2. From the File menu, choose Symbols File Path
3. In the Symbol Search Path dialog box, enter \\localhost\Symbols\dbg
4. Click Ok
5. From the File menu, choose Open Crash Dump
6. Navigate to the dmp file and click Open
7. Click Yes to the Save Workspace dialog
You may see an error such as:

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntdll.dll –
This dump file has an exception of interest stored in it
The stored exception information can be accessed via .exr

8. On the white line at the bottom of the Command window type .exr -1 and hit enter
9. In the command line at the bottom of the Command window, type  k 20 and hit enter (This will show the to 20 lines of the stack trace)
10. Click on “View” in the top menu bar and select “Call Stack” – A new window will open
11. Click on “View” in the top menu bar and select “command” – a new window will open
12. Click on “View” in the top menu bar and select “locals” – a new window will open
13. Click on “View” in the top menu bar and select “processes and threads” – a new window will open
14. Click on “Window” in the top menu bar and select “Undock all”.
15. Click on “Window” in the top menu bar and select “Vertically tile floating windows” – The screen should show four windows
16. In the call stack window (“Calls”), click on the button “More” at the top until you get to the bottom of the stack
17. We need to locate an entry similar to the following:  RSReportService!RSASyncExecutionThread::run+0x606
18. Double click on this entry. Then move to the “Locals” Window and look for the following thread: “this”
19. Expand the plus sign next to “this” and you should see the following: m_pPrimaryRequest
20. Expand the thread m_pPrimaryRequest and you should see the following: m__objectPath
21. Expand the thread m__objectPath and you should see the following: m__value
22. Note down the value corresponding to the entry. It could be or it could indicate a particular report name.

If the value shows , it could be that the system did not have enough resources but is not conclusive.

Product:
Cognos BI 10.2.2 fix pack 7
Microsoft Windows 2008 R2 Server

Symptom:
Running the installation program for Cognos BI and Cognos BI fix pack are very slow. The program stand still a long time at same step.

Cause:
If you look in task manager you will see that the process using more than 25% of the CPU are MsMpEng.exe Antimalware service Executable. The System Center Endpoint Protection program is installed and set to have real-time protection on the server.

Antivirus software will always slow down the copy of files during installation of Cognos Programs. It is recommended to turn off Antivirus software during install and exclude the Cognos program and subfolder from the real time scan on the servers.

Installation of IBM Cognos Business Intelligence Server Updates 7 took 3 hours with Microsoft anti-virus software turned on instead of a few minutes when it was turned off.

If IT department do not want to turn off Antivirus on servers, work around is that you can try to install both Cognos BI and Cognos TM1 at the same time but to different folders. This will gain you a little time.

Product:
Cognos BI 10.2.2 fix pack 7
Microsoft Windows 2008 R2 Server

Symptom:
When user surf to http://biservername.domain.com/ibmcognos they get a windows security login dialog. If they surf to only http://biservername.domain.com they get the standard IIS7 start page.
If the same user surf to http://biservername.domain.com/ibmcognos direct from inside the BI server with Internet Explorer there is no problem.

On both server and client the *.domain.com is added as local intranet in Internet Options.

Solution:
On the Microsoft Windows 2008 server start up Internet Information Services (IIS) Manager program and go to the IBMCOGNOS folder.
Select Authentication.
Select Windows Authentication (that is enabled) and click on Providers link at the right.
Move NLMT to be on top over Negotiate.
Click OK.

Test now from the client laptop computer – now SSO should work.

Product:
Cognos Lifecycle manager
Microsoft Windows 2008 R2

Symptom:
Error when try to create a new project in Lifecycle Manager

Error message:
An error has occured in Lifecycle Manager.
Could not create a new project

HTTP Status 500 –

Cause:
Check that the tomcat service have started. In the DOS window there can be text like filenotfoundexception. … \logs\catalina,2014-02-25.log (the system cannot find the path…. show that the tomcat service never started correct.
If you check the logs folder under tomcat directory, this folder is empty. The Windows server is looked down – the normal user do not have rights to files under c:\program files folders.

Solution:
Uninstall Lifecycle Manager.
Install it to a different folder on your server – e.g. d:\ibm\cognos\Lifecyclemanager\
Where the user have more access rights and can create temp files.

Then start Lifecycle manager again and surf to http://localhost:4797/LifecycleManager

More Information
http://www.ibm.com/developerworks/data/library/cognos/upgrade_and_migration/bi/page579.html