by ·0 Comments

Product:

Cognos Contoller 10.1.1

Windows 2008 R2 Server

Oracle 11g

Symptom:

New installation of Cognos controller 10, to be used with Oracle database.

When click connect in Cognos Controller DBCONV program you get a error message.

Error message:

** ERROR: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 50

** ERROR: java.sql.SQLRecoverableException: IO-Fel: could not resolve the connect identifier

 

Solution:

Change the tnsnames.ora file for the oracle client on the Cognos Controller server.

Ensure the tnsnames.ora file only contain the values for the cognos controller database, not reference to other oracle schema or databases.

Ensure the information is written in several lines, as shown below, and not in a single line in the tnsnames.ora file.

FRANGO=  (DESCRIPTION=    (ADDRESS=(PROTOCOL=TCP)(HOST= SERVERNAME.DOMAIN.COM)(PORT=1521) )   (CONNECT_DATA= (SERVICE_NAME=service_name)))

Replace italic above with the schema/oracle server name.

 

More information

http://pic.dhe.ibm.com/infocenter/cfpm/v10r1m0/index.jsp?topic=%2Fcom.ibm.swg.im.cognos.ctrl_inst.10.1.0.doc%2Fctrl_inst_id311UpdatedinstallationinstructionsforCreateanIBMCogno.html

http://docs.oracle.com/cd/B28359_01/network.111/b28317/tnsnames.htm

by ·Comments Off on Could not create the view: !Could not create controller of type

Product:

Cognos Controller 10.1.1

Windows 2008 R2 Server

Oracle database

Symptom:

New installation of Cognos Controller 10.1.1. When user select maintain – jobs – define menu, they get a error message after some time.

Problem message:

Could not create the view: !Could not create controller of type com.ibm.cognos.ccr.integration.internal.job.ui.JobDialogDefinitionViewController for composite class com.ibm.cognos.ccr.integration.internal.job.ui.JobDialogDefinitionUI!

java.lang.reflect.InvocationTargetException

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:44)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:516)

at com.ibm.cognos.ccr.core.ui.databinding.widgets.AbstractControllableComposite.createController(AbstractControllableComposite.java:67)

at com.ibm.cognos.ccr.core.ui.databinding.widgets.AbstractControllableComposite.getController(AbstractControllableComposite.java:58)

at com.ibm.cognos.ccr.core.ui.view.AbstractViewPart.initializeController(AbstractViewPart.java:547)

at com.ibm.cognos.ccr.core.ui.view.AbstractViewPart.initializeController(AbstractViewPart.java:490)

at com.ibm.cognos.ccr.integration.internal.job.ui.JobDialogDefinitionView.createPartControl(JobDialogDefinitionView.java:55)

at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:375)

at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:229)

at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)

at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:313)

at org.eclipse.ui.internal.ViewPane.setVisible(ViewPane.java:534)

at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180)

at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270)

at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)

at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473)

at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1245)

at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1198)

at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1597)

at org.eclipse.ui.internal.PartStack.createControl(PartStack.java:643)

at org.eclipse.ui.internal.PartStack.createControl(PartStack.java:570)

at org.eclipse.ui.internal.PartSashContainer.createControl(PartSashContainer.java:568)

at org.eclipse.ui.internal.PerspectiveHelper.activate(PerspectiveHelper.java:272)

at org.eclipse.ui.internal.Perspective.onActivate(Perspective.java:981)

at org.eclipse.ui.internal.WorkbenchPage.onActivate(WorkbenchPage.java:2714)

at org.eclipse.ui.internal.WorkbenchWindow$27.run(WorkbenchWindow.java:3023)

at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)

at org.eclipse.ui.internal.WorkbenchWindow.setActivePage(WorkbenchWindow.java:3004)

at org.eclipse.ui.internal.WorkbenchWindow.busyOpenPage(WorkbenchWindow.java:799)

