Follow us on Twitter


48.4%United States United States
7.4%India India
7%United Kingdom United Kingdom
5.6%Canada Canada
5.3%Australia Australia


Today: 93
Yesterday: 54
This Week: 93
Last Week: 2231
This Month: 7213
Last Month: 11512
Total: 654316

Lifecycle Manager HTTP Status 500 error PDF Print E-mail
Written by Roger   


Cognos Lifecycle manager
Microsoft Windows 2008 R2

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 -

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.

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





How change the TEMP variable for a service account PDF Print E-mail
Written by Roger   


IBM Cognos Planning 10.1.1
Microsoft Windows 2008 R2 Server

How change the TEMP variable for a service account, without logging in as the user on the Windows Server?


Create the service account in the Domain.
Ensure the service account is part of the local administration group on the planning server.
Go to the Administration tools - services.
(you can start it by type services.msc in Run dialog)
Double Click on  your IBM Cognos 10 Planning service and select Log On tab.
Select this account and browse to your service account, in our example named cogplan.
Enter Password and click OK to save the change.
Click OK on message that the account have been added to "log on as a service" function.
Right Click on the service IBM Cognos 10 Planning and select RESTART.
Ensure that Cognos planning service have started.

The planningerrorlog.csv file is created in folder \users\cogplan\appdata\local\temp

Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
Check the last number in list - it is possible your service account.
You should see it on the ProfileImagePath value who would be : C:\Users\cogplan
Note the number if the user down
Go to HKEY_USERS\S-1-5-21-2298123480-4089459362-31738xxxxx-1001\Environment
(the number should be the number of the user you found under ProfileList.)
Double click on TEMP to change the value from
Click OK
Repeat the change for TMP

Restart the Cognos Planning service.

Now the log file is in the D:\TEMP folder.



In & outs of IBM Cognos Dynamic Cubes PDF Print E-mail
Written by Roger   
IBM Cognos BI 10.2.1
LICENSE_BI_SERVER_name=IBM Cognos License
C8BISRVR_name=IBM Cognos Business Intelligence Server
Microsoft Windows 2008 R2 server

What does IBM Cognos Dynamic Cubes need?


IBM Cognos Dynamic Cubes is used to model dimensional metadata and to create dynamic cubes to use as data sources in the Content Manager. The software to create this is IBM Cognos Cube Designer for designing dynamic, aggregate, and create virtual cubes.

To install the IBM® Cognos® Dynamic Cubes software, perform the following tasks:

Upgrade or install version 10.2.1 of the Business Intelligence Server software on a Windows, UNIX or Linux operating system.
Upgrade or install version 10.2.1 of the Framework Manager software on computers configured for modeling dynamic cubes.
Ensure you have turned "User Account Control" to "Never Notify" before installing Cognos Cube Designer.
Install IBM Cognos Cube Designer on workstation for developer to create cubes.
Upgrade or install version 10.2.1 of IBM Cognos Dynamic Query Analyzer on a 32-bit or 64-bit computer where the IBM Cognos Business Intelligence Application Tier components are currently installed, that is the Cognos BI server itself.
Enable the 64-bit version of Report Server, inside Cognos Configuration.
Support for relational databases through JDBC connectivity.
Configure data connectivity to relational data sources.
Test the IBM Cognos Cube Designer installation from the Framework Manager software.

The report server component, included with the Application Tier Components, is provided in both 32-bit and 64-bit versions. Selecting which version you use is done by using IBM Cognos Configuration after installation. By default, the report server component is set to use the 32-bit mode, even on a 64-bit computer. By using the 32-bit mode, you can run all reports, whereas by using the 64-bit mode, you can run only reports created for dynamic query mode..

The report server component, when installed with a Cognos BI 64 bit version ( in folder C:\Program Files\ibm\cognos\c10_64 ) in default mode, where Report Server execution mode is set to 32 bit. then the Report service is run in 32 bit mode but its JAVA process is run in 64 bit mode.  The old CQM (Classic Query Mode) process part of BIBusTKServerMain.exe *32 is a 32 bit process.
A 32 bit process have a limit of only accessing 4 GB of RAM. This can be a issue if you have complex reports, that need to calculate a lot of data before showing the resulting data in the Report.  In this mode, the Cognos BI server can handle reports that access both DQM and CQM data sources. But it is not recommended to use for Dynamic Cubes, even to they can look to work. For Dynamic Cubes you need to setup a separate Cognos BI server with Report Server Execution Mode set to 64 bit.

In 32 bit mode, the functions and cache benefits of DQM are there. Suggestion is to start the new Cognos BI 10.2.1 server in this mode, and then test some reports with a DQM data source.

DQM uses the Query Service. If you set Query Service to false in Cognos Configuration, you disable DQM totally and also saves memory for one JAVA process less. This is not recommended, if you going to use DQM.

Although the dynamic query mode (DQM) is supported in 32 bit installations of IBM Cognos BI servers, 64 bit servers are recommended for DQM. Install Cognos 64 bit version on 64 bit OS like Microsoft Windows 2008 R2, then DQM will use 64 bit for its report processing.

The initial size and size limit of the JVM heap for DQM can be set in Cognos Administration via the Settings tab of the QueryService. By default each of these are set to 1 GB.

In production environments where Cognos Dynamic Cubes are not employed, it is recommended to set the initial heap size to 4 GB and the limit to 8 GB (a 64 bit server is required for memory settings above 2GB) and then monitor system resource usage during peak hours and adjust the settings accordingly.

For a server that is operating one or more Cognos Dynamic Cubes, the size limit of the query service should be set in accordance to the Dynamic Cubes hardware sizing recommendations.


Report Server Execution Mode:
There are 2 options 32-Bit and 64-bit

