Dispatcher communication errors, CAF-WRN-2082 and DPR-ERR-2072, when you run a report

When these errors occur, you cannot run a report.

When trying to run the report, you see the following message:

CAF-WRN-2082 An error has occurred. Please contact your administrator.
The complete error has been logged by CAF with SecureErrorID: <...>

The CAF-WRN-2082 message is triggered by the following, underlying error that is logged to the Cognos® Analytics server in the install_location/logs/cogaudit.log or install_location/logs/cognosserver.log file:

DPR-ERR-2072 Unable to load balance a request with absolute affinity, 
most likely due to a failure to connect to the remote dispatcher. See the remote 
dispatcher detailed logs for more information. Check the health status 
of the installed system by using the dispatcher diagnostics URIs.

Handler trace back: [the_dispatcher] 
com.cognos.pogo.handlers.performance.PerformanceIndicationHandler
[the_dispatcher] com.cognos.pogo.handlers.logic.ChainHandler
[service_lookup] com.cognos.pogo.handlers.engine.ServiceLookupHandler
[load_balancer] com.cognos.pogo.handlers.logic.ChainHandler
[lb_forwarder] com.cognos.p2plb.clerver.LoadBalanceHandler
Note: For information about viewing full details of secured error messages, see CAF-WRN-2082 An error has occurred.

These errors occur in a distributed Cognos Analytics installation when the Cognos Application Firewall (CAF) settings are not consistently configured for all of the Cognos Analytics dispatchers in the environment.

Resolving the problem

Ensure that CAF is enabled, and all CAF settings are consistent for all Cognos Analytics dispatchers.

For each Cognos Analytics instance, verify or change the CAF settings by using the following steps:

  1. In IBM Cognos Configuration, stop the IBM Cognos services.
  2. For the IBM Cognos Application Firewall category, set the Enable CAF validation property to True, and specify the remaining CAF properties as required.

    If these properties are inconsistent for the different Cognos Analytics instances, change the values accordingly. For more information, see Configuring IBM Cognos components to use IBM Cognos Application Firewall.

  3. From the File menu, click Save to save the configuration.
  4. Start the IBM Cognos services.

    If you changed the Content Manager instance, you must stop and start the services for all other installed instances, even if you didn’t change their properties.

    If you changed a non-Content Manager instance, stop and then start the services for this instance only.