Product:
Cognos Planning 10.1.1
Windows 2008 R2 server
Oracle database

Problem:
You can not create new Cognos Planning Applications from Cognos Administration Consolde (CAC) and get an error about the password.

{1F3E2C63-11E3-4091-917B-537CFAF5D155} 7 2014-08-18 18:49:20.449 UTC +120 EAdminUI_10 10.1.4074.0 MTSEAdminDB MTSCreateAndPopulateApplication 140 Oracle Automation 440 Unable to execute statement. 28003 ORA-28003: password verification for the specified password failed~ORA-20009: Password must contain at least one digit, one character~~~~~The SQL was:~~CREATE USER go_expenses_contributor IDENTIFIED BY PASSWORD DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP QUOTA UNLIMITED ON USERS QUOTA UNLIMITED ON USERS QUOTA UNLIMITED ON USERS~~~~The Connect String was:~~Provider=OraOLEDB.Oracle;Data Source=servername.COM;User ID=PLANADM;Password=*********;~~~~SQL execution error, ORA-28003: password verification for the specified password failed~ORA-20009: Password must contain at least one digit, one character~

The issue is that the Oracle Database DBA have applied a strong password policy.
Possible Solution:
Change the default password used by Cognos Planning during creation of the Planning application schema.
Go to the Cognos Planning Admin server. Open the file C:\Program Files (x86)\ibm\cognos\c10\bin\ epEAdminORA8Resources.xml in notepad.
Change the row <![CDATA[CREATE USER %1 IDENTIFIED BY PASSWORD
DEFAULT TABLESPACE %4
TEMPORARY TABLESPACE %5
To a new row with a new password that contain a combination of a-z and numbers (0-9)
<![CDATA[CREATE USER %1 IDENTIFIED BY donaldduck747

Save the file. The new default password is now donaldduck747.
Log in to CAC again and test again.

Product:
Cognos Planning 10.1.1
Windows 2008 R2 server
Oracle database

Problem:
You get an error message when you try to add an existing application to the Planning store from inside Cognos Planning Administrator Console.
And the Cognos 10 Planning service is shut down on the Planning Admin Server. You need to restart the Windows Cognos 10 Planning service to continue to work in CAC.
Error message:
An error occurred during the in-place upgrade of your Cognos Planning Application.
Please see the Cognos Planning error log for details on the error.
In the Planningerrorlog.csv file (on the Cognos planning server) you will find;
{B581E2FC-7A35-439C-87D4-FE9AD820842D} 2 2014-08-18 10:44:27.256 UTC +120 AppModelAdmin_10 10.1.4074.0 Admin ApplicationStateWriteDevelopmentDefinitionUsingConnection 240 Microsoft Cursor Engine -2147217864 Unable to update the recordset with SQL of: SELECT definition, definitiondt, appstateguid ~~FROM PSC_ADMIN.applicationstate ~~WHERE appstateguid='{520980BF-780D-46E3-9542-AA695B383343}’~~~~The BLOB with 30418 characters was being written to field ‘PSC_ADMIN.applicationstate.definition’.~~~~Row cannot be located for updating. Some values may have been changed since it was last read.
Other errors you can get as a follow up error are;
{04E4AF77-106D-4829-9129-6C9E4FE34EB7} 1 2014-08-19 08:45:17.655 UTC +120 epsTransport 10.1.4074.0 default OSStub.cpp invokeRemoteMethod 180 epsTransport::default::OSStub.cpp::invokeRemoteMethod::180 -2147467259 general exception in try block
{8BD66C73-3272-4073-A8F5-AA5953A4EB70} 5 2014-08-18 19:32:21.256 UTC +120 UpgradeEng_10 10.1.4074.0 Upgrader InPlaceApplicationUpgrade 110 DebugTools_10 -2147417848 Unable to collect error information from underlying component
{459D64CA-9D0D-46F7-846F-E89B5C9AA5C4} 2 2014-08-19 08:37:55.472 UTC +120 ModelHelper_10 10.1.4074.0 Helper UnPackModel 190 ACE2_10.Model -2147352567 Unable to set the EnvironmentID on the Model, this may be because the J Server is not registered.~~~~Unknown error
Possible solution:
The Oracle driver is not correct installed on the Cognos Planning server.
It can be missing components, like Oracle Data Access Components, in the Oracle client install.
Stop the Cognos Planning and Cognos BI services.
Uninstall the Oracle driver, and manually install a new Oracle driver.
Open Cognos Configuration, save and start the Cognos services again.
Test if you can link to existing application again.
In some cases you may need to erase the fields for the PAD connection inside the Cognos planning application database before you can attach the Application to the pad again.
Open Oracle SQL Developer, log in as a super user account for Cognos Planning, and expand you planning application schema ( for example GO_CAPEX_CONTRIBUTOR).
Open the tables and open the data for ADMINOPTION table.
Clear the optionvalue for PAD_NAME, PAD_GUID and PAD_NAMESPACE.
Commit and exit SQL developer.
Run the test again in Contributor Administration Console (CAC).

Product:

Cognos Planning 10.1.1

Windows 2008 R2 Server

Oracle Database

 

Symptom:

Have setup new servers, and try to from inside Cognos Planning Contributor Administration Console (CAC) add new JOB SERVERS to your job server cluster, you get a error.

 

Error message:

Errors occurred while trying to communicate with each of the following

servers:   xxxxx

 

Communication failure could result from:

-The server is not running

-Planning is not installed on the server

-The servers firewall is blocking requests

xxxxx

 

Error in planningerrorlog files:

{4904905A-9BAF-4B99-B054-E41891C9E36C} 2 2014-05-08 19:33:44.433 UTC +120 EAdminDB_10 10.1.4074.0 JobServer GetEnabledAndNameLocal 100 Factory_10 70 Unable to create the object with ProgID ‘epPlanningService_10.JobExecManager’ (request was for ‘epPlanningService_%v.JobExecManager’)~~~~Permission denied domain\serviceaccount domain\servername domain\serviceaccount domain\servername  1744 5020

 

Error in windows event log:

Log Name: System

Source: Microsoft-Windows-DistributedCOM

Date: 5/8/2014 6:46:16 PM

Event ID: 10016

Task Category: None

Level: Error

Keywords: Classic

User: domain\serviceaccount

Computer: servername

Description:

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID

{7B59D7CC-3FD8-41A4-9F2A-40D2D6B5590A}

and APPID

{324E655C-61EF-4500-85D1-2791358B531E}

to the user domain\serviceaccount SID (S-1-5-21-3598516276-3377520961-430964465-92766) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Event Xml:

<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>;

<System>

<Provider Name=”Microsoft-Windows-DistributedCOM” Guid=”{1B562E86-B7AA-4131-BADC-B6F3A001407E}” EventSourceName=”DCOM” />

<EventID Qualifiers=”49152″>10016</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime=”2014-05-08T16:46:16.000000000Z” />

<EventRecordID>14320</EventRecordID>

<Correlation />

<Execution ProcessID=”0″ ThreadID=”0″ />

<Channel>System</Channel>

<Computer>servername</Computer>

<Security UserID=”S-1-5-21-3598516276-3377520961-430964465-92766″ />

</System>

<EventData>

<Data Name=”param1″>machine-default</Data>

<Data Name=”param2″>Local</Data>

<Data Name=”param3″>Activation</Data>

<Data Name=”param4″>{7B59D7CC-3FD8-41A4-9F2A-40D2D6B5590A}</Data>

<Data Name=”param5″>{324E655C-61EF-4500-85D1-2791358B531E}</Data>

<Data Name=”param6″>domain</Data>

<Data Name=”param7″>serviceaccount</Data>

<Data Name=”param8″>S-1-5-21-3598516276-3377520961-430964465-92766</Data>

<Data Name=”param9″>LocalHost (Using LRPC)</Data>

</EventData>

</Event>

Solution:

The service account set to run the IBM Cognos Planning service on the Microsoft Windows 2008 Server is not set to be local admin on the server.

Go to Manage – Configuration – Local user and groups – Groups

Click on Administrators

Click ADD to add the windows service account to this group on your Planning server.

Save and restart the Cognos Planning servers.

Then you can test again.

 

You can also test this with change back to local system to run the Cognos Planning service, if it works then to add as job server then it is the rights for the windows service account that is the case.

Product:
Cognos Planning 10.1.1 fix pack 3
Windows 2008 R2 server
Oracle Database

Problem:
There is a difference in time to do import of deployment packages in the Cognos Planning PROD and DEV environments. In Production it takes 1 minute, in Development servers it take 40 minutes.
On the Cognos Planning server there is little use of CPU or Memory, also on the Oracle server there is little use of CPU and Memory. It looks like it is waiting.
The time between the step “Creating…” and “Created…” in CAC Monitor Console Deployments is the one that take time because of this.
Because:
In the file SQLNET.ORA the search order is defined to access the Oracle database.
If there are firewalls between the DEV servers and the PROD DNS/LDAP servers, then this can happen if the LDAP is first in the list. The Oracle client need to time out before it will look into the TNSNAMES file on the server to find the Oracle database.

Solution:
Open the file C:\orarun\tnsadmin\sqlnet.ora on the Cognos servers
And change
NAMES.DIRECTORY_PATH= (LDAP, TNSNAMES, EZCONNECT, HOSTNAME)
To
NAMES.DIRECTORY_PATH= ( TNSNAMES, EZCONNECT, HOSTNAME)
Save the file.
Test to use the deployment import again in Cognos Planning.
Then it should be faster.

Product:
IBM Cognos Planning 10.1.1
Microsoft Windows 2008 R2 Server

Problem:
How change the TEMP variable for a service account, without logging in as the user on the Windows Server?

Solution:
Create the service account in the Domain.
Ensure the service account is part of the local administration group on the planning server.
Go to the Administration tools – services.
(you can start it by type services.msc in Run dialog)
Double Click on your IBM Cognos 10 Planning service and select Log On tab.
Select this account and browse to your service account, in our example named cogplan.
Enter Password and click OK to save the change.
Click OK on message that the account have been added to “log on as a service” function.
Right Click on the service IBM Cognos 10 Planning and select RESTART.
Ensure that Cognos planning service have started.

The planningerrorlog.csv file is created in folder \users\cogplan\appdata\local\temp

Start REGEDIT
Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
Check the last number in list – it is possible your service account.
You should see it on the ProfileImagePath value who would be : C:\Users\cogplan
Note the number if the user down
Go to HKEY_USERS\S-1-5-21-2298123480-4089459362-31738xxxxx-1001\Environment
(the number should be the number of the user you found under ProfileList.)
Double click on TEMP to change the value from
%USERPROFILE%\APPDATA\LOCAL\TEMP
to
D:\TEMP
Click OK
Repeat the change for TMP
Close REGEDIT

Restart the Cognos Planning service.

Now the log file is in the D:\TEMP folder.

Product:
Cognos Planning 10.1.1. Fix pack 3 (version 10.1.6303.19-0)
Windows 2008 R2 Server
Oracle database

Symptom:
When you start Cognos Planning Administration Console on a client you get a error message.
When opening the CAC the following error occurs:
“An error has occurred while starting IBM Cognos Planning Administrator.
Main form failed to initialize.
Error Details:
Unable to determine if the Planning Tables exist in Content Manager. Please ensure the Planning Service is running.”

Unexpected: missing HRESULT parameter”

When opening Analyst the following error occurs:
“Analyst failed to communicate with the Content Manager database. This can happen if the Cognos 10 Planning service is not running. Please check that the service is running.”

Error was:

DISP_E_EXCEPTION
Failed HRESULT [0x80020009] Exception occurred.”
Cause:
The gateway url in Cognos Configuration is not the same as the gateway url on the Cognos BI server for authentication.

Solution:
Log on to the Cognos Planning BI server.
Start Cognos Configuration.
Copy the value for Gateway URI under environment section.
Go to the client computer where you have CAC and Cognos Planning Analyst installed.
Start Cognos Configuration
Paste the value for Gateway URI under Gateway settings.
Click on Save
Exit Cognos Configuration
Try to start the IBM Cognos Planning – Contributor Administrator Console.

Can also be other causes;
http://www-01.ibm.com/support/docview.wss?uid=swg21621002

Product:
Cognos Planning 10.1.1
Windows 2008 R2 server
Oracle database

Symptom:
When doing a GTP you get the PREPARE_ACCESS_BLOCKS to say QUEUING all the time. Why ?

Cause:
The Cognos Planning solution is setup with one JOB server and one ADMIN server.
The PREPARE ACCESS BLOCKS step is a change in the Cognos Planning application that is done from the job server. The other steps of a GTP is update of the Cognos Planning store database, that is accessed with the settings defined in Cognos Configuration. So Cognos Planning use different parts to access the databases.

Solution:
For access to oracle database to work you need to have a correct TNSNAMES.ORA file in your \oracle\client\network\admin folder on your Planning servers.

In this case the issue was solved by adding the tnsnames.ora file to the job server, there it was missing, the tnsnames.ora file was on the ADMIN server only, therefor some GTP task worked, that does not need a tnsnames.ora file.

Access defined in Cognos Configuration can be setup for oracle to direct define and access the server.

Product:
Cognos Planning 10.1.1
(PLANSRVR_version=PLANSRVR-AW32-ML-RTM-10.1.6235.51-0)
C8BISRVR-AW32-ML-RTM-10.1.6304.10-0 = IBM Cognos Business Intelligence Server Update, PLANSRVR-AW32-ML-RTM-10.1.6303.19-0 = Planning Server Update
Windows 2008 R2 server
Oracle Database

Symptom:
Error when you try to Start Cognos Planning service.

Error message in Planningerrorlog.csv file:
E6525D43-48B1-4123-8C99-7BFA5DFA2515} 14 2014-04-09 16:57:09.832 UTC +120 epPlanningService 10.1.4074.0 default ThreadSystemConnectionPool.cpp RefreshConnectionPool 260 OraOLEDB -2147467259 Unable to open connection using connection string of Provider=OraOLEDB.Oracle;Data Source=server.DOMAIN.COM;User ID=SERVICEACCOUNT;Password=*********; and timeout of 15 seconds.~~~~ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA DOMAIN\UserAccount DOMAIN\SERVER DOMAIN\UserAccount DOMAIN\SERVER 3408 4968
{E6525D43-48B1-4123-8C99-7BFA5DFA2515} 15 2014-04-09 16:57:09.847 UTC +120 epPlanningService 10.1.4074.0 default ThreadSystemConnectionPool.cpp Run 138 OraOLEDB -2147467259 Unable to open connection using connection string of Provider=OraOLEDB.Oracle;Data Source=server.DOMAIN.COM;User ID=SERVICEACCOUNT;Password=*********; and timeout of 15 seconds.~~~~ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA DOMAIN\UserAccount DOMAIN\SERVER DOMAIN\UserAccount DOMAIN\SERVER 3408 4968

Possible Cause:
This can happen when you restart the Cognos Planning service, from Cognos configuration or direct from windows services.

And the planning store settings inside Cognos configuration for oracle is set to advance and you use this syntax;
databasehostname.domain.COM:1521/oracleserverid.domain.COM

instead of this syntax;
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=databaseserver.domain.COM)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=oraclename.domain.COM)))