at org.eclipse.ui.internal.Workbench$23.runWithException(Workbench.java:1224)

at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)

at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:180)

at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150)

at org.eclipse.swt.widgets.Display.syncExec(Display.java:4683)

at org.eclipse.ui.internal.StartupThreading.runWithWorkbenchExceptions(StartupThreading.java:50)

at org.eclipse.ui.internal.Workbench.busyOpenWorkbenchWindow(Workbench.java:1220)

at org.eclipse.ui.internal.Workbench.access$31(Workbench.java:1196)

at org.eclipse.ui.internal.Workbench$58.run(Workbench.java:2215)

at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)

at org.eclipse.ui.internal.Workbench.openWorkbenchWindow(Workbench.java:2212)

at com.ibm.cognos.ccr.core.ui.util.WorkbenchUtil.openPerspective(WorkbenchUtil.java:685)

at com.ibm.cognos.ccr.integration.application.internal.IntegrationServiceImpl$MyPerspectiveOpener.openNewPerspective(IntegrationServiceImpl.java:136)

at com.ibm.cognos.ccr.integration.application.internal.IntegrationServiceImpl$MyPerspectiveOpener.run(IntegrationServiceImpl.java:112)

at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)

at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)

at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757)

at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)

at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)

at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)

at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)

at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)

at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)

at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)

at com.ibm.cognos.ccr.integration.application.internal.IntegrationApplication.start(IntegrationApplication.java:85)

at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)

at com.ibm.cognos.ccr.integration.IntegrationServiceAdapter$MyEclipseStarter.run(IntegrationServiceAdapter.java:144)

at java.lang.Thread.run(Thread.java:736)

Caused by: com.ibm.cognos.ccr.common.InvalidContextException: !Could not load model: job!

at com.ibm.cognos.ccr.integration.application.AbstractLifeCycleManager.getModel(AbstractLifeCycleManager.java:235)

at com.ibm.cognos.ccr.integration.application.AbstractLifeCycleManager.<init>(AbstractLifeCycleManager.java:100)

at com.ibm.cognos.ccr.integration.application.AbstractLifeCycleManager.<init>(AbstractLifeCycleManager.java:89)

at com.ibm.cognos.ccr.integration.application.ValidatingLifeCycleManager.<init>(ValidatingLifeCycleManager.java:47)

at com.ibm.cognos.ccr.integration.application.views.AbstractDialogController.<init>(AbstractDialogController.java:91)

at com.ibm.cognos.ccr.integration.internal.job.ui.JobDialogDefinitionViewController.<init>(JobDialogDefinitionViewController.java:39)

… 63 more

Caused by: com.ibm.cognos.ccr.common.NoSuchModelException: !Unable to find instance of model of type: job[JobModel]!

at com.ibm.cognos.ccr.common.DefaultModelContext.throwNewNoSuchModelException(DefaultModelContext.java:422)

at com.ibm.cognos.ccr.common.DefaultModelContext.getModelByIdentifier(DefaultModelContext.java:396)

at com.ibm.cognos.ccr.common.DefaultModelContext.getModel(DefaultModelContext.java:255)

at com.ibm.cognos.ccr.integration.application.AbstractLifeCycleManager.getModel(AbstractLifeCycleManager.java:233)

… 68 more

