Product:
TM1 10.1 Perspective
Windows 2008 R2 Server
Citrix Server

Symptom:
When you start TM1 Perspective (Excel 2010) from Citrix portal you get a error message.

Error message:
Run-time error ‘429’: ActiveX component can’t create object

Solution:
After you have installed TM1 Perspective on the server,
you need to start the application once to create some registry values before other can run it.

Log in as local administrator on the server
Start TM1 Perspective.
Close TM1 Perspective (and Excel)
Log out from server.

Now other users should be able to login.

Product:
Cognos TM1 9.5.2
Windows 2008 R2 server
Microsoft Excel 2003 (11.5612.5606)

Symptom:
When from TM1WEB select to slice to excel or snapshot to excel, you select “export rows in current page” and “plan_version” for dimensions titles to export. That give a total of 5 new sheets to be generated. You get a error message after some time.

Error message:
Export in process. Please wait…
A problem occurred while resetting culture settings : Old format or invalid type library. (Exception from HRESULT: 0x80028018 (TYPE_E_INVDATAREAD))

Possible Solution:
Stop all TM1 services on the Windows server, including the TM1 Excel Service.
For Office 2003 users you must Create a 1033 directory under C:\Program Files\Microsoft Office\Office11. Then, copy excel.exe to the 1033 directory, and rename it as xllex.dll.
For Office 2007 users you must copy (DO NOT CUT) the “xllex.dll” that is in C:\Program Files\Microsoft Office\OFFICE12\1033 into the following directory: C:\Program Files\Microsoft Office\Office12.
For Office 2010 users you must copy (DO NOT CUT) the “xllex.dll” that is in C:\Program Files\Microsoft Office\OFFICE14\1033 into the following directory: C:\Program Files\Microsoft Office\Office14.
Ensure that all TM1 service use the same Windows domain service account.
Start all TM1 service on the Windows server.
Check that your version of Excel is English.
Ensure that Internet explorer uses English (United States) [en-US] as Language Preference,
set in Internet Explorer under TOOLS – INTERNET OPTIONS – GENERAL – LANGUAGES.
Click on ADD to add the English language.
Click on MOVE UP to place English as first language in the list.
Click OK
Close Internet Explorer

In some cases you need to ensure that Regional settings on the TM1 server for the Windows service account is set to English.
Go to control panel and click on “region and language” settings.
Select format to be English (United States)
Click APPLY

If you get a new error after above changes that say
“There was a problem sending the command to the program”
when you start TM1 perspective with Excel 2003 then you must in excel do this;
Go to TOOLS – OPTIONS – GENERAL tab
clear the checkbox for “Ignore other applications”
Click OK.

For Excel 2007 you need to Bring up the Excel options, go to advanced and then scroll down to the “General” section. Make sure that
“Ignore other applications that use Dynamic Data Exchange (DDE)” is not checked.

Now TM1 perspective will work.

More information
The additional workaround for Office 2007 & Office 2010 is slightly different for Office 2003 which is listed in the “KB 320369” article.

Product:
Cognos TM1 9.5.2
Windows 2008 R2 server

Symptom:
When you are inside TM1 Contributor web site and click on “update application” icon you get a error message. You can start the TM1 application, it is only the Admin dialog that does not work.

Error message:
Connecting to server application error
Could not open specified application

Cause:
The TM1 application have not been successfully installed to the new TM1 contributor server

Solution:
You need to do this steps if you want to move a complete TM1 application between servers.

How to export a TM1 contributor application from PROD server:

Open the TM1 Contributor Portal.
1. Mark the application to export.
2. Click Export button.
3. Click Save on the File Download dialog box.
4. Navigate to the directory where you want to save the export file.
5. Click Save.
This create a zip file of your TM1 Contributor application.

Go into TM1 Architect and open you TM1 application – select SAVEALL.
Exit TM1 Architect.
Stop the TM1 windows service.

Zip the datafolder for your TM1 application on the PROD server.

Copy the ZIP files over to the other TM1 server.

How to import a TM1 contributor application to DEV server:

We assume you already have a TM1 application here, that you only want to update with data from the other TM1 server.

If you allready have a application in the TM1 Contributor application with the same name, you need to delete it first as Administrator in the TM1 Contributor Portal on the DEV server.

Stop the TM1 windows service.
Unzip the datafolder files to the TM1 application folder on the DEV server.
Make any changes needed to tm1s.cfg file ( e.g. change server name)
Start the TM1 windows service.