Redo the access syntax in Cognos Configuration and try to start Cognos again.
Both syntax of access to Oracle work for Cognos Content Store, but not for Cognos Planning Store.

Product:
Cognos Planning 10.1.1
(PLANSRVR_version=PLANSRVR-AW32-ML-RTM-10.1.6235.51-0)
C8BISRVR-AW32-ML-RTM-10.1.6304.10-0 = IBM Cognos Business Intelligence Server Update, PLANSRVR-AW32-ML-RTM-10.1.6303.19-0 = Planning Server Update
Windows 2008 R2 server
Oracle Database

Symptom:
Error when you try to Start Cognos Planning service.

Error msg:
02E05353-AF07-4C9D-B859-9CF2760616A4} 17 2014-04-09 17:35:09.522 UTC +120 epPlanningService 10.1.4074.0 default ThreadSystemConnectionPool.cpp ThreadProc 104 OraOLEDB -2147467259 Process exception DOMAIN\SERVICEACCOUNTNAME DOMAIN\SERVERNAME DOMAIN\SERVICEACCOUNTNAME DOMAIN\SERVERNAME 3880 1312
{481087D0-09B5-48E0-A685-A28D2E363A44} 1 2014-04-09 17:39:23.194 UTC +120 epPlanningService 10.1.4074.0 default Poller.cpp ManageErrorLogging 345 epPlanningService::default::Poller.cpp::ManageErrorLogging::345 0 Database Errors: Source: OraOLEDB Description: ORA-00942: table or view does not exist Number: -2147467259 SQLState: NativeError: 942 Source: OraOLEDB Description: ORA-00942: table or view does not exist Number: -2147217865 SQLState: NativeError: 942 DOMAIN\SERVICEACCOUNTNAME DOMAIN\SERVERNAME None\None None\None 3456 368
{B16556CC-68A9-40E0-92BA-4CF7C75D61B6} 1 2014-04-09 17:39:25.034 UTC +120 epPlanningService 10.1.4074.0 default Poller.cpp ManageErrorLogging 345 epPlanningService::default::Poller.cpp::ManageErrorLogging::345 0 Database Errors: Source: OraOLEDB Description: ORA-00942: table or view does not exist Number: -2147467259 SQLState: NativeError: 942 Source: OraOLEDB Description: ORA-00942: table or view does not exist Number: -2147217865 SQLState: NativeError: 942 DOMAIN\SERVICEACCOUNTNAME DOMAIN\SERVERNAME None\None None\None 3456 3872

