Symptom
Planningerrorlog.csv shows error message

 There was a problem running the Deployment Wizard.~~Caused by:
 java.util.NoSuchElementException: null~~~at
 java.util.TreeMap.key(TreeMap.java:448)~~~at
 java.util.TreeMap.firstKey(TreeMap.java:302)~~~at
 com.cognos.ep.dtp.exporting.ExportObjectSelectionPane.populateExportTree(line 263)~~~at
 com.cognos.ep.dtp.PlanningTransferWizard.showExportWizardPane(line 1863)~~~at
 com.cognos.ep.dtp.PlanningTransferWizard.runPlanningExportWizard(line 1480)~~~at
 com.cognos.ep.dtp.PlanningTransferWizard.showWizardPage(line 1340)~~~at
 com.cognos.ep.dtp.PlanningTransferWizard.access$900(line 84)~~~at
 com.cognos.ep.dtp.PlanningTransferWizard$5.widgetSelected(line 460)~~~at
 org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)~~~at
 org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)~~~at
 org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)~~~at
 org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)~~~at
 org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)~~~at
 com.cognos.ep.dtp.PlanningTransferWizard.showGUI(line 293)~~~at
 com.cognos.ep.dtp.PlanningTransferWizard.main(line 256)~~

The true problem is in the export screen. You will see Export object select and then what would you like to export. The problem of the export is just underneath it, whether it's the admin link or macro that could be causing the problem.

Problem
When attempting to create a new deployment it fails with the following message:

"There was a problem running the Deployment Wizard null"

Cause
Either there are two applications with the same name or two macros with the same name in the Cognos Administration Console.

Solution
Remove or rename one of the macros/applications or delete the admin link in question.

www.cogknowhow.com

Product:
Cognos Planning 8.4.1 rich client

Symptom:
Can not move tabs in Cognos Contributor web 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 <application>/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 <install location>\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.

www.cogknowhow.com

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.

www.cogknowhow.com

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.

www.cogknowhow.com

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 server machine.

www.cogknowhow.com

Problem

How to publish the Contributor Macro to Cognos Connection

Solution
Steps:

1) In Contributor Admin Console (CAC), check the box "Publish to Cognos Connection" when creating the Macro. If the box was not checked when creating the Macro, edit the Macro and check the box and then click"OK". This causes the Macro to be accessible in Cognos Connection.

2) Open Cognos Connection as planning administrator or system administrator, select 'Tools'-> Content Administration.

3) Click the 'Planning' folder and then the 'Macros' folder and you shall see the Macro that was published from CAC

4) Click the Schedule Icon and you will be able to set the schedule of running this Macro.

www.cogknowhow.com

Symptom:
During creation of a full deployment the following error pops up. "Widget is disposed". All check boxes are checked (ie. planningstore, macros, applications and analyst libraries)

Problem:
There was a problem running the Deployment Wizard.

~~Caused by: com.cognos.ep.planningnetworkindex.exceptions.SerializationException: org.eclipse.swt.SWTException: Widget is disposed
~~~at com.cognos.ep.dtp.PlanningTransferWizard.createExportRequest(line 802)
~~~at com.cognos.ep.dtp.PlanningTransferWizard.kickOffExport(line 581)
~~~at com.cognos.ep.dtp.PlanningTransferWizard.completeProcess(line 508)
~~~at com.cognos.ep.dtp.PlanningTransferWizard.access$1100(line 84
)~~~at com.cognos.ep.dtp.PlanningTransferWizard$7.widgetSelected(line 484)~~~at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)~~~at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)~~~at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)~~~at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)~~~at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)~~~at com.cognos.ep.dtp.PlanningTransferWizard.showGUI(line 293)~~~at com.cognos.ep.dtp.PlanningTransferWizard.main(line 256)~~Caused by: org.eclipse.swt.SWTException: Widget is disposed~~~at org.eclipse.swt.SWT.error(SWT.java:2942)~~~at org.eclipse.swt.SWT.error(SWT.java:2865)~~~at org.eclipse.swt.SWT.error(SWT.java:2836)~~~at org.eclipse.swt.widgets.Widget.error(Widget.java:395)~~~at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:297)~~~at org.eclipse.swt.widgets.Widget.getData(Widget.java:448)~~~at com.cognos.ep.dtp.common.RequestInformation.addSelectedItemsToExportIndex(line 99)~~~at com.cognos.ep.dtp.PlanningTransferWizard.createExportRequest(line 783)~~~at com.cognos.ep.dtp.PlanningTransferWizard.kickOffExport(line 581)~~~at com.cognos.ep.dtp.PlanningTransferWizard.completeProcess(line 508)~~~at com.cognos.ep.dtp.PlanningTransferWizard.access$1100(line 84)~~~at com.cognos.ep.dtp.PlanningTransferWizard$7.widgetSelected(line 484)~~~at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)~~~at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)~~~at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)~~~at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)~~~at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)~~~at com.cognos.ep.dtp.PlanningTransferWizard.showGUI(line 293)~~~at com.cognos.ep.dtp.PlanningTransferWizard.main(line 256)~~

