Product:

Cognos Planning 10.1.1

 

Symptom:

In Cognos connection you get error when viewing a Cognos planning application.

 

Error message:

CPS-PAG-4801 ………….

PRS-OBJ-0606 …………

PRS-BLK-0667 ………………..

 

Solution:

In the properties to the HTML viewer the URL link to the application is specified with server name only and you need to specified it with FQDN (Fully Qualified Domain Name).

 

To change;

Click on edit icon to the right of the HTML page pane.

Below the bookmarks change the URL for the links.

From http://servername:80/ibmcognos/cgi-bin….

To http://servername.domain.com:80/ibmcognos/cgi-bin….

Click OK

Try again.

Product:

Cognos Planning 10.1.1

Windows 2008 R2 server

Symptom:

Error message when starting up Cognos Analyst or Cognos Planning Administration Console.

Error message:

An error has occured while starting IBM Cognos Planning – Administrator.

Main form failed to initialize.

 

Error Details:

Could not logon. Please ensure you can access Cognos Connection using the Gateway URI specified in Cognos Configuration.

 

Possible Solution:

Change to not use FQDN in Cognos Configuration, and use only server name in environment tab.

(above will work if you are on the Cognos Planning server itself)

Change from http://servername.domain.org:80/ibmcognos to http://servername:80/ibmcognos

in cognos configuration on all existing places.

or add the Cognos URL FQDN to your Internet Explorer local intranet zone.

select internet options

select security

select local intranet

click on sites

click on advanced

enter the web site e.g. http://servername.domain.org/ibmcognos

click add

click close

click OK

click OK

 

Close Internet Explorer and test again to login.

Product:

Cognos Planning 10.1.1

Windows 2008 R2 server

 

Symptom:

Error when starting the Cognos Planning Analyst on a 64 bit server.

Cognos Planning Analyst only works for the account that was used during installation.

 

Error Message:

A Fatal Error has occured in the startup section of the application.

The application will be terminated.

 

Please report the following information:

Function name: SystemIniGet

Namespace: #._US

=============================

RegOpenKeyA returned a nonzero error code

SystemIniGet[10]Hkey,,0 MyOpenKey Key

 

 

Solution:

You need to update the current users registry with some values.

 

In notepad you need to create two text files with similar content as below:

—————–File 1—————————————————-

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Cognos]

“Analyst”=”d:\\cognos\\c10\\bin\\”

 

—————–File 2—————————————————–

Windows Registry Editor Version 5.00

 

[HKEY_CURRENT_USER\Software\IBM\Cognos\Planning101]

[HKEY_CURRENT_USER\Software\IBM\Cognos\Planning101\Analyst]

“-“=””

[HKEY_CURRENT_USER\Software\IBM\Cognos\Planning101\Analyst\Analysthelp]

@=””

[HKEY_CURRENT_USER\Software\IBM\Cognos\Planning101\Analyst\AnalystMessageLibs]

@=””

[HKEY_CURRENT_USER\Software\IBM\Cognos\Planning101\Analyst\BX]

@=””

[HKEY_CURRENT_USER\Software\IBM\Cognos\Planning101\Analyst\Compatibility]

@=””

[HKEY_CURRENT_USER\Software\IBM\Cognos\Planning101\Analyst\CP]

“CubeStackBytes”=”1024”

“DataMacros”=”0”

“EditMacros”=”0”

“MaxTranscriptBytes”=”400”

“MaxViewCells”=”10”

“NotEnoughMemFlag”=”Yes”

“StackBytes”=”1024″

[HKEY_CURRENT_USER\Software\IBM\Cognos\Planning101\Analyst\Custom]

@=””

[HKEY_CURRENT_USER\Software\IBM\Cognos\Planning101\Analyst\Main]

“DefaultUser”=”Admin”

[HKEY_CURRENT_USER\Software\IBM\Cognos\Planning101\Analyst\MRU]

@=””

[HKEY_CURRENT_USER\Software\IBM\Cognos\Planning101\Analyst\Settings]

“LastLib”=”0”

“Position”=”23 0”

“Size”=”840 1260”

“State”=”Maximised”

“Language”=””

[HKEY_CURRENT_USER\Software\IBM\Cognos\Planning101\Analyst\StartUp]

@=””

[HKEY_CURRENT_USER\Software\IBM\Cognos\Planning101\Contributor]

[HKEY_CURRENT_USER\Software\IBM\Cognos\Planning101\Contributor\Settings]

“Language”=””

---

Name the files with REG endings and then you can click on them to install the values.

 

At below site you have complete instructions on how to do it:

https://www-304.ibm.com/support/docview.wss?mynp=OCSSPN2D&mync=R&uid=swg21472649&myns=swgimgmt

 

(Only edit the Windows registry if you know what you are doing.)

Product:
Cognos Planning 10.1.1
Windows 2008 R2 Server
Oracle database

Problem:
When a user inside Cognos Planning Administration Console ( CAC ) click on the Monitoring Console tab he get a error message and when he click OK the CAC program exits (crash).

Error message:
Run time error 13 – type mismatch

Solution:
Truncate two tables inside the Cognos Planning Store.

p_pnrequestprogress
and p_pnrequest

Start SQL developer
Login to the database as COGPLAN (the schema that have access as the planning and planning store databases)
Enter;

truncate p_pnrequestprogress
truncate p_pnrequest

Commit
And test again from inside Cognos Planning Administrator to click on Monitoring Console.

Product:
IBM Cognos Planning 10.1.1 Fix Pack 3
Microsoft Windows 2008 R2 server
Oracle Database

