Product:

Cognos TM1 Architect 10.2.2

Windows 2008 R2 Server

Cognos BI 10.2.1 Fix pack 2

Problem:

Sometimes when try to add users to a existing TM1 application inside TM1 architect you get a crash. After that you need to logoff the computer and login again to maybe be able to not get this crash. The crash happens random, but always when you add CAM users.

Error message:

TM1 Architect has stopped working

-Check online for a solution

-Close the program

Problem signature:

Problem Event Name: APPCRASH

Application Name: tm1a.exe

Application Version: 10.2.20000.50159

Fault Module Name: C8ITKShared.dll

Fault Module Version: 10.2.50.0

…

Error found in Microsoft Event log on client:

Log Name:      Application

Source:        Application Error

Date:          2014-12-09 08:38:56

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      servername.domain.com

Description:

Faulting application name: tm1a.exe, version: 10.2.20000.50159, time stamp: 0x536252da

Faulting module name: C8ITKShared.dll, version: 10.2.50.0, time stamp: 0x51840c06

Exception code: 0xc0000005

Fault offset: 0x000146e0

Faulting process id: 0x3a4

Faulting application start time: 0x01d01382c5a63795

Faulting application path: C:\Program Files (x86)\IBM\Cognos\tm1_architect\bin\tm1a.exe

Faulting module path: C:\Program Files (x86)\IBM\Cognos\tm1_architect\bin\C8ITKShared.dll

Report Id: 6df507c2-7f76-11e4-a9fc-fc15b4179054

Event Xml:

<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>

<System>

<Provider Name=”Application Error” />

<EventID Qualifiers=”0″>1000</EventID>

<Level>2</Level>

<Task>100</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime=”2014-12-09T07:38:56.000000000Z” />

<EventRecordID>49328</EventRecordID>

<Channel>Application</Channel>

<Computer>servername.com</Computer>

<Security />

</System>

<EventData>

<Data>tm1a.exe</Data>

<Data>10.2.20000.50159</Data>

<Data>536252da</Data>

<Data>C8ITKShared.dll</Data>

<Data>10.2.50.0</Data>

<Data>51840c06</Data>

<Data>c0000005</Data>

<Data>000146e0</Data>

<Data>3a4</Data>

<Data>01d01382c5a63795</Data>

<Data>C:\Program Files (x86)\IBM\Cognos\tm1_architect\bin\tm1a.exe</Data>

<Data>C:\Program Files (x86)\IBM\Cognos\tm1_architect\bin\C8ITKShared.dll</Data>

<Data>6df507c2-7f76-11e4-a9fc-fc15b4179054</Data>

</EventData>

</Event>

 

Possible solution:

Inside TM1 Architect, ensure you use FQDN server names to connect to TM1 servers.

Select File and Options

At login parameters at admin host field ensure you have written servername.domain.com instead of only server name.

Change and try again.

Check that the IBM Cognos TM1 Server version of the file C8ITKShared.dll

is exactly the same as the one on the TM1 Architect client computer.

If they are not the same version, you can get this error.

 

On the client computer you have installed the TM1 client’s files, and the TM1 Architect files in different folders.

Add the path to the TM1 Bin folder for the client files to the PATH variable in Windows.

Right click on My Computer and select  Properties.

Click on Advance System settings

Click on Environments Variables

Mark PATH and click on EDIT.

Add  C:\Program Files (x86)\IBM\Cognos\tm1_api\bin to the Variable Value

Click OK

Click OK

Click OK

Logoff  the computer and login again.

The path to the bin folder can be different in your installation.

Product:

Cognos TM1 10.2.2

Cognos Insight

Windows 2008 R2 Server

Cognos BI 10.2.1

Problem:

When you start Cognos Insight from TM1 Application Web you get a error message.

Error Message:

Unexpected error. Contact your system administrator.

[CCLMsg: system text=’Unable to create the directory app-tempdir: temp

Verify that the directory exists. Verify that the application has permission to access the directory.’]

com.cognos.ccl4j.exceptions.CCLRuntimeException (root com.cognos.ccl4j.exceptions.CCLRuntimeException):

