CogKnowHow

Product:
Cognos Analytics 11.0.9
Microsoft Windows 2012 R2 Server

Issue:
Does Cognos BI send a mail when you click on TEST of notifications i Cognos Configuration?

Solution:
Yes, cognos configuration test mail function, will send a mail to the default sender with the default sender as sender.
If you enter a valid mail address at the company as the default sender, and click test, that person will have a mail.

Under Data Access – Notifications set it up like this:
SMTP mail server: smtpserver.company.com:25
Account and password: (can be blank if the SMTP server allow resend of anonymous mail)
Default sender: roger@company.com (use the mail address to a person at the company)
SSL Encryption Enabled: False

More information:
http://www-01.ibm.com/support/docview.wss?uid=swg21445621
http://www-01.ibm.com/support/docview.wss?uid=swg21339824

Product
Planning Analytics 2.0.5
Microsoft Windows 2012 R2 Server

Problem
How to avoid the time out for users of TM1?

Solution

CA11 (Cognos BI) should have the lowest time out, e.g. 3600 seconds as default. This gives
CA Session timeout  < PAW Session Time-Out , should then have SessionTimeout= 60m and ProxyTimeoutSeconds=900 (15 min)
< TM1 Web in \tm1_64\webapps\tm1web\WEB-INF\web.xml at <session-timeout>70</session-timeout> & TM1 Web Applications timeout in Cognos Configuration > TM1 Applications set to 70 for Session timeout (default is 60 min).
< TM1 Database timeouts (tm1s.cfg settings IdleConnectionTimeOutSeconds= 4800, and a Rest-API connection HttpSessionTimeout= 80.)
< IIS timeout settings on the Windows server for CA gateway.

(below text copied from the web)

IIS server:
HTTP Response Headers at the ibmcognos/samples/images level – set common headers to Expire Web Content to After 5 days.
At the Default Web Site – Limits – set Connection time-out (in seconds): to 900.

At Application Pools – ICAPool – Advanced Settings, change Idle Time-out (minutes) to 90.

More information:

https://www.ironsidegroup.com/2011/06/27/session-timeout-101/

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

3 Ways to Optimize Cognos Timeout Settings

Product:
Planning Analytics 2.0.3
TM1SERVER_APP_version=TM1SERVER_APP-AW64-ML-RTM-11.0.3.119-0
Cognos Analytics 11.0.9 kit_version=11.0.9.17121514
kit_name=IBM Cognos Analytics
Planning Analytics Workspace version 29
Microsoft Windows 2012 R2 Server

Problem:
How make SSO with Planning Analytics for Excel work?

Contact IBM Cognos Support to get the latest instructions on how to setup PAX.

https://www.ibm.com/support/knowledgecenter/en/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_inst.2.0.0.doc/t_tm1_inst_pax_cam.html

Solution:
Setup of Content Store database in SQL server
See here how: https://www.ibm.com/support/knowledgecenter/en/SSEP7J_10.2.2/com.ibm.swg.ba.cognos.qrc_inst.10.2.2.doc/t_qrc_inst_sqlserver_createacontentstore.html

Setup of Cognos Analytics 11
See here how: http://cogknowhow.tm1.dk/archives/1056
Ensure that all servernames in Cognos Configuration uses FQDN, dvs servername.domain.com, this is a must for PAW setup.

The manual for CA11
http://www-01.ibm.com/support/docview.wss?uid=swg27047187

Setup of IIS and Cognos Analytics 11 Gateway
See here how: https://www.ibm.com/support/knowledgecenter/en/SSEP7J_11.0.0/com.ibm.swg.ba.cognos.inst_cr_winux.doc/t_gateway_iis.html

Check that SSO is working, to the Windows Active Directory, by surf to http://caservername.domain.com/ibmcognos/bi

Check the .\webcontent\default.htm and .\webcontent\index.html files. Update the last line starting with <meta http-equiv=”refresh” as shown below, (where <alias name> is the alias used in the CA_IIS_config.bat script file). Add /ibmcognos/ in most cases.

Important that Windows Authentication is on the /ibmcognos/sso folder in IIS manager and that you may need to add Advance properties singleSignOnOption: IdentityMapping in Cognos Configuration for CA11 at security – authentication – namespace – active directory.

If Cognos Application Firewall is used, then you need to add the TM1 servers here also with port 9510.
Open Cognos Configuration for CA11. Go to Local Configuration – IBM Cognos Application Firewall. Click on Valid domains or hosts to add the PAservername to the list of approved domains.

