CogKnowHow – Page 76 – Just another WordPress site

LicenseMetricTime

November 10, 2016 by Roger·0 Comments

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”>

<ProductName>IBM Cognos TM1</ProductName>

</Product>

<Type>GROUP_INFO</Type>

<SubType>GROUP_DETAIL</SubType>

</Period>

</Metric>

<Type>GROUP_INFO</Type>

<SubType>GROUP_DETAIL</SubType>

</Period>

</Metric>

<Type>GROUP_INFO</Type>

<SubType>GROUP_DETAIL</SubType>

</Period>

</Metric>

<Type>GROUP_INFO</Type>

<SubType>GROUP_DETAIL</SubType>

</Period>

</Metric>

<Type>GROUP_INFO</Type>

<SubType>Number of Modeling groups</SubType>

</Period>

</Metric>

<Type>GROUP_INFO</Type>

<SubType>Number of Contributor groups</SubType>

</Period>

</Metric>

<Type>GROUP_INFO</Type>

<SubType>Number of Explorer groups</SubType>

</Period>

</Metric>

<Type>AUTHORIZED_USER</Type>

<SubType>MODELER</SubType>

</Period>

</Metric>

<SubType>MODELER</SubType>

</Period>

</Metric>

<Type>AUTHORIZED_USER</Type>

<SubType>MODELER</SubType>

</Period>

</Metric>

<SubType>MODELER</SubType>

</Period>

</Metric>

<SubType>Number of Modeling users</SubType>

</Period>

</Metric>

<SubType>Number of Contributor users</SubType>

</Period>

</Metric>

<SubType>Number of Explorer users</SubType>

</Period>

</Metric>

</Metrics>

</LicenseMetrics>

Error login to CDM

November 10, 2016 by Roger·0 Comments

Product:
CDM version 10.2.4
Microsoft Windows 2008 R2 server

Symptom:
Can not log on to CDM, the user get this error after selection of server
“Säkerhetsförhandlingsfel”

Error message in log file:
2016-10-19 14:19:03,628 [4] ERROR Ibm.CognosDM.Api.PluginsManager – CDCGN00500E (null) Plugin DashboardPlugIn was loaded. ErrorFormat 0
2016-10-19 14:19:03,675 [4] ERROR Ibm.CognosDM.Api.PluginsManager – CDCGN00500E (null) Plugin Filing was loaded. ErrorFormat 0
2016-10-19 14:19:03,675 [4] ERROR Ibm.CognosDM.Api.PluginsManager – CDCGN00500E (null) Plugin TasksPlugIn was loaded. ErrorFormat 0
2016-10-19 14:19:20,993 [1] ERROR Ibm.CognosDM.App – CDCGN00025E ExceptionToken: Unknown [LayoutPersistErrorException] Error 0 System.NullReferenceException: Object reference not set to an instance of an object.
at Ibm.CognosDM.Storage.Bases.UserDataSetBase..ctor(String storageLocation, String user)
at Ibm.CognosDM.Storage.DataSetInstances.get_UserSettings()
at Ibm.CognosDM.App.ApplicationExit(Object sender, ExitEventArgs e)

Check this as first step:
Can you also reset the IIS to see if it helps? Type “iisreset” in a Command Prompt window.

If the issue still persist, can you check whether the SSL certificate for CDM is still valid in IIS?

1. From the Start Menu, launch “Administrative Tools – Internet Information Services (IIS) Manager”
2. Highlight ‘Default Web Site’ or the Server name in IIS.
3. Click ‘Bindings’ or click on ‘Server Certificates’ – there you see Expiration Date direct.
4. Highlight your entry for ‘https’ and choose ‘Edit’
5. Click ‘View’
6. Check the Valid from/to dates

In this case the Certificate on the IIS for the default web site had expiry.

Solution:
Insert a new valid Certificate on the IIS server.

1. In the Internet Information Services (IIS) Manager console, under
Connections, select your server name.
2. Double-click Server Certificates.
3. Click Import.
4. Browse to and select the SSL certificate.
5. Enter the password for the certificate, and click OK.
6. Under Connections, select the website where the CognosDM-Server virtual directory is located. For example, select default.
7. Click Bindings. Select the https type, and click Edit.
9. In the SSL certificate window, select the certificate you imported, and click OK.
10. Close the Site Bindings window.
11. Select the CognosDM-Server website application.
12. Double-click SSL Settings.
13. Ensure that Require SSL is selected, and select Ignore in the Client certificates section.
14. Click Apply.