32 Bit mode supports CQM and DQM models
64 Bit mode only supports DQM models and Dynamic Cubes

Only 64 Bit mode of DQM supports Dynamic Cubes, this mean in most environment where you have a mix of reports and data sources that use both DQM and CQM, you need to set up more than one server and route the reports on the data source level (frame work package). So reports that will use Dynamic Cubes are routed to the Cognos BI server who have 64 Bit DQM mode, and also only supports DQM reports.

To prevent reports to be processed on a server that does not support them, you must implement Cognos Routing rules. This can be done in several ways, one is to apply a routing on Framework manager packages, like this:
Go to Cognos Connection and locate the package you would like to apply the routing to.
Click the set properties button for the package.
Under the Advanced routing section, click Set…
The Assign routing sets page appears. Type a routing keyword, “Sales Dept“, in the Type Routing Sets section and click Add.
Click OK. You will notice that the routing keywords are now displayed under Advanced routing.
On the Set properties page, click OK.
You also need to create server groups and add a routing rule.
IBM Cognos BI 10.2.1 introduced a subtle change in the routing behavior, that untagged requests will be load-balanced across the whole system, instead the local Server Group only.

Before Cognos BI 10.2.1 a report that was send to a Cognos BI server, would stay in that server group that the first (primary) dispatcher was in. Meaning that Cognos BI reports would not be routed outside the server group of the first dispatcher. This have change, so now in Cognos BI 10.2.1 a report that is not connected to a "route set" on user or frame work manager package level, will be free to be processed on any of the Cognos BI reports servers in the solution.

If you implement Routing Rules in Cognos BI 10.2.1, you must have routing rules for all reports, to ensure that not any of them can end up uncontrolled on a Cognos BI server that does not have the data source it´s needs.  Can be done by a routing rule that takes all reports to one server group.  Set all the values to ANY and select a server group that will handle this reports.
•  Package Routing Set:
•  Group Routing Set:
•  Role Routing Set:
This Routing Rule should be the last one in the list, because if a reports is found matching a previous routing rule, it is not processed further down the list.

More Information:











How do i add a new user to a local group on the server from the command line PDF Print E-mail
(2 votes, average 4.00 out of 5)
Written by Roger   

Cognos Controller 10
Windows 2008 R2 server

How do i add a new user to a local group on the server from the command line ?

Can be needed in testing purpose on a new installation of Cognos software, to see if the issue is because of
the windows profiles temp files. Test with a new user can be good.

Start CMD as administrator on the Server ( or client computer).

Enter ; to create user mike

Enter ; to set his password to password

Enter ; to add mike to the local administrator group

Enter ; to list users in the local group

Enter ; to start a remote desktop session
MSTSC /v: /w:1024 /h:768

/v enter the name of the server or IP
/w set the width of the window
/h set the height of the window

More Information:







How do I start TM1TOP on the server? PDF Print E-mail
Written by Roger   

IBM Cognos TM1 10.1.1
Windows 2008 R2 server

How do I start TM1TOP on the server?

There are different ways to start the TM1top application.

One is to start it direct from an CMD dialog.
Log on to TM1 server.
Right click on Command Prompt and select Run as Administrator.
Enter the following line (after you change the path to yours) and press enter

"d:\program files\ibm\cognos\tm1_64\bin64\tm1top.exe" -servername "tm1planning"

Change tm1planning to the name of your tm1 application e.g. planning sample.
If you have made a TM1TOP.INI file you want to use and placed it in folder TOPTEMP you can use this command:

"d:\program files\ibm\cognos\tm1_64\bin64\tm1top.exe" -i  d:\toptemp\tm1top.ini

A different way to do it is to copy the TM1TOP.EXE and TM1TOP.INI files in a folder call d:\toptemp
Then you need to add path to TM1 bin folder in you path on the server.
Right click on Computer icon and select properties
Click on Advanced System Settings
Click on Environment Variables
Scroll down system variables and select PATH
Click on Edit
At the end of the variable value add;
;d:\program files\ibm\cognos\tm1_64\bin64
Click OK
Click OK
Click OK

Go to the d:\toptemp folder in windows explorer
Click on the tm1top.exe file to start tm1top application.

The TM1TOP.INI file should have this values


(Important to not have any spaces in above tm1top.ini file)
adminhost=the name of the windows server where tm1 admin service are
servername=the name of the tm1 application
logfile=the name of the logfile you want to create
logappend=True to add error messages to the file every time you start the tm1top
refresh=2 seconds between updates on the screen

Logperiod Specifies the time interval between updates being written to the log file, in seconds.
Setting this to zero disables logging.
For example, if the screen Refresh is set to 2 seconds, LogPeriod could be set to 10 seconds so that every fifth screen display will be output to decrease the amount of data written to the file.
The default value is 2 seconds.

The different commands in TM1TOP window:

N = Displays TM1 Top normal (thread status) mode.
S = Displays TM1 Top sandbox mode.
Q = Displays TM1 Top queue mode.
W = Writes the current TM1 Top information to a file.
X = Exits the TM1 Top utility.
H = Displays help text.
V  = Verifies a TM1 Top administrator session.
Displays a user name and password prompt so the TM1 administrator can log into the current session of TM1 Top and enter commands to cancel processing in other threads.

C = Cancels processing in another thread.
Note: Before using the Cancel command, an administrator must first log into the current session of TM1 Top by using the V (Verify) command.

K = Cancels a sandbox submission in the job queue for a specific job ID number.
Requires administrator login with the V (Verify) command.

Up, Down arrow keys = Use the up and down arrow keys to scroll the status display if there are more lines in the status than the height of the console window.

More Information




CogKnowHow Newsletter

Please register to the site before you can sign for a list.
No account yet? Register


How many users are working on your Cognos environment?