1. Open TM1 server from architect.
2. Run the following TM1 control TI Process: “}tp_admin_delete_all”
3. Click OK on Provide Parameters Values dialog.
4. Exit TM1 Architect program.

Import the TM1 Contributor application as an Administrator in the TM1
Contributor Portal

Steps:
1. Open the TM1 Contributor Portal.
2. Click import button.
3. The Application Import window opens.
4. Select the TM1 Server onto which you want to import the application.
5. Click Browse next to the Application file field.
6. Navigate to the application (.zip) file, then click Open.
7. Select the Import application security option if you want to import security
settings with the application.
8. Select the Import application properties option if you want to import
property settings with the application.
9. Click Import.

Now you should be able to click on the UPDATE APPLICATION icon.

Any status indicators of the TM1 contributor nodes can be lost during the process.

Product:
Cognos TM1 9.5.2
Windows 2008 R2 Server

Symptom:
User can not access the TM1 Contributor web site and user can not run Cognos BI reports against TM1 data. But Architect can access the TM1 applications. The Apache TOMCAT service have stopped working.

IT department can not access the Windows 2008, server that run TM1, with Remote Desktop tools, they believe only solution is to reboot physical server.

Task Manager report that the Windows server have free memory and free cpu power.

Error message on TM1 server when you try to start notepad:
There is not enough free memory to run this program. Exit one or more programs, and then try again.

Possible Solution:
If you have tuned your TM1 application, it may be using features that is using windows system resources more during heavy use than needed.

Remove the following parameter in your tm1s.cfg file:
LockPagesInMemory=T
or set it to
LockPagesInMemory=F
Then save the tm1s.cfg file
Update all tm1s.cfg file you have on your TM1 server.

Execute SaveAllData from inside TM1 Architect (to ensure no data is lost).
Restart the TM1 services from Windows services (to pickup the change in the tm1s.cfg file).

Monitor the TM1 server during heavy load to see if issue is solved.

More Information:
LockPagesInMemory=T locks the TM1 data in memory and take away system resources from the windows system to increase performance of TM1. But the Windows system will get lack of resources on a heavy used TM1 server, and therefore gradual stop the system from working.

Product:
Cognos TM1 9.5.2
Windows 2008 R2 server

Symptom:
TM1 application does not start.
In task manager the CPU usage is at 6% and the tm1sd application have a memory working set of 4840 Kb.
There are no error messages, or any new log files in the log folder for tm1.

Background:
You have moved a TM1 application from ONE server to a NEW server.
(this by coping the DATA folder from the old TM1 server)
You have updated the tm1s.cfg file with admin host and port number and log files paths.
You have register the TM1 application as a service with commando:

d:\program files\cognos\tm1\bin\tm1sd.exe -install -n TM1applicationname -z “d:\tm1data\TM1applicationfoldername”

(above path need to be modified to conform with your environment)

You have set the TM1 service to use a windows service account to start the service.

Cause:
The windows service account is not local admin on the new TM1 server.

Solution:
Add the windows service account to local administrator group and restart the service.

Start server manager
Go to Configuration
Go to Local Users and Groups
Go to Groups
Open Administrators
Click Add
Enter name of service account
Click Check Names
Click OK
Click OK

Product:
Cognos TM1 9.5.2
Microsoft Windows 2008 R2

Problem:
When user surf to Cognos Application Web on the url http://tm1servername.domain.com:8080/pmpsvc
Then click on the icon for “update application” in the list they get the error
“Could not open specific application”

Cause:
The wrong cert file are in user catalog
C:\Users\%username%\AppData\Roaming\CognosRCP\rcp\applications\ModelingADT_8.4.1\bins\bin_8.4.7347.0\ssl
Copy the new certificates to this folder then it will work for that user.
Cognos Tm1 9.5.2 is not supported, so there is no provision agent.

Solution:
Copy the new cert to folder D:\NewSSLCerts
Create a bat file with this content:
d:
cd D:\NewSSLCerts
copy /B /Y D:\NewSSLCerts\*.* “%appdata%\CognosRCP\rcp\applications\ModelingADT_8.4.1\bins\bin_8.4.7347.0\ssl*.*”
copy /B /Y D:\NewSSLCerts\*.* “%appdata%\CognosRCP\rcp\applications\ModelingADT_8.4.1\bins\bin_8.4.7343.0\ssl*.*”
copy /B /Y D:\NewSSLCerts\*.* “%appdata%\CognosRCP\rcp\applications\ModelingADT_8.4.1\bins\bin_8.4.7278.0\ssl*.*”