Possible Cause:
The database is new and you have only installed Cognos planning and started the services.
You have not run the Cognos planning contributor admin console, to create the Cognos planning store with all its tables.

During startup in Cognos Configuration, the Cognos Planning service checks for tables in the planning store database.

Product:
IBM Cognos Planning 10.1.1
Microsoft Windows 2008 R2 server

Problem:
Macro does not run, no error messages, but if you do a GTP manually it works.
You have several Cognos Planning servers, where some are dedicated Cognos Planning Job servers.

Solution:
Ensure that all Cognos Planning servers are added to the Cognos Planning JOB cluster in Cognos Contributor Administration Console (CAC). Not only the dedicated Job servers should be in the cluster, add also the Cognos Planning Admin servers. Set the number of Maximum of Concurrent job to 0 (zero) on the Cognos planning servers.
For Cognos Planning Job servers the number of maximum concurrent jobs should be one less than the number of cpu cores on the Cognos planning server. On a 4 cpu core server the value should be 3.
Start CAC
Login as administrator
Right click on cluster icon for Job Server and select Add Job Server.
From the dropdown list you should see all the Cognos Planning servers you can choose.
(All in list need to be added). But servers that are not JOB servers should have value 0 for maximum concurrent jobs.
Also add all the applications, by click on the ADD button under Monitored objects, on the Job server cluster level in CAC.
After you added all the job servers, you can test to run the macros again.
More Information:
Please note that for Cognos Planning 10.1.1 to work you should install both Cognos BI 10.1.1 and Cognos Planning 10.1.1 to the same folder. Then you do not need to enter a value in the Cognos Configuration for IBM Cognos BI installation location.
This versions will work together (there are other version that will also work)
tl-BISRVR-10.1-6235.144-
tl-PLANSRVR-10.1-6235.51-
tl-UPDATE_BISRVR-10.1-6304.10-
tl-UPDATE_PLANNING-10.1-6303.19-
(Above versions number from folder C:\Program Files (x86)\ibm\cognos\c10\instlog)
On the Cognos Planning Admin server only the QUERY Service enabled? is set to FALSE in the Cognos Configuration under Environment for IBM Cognos Service.
On the Cognos Planning Job servers only the Dispatcher Service enabled? and Planning Job Service enabled? is set to TRUE in the Cognos Configuration under Environment for IBM Cognos Service. The rest is set to FALSE.
There are other possibilities of configuration that will work for Cognos Planning.
http://www-01.ibm.com/support/docview.wss?uid=swg21507327
http://www-01.ibm.com/support/docview.wss?uid=swg21597536