[CCLMsg: system text=’Unable to create the directory app-tempdir: temp

Verify that the directory exists. Verify that the application has permission to access the directory.’]

at com.ibm.cdt.data.model.interfce.tm1.planning.model.Model.getDirpath(Model.java:582)

at com.ibm.cdt.data.model.interfce.tm1.planning.model.Model.getTempDirpath(Model.java:495)

at com.ibm.cdt.data.model.interfce.tm1.planning.model.Model.setApplicationConfiguration(Model.java:488)

at com.ibm.cdt.data.model.interfce.tm1.planning.model.Model.openModelForApplication(Model.java:408)

at com.ibm.cdt.data.model.interfce.tm1.planning.model.Model.openModel(Model.java:162)

at com.ibm.cdt.ui.common.utility.ApplicationConnectionHelper$CDFPlanningDataServer.getApplication(ApplicationConnectionHelper.java:517)

at com.ibm.cdt.ui.common.utility.ApplicationConnectionHelper.getCurrentApplication(ApplicationConnectionHelper.java:108)

at com.ibm.cdt.ui.common.application.CDFDashboardManager.getCurrentApplication(CDFDashboardManager.java:3863)

at com.ibm.cdt.ui.common.application.CDFDashboardManager.getCurrentModelState(CDFDashboardManager.java:3918)

at com.ibm.cdt.ui.common.application.CDFDashboardManager$3.handleCreatedEvent(CDFDashboardManager.java:462)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:94)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)

at java.lang.reflect.Method.invoke(Method.java:619)

at com.cognos.utils.events.EventSupport$MulticastHandler.invoke(EventSupport.java:332)

at com.sun.proxy.$Proxy5.handleCreatedEvent(Unknown Source)

at com.ibm.cdt.ui.common.application.CDFDashboardManager.createProject(CDFDashboardManager.java:1095)

at com.ibm.cdt.ui.common.tm1.connect.ConnectTm1Helper.relaunchDashboard(ConnectTm1Helper.java:177)

at com.ibm.cdt.ui.common.tm1.connect.ConnectTm1Helper.connect(ConnectTm1Helper.java:98)

at com.ibm.cdt.ui.common.tm1.connect.ConnectTm1Helper.connectToPlanningApp(ConnectTm1Helper.java:106)

at com.ibm.cdt.ui.common.operations.ConnectToPlanningAppOperation.execute(ConnectToPlanningAppOperation.java:45)

at com.ibm.cdt.ui.common.application.CDFApplicationDesktop.execute(CDFApplicationDesktop.java:1603)

at com.ibm.cdt.ui.common.actions.ConnectToTm1Action.connect(ConnectToTm1Action.java:106)

at com.ibm.cdt.ui.common.actions.ConnectToTm1Action.run(ConnectToTm1Action.java:62)

at com.ibm.cdt.ui.common.application.CDFDashboardManager.connectToTM1(CDFDashboardManager.java:1482)

at com.ibm.cdt.desktop.ui.command.ConnectToTM1Handler.execute(ConnectToTM1Handler.java:38)

at com.ibm.cdf.cui.common.commands.CDFCommandService.executeCommand(CDFCommandService.java:54)

at com.ibm.cdf.cui.common.actions.CDFCommandAction.executeCommand(CDFCommandAction.java:92)

at com.ibm.cdf.cui.common.actions.CDFCommandAction.run(CDFCommandAction.java:87)

at com.ibm.cdf.cui.utilities.popup.CDFBaseMenuItem.runAction(CDFBaseMenuItem.java:661)

at com.ibm.cdf.cui.utilities.popup.CDFBaseMenuItem.mouseUp(CDFBaseMenuItem.java:683)

at com.ibm.cdf.cui.utilities.popup.CDFBaseMenuItem$2.handleEvent(CDFBaseMenuItem.java:141)

at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)

at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1262)

at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1052)

at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)

at com.ibm.cdt.desktop.Application$6.run(Application.java:262)

at com.ibm.cdt.desktop.Application$1.run(Application.java:97)

