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.

Product:
Cognos Planning 8.4

Symptom:
Error when doing synchronize with Planning Analyst in Cognos Planning Contributor Administrator Console from a macro.
If you do it manually it works fine.

Message:
{3A9A7B10-F0A6-4A75-8517-6E9967C319BA} 1 2010-05-26 11:03:53.974 UTC +120 MacroUtilities_84 8.4.2721.0 AFWHelper ReportAFWError 140 MacroUtilities_84.AFWHelper.ReportAFWError -2147219667 E1008 Failed to logon to CAM. Logon aborted.. The return code was 1008. PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME None\None None\None 4244 2604
{3A9A7B10-F0A6-4A75-8517-6E9967C319BA} 2 2010-05-26 11:03:53.974 UTC +120 MacroUtilities_84 8.4.2721.0 AFWHelper LoggedOnAFW 150 MacroUtilities_84.AFWHelper.ReportAFWError -2147219667 E1008 Failed to logon to CAM. Logon aborted.. The return code was 1008. PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME 4244 2604
{3A9A7B10-F0A6-4A75-8517-6E9967C319BA} 3 2010-05-26 11:03:53.974 UTC +120 MacroUtilities_84 8.4.2721.0 AFWHelper GetLibraryNames 100 MacroUtilities_84.AFWHelper.ReportAFWError -2147219667 E1008 Failed to logon to CAM. Logon aborted.. The return code was 1008. PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME 4244 2604
{3A9A7B10-F0A6-4A75-8517-6E9967C319BA} 4 2010-05-26 11:03:53.974 UTC +120 EAdminDB_84 8.4.2721.0 iDB AnalystGetLibraryNames 100 MacroUtilities_84.AFWHelper.ReportAFWError -2147219667 E1008 Failed to logon to CAM. Logon aborted.. The return code was 1008. PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME 4244 2604
{3A9A7B10-F0A6-4A75-8517-6E9967C319BA} 5 2010-05-26 11:03:54.005 UTC +120 MacroAControls_84 8.4.2721.0 frmSelectBatchJob SetupForm 160 MacroUtilities_84.AFWHelper.ReportAFWError -2147219667 E1008 Failed to logon to CAM. Logon aborted.. The return code was 1008. PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME 3140 2824
{3A9A7B10-F0A6-4A75-8517-6E9967C319BA} 6 2010-05-26 11:03:54.021 UTC +120 MacroAControls_84 8.4.2721.0 peBatchJob cmdConfigure_Click 120 MacroUtilities_84.AFWHelper.ReportAFWError -2147219667 E1008 Failed to logon to CAM. Logon aborted.. The return code was 1008. PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME 3140 2824

Above message in Planningerrorlog.csv is found when executing the macro.