More information:
http://www.ibm.com/support/knowledgecenter/SSQK59_10.2.3/com.ibm.swg.ba.cognos.cdm_ig.10.2.3.doc/c_cdm_ig_ssl_certificates.html

The value must be numeric.

November 10, 2016 by Roger·0 Comments

Product:
Cognos Controller 10.2.1 Fix Pack 4
Microsoft Windows 2012 R2 server

Symptom:
Error when importing csv file with data, that have worked fine in previous version of Cognos Controller 10.1. The DiscardedRows are the same number as the Rowsread in Log Reports dialog.

Error message:
The value must be numeric.

The data we try to import contain a decimal value; e.g. 000.00

Solution:
Log on to the Cognos Controller server as the service account that run the Cognos Controller services.
Go to controller panel
Go to regional settings
Change to England (UK)
Click tab ‘Location’
Change this to ‘English (United Kingdom)’
Click tab “Administrative”
Click “Change system locale…” and change this to “English (United Kingdom)”:
Click “Copy Settings”
Tick the box “Welcome screen and system accounts”.
Tick the box “New user accounts”:
Click OK
Reboot the Controller application server

I think it is the value of Decimal symbol need to be changed from comma to a period that solves the issue.

The csv file that is imported to controller must be of a specific format.
Text file should use decimal point (not comma) for decimals and semicolon (not comma or
tab) as delimiter between the data fields.

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

How easy see version of Content Manager?

November 8, 2016 by Roger·0 Comments

Product:
Cognos BI 10.2.2
Microsoft Windows 2012 R2 Server

Question:
How to easy see if Content manager is up?

Solution:
Enter this in Internet Explorer
http://localhost:9300/p2pd/servlet
Change to localhost to your BI server name.

You get a text similar to this:

IBM Cognos Content Manager

IBM Cognos

Content Manager

Build: 10.2.6105.4
Start time: Tuesday, November 8, 2016 9:11:15 PM CET
Current time: Tuesday, November 8, 2016 9:21:28 PM CET
State: Running

More url you can use for testing:
# Get Dispatcher version
http://localhost:9300/p2pd/servlet/gc

# Determine if Content Manager is running
http://localhost:9300/p2pd/servlet

# Determine if Dispatcher (“pogo”) is alive
http://localhost:9300/p2pd/servlet/dispatch?b_action=/dbg

# View installed components
http://localhost:9300/p2pd/servlet/dispatch?b_action=cmplst

# Memory utilization
http://localhost:9300/p2pd/servlet/dispatch?b_action=/diagnostics

# Environment
http://localhost:9300/p2pd/servlet/dispatch/env

# Get load balancing statistics. Can also use this to verify the configuration of an install.
http://localhost:9300/p2pd/servlet/dispatch/p2plbDiag

# Pin requests for load balanced services to a specific Dispatcher (need to be logged in first)
http://localhost:9300/p2pd/servlet/dispatch/pin

# See if the Certificate Server is responding
http://localhost:9300/p2pd/servlet/dispatch/autoCAService

# Give some info if service is up — but that is easier to find with other command.
http://localhost:9300/p2pd/servlet/dispatch/testping

This is what you get with testping:

<?xml version=”1.0″?>

<SOAP-ENV:Envelope SOAP-ENV:encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” xmlns:bus=”http://developer.cognos.com/schemas/bibus/3/” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:SOAP-ENC=”http://schemas.xmlsoap.org/soap/encoding/” xmlns:SOAP-ENV=”http://schemas.xmlsoap.org/soap/envelope/”><SOAP-ENV:Header><bus:biBusHeader xsi:type=”bus:biBusHeader”><bus:tracking xsi:type=”bus:tracking”/><bus:dispatcherTransportVars xsi:type=”SOAP-ENC:Array” SOAP-ENC:arrayType=”bus:dispatcherTransportVar[]”><item xsi:type=”bus:dispatcherTransportVar”><name xsi:type=”xsd:string”>p2plb_result</name><value xsi:type=”xsd:string”>ok</value></item><item xsi:type=”bus:dispatcherTransportVar”><name xsi:type=”xsd:string”>p2plb_messagetimes</name><value xsi:type=”xsd:string”>1478636020024,1478636020024,1478636020024,0</value></item></bus:dispatcherTransportVars></bus:biBusHeader></SOAP-ENV:Header><SOAP-ENV:Body><l:p2plbPingResponse status=”ok” xmlns:l=”http://developer.cognos.com/schemas/p2pd/lb/1/”/></SOAP-ENV:Body></SOAP-ENV:Envelope>

# XML Parser Information
http://localhost:9300/p2pd/servlet/dispatch/xts.diag

