Product:
Cognos TM1 9.5.2 portlets
Cognos BI 10.1

Symptom:
You can not get a TM1 cube viewer to show up in your Cognos Connection Page.

Error message:
PRS-PRH-0221
The file “portal/variables_TM1.xml” could not be opened.

Cause:
The variables_tm1.xml file is installed to the Cognos Gateway folder, should be installed to folder C:\Program Files\ibm\cognos\c10_64\templates\ps\portal on the Cognos BI server.

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

Cause:
The URL in the variables_tm1.xml file is wrong. Ensure it is correct, by compare it to a variables_tm1.xml file from a working Cognos BI server.

Solution:
Note that you must always restart the Cognos BI service, after changes to variables_tm1.xml file for the change to take affect.

The variables_TM1.xml file should look like this; replace SRV001 with your TM1 server name.

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

<!–

IBM Confidential

OCO Source Materials

BI and PM: tm1fragments

(C) Copyright IBM Corp. 2008, 2009

The source code for this program is not published or otherwise

divested of its trade secrets, irrespective of what has been

deposited with the U.S. Copyright Office.

–>

<CRNenv>

<urls>

<url is-regex=”true”>http://srv001/TM1Web/TM1WebLogin.aspx</url>

<url is-regex=”true”>http://srv001/TM1Web/TM1WebLoginHandler.aspx</url>

<url is-regex=”true”>http://srv001/TM1Web/TM1WebMain.aspx</url>

</urls>

<cookies>

<param name=”cam_passport”/>

</cookies>

</CRNenv>

Product:
Cognos TM1 contributor version 9.5.1

Symptom:
Can not logon and access a previous working TM1 Contributor application.
User surf to http://tm1servername:8080/pmpsvc
Is prompted with TM1 Login dialog that ask for user name and password
No matter what you enter – you get a error message.

Error message:
Could not logon to any available servers with the provided credentials.

Cause:
The TM1 Contributor is tie to a TM1 Application that use CAM security.
But the TM1 application was not using CAM security when you setup TOMCAT and TM1 Contributor – you have change the TM1 application later to use CAM (Cognos 8 logon) and therefore the TM1 Contributor ask for a TM1 login- but can not find any TM1 application that supports that logon method.

Suggested Solution:
(There may be other way to solve this)

You need to setup TM1 Contributor again.
Logon to your TM1 Contributor windows server.
Stop Apache Tomcat 6 service.
Remove the values for server name and admin_host in the pmpsvc_config.xml file.
Start the Apache Tomcat 6 service again.
Surf to http://localhost:8080/pmpsvc

You will be prompted with the TM1 Contributor Configuration page again.

Enter the TM1 server name at Admin Host:
(this can be a different server than the TM1WEB – it should be the server that runs the TM1 admin service)

The TM1 Web Client URL should be:
http://tm1servername/TM1web/contributor.aspx
(this should point to the server that runs the tm1web portal – often the same server as the Cognos gateway server)

In the server drop down list you should select your previous selected tm1planning server.
Now you will get two new lines to enter information (for the CAM security)

IBM Cognos 8 Gateway URI: enter here a value like this;
http://cognosservername:80/cognos8/cgi-bin/cognos.cgi

IBM Cognos 8 Dispatcher URI: enter here a value like this;
http://cognosservername:9300/p2pd/servlet/dispatch/ext

Click OK to save.
Now you will be prompted with the Cognos 8 logon page.
Then you are back in the TM1 Contributor page with your application.

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 BI 10.1.1 office
Windows 2008 R2 server
Microsoft Excel 2007

Symptom:
Error message when you import a report with prompts to excel.

Part of Error message:
Client found response content type of (text/ type / HTML) but expected
(text/xml).

DOCTYPE html PUBLIC “-//W3C/DTD XHTML 1.0 Strict//EN”

500 – Internal server error.

There is a problem with the resource you are looking for, and it cannot be displayed.

Solution:
On you Cognos BI gateway server
Start Internet Information Service Manager
Expand the Default Web Site so you see cgi-bin folder
Click on application cgi-bin
Double-click on icon Error Pages.
Click on the right side on “Edit Feature Settings”
Mark “Detailed errors”
Click OK

Test again – you do not need to restart the IIS to active the change.