at com.ibm.cdt.desktop.Application.start(Application.java:267)

at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:94)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)

at java.lang.reflect.Method.invoke(Method.java:619)

at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)

at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)

at org.eclipse.equinox.launcher.Main.run(Main.java:1438)

 

Solution:

Create a TEMP folder at this location

C:\Program Files\IBM\Cognos Insight\bins\bin_10.2.5210.88

The path can be different at your installation, but under the bin folder with versions number create an empty TEMP folder.

Now it is only one TM1 folder below there.

The installation missed to create the TEMP folder.

Product:

IBM Cognos Tm1 10.1.1 (version PLANANALYTICS-AW64-ML-RTM-10.1.7000.91-0)

PLANANALYTICS-AW64-ML-RTM-10.1.7101.108-0 ( TM1 fix pack1)

Windows 2008 R2 server

Symptom:

Inside Tm1web, you click on export icon and select export to pdf.

Select a Choose number of rows to export:

Select a Choose dimension titles to export:

click OK

Gives error message;

Error message:

Export in process. Please wait…

Error while Printing to PDF: No printers are installed. To install a printer click the File tab, and then click Print. Click No Printers Installed, and then click Add Printer. Follow the instructions in the Add Printer dialog box.

 

Cause:

The windows service account that is set for the IBM Cognos TM1 Excel Service, is not the same account used when installing TM1 server ( and the pdfcamp printer driver ).

 

Solution:

Stop IBM Cognos TM1 Excel Services

Uninstall the pdfcamp printer driver by run, D:\Program Files\ibm\cognos\tm1_64\bin\PDFCamp\unpdfx64.exe

Log off the TM1 server

Login to the TM1 server with the windows account that is use to run the TM1 Excel service.

Install the pdfcamp printer driver by run. D:\Program Files\ibm\cognos\tm1_64\bin\PDFCamp\setupx64.exe

Now the printer driver is there for the user running the service.

Set the PDFcamp Printer as default printer.

Start the IBM Cognos TM1 Excel Services.

Log off the server.

Test the TM1web function export to pdf.

Product:

IBM Cognos TM1 10.1.1

Windows 2008 R2 server

 

Problem:

How do I start TM1TOP on the server?

 

Solution:

There is 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

 

adminhost=windowsservername

servername=tm1planning

logfile=tm1topplanninglog.txt

logappend=t

refresh=2

logperiod=10

 