Cause:
Analyst share is missing analyst model data for a particluar application

Solution:
Run the deployment without the Analyst libraries checked or exclude the missing Analyst model in the deployment

or

Make sure that all the Analyst models are available in the Planning Analyst share and run the deployment again

www.cogknowhow.com

Symptom:
Error message "Can not browse sql servers SQLDMO.application is missing" is displayed when restoring deplyment,

Problem:
Error when trying to restore a Planning deployment in Contributor Admin Console (CAC), because it is not possible to browse to the folder on the SQL server for the mdf and ldf files.

Environment:
IBM Cognos Planning 8.4.1
SQLserver 2008

Cause:
DMO support is there but not installed by default in SQL Server 2008 (except for SQL Server Express where it's removed entirely). The files to install DMO support are on the SQL Server install DVD. But it doesn't install via the main installer. You must find the SQLServer2005_BC.MSI file and install it manually..

Solution:
Take the following steps:

1. Look for SQLServer2005_BC.msi which is typically found in a path such as Z:\x86\Setup\x86 (presuming your dvd drive is Z:)

http://www.microsoft.com/downloads/details.aspx?FamilyId=C6C3E9EF-BA29-4A43-8D69-A2BED18FE73C&displaylang=en

2. Updates required for Microsoft SQL server connection string

You need to update the epEAdminSQL7Resources.xml file to accommodate the name of the native client driver that is used in Microsoft SQL Server 2008. This update is required to start the planning service. You must update the epEAdminSQL7Resources.xml file on each machine that has the IBM Cognos 8 Planning server installed.

You can update the epEAdminSQL7Resources.xml file immediately after installing the planning server, prior to opening IBM Cognos Configuration.
Please change from this original Resource ID value:

<Resource ID="DefaultProviderDriverString" Context="Customization" Hint="The default string used in the ADO connection string that is generated for a new Application.">
<![CDATA[SQLOLEDB or SQLNCLI] ]> </Resource>

To this new Resource ID value:

<Resource ID="DefaultProviderDriverString" Context="Customization" Hint="The default string used in the ADO connection string that is generated for a new Application.">
<![CDATA[SQLNCLI10] ]> </Resource>

3. Install the Microsoft SQL Server 2005 Backward Compatibility Components as well.
4. Restart Cognos Planning service and open CAC to test again.

www.cogknowhow.com

Symptom
When trying to create a new Cognos Planning 8.4.1 application, an error comes up when trying to generate scripts for an planning application

Problem
During the creation of a new application, the following error occurs "The db specified is in use by another system"

Environment
Oracle 10G, Windows 2003, Cognos Planning 8.4.1

Cause
The schema user created by the planning application during the application creation already exist, due to insufficient permissions of the oracle planning user.

Solution
1. check the permissions of the planning store Oracle user. These permissions are required.
- CREATE SESSION, USER
- CREATE ANY INDEX
- CREATE ANY SEQUENCE
- CREATE ANY SYNONYM
- CREATE ANY TABLE
- CREATE ANY TRIGGER
- CREATE ANY  VIEW
- DELETE ANY TABLE
- INSERT ANY TABLE
- UPDATE ANY TABLE
- SELECT ANY TABLE
- DROP ANY VIEW, TABLE
- DROP USER
- EXP_FULL_DATABASE

Table spaces “USERS” and“TEMP should be accessable for the schema_user

2. Drop the Oracle schema user and create the same planning application again
 

www.cogknowhow.com

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. he windows account must be local administrator on all Cognos servers in the solution.

Steps
1. Stop the Cognos 8 Planning service
2. Stop the Cognos 8 Bi service
3. Change the user from local system to the created windows service account.
4. Enter the password and click apply.
5. Start the Cognos 8 Bi service
6. Start the Cognos 8 Planning service
7. Start CAC (Contributor Administration Console) and test again your macro.

www.cogknowhow.com