Product:
Cognos Controller 10.4.2
Microsoft Windows 2016 server

Issue:
How change from Cognos BI report, to the Controller report engine.

Solution:

To activate the controller report function, you need to change a web.config file.

1. Make sure that the Windows service ‘IBM Cognos Controller Reports‘ has already been successfully installed

 

2. Browse to the folder: C:\Program Files\IBM\cognos\ccr_64\ControllerProxyServer
3. As a precaution, create a backup copy of web.config
4. Open the file web.config inside notepad
5. Search for the entry: <appSettings>
6. Underneath that line, add an entry similar to:
<add key=”ccrReports” value=”http://servername.domain.com:9082/fcm.reports/report” />
7. Save changes
8. Browse to the folder: C:\Program Files\ibm\cognos\ccr_64\fcmweb\wlp\etc\

9. As a precaution, create a backup copy of server.env
10. Open the file server.env inside notepad
11.  Add the following line and save changes.  The default location for Java home is: C:/Program Files/IBM/cognos/ccr_64/fcmweb/jre
JAVA_HOME=C:/Program Files/IBM/cognos/ccr_64/fcmweb/jre
12. Make sure that the Windows service ‘IBM Cognos Controller Reports‘ is re-started
To turn off the controller report function, and use Cognos BI again. Remark it out like this:
<!– <add key=”ccrReports” value=”http://win2019server.domain.com:9082/fcm.reports/report” /> –>
Save the file, and wait a while.
More information:

Product:

Cognos Controller 10.4.2
Microsoft Windows 10

Issue:

Go into maintain – batch queue – manage

You see a grey line to the left over the dialog. If you move the dialog window, the lines follow the window.

Workaround:

Go to Maintain – User – Personal Defaults.

Click on Layout tab.

Mark “Save Window Size”

Click Save.

Exit Cognos Controller Client program, and login again.

 

Product:
Cognos Controller 10.4.2
Microsoft Windows 2019 server

Issue:

When press the Schedule Job icon in Optimize Database dialog – the windows is not visible.
The button does not work.
Solution:
Most common is that the controller dialog is outside the screen.

To reset all cognos controller windows to center or top left corner, do this steps inside Cognos Controller client program:

1. Click “Maintain / User / Personal Defaults > tab Layout (2)”
2. Uncheck the box ‘Save Window Size’:

3. Click Save
4. Logoff from Controller, and re-launch the Controller client.

More information:

https://www.ibm.com/support/pages/hanging-slow-crashing-when-using-controller-triggered-message-appearing-inside-window-located-offscreen-triggered-save-window-size-being-enabled

https://www.ibm.com/support/pages/node/375391

https://www.ibm.com/support/pages/blurred-text-andor-strange-looking-fonts-andor-incorrect-display-layout-inside-controller-classic-client-caused-using-display-scaling-not-using-100-scaling-96-dpi-triggered-controller-not-being-high-dpi-aware

The values for Cognos Controller dialog position is stored in the users ccr.config file in there user profile folder, at C:\Users\%username%\AppData\Roaming\Cognos\ccr.

You can change them in the file — but that is more difficult, than reset them as above.

<WinPos>
<add key=”frmRightsSystemReport-Left” value=”1950″ />
<add key=”frmRightsSystemReport-Top” value=”945″ />
<add key=”frmFormsDefine-Left” value=”390″ />
<add key=”frmFormsDefine-Top” value=”390″ />
<add key=”frmFormsDefine-Width” value=”15225″ />
<add key=”frmFormsDefine-Height” value=”8520″ />
<add key=”frmDefineFormSets-Left” value=”225″ />
<add key=”frmDefineFormSets-Top” value=”525″ />
<add key=”frmDefineFormSets-Width” value=”15675″ />
<add key=”frmDefineFormSets-Height” value=”8925″ />
<add key=”frmOptimize-Left” value=”45″ />
<add key=”frmOptimize-Top” value=”390″ />
<add key=”frmSubmission-Left” value=”45″ />
<add key=”frmSubmission-Top” value=”315″ />
<add key=”frmSubmission-Width” value=”10590″ />
<add key=”frmSubmission-Height” value=”6960″ />
<add key=”frmSubmissionReport-Left” value=”45″ />
<add key=”frmSubmissionReport-Top” value=”330″ />
<add key=”frmScheduleJob-Left” value=”45″ />
<add key=”frmScheduleJob-Top” value=”330″ />
<add key=”frmCompanyStructDef-Left” value=”60″ />
<add key=”frmCompanyStructDef-Top” value=”345″ />
<add key=”frmCompanyStructDef-Width” value=”12105″ />
<add key=”frmCompanyStructDef-Height” value=”11400″ />
</WinPos>