Save the file as d:\updatecert.bat

Update the BAT file with correct path and ” characters.

Create a shortcut icon to that file on the users desktop by putting it in folder
C:\Users\Public\Desktop,   on a Microsoft Windows 2008 R2 server.
Let the user run the BAT file before starting administration of Cognos Application web.

If a new user start the administration program from the Tm1 application web (pmpsvc) in Tm1 9.5.2 he will get the error, but thereafter he maybe can update his user profile on his computer with above bat file.

More Information:

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

The version of the TM1 server installation can be determined be examining the contents of the cmplst.txt file and the file version of the tm1sd.exe file in the bin64 directory. The following is a list of version numbers from both the tm1sd.exe file and cmplst.txt file.
cmplst.txt file
Within the IBM Cognos TM1 install folder look for a file called cmplst.txt. The default installation location for TM1 10.1 and higher is typically C:\Program Files\ibm\cognos\tm1_64 and C:\Program Files\cognos\tm1 for 9.5.2 and lower.

Within this cmplst.txt 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.
tm1sd.exe file
To find the version of the TM1 server, browse to the TM1 Server bin64 directory (or bin in 9.5.2), right click and select properties on the tm1sd.exe file. Examine the Product version field.

Note that TM1 9.5.2 and lower versions do not include a cmplst.txt file. You must determine the version of the TM1 Server by examining only the details of the tm1sd.exe file.

TM1 9.5.2 RTM – 9.5.20000.11857
TM1 9.5.2 Fixpack 1 – 9.5.20100.18046
TM1 9.5.2 Fixpack 2 – 9.5.20200.22178
TM1 9.5.2 Fixpack 3 – 9.5.20300.29580
TM1 9.5.2 Fixpack 3 Interim Fix 7 (http://www-01.ibm.com/support/docview.wss?uid=swg24039812) – 9.5.20328.42361

TM1 10.1 RTM
cmplst.txt file – PLANANALYTICS_version=PLANANALYTICS-AW64-ML-RTM-10.1.6237.212-0
tm1sd.exe version – 10.1.00000.20166

TM1 10.1 Fixpack 1
cmplst.txt file – PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.1.6301.21-0
tm1sd.exe version – 10.1.00100.24600

TM1 10.1 Fixpack 1 Interim Fix 3
cmplst.txt file – PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.1.6301.86-0
tm1sd.exe version – 10.1.00111.37787

TM1 10.1.1 RTM
cmplst.txt file – PLANANALYTICS_version=PLANANALYTICS-AW64-ML-RTM-10.1.7000.91-0
tm1sd.exe version – 10.1.10000.26473

TM1 10.1.1 Fixpack 1
cmplst.txt file – PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.1.7101.108-0
tm1sd.exe version – 10.1.10100.31864

TM1 10.1.1 Fixpack 2
cmplst.txt file – PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.1.7102.32-0
tm1sd.exe version – 10.1.10200.39014

TM1 10.1.1 Fixpack 2 Interim Fix 4 (http://www-01.ibm.com/support/docview.wss?uid=swg24039813)
cmplst.txt file – PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.1.7102.133-0
tm1sd.exe version – 10.1.10312.42293

TM1 10.2 RTM
cmplst.txt file – PLANANALYTICS_version=PLANANALYTICS-AW64-ML-RTM-10.2.5000.367-0
tm1sd.exe version – 10.2.00000.36339

TM1 10.2 Fixpack 1
cmplst.txt file – PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.2.5001.145-0
tm1sd.exe version – 10.2.00100.39992

TM1 10.2 Fixpack 2
cmplst.txt file – PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.2.5002.20-0
tm1sd.exe version – 10.2.00200.41411

TM1 10.2 Fixpack 2 Interim Fix 4 (http://www-01.ibm.com/support/docview.wss?uid=swg24039814)
cmplst.txt file – PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.2.5002.1040-0
tm1sd.exe version – 10.2.00210.42310

TM1 10.2.2 RTM
tm1sd.exe version – cmplst.txt file – PLANANALYTICS_version=PLANANALYTICS-AW64-ML-RTM-10.2.5200.234-0
10.2.20000.50183

TM1 10.2.2 Fixpack 1
cmplst.txt file – PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.2.5210.167-0
tm1sd.exe version – 10.2.20100.123

TM1 10.2.2 Fixpack 2
cmplst.txt file – PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.2.5220.91-0
tm1sd.exe version – 10.2.2020055

TM1 10.2.2 Fixpack 3
cmplst.txt file – PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.2.5230.146-0
tm1sd.exe version – 10.2.20300.93

TM1 10.2.2 Fixpack 3 Interim Fix 1009
cmplst.txt file – PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.2.5230.1009-0
tm1sd.exe version – 10.2.20300.98

TM1 10.2.2 Fixpack 4
cmplst.txt file – PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.2.5240.167-0
tm1sd.exe version – 10.2.20400.80

TM1 10.2.2 Fixpack 5
cmplst.txt file – PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.2.5250.191-0
tm1sd.exe version – 10.2.20500.75

 

Information is from this site:

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

Product:
Cognos TM1 10.2.2
Microsoft Windows 2012 Server

Problem:
How do I list the Admin users in a TM1 application?

Solution:
There are different ways to get similar information;

List of users who have logged in to the TM1 application can be seen in the log file.

Here is a quick way to track user login/logout in TM1 using standard TM1 functionality, i.e. ACTIVE or blank STATUS Value from the }ClientProperties cube.

As of the TM1 9.1 release and later, the STATUS field is not automatically updated, so you will need to enable a background thread to keep the STATUS field up-to-date by setting the ClientPropertiesSyncInterval configuration parameter in tm1s.cfg file.

The background thread will wake up periodically and update the STATUS field for all clients indicating which are currently connected to the server. The configuration parameter ClientPropertiesSyncInterval is the number of seconds the background thread waits between updates. Example: ClientPropertiesSyncInterval=5

• In the Server Explorer (TM1 Architect) , select View–>Display Control Objects from the top menu bar. Right click on Cubes and select Security Assignments.
• Scroll down and ensure that Logging is checked for the }ClientProperties cube.
• Select the tm1server and right click on View Transaction Log.
• Select Cubes: }ClientProperties and the required date range.
• Click Edit–>Select All–>Copy and then paste the records into an Excel spreadsheet.