Caused by: com.ibm.cognos.ccr.common.WebServiceConnectionException: exceptionId=ERR.ANY.WEBSERVICECONNECTIONEXCEPTION.CANNOT_EXECUTE_SERVICE, argument(s)=[FAIL:!Array index out of range: 50!, http://servername/ibmcognos/cgi-bin/cognosisapi.dll?t=controller, ?]

at com.ibm.cognos.ccr.ccrws.JAXWSClient.executeTask(JAXWSClient.java:107)

at com.ibm.cognos.ccr.ccrws.persistence.RemoteDao.executeTask(RemoteDao.java:91)

at com.ibm.cognos.ccr.ccrws.persistence.RemoteDao.getLatestSequenceNumber(RemoteDao.java:63)

at com.ibm.cognos.ccr.common.persistence.caching.CachingDao.getLatestSequenceNumber(CachingDao.java:78)

at com.ibm.cognos.ccr.common.persistence.caching.CachingDao.isUpToDate(CachingDao.java:175)

at com.ibm.cognos.ccr.common.persistence.caching.CachingDao.load(CachingDao.java:90)

at com.ibm.cognos.ccr.common.AbstractModel.load(AbstractModel.java:572)

at com.ibm.cognos.ccr.common.AbstractModel.load(AbstractModel.java:562)

at com.ibm.cognos.ccr.common.AbstractModelFactory.getNewModel(AbstractModelFactory.java:74)

at com.ibm.cognos.ccr.common.AbstractModelFactory.getNewModel(AbstractModelFactory.java:66)

at com.ibm.cognos.ccr.common.DefaultModelContext.getModelByIdentifier(DefaultModelContext.java:394)

… 70 more

Caused by: java.lang.RuntimeException: MTsxMDE6MjM4ZmZkZWUtZDdhMC1hZTc5LTI1MDQtMjEyYjQ5MTJjNzQwOjMzNDkxMjM0OTQ7MDszOzA7

at com.ibm.cognos.ccr.common.WebServiceConnectionException.<init>(WebServiceConnectionException.java:65)

at com.ibm.cognos.ccr.common.WebServiceConnectionException.<init>(WebServiceConnectionException.java:52)

… 81 more

 

Cause:

The tnsnames.ora file is to large for Cognos Controller to use.

Solution:

Create a smaller tnsnames.ora file and place in a separate folder on the controller server, for example d:\oracle.

Make the tnsnames.ora file only contain the information for the Cognos Controller database, and no other oracle database or oracle schemas.

 

Then update the ccr-system-properties.properties file, often located in folder, c:\Program Files (x86)\Cognos\C8\Server\integration.

 

# IBM SOURCE CODE HEADER START

# =====================================================================

# OCO Source Materials

#

# BI and PM: ccr

#

# (C) Copyright IBM Corp. 2004, 2009. All Rights Reserved

#

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

# =====================================================================

# IBM SOURCE CODE HEADER END

# User defined System properties

# Oracle Network admin directory path, the location of the TNSNAMES.ORA file

oracle.net.tns_admin=D:\\oracle

You must reboot the Controller server to make changes to file ccr-system-properties.properties take affect.

More Information:

http://pic.dhe.ibm.com/infocenter/cfpm/v10r1m0/index.jsp?topic=%2Fcom.ibm.swg.im.cognos.ctrl_inst.10.1.0.doc%2Fctrl_inst_id311UpdatedinstallationinstructionsforCreateanIBMCogno.html

by ·0 Comments

Product:

Cognos Controller 10.1.1

Microsoft Windows 2008 R2 server

Citrix server

Symptom:

Cognos Controller client program is slow to start. The citrix server that run the Cognos Controller client have no access to internet. When checking the Internet Explorer settings for  “Check for publisher’s certificate revocation” it is marked. Removing the mark, makes the program start faster.

 

Solution:

You can force the setting in Internet explorer for the user by create a power shell script, and then make it run before the users starts the cognos controller client on the citrix server.

Below a example of a script to update the registry:

# Change registry key to uncheck IE security setting: “Check for publisher’s certificate revocation”

Push-Location

  Set-Location “HKCU:\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust        Providers\Software Publishing”

Set-ItemProperty . State “dword:00023e00”

Pop-Location

 

More information:

http://www-01.ibm.com/support/docview.wss?uid=swg21441779

by ·0 Comments

Product:

Cognos Controller 10.1.1

Microsoft Excel 2007

Windows 2008 R2 Server

Citrix server

Symptom:

When user run a standard report in Cognos Controller, and select to view the report in Microsoft Excel 2007 ( or Excel 2010) they get a dialog, telling the file content is wrong.

Error message:

“The file you are trying to open, [File_name.xls] is in a different format than specified by the file extension. Verify that the file is not corrupted and is from a trusted source before opening the file. Do you want to open the file now?”  (Yes | No | Help)

 

Solution:

Excel 2007 introduced the concept of Extension Hardening.  Extension Hardening does checks ahead of time to ensure that the file content matches the extension and, if applicable, the MIME type. The upside of Extension Hardening is that it blocks one vector for malformed Excel content attacks, like Trojans. The downside is that it also breaks the classic ASP method of Excel reporting, and the opening of Cognos Controller reports in Excel.

 

There is no granularity in the setting. Extension Hardening cannot be turned off for some websites or content sources, and on for others. It can only be disabled, enabled with a prompt, or enabled with blocking. Extension Hardening can be controlled during installation by the Office Deployment files, or afterwards by group policy or editing the registry.

 

Registry:

[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Excel\Security]

“ExtensionHardening”=dword:00000000

Possible value settings: Allow different (dword:00000000); Allow different, but warn (dword:00000001); Always match file type (dword:00000002). If the

ExtensionHardening value is not present, Excel defaults to Allow different, but warn.

 

Create a powershell script that is run before the Cognos Controller client program on the citrix server, to set the value off.

This is a example of the script:

Push-Location

If (!(Test-Path “HKCU:\Software\Microsoft\Office\12.0\Excel\Security”))

{

New-Item “HKCU:\Software\Microsoft\Office\12.0\Excel\Security” -force

}

Set-ItemProperty “HKCU:\Software\Microsoft\Office\12.0\Excel\Security” -Name  ExtensionHardening -Value “0” -Type DWORD -force

Pop-Location

 

More information:

http://www.jwgoerlich.us/blogengine/post/2009/08/11/Excel-Extension-Hardening-and-Web-Applications.aspx

by ·0 Comments

Product:
TM1 10.1 Perspective
Windows 2008 R2 Server
Citrix Server

Symptom:
When you start TM1 Perspective (Excel 2010) from Citrix portal you get a error message.

Error message:
Run-time error ‘429’: ActiveX component can’t create object

Solution:
After you have installed TM1 Perspective on the server,
you need to start the application once to create some registry values before other can run it.

Log in as local administrator on the server
Start TM1 Perspective.
Close TM1 Perspective (and Excel)
Log out from server.

Now other users should be able to login.

by ·0 Comments

Product:
Cognos Planning 10.1.1 32 bit
Windows 2008 R2 server 64 bit
Microsoft SQL 2008 R2 64 bit

Symptom:
Error when starting cognos analyst after new install of Cognos Planning 10.1.1
There are different errors in the applications.

If cognos planning service is run as local system then the planningerrorlog.csv file is found under \windows\temp, but if the plannig service is run as a service account, then the planningerrorlog.csv file is found under C:\Users\service_account\AppData\Local\Temp folder.

Error message:
Database Errors: Source: Microsoft SQL Server Native Client 10.0 Description: Invalid object name ‘cognos_planningstore..P_PAD’. Number: -2147217865 SQLState: 42S02 NativeError: 208
found in ..\windows\temp\planningerrorlog.csv file

Planning – Analyst:
There was a problem login on. Please ensure you can access IBM Cognos Connection using Gateway URI specified in IBM Cognos Configuration.

Planning – Contributor Administration:

An error has occurred while starting IBM Cognos Planning – Administrator.
Main form failed to initialize.
Error Details:
ActiveX component can’t create object.

Solution:
Install Cognos Planning 10.1.1 Fix Pack 2 from IBM
http://www-01.ibm.com/support/docview.wss?uid=swg24033577

Log on to Windows 2008 server as administrator
Start Internet Information Service (IIS) Manager from Administrative Tools
Expand Application Pools
Create a new application pool called COGNOS
Click on Advanced Settings for application pool COGNOS
Set “enable 32-bit applications” to true
Set “process model identity” to ApplicationPoolIdentity
(if it does not work try next time with LocalSystem)
Set “Idle time-out (minutes)” to 60

If the cognos plannig program is installed to non default folder , like d:\, then you need to check and ensure that the IIS and Cognos service account have access to that folder.

Go to Windows Explorer to see the file system.
Right click on cognos folder and select properties.
Select security tab.
Add local group IIS_IUSRS and give it read and execute rights.
Click OK and close the dialog.

Right click on inetpub folder and select properties.
Select security tab.
Add local group IIS_IUSRS and give it read and execute rights.
Click OK and close the dialog.

Right click on your Computer icon and select Manage
Expand Configuration and local users and groups
Click on group IIS_IUSRS
Click add
Add the service account that will run the cognos services

Click on group administrators
Add the service account used for cognos services.

Ensure that you have the cognos planning servern name is part of local intranet zone in Internet Explorer on the server.

Then restart the iis with iisreset command in cmd.
And test again.

If that does not help also check below:

Ensure that you have installed the following roles on the Microsoft 2008 server before you install Cognos Planning:
+Application Server
+File Server
+Web Server (IIS)

Add “COM+Network Access” under select Role Services is not needed, cognos planning 10.1.l does not create a COM+ object anymore.

Also ensure that you have Data Execution Prevention off on the Windows 2008 Server.
Cognos planning requires that the option “Turn on DEP for essential windows programs and services only” is selected
And that any anti-virus software is turned off during installation.

Reinstall cognos planning 10.1.1

by ·0 Comments

Product:
Cognos Planning 10.1.1
Windows 2008 R2 server
Microsoft SQL 2008 R2

Symptom:
Error when starting cognos service after new install of Cognos Planning 10.1.1
No errors in windows event log or cogserver.log file are created.

Error message:
CLASS NOT REGISTERED

Solution:

Register CFGAPICOM.dll from the /bin directory of Cognos 10 :
– In Windows Explorer, go to c:\windows\system32,
– Right-click “cmd.exe” and select “Run as Administrator”
– Go to folder ..\program files (x86)\ibm\cognos\c10\bin\
– Run the DOS command:
regsvr32.exe CFGAPICOM.dll

If that does not help, try below:

Log on to Windows server as local administrator
Go to folder ..\cognos\c10\bin
Create a text file and enter the following line:

FOR %%1 IN (*.DLL) DO REGSVR32 /S %%1

Save the file as regdll.cmd
Start a commando prompt by right click on command prompt and select run as administrator
change to the ..\bin folder
enter regdll to start the script
(it will now registered all the dll files in that folder again)
Wait a few minutes until it is finished.

Then try again to start the Cognos services.

by ·0 Comments

Product:
Cognos Planning 10.1.1
Cognos BI 10.1.1
Windows 2008 R2 server

Symptom:
In your environment, you have installed Cognos product in VMWARE servers, and now you want to make a test environment from you working Cognos product environment.
You have copied the Cognos Windows server image to a new VMWARE image on other VMWARE host machine. You have renamed the Windows server that run the Cognos products and give it a new IP address. When you start Cognos Configuration you get a error.
When you press OK, Cognos configuration exit.

Error message:
CAM-CRP-1280 An error occurred while trying to decrypt using the system protection key. Reason: javax.crypto.BadPaddingException: Given final block not properly padded

Solution:
Export a unencrypted cogstartup.xml file from the previous Cognos Configuration program in you original Cognos server.
Start Cognos Configuration on the old server.
Select File – Export As
Enter a name of the file e.g. backup_cogstartup.xml and save the file to d:\
Copy that backup_cogstartup.xml file to you new Cognos server, to folder c:\program files\ibm\cognos\c10\configuration.
Rename the none working the cogstartup.xml file to cogstartup_org.xml.
Replace it with the unencrypted cogstartup.xml file, by rename the backup_cogstartup.xml to cogstartup.xml
On the new Cognos Server, start Cognos Configuration.
When it start, you have to change server name to reflect the new server name inside Cognos Configuration. This to make it work in the new Cognos solution, and not point to old servers.
Also change Content Store connections, so they point to the new database server.

If above does not help to allow you to start Cognos Configuration, you can try this:
Delete the caSerial and cogconfig.prefs files in the configuration directory.
Also delete the three subdirectories: csk, encryptkeypair, and signkeypair.
Start IBM Cognos Configuration again.

If you copy a vmware image with Cognos installed, and change the name of the server, it is many places that need to be updated. So I recommend that you install a fresh Windows 2003 R2 server instead, and then if you have fast dedicated CPU and ram in your system, you install Cognos software again to the new server. That can be a fast way to setup a test environment.

by ·0 Comments

Product:
Cognos Planning 10.1.1
Analyst on Microsoft Windows 7 64 bit

Symptom:
When you start ODBC Data source administrator to add ODBC connections to xls files you get a error on your brand new Windows 7 computer.

You need to add ODBC connection to be able to import xls files into Cognos Analyst for Planning. Inside Analyst how you selected New D-Link and then click on source, and selected ODBC (SQL) database. But then there are no connections to select, you have to create the connections in the ODBC tool.

Problem:
The setup routines for the Microsoft Excel Driver (xls xlsx xlsm xlsb) ODBC driver could not be found. Please reinstall the driver.

Cause:
In windows 7 the odbc icon in administrative tools are for 64 bit connections, and cognos planning use only 32 bit connections.

Solution:
Create a shortcut to the file c:\windows\syswow64\odbcad32.exe

Use this icon to edit the ODBC connection for Excel to be used in Cognos Planning.

by ·0 Comments

Product:
IBM Cognos Planning 10.1.1
Windows 2008 R2 server

Symptom:
When you start Cognos Analyst you get a login message from the IIS server.
You have setup to use SSO together with Active Directory in Cognos Configuration on the Cognos server.

You have created a global security group for you Cognos Planning users in your Microsoft Active Directory, that you call GlobalCognosUsers.
You have added the GlobalCognosUsers group to the Planning Rights Administrators group in Cognos Connection.
You have also try to add this GlobalCognosUsers group to the System Administrators group in Cognos Connection.

Message:
Windows Security
connecting to servername
user:
password:
domain: corp
remember my credentials
OK CANCEL

Possible Solution:
The cognos planning user does not have rights to the cognos planning folder on the windows IIS server. Do this steps to solve the issue.

Start Internet information Service Manager
Click on default web site in the left side
Click on authentication in the middle
Ensure only “Windows Authentication” and “Anonymous Authentication” are enabled.

Click on IBMCOGNOS in the left side in Internet Information Service Manager.
Click on authentication in the middle
Ensure only “Windows Authentication” are enabled.

Start Windows Explorer
Go to the INETPUB folder on the hard disk
Right click on the folder and select properties
Click on the Security tab
Click EDIT button
Click ADD button
Enter GlobalCognosUsers at “Enter the object names to select ” and click on check names
Click OK
Now you have added the ad group with cognos users to the folder
Click OK
Click OK

Go to the COGNOS folder on the hard disk (where the cognos planning program is installed)
Right click on the folder and select properties
Click on the Security tab
Click EDIT button
Click ADD button
Enter GlobalCognosUsers at “Enter the object names to select ” and click on check names
Click OK
Now you have added the ad group with cognos users to the folder
Click OK
Click OK

Try to start the analyst client again.

Try to surf to the windows server (Http://servername) from Internet Explorer to find if that connection is working at all first. This need to be working before Planning Analyst will work.