https://www.ibm.com/support/pages/window-sizes-changeshrink-and-cannot-be-resized-plus-font-text-size-changes-when-using-java-functions-remote-desktop-caused-using-windows-81-option-let-me-choose-one-scaling-level-all-my-displays

Product:
Cognos Controller 10.4.2
Microsoft Windows 2019 server
Microsoft SQL server 2016

Issue:

When open data entry, you get a system.exception error:

Source: ControllerForms12
Description: System.Web.Services.Protocols.SoapException: Server was unable to process request. —> System.Exception: Cannot resolve the collation conflict between “SQL_Latin1_General_Pref_CP1_CI_AS” and “SQL_Latin1_General_CP1_CI_AS” in the equal to operation.
at Microsoft.VisualBasic.ErrObject.Raise(Int32 Number, Object Source, Object Description, Object HelpFile, Object HelpContext)
at ControllerServerCommon.RaiseErrSrv.RaiseException….

This on a new SQL server installation, where you have restored your Controller database backup.

Solution:

Change collation settings on the SQL server. Cognos Controller demand that the SQL server and its TEMPDB have the same collation as the controller databases. Therefor you often have dedicated SQL servers for Cognos Controller systems.

Recommended format is: “SQL_Latin1_General_CP1_CI_AS”

Other collations will work, as described here: https://www.ibm.com/support/pages/which-sql-collations-are-supported-controller

You can change the SQL server collation without reinstall it, by this hidden feature.

  • Stop all Cognos services.
  • Detach all user databases (right click on Controller database in SQL manager and select Tasks – Detach)
  • Make backup of all other stuff
  • Stop SQL Server Service – can be done in Windows services.
  • Start a CMD prompt as Administrator
  • Go to folder C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn
  • Start the SQL Server Service using this command:
    sqlservr -m -T4022 -T3659 -q”SQL_Latin1_General_CP1_CI_AS”
  • Now check for the message “Recovery is completed”, and then press CTRL+C to Stop the SQL Server service
  • Start the SQL Services Normally – from Windows services.
  • Check for the change in SQL Management Studio with below query:
    select serverproperty(‘COLLATION’) as servercollation
  • Attach the user databases back (right click on Databases in SQL manager and select Attach)

Use this with extra care and with your own risk!

 

More information:

https://www.sanssql.com/2013/10/change-sql-server-collation-without.html

https://www.mssqltips.com/sqlservertip/3519/changing-sql-server-collation-after-installation/

Download SQL manager from https://docs.microsoft.com/en-us/sql/ssms/release-notes-ssms?view=sql-server-ver15#previous-ssms-releases

https://www.dbvis.com/download/

 

Product:

Cognos Analytics 11.1.7

Microsoft Windows 2016 server

Issue:
Only one user get a error when running a report in CA11, after he have logged in with SSO, if he do not use SSO with IIS, and instead enter name and password at Cognos dialog, then the report works.

A check of the users – showed he belongs to a lot of domain groups.

net user  donaldduck  /DOMAIN   >  c:\temp\userlist.txt

Error message:

HTTP Error 400. The size of the request headers is too long.

Solution:

Increase the allowed header size on the Cognos Gateway server

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters]

"MaxFieldLength"=dword:00032768

"MaxRequestBytes"=dword:01000000

Login to the server, and start REGEDIT program.

Expand to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters]

Add the DWORD values.

You must restart the Windows server, for the registry changes to take affect.

You may also need to update the TCPIP values:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"MaxUserPort"=dword:0000fffe
"TcpTimedWaitDelay"=dword:00000032

or change the IIS \ibmcognos\bi folders Request Filtering to a higher value, to get the report to work.

 

More information:

https://stackoverflow.com/questions/1097651/is-there-a-practical-http-header-length-limit

Although each web server software has some limitations, there is a difference whether there’s a limit for the HTTP request line plus header fields or for each header field.

Here’s a summary:

  • Apache 1.3, 2.0, 2.2, 2.3: 8190 Bytes (for each header field)
  • IIS:
    • 4.0: 2097152 Bytes (for the request line plus header fields)
    • 5.0: 131072 Bytes, 16384 Bytes with Windows 2000 Service Pack 4 (for the request line plus header fields)
    • 6.0: 16384 Bytes (for each header fields)
  • Tomcat:
    • 5.5.x/6.0.x: 49152 Bytes (for the request line plus header fields)
    • 7.0.x: 8190 Bytes (for the request line plus header fields)

So to conclude: To be accepted by all web servers above, a request’s request line plus header fields should not exceed 8190 Bytes. This is also the limit for each header fields (effectively even less).

You can edit tomcat/conf/server.xml’s HTTP/1.1 Connector entry, and add a maxHttpHeaderSize=”65536″ to increase from the default maximum of 8K or so, to 64K