# Determine if the SDK is installed by having the Dispatcher access the SDK WSDL file
http://localhost:9300/p2pd/servlet/dispatch?wsdl

# About IBM Cognos Connection
http://localhost:9300/p2pd/servlet/dispatch?b_action=xts.run&m=portal/about.xts

More information:

http://www.cogknowhow.com/index.php/knowledge-articles/36-tools/105-jvm-memory-utilization

https://community.watsonanalytics.com/discussions/questions/23687/what-diagnostic-urls-are-available-with-cognos-ana.html

com.ibm.ba.pm.resource.tm1.dictionary

October 25, 2016 by Roger·0 Comments

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

The system administrator has set policies to prevent this installation

October 25, 2016 by Roger·0 Comments

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.

A problem occurred while resetting culture settings : Old format or invalid type library

October 18, 2016 by Roger·0 Comments

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.

Could not open specified application

October 18, 2016 by Roger·0 Comments

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.

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.

Open TM1 server from architect.
Run the following TM1 control TI Process: “}tp_admin_delete_all”
Click OK on Provide Parameters Values dialog.
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.

Select the Import application properties option if you want to import
property settings with the application.
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.

How do I upgrade my analyst folders

October 18, 2016 by Roger·0 Comments

Product:

Cognos Planning 10.1.1

Windows 2008 R2 server

Symptom:

How do I upgrade my analyst folders from Cognos Planning version 8.4 ?

Solution:

Create a file share on the new planning 10.1.1 server.

In our example we call it \\newplanserver\cognosplanning

Make everyone have full access to the share

(later change that to only allow planning administrators and service accounts to have access)

Copy you analyst models folders over to the new share from the old Cognos planning server.

(check inside Cognos Planning Analyst for the path to the files – under File -Administration – Maintain Libraries and Users)

Copy the LIBS.TAB file from the old planning filesys.ini share to the new share.

Disconnect from the old Cognos planning server, so you are not mapped to it any more.

Start New Cognos Analyst on the New Cognos planning server.

Select File – Administration – Upgrade – Existing Libraries

Browse to your local LIBS.TAB file.

Click on OPEN.

“Some of the libraries you are about to import has the same library number as libraries that already exists in analyst.

These libraries cannot be imported.

You can manually copy existing libraries to a different library number, and them manually connect to the old libraries via the Add Library functionality in the Admin screens.”

Click OK.

Now you have the Analyst libraries in the list of Maintain Libraries and Users.

But they have the old path, that is wrong and need to be changed.

Right click on a library in the list and select “Change Library Path…”

In the Find string you enter the part of the path you want to replace

can be \\oldservername\analystshare

In the replace with string you enter the new path to your librarys

in our case that is \\newplanserver\cognosplanning

Click Replace

“The path will be changed for xx libraries.

You can press Cancel to abort the operation.

OK to continue.”

Click OK

Now all the path are updated – they are shown in CAPITAL LETTERS.

To validate the path afterwards, just click Properties for each library since that will report if there are any problems.

IMPORTANT: We do not guarantee this process, you need to make sure you have valid backup of your Cognos planning files before starting the upgrade process.

There was a problem running the Deployment Wizard.

October 18, 2016 by Roger·0 Comments

Product:

Cognos Planning 10.1.1

Windows 2008 R2 server

Symptom:

You want to move Cognos planning deployment files (macro) from one server in test to another server in prod environment. You have copied the macro folder to the new servers deployment folder. When you have many Cognos servers in the same environment it is recommended to have them all point to the same file share for deployment files.

When you run the Cognos planning deployment wizard get error when you select import.

Error message:

There was a problem running the Deployment Wizard.

null

There was a problem running the Planning Network Transfer Wizard. Please see the error log for more information.

Cause:

Strange characters like – and space are not allowed in server name or share name (folder name) for the deployment folder.

You can test if the servername is bad, by change in Cognos Configuration to use the IP address instead of the servername in the field for deployment.

E.g. \\192.168.1.10\deployment

If the IP address works, then you know it is the planning server name that make the deployment not to work.

Solution:

Go in to Cognos Configuration

Select Environment

Go to value for Deployment files location in Environment – Group Properties.

Change from \\server-name\deployment to

\\192.168.1.10\deployment

(default value is ../deployment)

(default value will look for the cognos planning files in folder c:\program files (x86)\ibm\cognos\c10\deployment.)

Click on Save

Click Stop on services

Click Start on services (check Details for error messages, should not be any).

Exit Cognos Configuration

or place the share on a windows server that have a short name with only letters in it.