The raw data in the Excel spreadsheet can be analyzed by creating a pivot table to count the number of OldValue or NewValue for each user (Key1) and for each day (LogTime). Convert the LogTime to a suitable month/year format to analyze the user login counts by month. Create your own Excel format for reporting TM1 User activity.

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

Use an external program to find the usages, try this to see if they can help you;

http://www.bspsoftware.com/products/metamanager/tm1/

https://www.motio.com/content/CognosTM1-free-software.do

Use a TI process to list the users in the security cube, into a different cube, this script below need to be edit to have the USERGROUPS you want to list, and then you have to look into the result cube, to see what GROUPS each user is part of. Should give that it is easy for you to see the number of user that are ADMIN in an application.

In each TM1 application, create a new TI process, and paste below code in PROLOG and EPILOG.

“edit” groups and save and run. You will have a new cube that will list users in group.

#————————————–

# Below code should be in PROLOG
# set default values
#————————————–

sTargetCube=’ClientMemberships’;
sClientDim=’Clients’;
sClientMemberDim=’ClientsMembership’;

sCube=’}ClientGroups’;
sDim=’}Clients’;

sGroup1=’ADMIN’;
sGroup2=’DataAdmin’;
#————————————–
# create dimensions if they do not exist
#————————————–

if (DimensionExists (sClientDim)=0);
DimensionCreate (sClientDim);
endif;

if (DimensionExists(sClientMemberDim)=0);
DimensionCreate (sClientMemberDim);
endif;
#——————————————–
# create cube if not exist
#——————————————–

If (Cubeexists (sTargetCube)=0);
CubeCreate (sTargetCube,sClientDim,sClientMemberDim);
endif;

#—————————————–
# create dimension hierarchy
#——————————————

#dimensiondeleteAllElements(‘ClientsMembership’);
dimensionelementInsertDirect( sClientMemberDim,”,’Sum’,’c’);
dimensionelementComponentAdddirect(sClientMemberDim,’Sum’,sGroup1,1);
dimensionelementComponentAdddirect(sClientMemberDim,’Sum’,sGroup2,1);

dimensiondeleteAllElements(sClientDim);
#————————————————————