Click OK, save the new Configuration and restart the Cognos Analytics services. If above is not done, you get error DPR-ERR-2079 when you logout of TM1WEB.

Download of Planning Analytics 2.0.3
List of files
http://www-01.ibm.com/support/docview.wss?uid=swg24044001

Download from here
http://www-01.ibm.com/support/docview.wss?uid=swg24044081

Setup of PA 2.0.3
https://www.ibm.com/support/knowledgecenter/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_inst.2.0.0.doc/tm1_inst.pdf

Check that Print Spooler Service is running in your Windows 2012 server.
Install NET Framework 4.6.1 (NDP461-KB3102436-x86-x64-AllOS-ENU.exe) in the Windows server, from here: https://support.microsoft.com/en-us/help/3102436/the–net-framework-4-6-1-offline-installer-for-windows
Install C++ 2010 x64 redistribution (vcredist_x64.exe).

Run the installation from the unziped file in D:\install\pa 2.0.3\tm1_winx64h_2.0.3.119_ml.tar\winx64h\issetup.exe

Go into Cognos Configuration for TM1 (PA2.0.3)

Under Environment point to the CA11 server.
Set gateway URI to be to the CA11 gateway like this http://caservername.domain.com:80/ibmcognos/bi/v1/disp
Set External Dispatcher URI to http://caservername.domain.com:9300/p2pd/servlet/dispatch
Set Content Manager URI to http://caservername.domain.com:9300/p2pd/servlet

At IBM Cognos TM1 you can tune your WebSphere Liberty Profile;
Set Ping timeout in seconds to a value like 480 seconds.
Set Maximum memory for Websphere Liberty Profile in MB to 4096, if TM1 Web or TM1 Application Web are getting unresponsive and Planning Analytics logs contain some errors java.lang.OutOfMemoryError.

At TM1 Applications leave the Maximum memory in MB at default 768.
Enter TM1 Application Server Gateway URI to http://paservername.domain.com:9510/pmpsvc and External server URI to http://paservername.domain.com:9510.
Consider to change Session timeout to a higher value.
Set TM1 Application Server Dispatcher URI to http://paservername.domain.com:9510/pmpsvc/dispatcher/servlet

At TM1 Clients change the Cognos Insight ping frequency (seconds) to a higher value like 90. See separate page about timeout values http://www-01.ibm.com/support/docview.wss?uid=swg22002419
Skip the Logging, Security, IBM Cognos Application Firewall – they have limited function in this version of PA2.

Start the SDATA and Proven_Techniques example TM1 instances.
We use Proven_Techniques to test SSO, because it have a short TM1S.CFG file, so it is easy to add fields.

Setup of SSO
http://www-01.ibm.com/support/docview.wss?uid=swg22000283

Open C:\Program Files\ibm\cognos\tm1_64\samples\tm1\Proven_Techniques\tm1s.cfg in notepad++.
Add the lines;
IntegratedSecurityMode=2
ServerCAMURI=http://caservername.domain.com:9300/p2pd/servlet/dispatch
ClientCAMURI=http://caservername.domain.com:80/ibmcognos/bi/v1/disp
Save the file and restart the TM1 instance Proven_Techniques.

Exit TM1 Architect.
Erase the tm1p.ini file from here C:\Users\%username%\AppData\Roaming\Applix\tm1 to allow it to get the new values.
Open C:\ProgramData\Applix\TM1\tm1p.ini in notepad and add the values AllowImportCAMClients = T
CognosGatewayURI = http://caservername.domain.com:80/ibmcognos/bi/v1/disp

Save the file.

Add users
Start Tm1 Architect, double click on Proven_Techniques to login.
Enter ADMIN as user to login. Right click and select Security – Client/Groups. From menu Clients select Add New Client.

Click on your namespace name, in out example AD.

Click on TYPE in top right corner to enter the name of the user.

Enter the domainnamespace/username. Namespace name is the name you gave it in CA11 cognos configuration. Username most be the users name correct spelled as it is entered in Active Directory.
Click on yellow arrow to add the user, and click on OK.

Mark the user to be ADMIN, so he can then add other users later.
Click OK and exit TM1 Architect. Now you turn TM1 application to security mode 5,and then this user can login and add additional users in TM1 architect.