(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=10

 

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

http://pic.dhe.ibm.com/infocenter/cbi/v10r2m1/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.tm1_op.10.1.1.doc%2Fc_usingthetm1toputility_n160f47.html

Product:

Cognos TM1 10.1

Windows 2008 R2 Server

 

Symptom:

Start a new TM1 server and try to connect to it with the TM1 Architect program.

You get a error after you have enter name and password.

 

Error message:

The specified server is not found

 

Solution:

If the error message “The specified server is not found” is before the login dialog in TM1 Architect then the local firewall is blocking the TM1 port.

 

Go to Windows Firewall with Advanced Security

Go to Inbond rules

Create a rule to allow local TCP port “12346” to any ip address.

Enable it and restart the firewall.

 

If the error message “The specified server is not found” is after the login dialog in TM1 Architect then there is some other process using the same port.

 

Stop the TM1 service.

Open Tm1s.cfg in notepad

Check the port number used by TM1 application server at line PortNumber=12346

Start a commando prompt (cmd)

Enter netstat to find if that port is in use by enter below command:

netstat -a | find “12346”

 

If no row is shown, then the port is free to use.

 

If you see below row – then it is occupied, and you need to use other port.

TCP 0.0.0.0:12346     SERVERNAME:0    LISTENING

 

Change if needed port in TM1S.CFG and start the TM1 service.

 

More Information:

If you move a TM1 application to a new server, you need to check this lines in the TM1s.cfg file to ensure they point to the correct value for the new environment.

 

IntegratedSecurityMode=5 You can try mode 1 if you have problems to login.

ServerName=  Should be the same, the name of the TM1 application in architect

DataBaseDirectory= Should be the folder path to the datafiles (often same as before)

LoggingDirectory= Should be the folder path to the logfiles (often same as before)

AdminHost= Should be the new TM1 admin servername

PortNumber= Should be the same number, if it is available on the new server

ServerCAMURI= Should be changed to the new Cognos BI server’s dispatch address

ClientCAMURI=  Should be changed to the new Cognos BI server’s gateway

Product:

Cognos TM1 10.2

PLANANALYTICS_version=PLANANALYTICS-AW64-ML-RTM-10.2.5000.367-0

LICENSE_TM1_version=LICENSE_TM1-AW64-ML-RTM-10.2.5001.0-0

Windows 2008 R2 Server

Cognos BI

Symptom:

Can not login to Cognos TM1 when using CAM security.

It works when using the TM1 native security.

Error message:

The forward URL does not exist or it has failed validation. Ensure that a valid forward URL is specified.

Cause:

The file variables_tm1.xml is on the wrong BI server.

 

Solution:

Copy your updated variables_tm1.xml file to all your Cognos BI servers in your solution.

Place the file in folder \\biservername\d$\Program Files (x86)\ibm\cognos\c10_64\templates\ps\portal

 

In short is the installation to get CAM to work for TM1 10.2 web different from previous version.

 

Unzip the D:\Program Files\IBM\cognos\tm1_64\webapps\tm1web\gateway_files\ tm1web_gateway.zip files.

Rename d:\Program Files\ibm\cognos\tm1_64\webapps\tm1web\gateway_files\tm1web_gateway\templates\ps\portal variables_TM1.xml.sample to variables_TM1.xml.

Update variables_tm1.xml with the TM1 server name at line 23 instead of localhost:

<CRNenv>

<urls>

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

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

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

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

</urls>

<cookies>

<param name=”cam_passport”/>

</cookies>

</CRNenv>

 

Update the tm1web.html file to Cognos TM1 Web server name at line 40:

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

var tm1webServices = [“http://localhost:8080”];

Change to:

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

 

Copy the files to your Cognos BI installation:

variables_TM1.xml = Copy to d:\Program Files\ibm\cognos\c10_64\templates\ps\portal templates\ps\portal on your Cognos BI report server and content manager server.

Tm1web.html = Copy to d:\Program Files\ibm\cognos\c10\webcontent\tm1\web on your Cognos BI gateway server.

 

In tm1s.cfg file you need for each TM1 application add the values for:

 

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

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

ClientPingCAMPassport=900

CAMPortalVariableFile=portal\variables_TM1.xml

DistributedPlanningOutputDir=.\tunit

ForceReevaluationOfFeedersForFedCellsOnDataChange=T

AllowSeparateNandCRules=T

 

The value CAMPortalVariableFile is not needed in the TM1S.CFG file for tm1web to work.

 

More (same) Information:

http://pic.dhe.ibm.com/infocenter/cbi/v10r2m1/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.tm1_inst.10.2.0.doc%2Ft_tm1_inst_tm1web_cogsecurity.html

Product:

Cognos TM1 10.1.1

Windows 2008 R2 server

Cognos BI 10.1.1 CAM security

Symptom:

When you surf to TM1 application web you get a error when you try to sign in.

(http://biserver.domain.se/ibmcognos/cgi-bin/cognosisapi.dll?…)

You have upgrade or installed a new TM1 10.1.1 server and connected it with a existing Cognos BI installation.

Error message:

PRS-PRH-0221

The file “portal\variables_plan.xml” could not be opened.

Cause:

The variables_plan.xml file is not on the correct location on the Cognos BI server.

 

Solution:

On the TM1 server find the folder D:\Program Files\ibm\cognos\tm1_64\webapps\pmpsvc\gateway_files

Unzip the file planning_gateway.zip to your Cognos BI server and your Cognos BI gateway server.

 

This should give that the files come to this folders:

planning.html  should in folder …\c10\webcontent

variables_plan.xml should in folder …\c10\templates\ps\portal

icon_active_application.gif  should in folder …c10\webcontent\ps\portal\images

Update the planning.html file to contain the name of the TM1 server at line 38

…

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

var planningServices = [“http://tm1server.domain.se:9510”];

…

 

More information:

http://pic.dhe.ibm.com/infocenter/cbi/v10r2m1/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.tm1_inst.10.1.1.doc%2Ft_depl_tm1_cont_admin.html

Product:

Cognos TM1 10.1.1 Perspective

PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.1.7101.108-0

Windows 2008 R2 server

Microsoft Office 2010 32 bit  version 14.0.6023.1000

Symptom:

When you start TM1 perspective on a new computer you get a error message, and can not load TM1 perspective into Microsoft Excel 2010.

Error Message:

Could not load an object because it is not available on this machine.

Compile error in hidden module: MenuFuncs.

This error commonly occurs when code is incompatible with the version, platform, or architecture of this application. Click “Help” for information on how to correct this error.

 

Cause:

http://support.microsoft.com/kb/2597986

 

Solution:

Find the correct MSCOMCTL.OCX file from a different computer, where TM1 perspective is working with Microsoft Excel 2010.

 

Correct version is dated 2012-06-06 8:49 AM and 1046 KB in size.

File version 6.1.98.34

Product version 6.01.9834

 

On the computer where you have the problem.

Exit Excel

Go to folder %systemroot%\sysWOW64

Rename file mscomctl.ocx to mscomctl.ocx.old.txt

Copy the correct mscomctl.ocx fil to folder c:\windows\syswow64

Start a cmd prompt with “run as administrator”

Enter cd %systemroot%

Enter cd syswow64

Enter regsvr32 /u mscomctl.ocx

Click OK on dialog

Enter regsvr32  mscomctl.ocx

Click OK on dialog

 

Start Tm1 Perspective again and test.

Product:

IBM Cognos TM1 10.1.1

PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.1.7101.108-0

Performance Modeler

Windows 2008 R2 server

Symptom:

When adding CAM users in Cognos TM1 Performance Modeler, you get a error message when you click on CANCEL in the add user dialog (this is the dialog showing the Cognos and namespace groups from the Cognos connection portal security tab).

Error message:

Internal Application Problem

There was an internal application problem. Try to save your work and exit the application. Check console for complete stack trace.

java.lang.NullPointerException

at

com.ibm.mdt.widgets.cube.actions.AddGroupAction.run(AddGroupAction.java:110)

at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)

 

Solution:

Instead of adding user by right click on the list of users inside Performance Modeler, use the icon in the toolbar at the top to add users, or add groups.

By using the icon for this function, it will work better.

The context menu can in some cases give errors.

Product:

TM1 10.1.1

Operations Console

Windows 2008 R2 server

 

Symptom:

Try to login to a Operations Console session, you have enter the following:

adminhost: localhost

servername: planning sample

group: cognos\admin

username: admin

password: apple

 

Error message:

The specified group does not exist on the server

 

Cause:

Operations Console may have problems with group names that contain a \ backslash or other characters. Recommendation to use simple group names like  MONITOR or ADMIN.

 

Solution:

Start TM1 Architect and add a group with name MONITOR

Add users to this group MONITOR that should be allowed to MONITOR the TM1 application.

Exit Architect.

 

Update the D:\Program Files\ibm\cognos\tm1_64\webapps\tm1operationsconsole\WEB-INF\configuration\ OpsConfig.xml file to reflect the change of group.

 

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

<Ops>

<AdminHost name=”localhost”>

<Server name = “Planning Sample”>

<Group>MONITOR</Group>

</Server>

</AdminHost>

<DashboardRefreshRate>5</DashboardRefreshRate>

<EnhancedStatusDetail>true</EnhancedStatusDetail>

</Ops>

 

Opsconfig.xml should look like above. Save the file.

You may need to change localhost with your servername, and planning sample if you want to use a different TM1 application as security container for Operation Console.

 

Go to Windows services and restart the “IBM Cognos TM1 Application Server” to make changes take affect.

Surf to http://localhost:9510/tm1operationsconsole/ to test the change.