# Below code should be in EPILOG
# check if client is member of group
#————————————————————-

i=1;
while(i<=dimsiz(sDim));
vClient=dimnm(sDim,i);
if(long(attrs(sDim,vClient,’}TM1_DefaultDisplayValue’ ))>0);
vClientName=attrs(sDim,vClient,’}TM1_DefaultDisplayValue’ );
else;
vClientName=vClient;
endif;

if(cellgets(sCube, vClient, sGroup1) @=sGroup1);
dimensionelementinsertdirect(sClientDim,”,vClientName,’n’);
cellputn(1,sTargetCube,vClientName, sGroup1);
endif;

if(cellgets(sCube, vClient, sGroup2) @=DimensionElementPrincipalName(  ‘}Groups’,sGroup2 ) );
dimensionelementinsertdirect(sClientDim,”,vClientName,’n’);
cellputn(2,sTargetCube,vClientName, sGroup2);
endif;

i=i+1;
end;
#——————————————————————
# end of code
#——————————————————————

 

List license usage of TM1 with the TM1S.CFG parameter LicenseMetricTime

LicenseMetricTime=00:14:36

The file is created under the folder \ C:\Program Files\ibm\cognos\tm1_64\slmtagraw.

File name is IBM Cognos TM1_10.2.0_medlem register20150113200502294.slmtagraw , see the content of this file last in this doc.

 

Based on the little documentation that exists (i.e. in the .cfg file), I believe this will generate an XML file for the ILMT tool to pick up which is required for sub-capacity license monitoring.

 

NOTE: ILMT https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM+License+Metric+Tool

is IBM software which is free and is required when PVU licensed software has been installed on a Virtual environment.

# LicenseMetricTime
# Sets the time of day the TM1 server will generate a License Metric Tag file.
# A License Metric Tag file is an XML file which contains information about license metrics consumed by software product instances.
# In the case of TM1 server, the reported authorized user metrics are the number of Modelers, Contributors and Explorers.
# The License Metric Tag files produced by various instances of TM1 servers are collected by the IBM License Metric Tool (ILMT) agent and aggregated to produce final metrics based on the TM1 product version.
#
# The format of the LicenseMetricTime parameter is dd:hh:mm where:
# * dd is the number of days from today that the system will start automatically producing License Metric tag files. For example, 00 is today, 01 is tomorrow.
# * hh:mm is the time of day in 24-hour format.
# Type: optional, dynamic
LicenseMetricTime=00:14:36

More information:

http://www-01.ibm.com/support/docview.wss?uid=swg21959520&myns=swgimgmt&mynp=OCSS9RXT&mync=E&cm_sp=swgimgmt-_-OCSS9RXT-_-E

Use AUDIT logging to find when users are logged into the Applications.

You want to enable audit logging for the TM1 server, process the audit log, and review the details of the audit log.

 

This shows how to use the audit log, for your or use any TM1 server that you have available.

 

Open Windows Explorer, and then navigate to Tm1 folder for your application or the example application GreatOutdoors

Open the tm1s.cfg file in Notepad.

You want to enable the audit log and specify how frequently this log is to be updated.

Set the value of the AuditLogOn parameter to T.

Set the value of the AuditLogUpdateInterval parameter to 60.

The AuditLogUpdateInterval indicates the amount of time, in minutes, that TM1waits before moving the events.  The events are moved from the temporary audit file into the final audit log.

Save the file and close Notepad.

 

You may need to restart your TM1 applications service to make the changes in TM1S.CFG to take affect.

 

From the Start menu, point to All Programs\IBM Cognos\TM1, and then click Architect.

Expand TM1, and then double-click greatoutdoors.

You are prompted to log on to the GreatOutdoors TM1 server.

In the UserName box, type admin, leave the Password box blank, and then click OK.

Ensure that greatoutdoors is selected, and then from the Server menu, click Process Audit Log Events.

You are prompted to update the audit log with the latest events.

Click Yes, and then from the Server menu, click View Audit Log.

The Audit Log window opens.

Click Run Query.

The Results section of the Audit Log window shows a list of audit events.

You can further refine your results by choosing a different time period, as well as by specifying the event owner and type.

Close the Audit Log window.

 

Export the Audit log to Excel for further processing.

 

More Information on the file:

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

<LicenseMetrics version=”0.1″

xmlns=”http://www.ibm.com/xml/ns/licensemetrics”

xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”