Open C:\Program Files\ibm\cognos\tm1_64\samples\tm1\Proven_Techniques\tm1s.cfg in notepad++.
Change the line to 5
IntegratedSecurityMode=5
Save the file and restart the TM1 instance.

Unzip the file C:\Program Files\ibm\cognos\tm1_64\bi_interop\bi_interop.zip to a separate folder like c:\install
There should be two folders
templates
webcontent
Go and update this files with the PA server name and PAW server name;
C:\install\webcontent\planning.html
Update the following to point to the location of the planning service(s)
var planningServices = [“http://paservername.domain.com:9510″,”http://pawservername.domain.com”];
C:\install\webcontent\pmhub.html
Update the following to point to the location of the pmhub service(s)
var pmhubURLs = [“http://paservername:9510″,”http://paservername.domain.com:9510″,”http://pawservername.domain.com”];
C:\install\webcontent\tm1\web\tm1web.html
// Update the following to point to the location of the TM1Web service(s)
var tm1webServices = [“http://paservername.domain.com:8080”, “http://paservername.domain.com:9510”];
Save the files.

The files in C:\install\templates\ps\portal should not be changed.


If variables_TM1.xml is not referenced in TM1S.CFG file, then it is most likely not used.

Copy the files and folders in C:\install\webcontent ontop the C:\Program Files\ibm\cognos\analytics\webcontent folder.
Go into C:\Program Files\ibm\cognos\analytics\webcontent\tm1\web\tm1web.html and see that it is the updated file.
Copy the files and folders in C:\install\templates to the C:\Program Files\ibm\cognos\analytics\templates folder.
Replace files as needed.

Copy the C:\Program Files\ibm\cognos\analytics\webcontent\tm1 folder to C:\Program Files\ibm\cognos\analytics\webcontent\bi folder. So you also got a TM1 folder under /webcontent/bi.

Copy the updated files planning.html, pmhub.html, default.htm and index.html from C:\Program Files\ibm\cognos\analytics\webcontent to folder C:\Program Files\ibm\cognos\analytics\webcontent\bi.

Restart IIS with iisreset from a CMD prompt.
Surf to http://paservername.domain.com:9510/tm1web to check that it works.

The first time you start TM1 Application portal, then it will connect to the PA and BI setup. You must surf to http://paservername.domain.com:9510/pmpsvc to set it up.
Enter the host name and the list of TM1 server names should be filled out. Select the proven_techniques from the list.

If it looks like above – please try a different version of web browser.

Above is the correct look, you get in FireFox.

Press F12 inside Internet Explorer to find the Emulation in use.
Above you see it is using Document Mode 7. The blue text “via intranet compatibility settings” tell us that it is the compatibility settings in internet options on your computer that give the issue. Open it and clear all values out. Test again.

Change the mode to Edge and it may work for you.
Press OK to save the values to TM1 Application Portal.

When it is working it should look like above, if you are ADMIN in the Proven_Techniques application you should see all the icons to the right.
This configuration is stored in C:\Program Files\ibm\cognos\tm1_64\webapps\pmpsvc\WEB-INF\configuration\fpmsvc_config.xml.

TM1 Operations Console is configured in a web interface. This UI presents multiple options of configuration, including the references to the Cognos Analytics environment.
Surf to http://paservername.domain.com:9510/pmhub/pm/admin

Expand configurations and select PMHub Security.
At CAMBIURL enter http://caservername.domain.com:9300/p2pd/servlet/dispatch
At CAMGatewayURL enter http://caservername.domain.com:/80/ibmcognos/bi/v1/disp
The values should save automatically in a few minutes.

Surf to http://paservername.domain.com:9510/pmhub/pm/opsconsole
to check that it works.

TM1 PMPSVC and PMHUB must be setup before you can get PAW to work.

You must setup PAW before PAX are setup.

Download of PAX from here
http://www-01.ibm.com/support/docview.wss?uid=swg27049597
(cor_win32_2.0.29.10_ml.tar.gz)
Installation of PAX
Install NET Framework 4.6.1 (NDP461-KB3102436-x86-x64-AllOS-ENU.exe) from here: https://support.microsoft.com/en-us/help/3102436/the–net-framework-4-6-1-offline-installer-for-windows

Check that Microsoft Office have the primary interop assemblies (PIAs) for Excel installed.
You can download the PIAredist.exe for Office 2010 from here https://www.microsoft.com/en-us/download/details.aspx?id=3508
In Office setup it is named NET Programmable support.

PIA – Primary Interop Assemblies (PIA) redistributable package for your version of Microsoft Outlook. The PIA is only needed if you have Outlook 2007 or 2010. PIA is not needed for Office 2013 or Office 365, it is part of the Office installation package as .NET Programmability Support for Office. In all version of Office you also need to make sure the .NET Programmability Support is installed (Control Panel – Program and Features – locate Microsoft Office installation, click on Change and Add/Remove features and expand Outlook, it is the first option you can check the box and install it)

Run the file D:\install\pa 2.0.3\pax\cor_win32_2.0.29.10_ml.tar\win32\issetup.exe

If your excel is 32 bit then you get this error if you select the wrong file. File cor_winx64h_2.0.29.10_ml.tar is for 64 bit excel.

Click Next

Select I Agree and click Next

Click Next

Click Next

Click Next

Click Next

Click Finish.

Configure PAX
Start Microsoft Excel to configure IBM Planning Analytics

Select tab IBM Planning Analytics and click on Options

Click on IBM

Select IBM Planning Analytics and click on ADD button

Enter your servername http://paservername.domain.com:9510   (this will make the SSO to work)

PAX should connect to the PAW (Planning Analytics Workspace) URL, like http://pawservername.domain.com:80/ to get the “set editor” to work.

Enter a friendly name, like PMPSVC Connect.
Click on Test Connection

Click Save
If the test fails, check that servername is correct spelled, and check that Windows Firewall on the server does not block port 9510.
Click OK

Now you can in Excel click on Connect – Your Friendly name – proven_techniques to start working with that.

Now you can drag views from PA2 (TM1) into the spreadsheet.

How to use it http://www.element61.be/en/resource/ibm-planning-analytics-excel-pax

To get “Replace members” to work you need to install PAW.

If you use a TM1 instance that use securitymode=1 (like example SData) then “set editor” will work.

Above when you point PAX to the PA server and use a PA (TM1 instance) that uses SSO.

If you in PAX connect to PA (Tm1) server at address http://paservername.domain.com:9510/ or http://paservername.domain.com:9510/pmhub/pm then the settings inside pmhub security will tell pax where to go to authenticate.

if you in PAX connect to PAW like http://pawservername.domain.com then the setting in paw administration (http://pawservername.domain.com:8888) will point to the authentic provider.

Then the value in C:\Program Files\ibm\cognos\analytics\webcontent\pmhub.html and C:\Program Files\ibm\cognos\analytics\webcontent\tm1\web\tm1web.html, can also be important to make it work.  Note that this files are also in folder C:\Program Files\ibm\cognos\analytics\webcontent\bi.

Setup of PAW
Ensure you use only FQDN to the servers.

First time you start PAW, you point it to a Native TM1 instance with security mode 2. Then you add your CAM users with TM1 Architect. Set this CAM users to be ADMIN in that instance, and they will be the first ADMIN in PAW. Switch that TM1 instance over to security mode 5. Change in IBM Planning Analytics Workspace Administration Tool from TM1 to CAM authentication mode. You must use security mode 1 first, before you can use PAW with security mode 5.

In IBM Planning Analytics Workspace Administration Tool, you should have this settings:

TM1 Admin Server URI: https://paservername.domain.com:5898

TM1 Application Server Gateway URI: http://paservername.domain.com:9510

Authentication Mode: CAM

IBM Cognos BI Gateway URI: http://caservername.domain.com:80/ibmcognos
if you use CA11 then you should set IBM Cognos BI Gateway URI: http://caservername.domain.com:80/ibmcognos/bi/v1/disp

IBM Cognos BI Dispatcher URI: http://caservername.domain.com:9300/p2pd/servlet/dispatch
if you use CA11 then you should set IBM Cognos BI Dispatcher URI: http://caservername.domain.com:9300/bi/v1/disp

IBM Cognos BI Authentication Namespace ID: AD (the same namespace id you have entered in Cognos Configuration for CA(BI)).

Click Validate and Update.

If above is correct set, then PAX should work pointing to http://pawservername.domain.com

Please note that above setup is for PAW version 29. Other versions of PAW may require other configuration.

See here how to set PAW up http://cogknowhow.tm1.dk/archives/1090

More Information:

https://www.ibm.com/communities/analytics/cognos-analytics-blog/cognosanalytics-and-planninganalytics-integration-walkthrough-part-3/
http://www-01.ibm.com/support/docview.wss?uid=swg22000283
http://www-01.ibm.com/support/docview.wss?uid=swg21958925
https://msdn.microsoft.com/en-us/library/kh3965hw.aspx
https://www.ibm.com/support/knowledgecenter/en/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_inst.2.0.0.doc/c_ig_cor_overview.html

#Cognos Analytics and #Planning Analytics Integration – Walkthrough – Part 2

Product:
Cognos Analytics 11.0.8
Microsoft Windows 2012 R2 Server
Issue:
New installation of Cognos Analytics 11, but when you surf to the http://servername/ibmcognos you get a error like “Error Message: 403.6 – Forbidden” or “This page can’t be displayed”.
You have tried to reinstall Cognos Analytics gateway server parts, that did not help.
If you surf direct to the dispatcher at http://IBM_Cognos_Analytics_server_host_name:9300/bi/v1/disp it works fine.

Please note that CA11 needs to use http://servername/ibmcognos/bi/ and not http://servername/IBMCOGNOS/bi with capital letters, that may not work.

If you get a blank page – click inside it and wait some more.

Solution:
The IIS setup have somehow become corrupt. Redo the IIS setup.
Inside IIS manager – mark cgi-bin and select delete.
Mark SSO under IBMCOGNOS and select delete.
Mark IBMCOGNOS (and COGNOS8 if it exist) and select delete.
Exit IIS manager and stop iis.
Erase web.config files from folders like c:\program files\ibm\cognos\analytics\webcontent\web.config file and c:\program files\ibm\cognos\analytics\webcontent\bi\.

If you run more than one IBM® Cognos® Analytics instances of the same product, on one computer, you must create a separate application pool for each instance and then associate the aliases for that gateway instance to each application pool.

Go into control panel – administrative tools – server manager. Select the local server.
In the Add Roles and Features Wizard, click Role-based or feature-based installation, and click Next.
Select Web Server (IIS), ensure that Common HTTP Features is selected including WebDAV Publishing, Performance Static Content Compression, Under Security select Request Filtering and Windows Authentication, and click Next until you get to the Role Services section of the wizard.
Expand Application Development.
Select CGI and ISAPI Extensions, ISAPI filters and click Next.
Select IIS Management Console, IIS Management Scripts and Tools, Management Service.
Features as NET framework 4.6 and ASP.NET 4.6 should be selected.
Click Install.

Download the IIS add ons needed for Cognos Reverse proxy. Install them in below order;
https://blogs.technet.microsoft.com/erezs_iis_blog/2013/11/27/installing-arr-manually-without-webpi/
1. Stop IIS first by typing net stop was /y and net stop wmsvc /y on an elevated command-line window

2. Download and install the Web Farm Framework module. It is currently available in version 1.1

3. Download and install the External cache module. It is currently available in version 1.0

4. Download and install the URL Rewrite module. It is currently available in version 2.0

5. Download and install ARR itself. It is currently available in version 3.0

6. Start the IIS services back by enter IISRESET (or, simply reboot your server).

Download the Cognos script to configure IIS. (CA_IIS_Config_v1.09(11.02.17).zip)
http://www-01.ibm.com/support/docview.wss?uid=swg22000097
1. Download the CA_IIS_config.zip file to your Cognos Analytics Gateway Server.
2. Extract the CA_IIS_config.bat file to a folder.
3. Open CA_IIS_config.bat in a text editor like Notepad++. https://notepad-plus-plus.org/download/v7.5.3.html
4. The variables, that are to be modified, are located at the top of the file. Edit the BAT file in Notepad++ before you run it.
Run the BAT file as a local administrator.

Then you need to Adjust request size limits.  Go into IIS Manager.

Select the bi directory under the ibmcognos application created earlier.
Double-click Request Filtering.
Click Edit Feature Settings… from the right-hand panel.
Set Maximum URL length (bytes) to 8192.
Set Maximum query string (bytes) to 8192.
Click OK.  (The Cognos Script have already change the values for /bi/ folder)

Configure IIS to allow to pass through the custom 441 errors that are used for recoverable exceptions from CAM. Otherwise, IIS can block these errors, and the customer sees the “Invalid Logon Response” error when trying to log on.

Click the ibmcognos virtual directory.
In the Home view, Management section, double-click Configuration Editor.
In the Section drop-down list, expand system.webServer, and select httpErrors.
Set the existingResponse property to PassThrough. It may already be set correct by the Cognos script.
Apply the configuration change.

If you configured the SSO application in previous steps, enable Windows Authentication.

Select the SSO application folder in IIS manager. For Microsoft Edge browser, select the ibmcognos application folder.
Double-click Authentication. Disable Anonymous Authentication, and enable Windows Authentication.

If you do not want to use Kerberos, at the namespace, add Advance properties singleSignOnOption: IdentityMapping

Cognos Analytics should now be available at: http://iis-host/ibmcognos.

WebDav setup

Note: webdav is not working in 11.0.8 – update to a later version of CA 11.
http://www-01.ibm.com/support/docview.wss?uid=swg1PI90123

Under Connections, expand your web server, Sites, and select your website. For example, select Default Web Site.
Double-click WebDAV Authoring.
Click Enable WebDAV.
Click WebDAV Settings.
If you have anonymous access enabled, select True for Allow Anonymous Property Queries, and click Apply.
Select the directory or virtual directory /ibmcognos/bi/samples/images/ to which you want to allow WebDAV access.
Double-click WebDAV Authoring.
Click Add Authoring Rule, and add the appropriate rules for your environment. Like Allow access to: All Content, User: All users, Access: Read.

For example, if you installed the samples and you want to use the default path, under the ibmcognos virtual directory, expand bi/samples, and select images, and add an authoring rule for the image files in that folder.
In Windows Explorer right-click the directory or virtual directory you added authoring rules to, in above it can be /cognos/analytics/webcontent/bi/samples/images, and click Properties.
Click Security tab, and add the appropriate permissions. For example,  add permissions for the anonymous user access.
You may need to setup webdav for other images folders on the IIS gateway server if they are used in the reports.

http://www-01.ibm.com/support/docview.wss?uid=swg22002398&aid=1

Best is to keep all pictures in the same folder /ibmcognos/bi/samples/images/ on all the Cognos BI servers.

Change the Gateway URI in IBM Cognos Configuration to match the new IIS configuration, i.e. http(s)://web-host:80/ibmcognos/bi/v1/disp
Access the Gateway through http(s)://web-host:80/ibmcognos/bi/

Create a redirect file and place in the C:\inetpub\wwwroot as default.htm
<html>
<head>
<title>Cognos Connection</title>
<meta http-equiv=”refresh” content=”0 ;url=http://cognosserver.domain.com/ibmcognos”>
</head>
</html>

More information:
https://www.ibm.com/support/knowledgecenter/en/SSEP7J_11.0.0/com.ibm.swg.ba.cognos.inst_cr_winux.doc/t_gateway_iis.html
https://www.ibm.com/support/knowledgecenter/SSEP7J_11.0.0/com.ibm.swg.ba.cognos.inst_cr_winux.doc/t_enablewebdavoniis.html
https://www.ibm.com/support/knowledgecenter/en/SSEP7J_11.0.0/com.ibm.swg.ba.cognos.inst_cr_winux.doc/c_inst_crit_config.html

Samples Landing Page

Product:
Cognos Analytics 11.0.7
Microsoft Windows 2012 R2

Problem:
When you inside Cognos Administration on Dynamic Cubes click on “properties” for a specific cube you get a error.
If you surf direct to the dispatcher on port 9300, and do the same thing inside Cognos Connection you do not get a error. Therefor the error is with IIS. Check the windows event log for more details:

Error message:
An unhandled exception has occurred.
/ibmcognos
C:\Program Files\ibm\cognos\analytics\webcontent\
w3wp.exe
IIS APPPOOL\ICAPool
HttpException
The length of the query string for this request exceeds the configured maxQueryStringLength value. at System.Web.HttpRequest.ValidateInputIfRequiredByConfig() at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)

Solution:
Withing IIS Default Web Site > ibmcognos > bi

Click on ‘Configuration Editor’

Select Section ‘system.web/httpRuntime’
set the following attribute setting –

maxQueryStringLength = 2048 -> 8192
maxRequestLength = 4096 -> 8192

Restart IIS

More information:
https://www.ibm.com/support/knowledgecenter/en/SSEP7J_11.0.0/com.ibm.swg.ba.cognos.inst_cr_winux.doc/t_gateway_iis.html

Adjust request size limits. (Sometimes this settings does not work and you need to edit as above).
Select the bi directory under the ibmcognos application created earlier.
Double-click Request Filtering.
Click Edit Feature Settings… from the right-hand panel.
Set Maximum URL length (bytes) to 8192.
Set Maximum query string (bytes) to 8192.
Click OK.