Symptom:
When user in CAC (Cognos Planning Administration Console) click on Monitoring Console tab to Monitor a Deployment they get a error message. When they click OK on error message the CAC is closed down.

Error message:
‘Runtime Error 13’
‘Type Mismatch’

Solution:
Stop the Cognos BI and Cognos Planning services in Windows on all Planning servers.
Log into the Planning Store database with SQL developer ( or TOAD ).
Ensure you have a backup of the oracle database.
Run this commands to truncate the two tables:

truncate table p_pnrequestprogress;
truncate table p_pnrequest;

Start Cognos Configuration for the server that contain Content Manager first.
Start the Cognos services here first – both BI and Cognos Planning.
After they are up, then go to next server – the Cognos Planning Job server.
Start Cognos Configuration for the Planning Job server and start that as second.
When all the Planning services are up, go into CAC and test again.

The start order of the Cognos BI and Planning servers are important.

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

Product:
Cognos Planning version 8.4.1

Symptom:
The handles are not expandable inside the Cognos Planning Contributor client.

Cause:
Rich Client Contributor front-end have the expand/collapse (plus/minus) handles for hierarchies.

This is controlled by this Hierarchical Dimensions in Analyst

For a dimension to be shown as a hierarchy in Analyst, the following requirements need to be met:
• The dimension must not be a time dimension.
• The dimension’s items must all be detail or simple sums.
• Do not use weighted or time averages.
• Do not use the Force to Zero calculation option.
• Priorities can only be 0 or 10.
• Do not use any formatting.

Solution:
Recreate your Cognos Planning application to only use above allowed values / properties.

Product:
Cognos Planning 8.4.1

Symptom:
On new install or on an upgrade to Cognos Planning 8.4.1 the Cognos Planning service does not start when you try from inside Cognos Configuration. Cognos 8 BI service will start fine on the other hand.

Cause:
When the SQL database is in an INSTANCE (not using the standard port number of 1433) then you must use the instance name for Cognos Planning to access the database. The use of the SQL port number in Cognos Configuration for the Planning Store database will give this error.
Cognos use java odbc connectors to access the database.

Solution:
Ensure that the SQL Browser service is started on the Microsoft SQL 2005 server

In Cognos Configuration under Planning Store – Database – Resource Properties
Ensure that you address the database server with servername\instance name
e.g. SRVSQL01\COGNOS

The use of SQL Aliases on the Cognos Planning server may not solve this issue.

You can try by installing the Microsoft SQL server 2005 client’s tools on the Application server.
Then from inside the Configuration Tools menu start SQL Server Configuration Manager.
Under the SQL Native Client Configuration right click on Alias and select New Alias.

Create a new alias named planningds for the planning database server.
Enter the server name and the port number.
Port number can be different when you use an instance of Microsoft SQL server on a database server machine.

Product:
Cognos Planning version 8.4.1

Symptom:
Can not start the Cognos Planning service from Cognos Configuration

Error Message:
Failed HRESULT [0x80004005] :The service failed to start because it could not successfully open a database connection with the Planning Store or the Content Store configured in Cognos Configuration. Details:
Database Errors: Source: Microsoft OLE DB Provider for SQL Server Description: Login failed for user ‘cognos_ps’. The user is not associated with a trusted SQL Server connection. Number: -2147467259 SQLState: 42000 NativeError: 18452

Cause:
The SQL login is setup in Microsoft SQL server management studio, but the SQL server is not set to support mix mode login.

Solution:
Start Microsoft SQL server management studio
Open properties for the SQL server
Change the server security to “SQL server and Windows Authentication mode”
Click OK to save changes.

Restart server and test database connection again from Cognos Configuration.

Product:
Cognos Planning 8.4.1 rich client

Symptom:
Can not move tabs in Cognos Contributor client.

More information:
Do below steps to reset the tab order to the default for the application:
Open up the Cognos planning administration console
choose /development /application maintenance/admin options
Change “persistent settings” from “client” to “server”
Save and GTP the application.
(cube order, orientation and sorting of the dimension made in the client grid will have to be re-done)

The Persist Contributor Web Client Setting can affect IBM Cognos Planning Rich Client Performance. Having the Persist Contributor Web Client Setting turned to Off may provide a slight improvement web client performance.

By turning the Persist Contributor Web Client Setting to Off, neither the server nor the client caches the user’s web grid layout. Therefore any grid customization will be lost once the user logs off and will need to be reset upon next entry. It is important this change in functionality is weighed carefully against the potential performance improvements. Persist client setting are global setting and will affect all users. When turning off Persist a dialog box will appear, this explains the loss in functionality that will result.

Solution:
Exit Cognos Planning Contributor and erase the local cache in Internet Explorer.

If the persisted settings are set to “Client” then this setting is saved on your client PC and you are looking out for an XML called “{GUID}workbench.xml ” under \CognosRCP\temp\contributor_8.4\RichClient

Deleting this will force the grid to take the settings that is set within CAC.

Then start Internet Explorer and your Cognos Planning application again.

Product:
Cognos Planning version 8.4.1

Symptom:
The Cognos service for planning or BI does not start, when you click on start in Cognos configuration program.

Error Message:
[Logging]
1. [ ERROR ] IPFTEST-006 Logging failed to connect to Database:jdbc:JSQLConnect://Server_Name:1433/Database_Name

Cause:
The SQL login created for the Cognos Audit or Planning Store are set to change password at first login.

Solution:
In SQL server management studio, right click and select properties for the SQL login used.
Uncheck “User must change password at next login”
Click OK

Now start the Cognos services from Cognos configuration.