Troubleshooting
Problem
User launches Cognos Connection (http://servername/ibmcognos). User then clicks 'Consolidate my financial information'. [Alternatively, user launches the following: http://servername/ibmcognos/controllerbin/ccr.exe]. An error appears.
Symptom
Screen error:
Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'ControllerFrmCommon, Version=10.2.705.0, Culture-neutral, ....
<...>
==============================
Alternatively, in some environments, the symptoms are slightly different. When the client device launches Controller, if the Administrator is logged onto the Controller application server (e.g. via Terminal Services) then they will see the following (on the application server itself):
Visual Studio Just-In-Time Debugger
An unhandled exception ('System.IO.FileNotFoundException') occurred in CCR.exe [3008].
<...>
Process Name: CCR.exe
User Name: IUSR [Elevated]
Cause
Incorrect web server (IIS) configuration.
- Specifically, the server is configured so that it (incorrectly) runs the file (CCR.EXE) as an executable directly on the webserver itself
- This is different from the correct configuration, where it is supposed to make the client device download the CCR.EXE file (so that the client device can run it locally itself).
More Information:
There are many different possible places where the IIS can be misconfigured.
- For example, the file 'applicationHost.config' acts on the entire IIS server (it acts as the 'root configuration').
- Also, there will be several files such as 'web.config' located in many folders on the application server. If they reside in a folder that is linked to a 'parent' virtual directory (of 'controllerbin') then they will affect how 'controllerbin' works.
Example #1:
In one real-life example, the cause was that the file 'applicationHost.config' was incorrectly configured to have 'Execute' permissions, as follows:
<system.webServer>
<handlers accessPolicy="Read, Execute, Script">
Example #2:
In a different real-life example, the cause was that the following file...
- C:\inetpub\wwwroot\web.config
...had an entry 'Execute' (inside the section '<system.webServer>'):
Resolving The Problem
Modify the IIS webserver so that it does not allow the execution of CCR.EXE on the webserver itself.
Steps:
IMPORTANT: The steps to achieve this will vary depending on where (in the IIS) the misconfiguration is located.
- In other words, the steps will vary depending on the configuration of the server.
=> It is VITAL that you take a backup of the entire Controller application server (for example a virtual server image copy) before making any changes!
Example #1:
In one real-life scenario, the solution was as follows:
1. Logon to the Controller application server (webserver) as an administrator
2. Open the following folder: C:\Windows\System32\inetsrv\config
3. As a precaution, create a backup copy of the file 'applicationHost.config'
4. Edit the file ''(e.g. inside NOTEPAD.EXE)
5. Locate the following section: <system.webServer>
6. Modify the section that currently reads as follows:
- <handlers accessPolicy="Read, Execute, Script">
Change it so that it is as follows:
- <handlers accessPolicy="Read, Script">
7. Save changes
8. Test.
Example #2:
In one real-life scenario, the solution was as follows:
1. Logon to the Controller application server (webserver) as an administrator
2. Open the following folder: C:\inetpub\wwwroot
3. As a precaution, create a backup copy of the file 'web.config'
4. Edit the file ''(e.g. inside NOTEPAD.EXE)
5. Locate the following section: <system.webServer>
6. Modify the section that currently reads as follows:
<handlers accessPolicy="Read, Execute, Script">
Change it so that it is as follows:
<handlers accessPolicy="Read, Script">
7. Save changes
8. Test.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21678173