{EDED3F30-E2F5-4BF4-B943-EA9083F27678} 1 2010-05-26 11:22:37.052 UTC +120 MacroUtilities_84 8.4.2721.0 AFWHelper ReportAFWError 140 MacroUtilities_84.AFWHelper.ReportAFWError -2147219667 E1008 Failed to logon to CAM. Logon aborted.. The return code was 1008. PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME None\None None\None 4244 3968
{EDED3F30-E2F5-4BF4-B943-EA9083F27678} 2 2010-05-26 11:22:37.068 UTC +120 MacroUtilities_84 8.4.2721.0 AFWHelper LoggedOnAFW 150 MacroUtilities_84.AFWHelper.ReportAFWError -2147219667 E1008 Failed to logon to CAM. Logon aborted.. The return code was 1008. PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME 4244 3968
{EDED3F30-E2F5-4BF4-B943-EA9083F27678} 3 2010-05-26 11:22:37.068 UTC +120 MacroUtilities_84 8.4.2721.0 AFWHelper GetLibraryNames 100 MacroUtilities_84.AFWHelper.ReportAFWError -2147219667 E1008 Failed to logon to CAM. Logon aborted.. The return code was 1008. PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME 4244 3968
{EDED3F30-E2F5-4BF4-B943-EA9083F27678} 4 2010-05-26 11:22:37.068 UTC +120 EAdminDB_84 8.4.2721.0 iDB AnalystGetLibraryNames 100 MacroUtilities_84.AFWHelper.ReportAFWError -2147219667 E1008 Failed to logon to CAM. Logon aborted.. The return code was 1008. PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME 4244 3968
{EDED3F30-E2F5-4BF4-B943-EA9083F27678} 5 2010-05-26 11:22:37.099 UTC +120 MacroAControls_84 8.4.2721.0 peLibraryList PopulateListOfLibraries 130 MacroUtilities_84.AFWHelper.ReportAFWError -2147219667 E1008 Failed to logon to CAM. Logon aborted.. The return code was 1008. PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME 3140 2824
{EDED3F30-E2F5-4BF4-B943-EA9083F27678} 6 2010-05-26 11:22:37.099 UTC +120 MacroAControls_84 8.4.2721.0 peLibraryList RenderSimpleParameter 120 MacroUtilities_84.AFWHelper.ReportAFWError -2147219667 E1008 Failed to logon to CAM. Logon aborted.. The return code was 1008. PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME 3140 2824
{EDED3F30-E2F5-4BF4-B943-EA9083F27678} 7 2010-05-26 11:22:37.115 UTC +120 MacroSControls_84 8.4.2721.0 ocxLabelAndBox RenderParameter 160 MacroUtilities_84.AFWHelper.ReportAFWError -2147219667 Unable to set parameter object for ‘ParameterRendererspecifylibraryname’ with ProgID of ‘MacroAControls_84.peLibraryList’~~~~E1008 Failed to logon to CAM. Logon aborted.. The return code was 1008. PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME 3140 2824
{EDED3F30-E2F5-4BF4-B943-EA9083F27678} 8 2010-05-26 11:22:37.115 UTC +120 MacroSControls_84 8.4.2721.0 ocxOptionPE RenderParameter 580 MacroUtilities_84.AFWHelper.ReportAFWError -2147219667 Unable to set parameter object for ‘ParameterRendererspecifylibraryname’ with ProgID of ‘MacroAControls_84.peLibraryList’~~~~E1008 Failed to logon to CAM. Logon aborted.. The return code was 1008. PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME 3140 2824
{EDED3F30-E2F5-4BF4-B943-EA9083F27678} 9 2010-05-26 11:22:37.130 UTC +120 MacroSControls_84 8.4.2721.0 AdvContainer Add 130 MacroUtilities_84.AFWHelper.ReportAFWError -2147219667 Unable to set parameter object for ‘ParameterRendererspecifylibraryname’ with ProgID of ‘MacroAControls_84.peLibraryList’~~~~E1008 Failed to logon to CAM. Logon aborted.. The return code was 1008. PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME 3140 2824
{EDED3F30-E2F5-4BF4-B943-EA9083F27678} 10 2010-05-26 11:22:37.130 UTC +120 EAdminUI_84 8.4.2721.0 ocxParameters RenderParameters 420 MacroUtilities_84.AFWHelper.ReportAFWError -2147219667 Unable to render parameter ‘libraryname’~~~~Unable to set parameter object for ‘ParameterRendererspecifylibraryname’ with ProgID of ‘MacroAControls_84.peLibraryList’~~~~E1008 Failed to logon to CAM. Logon aborted.. The return code was 1008. PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME 3140 2824
{EDED3F30-E2F5-4BF4-B943-EA9083F27678} 11 2010-05-26 11:22:37.146 UTC +120 EAdminUI_84 8.4.2721.0 frmMacroStepEditor RenderMacroStepScript 230 MacroUtilities_84.AFWHelper.ReportAFWError -2147219667 Unable to render parameter ‘libraryname’~~~~Unable to set parameter object for ‘ParameterRendererspecifylibraryname’ with ProgID of ‘MacroAControls_84.peLibraryList’~~~~E1008 Failed to logon to CAM. Logon aborted.. The return code was 1008. PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME 3140 2824
{4155F309-465C-4A51-A725-018AFE311328} 1 2010-05-26 11:22:37.146 UTC +120 EAdminUI_84 8.4.2721.0 pgMacros CreateNewMacroStep 320 0 Unable to create new macro step.~~~~ PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME None\None None\None 3140 2824
{4155F309-465C-4A51-A725-018AFE311328} 2 2010-05-26 11:22:37.146 UTC +120 EAdminUI_84 8.4.2721.0 pgMacros cmdMacroStepAdd_Click 150 5 Unable to create new macro step.~~~~ PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME PLANNINGSERVERNAME\UserName CD\PLANNINGSERVERNAME 3140 2824

Above error is found in planningerrorlog.csv when try to create a macro that access analyst files.

Cause:
The Cognos 8 Planning service is run as local system on the Windows server
Or the filesys.ini file is not using UNC path to the applications.

Solution:
Check the filesys.ini file on the Cognos planning servers, ensure that they use UNC path to the Cognos planning applications. You may need to register the planning applications again in Cognos Planning Analyst with UNC path to get this to work correctly.

Create a windows domain account that is used for the Cognos services.
The windows account must be local administrator on all Cognos servers in the solution.

Stop the Cognos 8 Planning service
Stop the Cognos 8 Bi service
Change the user from local system to the created windows service account.
Enter the password and click apply.
Start the Cognos 8 Bi service
Start the Cognos 8 Planning service

Start CAC (contributor administration console) and test again your macro.

Symptom
Schedule a Planning job to run but it stays pending.
Problem
Schedule a Planning Job to run a macro. The job stays in pending status. The macro by itself can be set to run later. This occurs mostly in a multi server environment.
Cause
Monitor service is set to False
Solution
Change the monitor service to true on the Application server and Web Server, restart services.