Product:

Cognos Planning 10.1.1

Microsoft Windows 2008 R2 server

SQL 2008 server

Symptom:

When user try to open Cognos Planning Contributor node they get error message:

 The application is now unavailable

 

Cause:

You must make the Cognos Planning application online inside Cognos Administration console after a GTP or a upgrade. This is different behavior than in previous versions of Cognos Planning.

 

Solution:

Log in to Cognos Planning Administration Console (CAC)

Mark you application in the left side.

Click on SET ON-LINE icon on the top left side.

 

Now you can ask the users to test to access the application again.

Product:

Cognos Planning 10.1.1

Windows 2008 R2 Server

Symptom:

When you start Cognos Planning Administrator you get a error message.

This is a new installation of Cognos Planning.

Error Messages:

An error has occurred while starting IBM Cognos Planning – Administrator

Main Form failed to initialize

Error Details:

ActiveX component can’t create object.

Unable to execute EAdminIU_10.frmMain.mnuLogonAs_Click

At line 0

There was a problem logging on. Please ensure you can access IBM Cognos Connection using the Gateway URI specified in IBM Cognos Configuration.

 

Possible Solutions:

Ensure that the URL to cognos connection are part of local intranet zone in Internet Explorer for the user that start cognos planning.

Change to use cognosisapi.dll instead of cognos.cgi in cognos configuration. IIS on the Windows 2008 R2 server is maybe setup to only allow ISAPI instead of CGI.

 

Ensure that the IBM Cognos Planning service is run by a windows domain account and not local system.

 

Apply the latest Cognos FixPack for Cognos Planning 10.1.1

Product:

Cognos Planning 10.1.1

Windows 2008 R2 server

Microsoft SQL 2008 database

Symptom:

Can not create database to imported Cognos Planning application

Have installed Cognos Planning 10.1.1 on a new server and want now to move the old Cognos Planning 8.4 application to the new server.

Recommended way is to export deployment packages from the Cognos Planning 8.4 administration console, and then import the files in the new Cognos Planning 10.1.1

 

Workaround:

Take a backup of the Cognos Planning application database on the old SQL 2005 server.

Restore the database on the new SQL 2008 server.

Make the cognos SQL login to be dbowner on the cognos planning database.

From Microsoft SQL Server Management Studio

Select the cognos planning database

expand tables and select table dbo.adminoptions

right click and select “edit top 200 rows”

find in column optionid the following 3 rows and erase the value at optionvalue for these

PAD_GUID

PAD_NAME

PAD_NAMESPACE

(Consider to update the value for BACKUP_LOCATION to a windows folder on the new SQL server.)

Close SQL Server Management Studio

 

Go into Cognos Planning Administration on the New Cognos Planning server

Expand datastores down to Applications.

Right click on applications and select Link to existing Applications…

You will get a list of the available Cognos Planning applications databases.

(if the list is empty, you point the datastore to the wrong database server or have not done above change in adminoption table correct)

Mark one of them and enter a application ID in the right column.

(Application ID should only be of A-Z and numbers, and no spaces.)

Click Add

 

“Your Cognos Planning Application needs to be upgrade from Cognos Planning 8.4 to Cognos 10 Planning 10.1. This is a major functional upgrade and therefore Cognos recommends that you migrate and upgrade your existing applications via Deployments. To proceed with a deployed upgrade press No and refer to the product documentation.

Would you like to continue with an in-place upgrade?”

Press Yes

 

“Are you sure you want to do an in place upgrade of your Cognos Planning Application? The Application will be updated and will no longer be functional in Planning 8.4.  Please ensure that you have backed up the Planning Application database before proceeding. The upgrade components create schemas and tables and populate them with data. Therefore users specified for connections must have been granted privileges to create and drop schemas and tables.

Do you want to proceed with the upgrade now?”

After you ensure you have backup of databases, Press Yes

 

“The application upgrade to version 10.1 was successful.

You must GTP your applications and set them online before they can be used.”

Press OK.

Expand the Cognos Planning application to –

development – application maintenance – Go To Production Options.

Check Location value to be a existing Cognos connection folder in the new Cognos Planning 10.1.1 installation.

Do a GTP.

Set the application ONLINE.

Repeat above for the other Cognos Planning applications you want to move and upgrade.

 

Try to upgrade and move the macros and admin links with use of a deployment package.

You need go through each macro and ensure path to applications are correct.

 

Ensure that your new applications are added to the Cognos Planning job cluster.

 

More Info

You must create a data store to the new SQL server in Cognos Planning Administration first.

http://publib.boulder.ibm.com/infocenter/cfpm/v10r1m0/index.jsp?topic=%2Fcom.ibm.swg.im.cognos.contrib_admin.10.1.0.doc%2Fcontrib_admin_id2297WP0192.html

 

You need also create a Job server cluster, and add your new Cognos Planning servers to this cluster.

http://publib.boulder.ibm.com/infocenter/cfpm/v10r1m0/index.jsp?topic=%2Fcom.ibm.swg.im.cognos.contrib_admin.10.1.0.doc%2Fcontrib_admin_id2297WP0192.html

 

You can not use “Upgrade Planning Administration Domain” with Cognos Planning 8.2 or newer installations. This is for upgrading from a older version of Cognos Planning.

Product:

Cognos Planning 10.1.1

Windows 2008 R2 server

Microsoft SQL 2008 R2

 

Symptom:

Can not load data into cognos planning application, where you use SQL alias to the datastore.

 

Error in PlanningErrorLog.csv file:

{DD2EF639-179C-4470-9F75-BF59A01CD86A}    6          2012-06-05 14:35:18.688 UTC +180       EAdminUI_10 10.1.3008.0     pgImportData             cmdLoad_Click            130      EAdminSQL7_10.SQL7.CheckOutputForErrors      -2147220469            Unable to Bulk Load the data.~~~~Error found in output.~~~~SQLState = 08001, NativeError = 53~~Error = [Microsoft][SQL Server Native Client 10.0]Named Pipes Provider: Could not open a connection to SQL Server [53]. ~~SQLState = 08001, NativeError = 53~~Error = [Microsoft][SQL Server Native Client 10.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.~~SQLState = S1T00, NativeError = 0~~Error = [Microsoft][SQL Server Native Client 10.0]Login timeout expired      CNS\CNSMANER            CNS\FIHECNS110AS            CNS\CNSMANER      CNS\FIHECNS110AS            4400    5056

 

Possible Solution:

If you are using SQL server alias to access the Microsoft SQL 2008 server, then you need to create the alias in both 32 bit and 64 bit drivers.

 

On the Cognos Planning server start SQL Server Configuration Manager

Expand SQL Native Client 10.0 Configuration

Right Click on Aliases and select New Alias.

Enter a alias name  (e.g. cognosds)

Enter the port no, if you do not know port number enter the instance name in the server name field ( servername\instancename )

Enter the Server name, (e.g. name of the SQL server)

Click OK

 

Repeat above for SQL Native Client 10.0 Configuration (32bit).

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.)