xsi:schemaLocation=”http://www.ibm.com/xml/ns/licensemetrics licensemetrics.xsd”>

<Product>

<ProductName>IBM Cognos TM1</ProductName>

<ProductVersion>10.2.0</ProductVersion>

<ProductId type=”guid”>4acad4f5525b4bd0a78723fcd6cd6154</ProductId>

<InstanceId type=”installation_path”><![CDATA[C:\Program Files\ibm\cognos\tm1_64\bin64]]></InstanceId>

<InstanceName><![CDATA[medlem register]]></InstanceName>

</Product>

<Metrics>

<Metric LogTime=”Apr 18, 2016 7:05:02 PM GMT”>

<Type>GROUP_INFO</Type>

<SubType>GROUP_DETAIL</SubType>

<Value><![CDATA[Group ADMIN is a modeling group: The predefined admin group ADMIN is considered a Modeling group.]]></Value>

<Period>

<StartTime>Apr 18, 2016 7:05:02 PM GMT</StartTime>

<EndTime>Apr 18, 2016 7:05:02 PM GMT</EndTime>

</Period>

</Metric>

<Metric LogTime=”Apr 18, 2016 7:05:02 PM GMT”>

<Type>GROUP_INFO</Type>

<SubType>GROUP_DETAIL</SubType>

<Value><![CDATA[Group DataAdmin is a modeling group: The predefined admin group DataAdmin is considered a Modeling group.]]></Value>

<Period>

<StartTime>Apr 18, 2016 7:05:02 PM GMT</StartTime>

<EndTime>Apr 18, 2016 7:05:02 PM GMT</EndTime>

</Period>

</Metric>

<Metric LogTime=”Apr 18, 2016 7:05:02 PM GMT”>

<Type>GROUP_INFO</Type>

<SubType>GROUP_DETAIL</SubType>

<Value><![CDATA[Group SecurityAdmin is a modeling group: The predefined admin group SecurityAdmin is considered a Modeling group.]]></Value>

<Period>

<StartTime>Apr 18, 2016 7:05:02 PM GMT</StartTime>

<EndTime>Apr 18, 2016 7:05:02 PM GMT</EndTime>

</Period>

</Metric>

<Metric LogTime=”Apr 18, 2016 7:05:02 PM GMT”>

<Type>GROUP_INFO</Type>

<SubType>GROUP_DETAIL</SubType>

<Value><![CDATA[Group TESTGROUP is a contributor group: Group TESTGROUP has WRITE permission on cube ClientMemberships.]]></Value>

<Period>

<StartTime>Apr 18, 2016 7:05:02 PM GMT</StartTime>

<EndTime>Apr 18, 2016 7:05:02 PM GMT</EndTime>

</Period>

</Metric>

<Metric LogTime=”Apr 18, 2016 7:05:02 PM GMT”>

<Type>GROUP_INFO</Type>

<SubType>Number of Modeling groups</SubType>

<Value>3</Value>

<Period>

<StartTime>Apr 18, 2016 7:05:02 PM GMT</StartTime>

<EndTime>Apr 18, 2016 7:05:02 PM GMT</EndTime>

</Period>

</Metric>

<Metric LogTime=”Apr 18, 2016 7:05:02 PM GMT”>

<Type>GROUP_INFO</Type>

<SubType>Number of Contributor groups</SubType>

<Value>1</Value>

<Period>

<StartTime>Apr 18, 2016 7:05:02 PM GMT</StartTime>

<EndTime>Apr 18, 2016 7:05:02 PM GMT</EndTime>

</Period>

</Metric>

<Metric LogTime=”Apr 18, 2016 7:05:02 PM GMT”>

<Type>GROUP_INFO</Type>

<SubType>Number of Explorer groups</SubType>

<Value>0</Value>

<Period>

<StartTime>Apr 18, 2016 7:05:02 PM GMT</StartTime>

<EndTime>Apr 18, 2016 7:05:02 PM GMT</EndTime>

</Period>

</Metric>

<Metric LogTime=”Apr 18, 2016 7:05:02 PM GMT”>

<Type>AUTHORIZED_USER</Type>

<SubType>MODELER</SubType>

<Value><![CDATA[Admin]]></Value>

<Period>

<StartTime>Apr 18, 2016 7:05:02 PM GMT</StartTime>

<EndTime>Apr 18, 2016 7:05:02 PM GMT</EndTime>

</Period>

</Metric>