The error in GO OFFICE happen when “Detailed errors for local requests and custom error pages for remote requests” is marked in the IIS dialog.

Product:
Cognos BI 10.1.1
Windows 2008 R2 Server
Microsoft SQL database

Symptom:
Error message when test data source in Cognos connection for DQM.

Error Message:
Microsoft SQL Server (JDBC) / Dynamic Query Mode
XQE-GEN-0005 Found an internal error: XQE-JDB-0004 A problem occurred finding the driver class “com.microsoft.sqlserver.jdbc.SQLServerDriver”.

Solution:
You need to download and put the SQL Server JDBC type 4 (sqljdbc4.jar) drivers in the D:\Program Files (x86)\ibm\cognos\c10_64\v5dataserver\lib directory and restart the BI server.

You can download the SQL Server JDBC driver from here:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=21599

Unpack the files in a empty folder.
Copy the sqljdbc4.jar file to all Cognos BI servers
Place the file in the \ibm\cognos\c10_64\v5dataserver\lib folder.
Restart the BI servers.

Then you can configure the JDBC data source in Cognos Connection.

Product:
Cognos Controller 8.5
Microsoft Excel 2003

Symptom:
Error message in Cognos controller when you start Excel, by click on Excel icon or run data entry.

Error:
IBM Cognos 8 Controller Link
CoCreateInstance(ControllerXLDisp.MsgPusher) failed with 0x80131700

Cause:
A possible cause can be that the file EXCEL.EXE.CONFIG is missing from the folder where EXCEL.EXE is on the client computer.

Solution:
Create a text file in the \program files\microsoft office\office11\ folder
Name the file to be EXCEL.EXE.CONFIG

Inside the file add this text;

<configuration>

<startup>

<supportedRuntime version=”v2.0.50727″/>

</startup>

</configuration>

 

 

Product:
Cognos Controller 8.5

Symptom:
Error message when using the Cognos Controller program

Error:
Model not found in context: job
Unable to find instance of model of type: job, type interface com.cognos.ccr.models.job.JobModel (load=LAST)
exceptionId=ERR.ANY:WEBSERIVCECONNECTIONEXCEPTION.CANNOT_EXECUTE_SERVICE, argument(s)=[http://localhost/cognos8/controllerserver/CCRWS.asmx, 010:608b9fd0-fc2b-11de-9650-d3922c4dc45a:1756974638]
FAIL: Message: ActiveX component can’t create object Source: FrJavaProxyB

Cause:
One possible cause can be that The Visual C++ 2005 package is not installed on the Cognos Controller application server.

Solution:
Install VC++2005 redistributable package on the Cognos Controller application server.
Reinstall Cognos Controller on the server.

Download vcredist_x86.exe from here
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=32bc1bee-a3f9-4c13-9c99-220b62a191ee&displaylang=en

Product:
Cognos BI version 8.4.1

Symptom:
Can not start the Cognos BI service from Cognos Configuration.

Error Message:
09:52:45, ‘AuditDatabaseConnection’, ‘Execute’, ‘Success’.
09:52:45, ‘ContentManager’, ‘getActiveContentManager’, ‘Failure’.
DPR-CMI-4006 Unable to determine the active Content Manager. Will retry periodically.
[ ERROR ] CFG-ERR-0106 IBM Cognos Configuration did not receive a response from the IBM Cognos 8 service in the time allotted.
Check that IBM Cognos 8 service is available and properly configured.

Cause:
A possible cause can be that the port is set to wrong value in Cognos Configuration
Can be when you install two Cognos BI instances on the same server.

Solution:
On Cognos Application server, start Cognos Configuration
Check that port number is correct at:

• the shutdown port number under ‘Cognos 8 Service’
• the 4 port numbers under the “Environment” link (all URI’s except the gateway)
• the portal port number under the ‘Cognos Portal Services’
• the ‘local log server port number’ under the “Environment” and “Logging”.

Change the port numbers to be uniq and not the same as other Cognos installation on same server.

Standard port for Cognos dispatcher is 9300
Standard port for Cognos logging is 9362
Standard port for Cognos shutdown is 9399
Standard port for Cognos Portal is 9300

Standard port for Microsoft SQL is 1433