https://docs.microsoft.com/en-US/troubleshoot/iis/httpsys-registry-windows

https://stackoverflow.com/questions/42862828/how-to-increase-size-limit-for-http-header-value-in-request-for-azure-iis

https://docs.microsoft.com/en-us/troubleshoot/iis/http-bad-request-response-kerberos

https://www.leansentry.com/guide

https://docs.microsoft.com/en-us/iis/configuration/system.webserver/security/requestfiltering/requestlimits/headerlimits/

https://www.leansentry.com/guide/reset-restart-recycle-iis

https://www.ibm.com/support/pages/kerberos-based-single-sign-fails-some-not-all-users

 

Product:
Cognos Controller Client 10.4.2
Microsoft Windows 10

Issue:
During manual install of ccrlocalclient64.msi on a users laptop they get a error message.

Installing a program on a workstation demand that you are local administrator on that workstation.
In many cases, this is not allowed at companies, but you can get a temporary different user account that is local administrator.

But even when you use this temporary admin account, during installation, you get above error.

Solution:

First ensure that you account is local admin on the computer.

It should belong to a global Active Directory group that you can find in the list of administrator groups on the laptop.

The command net user adminDonald /DOMAIN will show the groups the account is part of.
Then check that one of these groups is part of the Administrator group on your computer.

Press the Win + R keys on your keyboard to open Run, enter the command compmgmt.msc, and then press Enter or OK.

Go to groups and click on Administrators to see what groups are listed.
If the group is in the list, that account is local admin on the workstation.
If it still does not work, ensure the workstation name is listed as allowed (see below).

If you run the below command for user Donald, you get a result similar to this.

C:\Windows\system32>net user adminDonald /DOMAIN
The request will be processed at a domain controller for domain europe.com.

User name Admindonald
Full Name Donald Duck admin
Comment 
User's comment
Country/region code (null)
Account active Yes
Account expires 2022-08-11 00:00:00

Password last set 2021-08-11 14:12:59
Password expires 2022-08-11 14:12:59
Password changeable 2021-08-12 14:12:59
Password required Yes
User may change password Yes

Workstations allowed myWorkstationName
Logon script
User profile
Home directory
Last logon Never

Logon hours allowed All

Local Group Memberships
Global Group memberships *Computers_local_admins *Domain Users
*other group x

The command completed successfully.

If Workstations allowed is missing, then you get above error.

More Information:

http://woshub.com/restrict-workstation-logon-ad-users/

https://www.digitalcitizen.life/ways-open-computer-management-windows/

Product:

Cognos Controller 10.4.2
Microsoft Windows 2019 server

Issue:
When starting and stopping the Cognos Controller client several times you get this error when you try to login.

System.Web.Services.Protocols.SoapException: Server was unable to process request. —> System.IndexOutOfRangeException: Index was outside the bounds of the array. at
Cognos.Controller.Proxy.ControllerReportNetService.RepNet.GetUserInfo ….

Solution:

There can be many cause of this issue, but first make sure you do not have previous errors that trigger this.

Logoff cognos controller client and restart your laptop, to ensure there are no excel or controller software running in the background.

Then login and try again.

When you get one error in Cognos Controller, it is best to logoff and restart the client completely to not get other errors as an affect of the first error.

More Information:

https://www.ibm.com/support/pages/error-occurred-while-trying-access-server-systemindexoutofrangeexception-index-was-outside-bounds-array-when-launching-controller-client

https://www.ibm.com/support/pages/troubleshooting-index-was-outside-bounds-array-when-launching-controller-client

Product:
Cognos Controller 10.4.2
Microsoft Windows 2019 server

Issue:
After new installation of Cognos Controller, when for example you check the data format in accusation registry.

It show like 28/02/2020

When it should look like 2020-02-28. This is the expected format for Sweden. Each country have its default format. This is often set inside your local computer, at Region in Control panel.

Solution:

Change the format in region to your country.

Go to Control panel.
Go to Region.

Change in the format drop down to your country, and click apply.
Click OK.
Start Cognos Controller client on your computer and try your report/view again.

On a citrix server, each users, have there own windows profile, and can have different region settings even do they are on the same citrix server.

More information:

https://www.ibm.com/support/pages/time-zone-clock-date-formats-controller-explanation-and-description

https://support.citrix.com/article/CTX103288

Product:

Cognos Analytics 11.1.7
Microsoft Windows 2016 server

Issue:
When try to change a old data source, in Cognos Analytics, the icon to change setting is missing.

Go to IBM Cognos Administration from the Manage menu by click on Administration console.
Click on Configuration tab.
Select the data source connection you want to change. For example Audit.

Then click on the more link for that data source.

Now click on Set Properties.

Click on the connections tab.

Here is now the pencil icon missing. This can be because the data source type is Other.

Solution:

Then you need to edit the data source direct in the string field.
Here you can change to other database server.

^User ID:^?Password:;LOCAL;OL;DBInfo_Type=MS;Provider=SQLOLEDB;User ID=%s;Password=%s;Data Source=SeRvErNaMe;Provider_String=Initial Catalog=AUDIT_PRD;@COLSEQ=

After you changed the Data Source value to your database server, click on OK.
This can be because the new version of CA11 does not support SQLOLEDB anymore.

Click on the link to test the data source again.

Click TEST button.

You should get a “Succeeded” Status if it works right.

More Information:

https://www.ibm.com/docs/en/cognos-analytics/11.1.0?topic=rt-data-servers-no-longer-supported-in-cognos-analytics

https://www.ibm.com/support/pages/equivalent-oledb-cognos-analytics

Product:
Microsoft Windows Server
Issue:
How configure the agent-config.yaml file to work?

Solution:
The new windows agent for Grafana Cloud should make it easy to collect some metrics from your  computers to the dashboard in the cloud.

Sign up for a account at https://grafana.com/auth/sign-up/create-user?pg=dl&plcmt=box-right


Download the agent and install the agent from here https://grafana.com/blog/2021/04/22/weve-added-first-class-windows-support-to-grafana-agent/

If you click “Get Started with Grafana”, from your grafana.net page, you will see a list of local agent you can install to collect metrics (data) from your system. Click on Windows exporter and Next.

After you have configure the windows agent, as below, you can go back to this page and click “Test integration and finish installation”.

There is a default agent-config.yaml file created, where you need to add your url and username to make the agent ship data to the grafana cloud.
You get your Password (API key) on your host page – go to your name under grafana cloud, and then click on prometheus details to get the key and urls.  Click on grafana details to go to your cloud dashboard.

You need to copy the following values, and place in your yaml file.
Remote Write Endpoint (Use this URL to send Prometheus metrics to Grafana Cloud.)
Username / Instance ID (Your Grafana Cloud Prometheus username.)
Password / API Key (Your Grafana Cloud API Key. Be sure to grant the key a role with metrics push privileges.)

Open C:\Program Files\Grafana Agent\agent-config.yaml in notepad++ on your computer.

You need to add the lines remote_write (very important that every line is indent with two spaces)

remote_write:
  - url: https://prometheus-blocks-prod-us-central1.grafana.net/api/prom/push
    basic_auth:
      username: (the user number from your account)
      password: (the long password from your account)

In YAML file is important to indent the text correct, and the order of the lines, have a meaning. Above setup worked for me, to send data to the grafana cloud. You may find other configurations, also work well.

Then go to your grafana.net page, and select “integration – Windows Exporter” dashboard.

Monitoring Windows Services with Grafana, InfluxDB ‎and Telegraf

You will soon fill up your free account, so you must limit the services that is reported up to the cloud.

Add last to your agent-config.yaml file this lines, to limit the information collected:

 # List of collectors to enable
 enabled_collectors: "cpu,system,os,cs,time"

You can copy your text to a YAML checker: https://codebeautify.org/yaml-validator

Here is some information of possible values in the file:

cpu CPU usage
cpu_info CPU Information
cs “Computer System” metrics (system properties, num cpus/total memory)
net Network interface I/O
os OS metrics (memory, processes, users)
process Per-process metrics
remote_fx RemoteFX protocol (RDP) metrics
service Service state metrics
smtp IIS SMTP Server
system System calls

https://github.com/prometheus-community/windows_exporter/blob/master/README.md

https://grafana.com/grafana/dashboards/6593

More Information:

https://github.com/prometheus-community/windows_exporter

https://github.com/grafana/agent/blob/main/docs/configuration/integrations-config.md#windows_exporter_config

For a full description of configuration options, see windows_exporter_config in the Grafana Agent documentation.

After installation, the Agent config is stored in C:\Program Files\Grafana Agent\agent-config.yaml. Anytime the config file is modified, run the following to restart the Windows Agent so it can pick up changes:

sc stop "Grafana Agent" 
sc start "Grafana Agent"

https://grafana.com/blog/2020/07/02/getting-started-with-the-grafana-agent-a-remote_write-focused-prometheus-agent/ 

Windows Server Monitoring using Prometheus and WMI Exporter

https://devconnected.com/how-to-setup-grafana-and-prometheus-on-linux/

https://prometheus.io/download/

https://githubmemory.com/repo/prometheus-community/windows_exporter/issues/757

https://grafana.com/docs/grafana-cloud/how-do-i/control-prometheus-metrics-usage/usage-reduction/

https://grafana.com/docs/grafana-cloud/how-do-i/control-prometheus-metrics-usage/usage-analysis-explore/ 

https://grafana.com/tutorials/grafana-fundamentals/