<Metric LogTime=”Apr 18, 2016 7:05:02 PM GMT”>

<Type>USER_INFO</Type>

<SubType>MODELER</SubType>

<Value><![CDATA[User Admin is a Modeler. Belongs to group ADMIN. The predefined admin group ADMIN is considered a Modeling group.]]></Value>

<Period>

<StartTime>Apr 18, 2016 7:05:02 PM GMT</StartTime>

<EndTime>Apr 18, 2016 7:05:02 PM GMT</EndTime>

</Period>

</Metric>

<Metric LogTime=”Apr 18, 2016 7:05:02 PM GMT”>

<Type>AUTHORIZED_USER</Type>

<SubType>MODELER</SubType>

<Value><![CDATA[Roger]]></Value>

<Period>

<StartTime>Apr 18, 2016 7:05:02 PM GMT</StartTime>

<EndTime>Apr 18, 2016 7:05:02 PM GMT</EndTime>

</Period>

</Metric>

<Metric LogTime=”Apr 18, 2016 7:05:02 PM GMT”>

<Type>USER_INFO</Type>

<SubType>MODELER</SubType>

<Value><![CDATA[User Roger is a Modeler. Belongs to group ADMIN. The predefined admin group ADMIN is considered a Modeling group.]]></Value>

<Period>

<StartTime>Apr 18, 2016 7:05:02 PM GMT</StartTime>

<EndTime>Apr 18, 2016 7:05:02 PM GMT</EndTime>

</Period>

</Metric>

<Metric LogTime=”Apr 18, 2016 7:05:02 PM GMT”>

<Type>USER_INFO</Type>

<SubType>Number of Modeling users</SubType>

<Value>2</Value>

<Period>

<StartTime>Apr 18, 2016 7:05:02 PM GMT</StartTime>

<EndTime>Apr 18, 2016 7:05:02 PM GMT</EndTime>

</Period>

</Metric>

<Metric LogTime=”Apr 18, 2016 7:05:02 PM GMT”>

<Type>USER_INFO</Type>

<SubType>Number of Contributor users</SubType>

<Value>0</Value>

<Period>

<StartTime>Apr 18, 2016 7:05:02 PM GMT</StartTime>

<EndTime>Apr 18, 2016 7:05:02 PM GMT</EndTime>

</Period>

</Metric>

<Metric LogTime=”Apr 18, 2016 7:05:02 PM GMT”>

<Type>USER_INFO</Type>

<SubType>Number of Explorer users</SubType>

<Value>0</Value>

<Period>

<StartTime>Apr 18, 2016 7:05:02 PM GMT</StartTime>

<EndTime>Apr 18, 2016 7:05:02 PM GMT</EndTime>

</Period>

</Metric>

</Metrics>

</LicenseMetrics>

Product:
Cognos TM1 10.2.2 café
Microsoft Windows 2012 R2 server

Symptom:
How setup CAFÉ on server so accessible from workstations?

Solution:
In PMHUB enter the name (server name) of the TM1 server in the HOST value for com.ibm.ba.pm.resource.tm1.dictionary.

This value is shown for the CAFÉ user when they try to login.
Default value is localhost.

To get to PMHUB surf to http://servername.domain.com:9510/pmhub/pm/admin

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

Product:
Cognos TM1 10.2.2 Performance Modeler
Microsoft Windows 2012 R2 Server

Symptom:
After uninstall of TM1 performance Modeler on 2012 server from add/remove programs in control panel. You cannot install PM again — either from the TM1 application web icon or from the MSI file itself.

This issue is caused by default security settings on Windows 2008 and Windows 2012 computers. The User Account Control (UAC) settings specify that non-administrators cannot run Microsoft Installer (.msi) files.

If you get an error like this:
Provagent bootsrap update failed: Could not copy “win32\x86_64\cognosrcp.exe” to d:\program files\ibm\cognos\tm1_64\coginsight
– Please try to install it again, in most cases it works the second try.

Error message:
The system administrator has set policies to prevent this installation

Solution:
When try to install the file from the TM1 application web site, select download and save the MSI file in a folder on your hard disk ( d:\temp)

1. Go to Start > Accessories.
2. Right-click Command Prompt and select Run as administrator.
3. In the command window, use the cd command to go to the directory containing either CognosInsight.msi or PerformanceModeler.msi.
4. Type either CognosInsight.msi or PerformanceModeler.msi.